POST
|
I noticed that when I right-click on a layer in the Contents pane and try to edit metadata I get a read-only error, but if I try it in the Catalog pane I can open the Metadata Editor.
... View more
12-13-2018
10:29 AM
|
0
|
2
|
1132
|
POST
|
Just for the record, the solution turned out to be: Leave the checkbox "Populate metadata with item details" UNCHECKED when importing FGDC-CSDGM metadata from XML.
... View more
08-14-2018
08:56 AM
|
2
|
0
|
477
|
POST
|
Thanks. Apparently there is a way to obtain the results we are looking for, but maybe there is something wrong with my XML metadata. I sent you an e-mail with my input XML and details on the workflow I used.
... View more
08-10-2018
02:00 PM
|
0
|
0
|
477
|
POST
|
The image below captures some quirks I encountered when importing XML metadata into ArcGIS Online. The XML file conformed to the FGDC-CSDGM standard and was in ArcGIS metadata format. I work for the Bureau of Land Management. Any GIS datasets we make public are supposed to carry required disclaimers in the metadata. (1) Access Constraints is a separate tag in the XML, but when imported to AGOL the wording in the XML file was replaced with "Access Constraints: None" and the XML wording for Access Constraints was lumped into the next item, Use Constraints. (2) In the Use Constraints, the phrase "as is" in quotations got rendered in AGOL as: ""as is"" (3) The Distribution Liability disclaimer in the XML file was omitted and replaced by: "Distribution Liability: See access and use constraints information." The BLM disclaimer is not the same. What is the solution for making the XML metadata come through to AGOL as written? Thanks.
... View more
08-09-2018
02:06 PM
|
0
|
3
|
584
|
Title | Kudos | Posted |
---|---|---|
2 | 08-14-2018 08:56 AM |
Online Status |
Offline
|
Date Last Visited |
07-21-2022
03:21 PM
|