FGDC spatial reference info missing when using Export Metadata

[EvanThoms]

When I export metadata to the FGDC standard using the Export Metadata tool in ArcGIS Pro 2.5.0, the spatial reference information section, aka the spref element, is missing. The information is shown when I view the item description, but it doesn't get exported. I have tried this with multiple feature classes from different file gdbs. For context, the Export Metadata tool in ArcMap will export the section correctly from the same data sources. I have tried upgrading the file geodatabases and synchronizing the metadata and nothing works. Am I missing a step? Can't find any discussion of this anywhere.

[LisaDong]

Hi Evan, warm greetings. It was nice working with you on the case. For anyone else who has the same question, this is a known defect: 

• BUG-000124294- In ArcGIS Pro, when an Extensible Markup Language (XML) file is generated using the Export Metadata command from the catalog view, it fails to add the spatial reference or 'spref' syntax information in the file.
• Current Status: In Product Plan
• Statuses- https://community.esri.com/docs/DOC-8293-statuses-for-arcgis-ideas
• Workaround: Use the ArcCatalog stand-alone application.

[curtvprice]

Update: As of today (2.7.1 release) BUG-000124294 is still marked as "In Product Plan"

[EvanThoms1 · Accepted solution]

Any progress on a solution to this bug? It is still marked as 'in product plan'.

ArcMap must be removed from all USGS computers by February 2024. When that happens, there will be no arcpy method to export the spref node into CSDGM metadata. For ArcGIS Pro we have been using a workaround that uses code from the Metadata Wizard library, but the resulting XML files for some spatial references are not completely valid.

[LaineyLe_Blanc1]

Any update to this? Still marked as 'in product plan' and the spatial reference information is missing from exported metadata, so I either get warned by the USGS metadata validation service (mp 2.9.52) for missing spatial reference information. Or I use Save As in ArcPro to an XML, and it throws hundreds of errors when using the validation service because it doesn't save in FGDC format. Marking this problem as solved and that one of the solutions is to use the Save As function in the Catalog view is not really a solution. 

Format when I Save as 

vs. when exported as an XML