Accepted Solutions
Tips and Tricks
This isn’t a comprehensive guide, rather just tips and tricks I’ve picked up along the way.
- Whenever possible, create metadata (MD) for the feature class, not a map layer. This enables the metadata to filter through multiple uses on different maps and when you export it. Map layer MD may be useful if you need to document things specific to that map (e.g.: definition query, advanced symbology, joins), but try to use it sparingly.
- When editing MD, save often. I think saving MD is separate from saving your project, kind of like saving a Jupyter Notebook or data edits.
- If there is any chance you will overwrite or recreate this feature class at some point, export the MD to a file so you don’t lose it.
- From the Catalog pane or the Catalog window, right click on a data set and choose to view or edit the metadata.
- View metadata may be disabled in the Catalog window, since it should have opened up by default as soon as you clicked on it.
Exporting and Importing
A typical workflow is to create MD for one layer, export it to a file, and then import it to another data set that is similar. For that reason, export usually comes before import in my workflow.
Exporting MD
First, create the metadata you want in the editor. Exporting it can only be done from the “View Metadata” interface, not the editor! This always trips me up.
There are two ways to export MD from a Pro feature class.
RECOMMENDED: In the Catalog pane, click on the feature class, raster layer, or other data type and find the “Catalog” ribbon with a “Metadata” group. There, you will see “Export” and “Save As”.
The Export dialog is really simple. I generally use ISO 19115-3 format. As described below, you need to know the format when you import it, so it helps to put this in the filename.
The other way to export is the “Save As” options. There is an option to save as HTML. This is good for end users to view it, but not for MD interchange. There is a Save As XML option, but I don’t understand how it’s different from Export, so I don’t use that.
Importing MD
To import MD, choose the “View Metadata” option for the data set in the Catalog pane. In the “Manage” context ribbon, use the “Import” button (to the left of the “Export” button in the screenshot above). I don’t know why you have to tell it the type when you import MD. It seems like this should be embedded in the XML file you’re importing, but I just choose the same format I exported as, assuming I created it.
Tips and Tricks
This isn’t a comprehensive guide, rather just tips and tricks I’ve picked up along the way.
- Whenever possible, create metadata (MD) for the feature class, not a map layer. This enables the metadata to filter through multiple uses on different maps and when you export it. Map layer MD may be useful if you need to document things specific to that map (e.g.: definition query, advanced symbology, joins), but try to use it sparingly.
- When editing MD, save often. I think saving MD is separate from saving your project, kind of like saving a Jupyter Notebook or data edits.
- If there is any chance you will overwrite or recreate this feature class at some point, export the MD to a file so you don’t lose it.
- From the Catalog pane or the Catalog window, right click on a data set and choose to view or edit the metadata.
- View metadata may be disabled in the Catalog window, since it should have opened up by default as soon as you clicked on it.
Exporting and Importing
A typical workflow is to create MD for one layer, export it to a file, and then import it to another data set that is similar. For that reason, export usually comes before import in my workflow.
Exporting MD
First, create the metadata you want in the editor. Exporting it can only be done from the “View Metadata” interface, not the editor! This always trips me up.
There are two ways to export MD from a Pro feature class.
RECOMMENDED: In the Catalog pane, click on the feature class, raster layer, or other data type and find the “Catalog” ribbon with a “Metadata” group. There, you will see “Export” and “Save As”.
The Export dialog is really simple. I generally use ISO 19115-3 format. As described below, you need to know the format when you import it, so it helps to put this in the filename.
The other way to export is the “Save As” options. There is an option to save as HTML. This is good for end users to view it, but not for MD interchange. There is a Save As XML option, but I don’t understand how it’s different from Export, so I don’t use that.
Importing MD
To import MD, choose the “View Metadata” option for the data set in the Catalog pane. In the “Manage” context ribbon, use the “Import” button (to the left of the “Export” button in the screenshot above). I don’t know why you have to tell it the type when you import MD. It seems like this should be embedded in the XML file you’re importing, but I just choose the same format I exported as, assuming I created it.
There is a separate save button in the ribbon for metadata. Are you clicking on that?
I do not believe that saving your project saves metadata.
