Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate Database 2.12.2 error #77

Open
sdudash opened this issue Sep 8, 2023 · 0 comments
Open

Validate Database 2.12.2 error #77

sdudash opened this issue Sep 8, 2023 · 0 comments

Comments

@sdudash
Copy link

sdudash commented Sep 8, 2023

Tried to validate my database using the toolbox I downloaded today 12.2.2. Received these errors. Help!

**Validate Database

Parameters

Input geodatabase or geopackage D:_COVID_SAFSOC_Dudash\PMF\GISdata\ProSunfairDB.gdb
Output workspace D:_COVID_SAFSOC_Dudash\PMF\GISdata\ValidateGDB
Validate standalone file
Validate embedded metadata
Report errors with _ID, not OBJECTID false
Skip topology checks false
Refresh GeoMaterialDict false
Delete unused Glossary and DataSources rows false
Compact GDB true
Open report when done true**

Messages

Start Time: Friday, September 8, 2023 10:18:11 AM
You are using an obsolete version of this tool!
Please download the latest version from https://github.com/DOI-USGS/gems-tools-pro/releases
Metadata not checked. File needs to be in XML format.

Looking at level 2 compliance
Rule 2.1 - Has required elements: nonspatial tables DataSources,
DescriptionOfMapUnits, GeoMaterialDict; feature dataset GeologicMap with
feature classes ContactsAndFaults and MapUnitPolys
Rule 2.2 - Required fields within required elements are present and correctly defined
2.3 All MapUnitPolys and ContactsAndFaults based feature classes obey Level 2 topology rules:
no internal gaps or overlaps in MapUnitPolys, boundaries of MapUnitPolys are covered by ContactsAndFaults
Topology in GeologicMap found
Validating topology
Looking at validation results for errors
2.4 All map units in MapUnitPolys have entries in DescriptionOfMapUnits table
2.5 No duplicate MapUnit values in DescriptionOfMapUnits table
2.6 Certain field values within required elements have entries in Glossary table
2.7 No duplicate Term values in Glossary table
2.8 All xxxSourceID values in required elements have entries in DataSources table
2.9 No duplicate DataSources_ID values in DataSources table

Looking at level 3 compliance
3.1 Table and field definitions conform to GeMS schema
3.2 All MapUnitPolys and ContactsAndFaults based feature classes obey Level 3 topology rules:
no ContactsAndFaults overlaps, self-overlaps, or self-intersections.
3.3 No missing required values
3.4 No missing terms in Glossary
3.5 No unnecessary terms in Glossary
3.6 No missing sources in DataSources
3.7 No unnecessary sources in DataSources
3.8 No map units without entries in DescriptionOfMapUnits
3.9 No unnecessary map units in DescriptionOfMapUnits
3.10 HierarchyKey values in DescriptionOfMapUnits are unique and well formed
Traceback (most recent call last):
File "D:\GeMS\LatestGeMSTools\20230906\gems-tools-pro-2.12.2\Scripts\GeMS_ValidateDatabase.py", line 1609, in
]
File "D:\GeMS\LatestGeMSTools\20230906\gems-tools-pro-2.12.2\Scripts\GeMS_ValidateDatabase.py", line 1529, in main
# ver_table = db_dict["Version"]["catalogPath"]
File "D:\GeMS\LatestGeMSTools\20230906\gems-tools-pro-2.12.2\Scripts\GeMS_ValidateDatabase.py", line 795, in rule3_10

TypeError: 'NoneType' object is not iterable

Failed script Validate Database...
Failed to execute (ValidateDatabase).
Failed at Friday, September 8, 2023 10:18:39 AM (Elapsed Time: 27.86 seconds)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant