Metadata step 2 multiple DASid issue #88
Comments
|
Hi Katie, Holly,
First off, no, you are not having this problem because you are using an ArcMap tool on a Pro database. As far as I know, geodatabases created in Pro are backwards compatible with ArcMap when it comes to dealing with the GeMS schema. I don't think we have taken advantage of any functionality in upgraded geodatabases that are not available in previous versions.
But, as you guessed, the ArcMap metadata tools do not expand concatenated DataSourceID values. I am afraid I don't know Metadata Wizard well enough to know about getting 'the log file to update to confirm' the changes, but if you can change the xml file to enumerate those data sources, you can continue from there; there's no reason to go back to the GeMS metadata tools.
Have you tried the ArcGIS Pro version of the three ArcMap tools? I posted it earlier this year and haven't gotten much feedback on it yet, so please let me know if you try it.
…--
Evan Thoms
US Geological Survey, Alaska Science Center
4210 University Drive, Anchorage, AK 99508
________________________________
From: VAGeoSurvey ***@***.***>
Sent: Thursday, June 9, 2022 5:01 AM
To: usgs/gems-tools-arcmap ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [EXTERNAL] [usgs/gems-tools-arcmap] Metadata step 2 multiple DASid issue (Issue #88)
This email has been received from outside of DOI - Use caution before clicking on links, opening attachments, or responding.
Hi,
We at the Virginia Survey are trying to create metadata for our conversion projects. We have multiple DASids in our DescriptionOfMapUnits feature and this is giving us an error in our Chester.gdb-metadataLog.txt file. Included in the first image below is what the text file looks like. We've attempted to fix this issue in the second image within the MetadataWizard but are unable to get the log file to update to confirm that change.
We are not sure if part of the problem is that we are using an ArcMap tool on a Pro geodatabase, since the metadata tools do not exist in the ArcPro toolbox. We're unsure if the metadata tool has been updated to include multiple DASids either.
Any guidance is appreciated.
Sincerely,
Katie Lang and Holly Mangum
[Capture2]<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F100316555%2F172852220-0be02ac4-66e7-4bd5-a3fa-81a264b4a1cf.JPG&data=05%7C01%7Cethoms%40usgs.gov%7Caa6f386577834fd5a1b208da4a183534%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637903765073806823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vlOWwAEErQYUjd08fi0DT0lN7GCueCbqglLtMjog8Uc%3D&reserved=0>
[Capture3]<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F100316555%2F172852757-1660ade8-73c5-42ab-b170-c12f039616fe.JPG&data=05%7C01%7Cethoms%40usgs.gov%7Caa6f386577834fd5a1b208da4a183534%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637903765073806823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=L3XYpfqggePqz4SM8f40J0PCiy9fBatRAutttjY1yAQ%3D&reserved=0>
—
Reply to this email directly, view it on GitHub<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fusgs%2Fgems-tools-arcmap%2Fissues%2F88&data=05%7C01%7Cethoms%40usgs.gov%7Caa6f386577834fd5a1b208da4a183534%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637903765073806823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TbF794vL1IinU1isJjWaqODivsAVaAhV277CducGmPA%3D&reserved=0>, or unsubscribe<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABJASO27KQELNZ7JBFV4D3TVOHTLNANCNFSM5YJ763AA&data=05%7C01%7Cethoms%40usgs.gov%7Caa6f386577834fd5a1b208da4a183534%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637903765073806823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RpZ9z0thSZ65XuP6jj1ltu8SCAnDTM%2FlVg6TDpQtviM%3D&reserved=0>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
Thanks for the feedback, Evan. We have tried a few things with the Pro Metadata tool today. Every time we ran the tool, it failed within a few seconds and gave us an output that looked like this: We also saw in the Gitter chat room that you were helping user chhalsted with a similar issue. We tried finding the proj.db file and couldn't seem to access it, but admittedly we don't have a lot of coding experience. Maybe we don't have the same ESRI version you were talking about? Additionally, we are planning on reaching out to the metadata wizard Github site to see if they have a solution to our outputs... Any more guidance or workflows to try would be much appreciated for the new Pro Metadata tool. |
|
The error message is about python not being able to find the lxml module, which, as far as I knew, is installed by default when ArcGIS Pro installs python. In Pro, could you check something? Go to Project and click on Python. It will take a while to pop up, but scroll down through the Installed Packages and you should see 'lxml'. Double-check that the Project Environment reads arcgispro-py3. Also, what license level do you have?
|
|
After checking with the rest of our staff, most of our Pro versions did not have the lxml file (Pro versions 2.3-2.6). However, one or two people had the Pro 2.8 version and did have that lxml file, and so I tried to get this working on their computers. I first tried to run the Pro tool, and came up with this error on line 752: In trying to be proactive and figure out the error for myself, I found out that you had updated the code yesterday to fix this issue on line 752 on another page of Github. So I downloaded the newest version of the toolbox on the computer running ArcPro 2.8, ran the metadata tool again to see if the issue was resolved. That issue was fixed, but I then came up with these new errors: So, is there something I should be doing here to fix these two other line errors? Or did I forget to include something? Thanks again, |
|
Hi again Evan, We had downloaded the most recent version of the toolbox last week but we checked again and are still getting the same two errors on line 843 and 321. Any insight on why this might be the problem this time? |
|
Thank you for troubleshooting this with us! Just tried the green code button, and downloaded that release on the main page. When I just ran the build metadata tool, the error on line 321 was resolved this time, but the error on line 843 is still popping up. It failed much more quickly this time, but that read out looks like this: |
|
Updated the code and toolbox again after you posted the update an hour ago. It resolved the error on line 843, but now it is showing an error on the next line (844). I'm sorry.... |
Hi,
We at the Virginia Survey are trying to create metadata for our conversion projects. We have multiple DASids in our DescriptionOfMapUnits feature and this is giving us an error in our Chester.gdb-metadataLog.txt file. Included in the first image below is what the text file looks like. We've attempted to fix this issue in the second image within the MetadataWizard but are unable to get the log file to update to confirm that change.
We are not sure if part of the problem is that we are using an ArcMap tool on a Pro geodatabase, since the metadata tools do not exist in the ArcPro toolbox. We're unsure if the metadata tool has been updated to include multiple DASids either.
Any guidance is appreciated.
Sincerely,
Katie Lang and Holly Mangum
The text was updated successfully, but these errors were encountered: