The new Generate Schema Report tool in Pro is a great way to export the details of all objects in a geodatabase. However, depending on which output format you choose, the data types provided for each geodatabase item will be something more intended for code rather than the common name displayed in the software to end users. For example, I have a Feature Dataset in my geodatabase. And it looks like this when you look at properties in the Pro catalog interface:
When I run the tool for an HTML output, it labels it as dataset type = 'FeatureDataset'. Notice there is no space.
In a similar fashion, in the JSON output of the tool gives the type as DEFeatureDataset
Similar things happen for geometry types of feature classes (point, line, polygon, etc.),
and field types (OID, Geometry, String, Integer, Date, etc.)
These are not the types users see when they look at the Fields view of a feature class in Pro.
Although I'm sure these types of names are great for coding and play their role in the SDK and backend, I'd prefer adding an additional property of the output with a proper human label that matches what all my GIS analysts see when they are looking at data in Pro through the catalog interface. Having those end-user friendly labels will help in using these reports in engagements with users about schema. I guess I could convert all these values to whatever the Human readable Pro UX label is, if I knew where the definitive list exists, but it would be great if it was in the raw output.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.