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

Make Topology Tool #63

Open
LLeBlanc110 opened this issue Apr 7, 2021 · 10 comments
Open

Make Topology Tool #63

LLeBlanc110 opened this issue Apr 7, 2021 · 10 comments

Comments

@LLeBlanc110
Copy link

MakeTopology

maketopology2

I'm using the most recent tools (feb. 2021), but I've tried running on the older versions and get the same result. Running in ArcCatalog produces the same result.

@LLeBlanc110
Copy link
Author

I realized I didn't have the most recent version (1.5.5), so I updated and the same issue is still happening. Also, the validate database tool doesn't run either.
image

@LLeBlanc110
Copy link
Author

The same errors are being thrown for the validate database and make topology tools in the pro GeMS tools (2.4.4).

image
image

@ethoms-usgs
Copy link
Collaborator

Ok, I will take a look at these today.

@ethoms-usgs
Copy link
Collaborator

First, the Make Topology tool - I cannot recreate this error. The path to your gdb looks good and I confirmed the tool ran correctly even when the names of GeologicMap, ContactsAndFaults, and MapUnits had been changed to include a prefix. Can you include a screenshot from ArcCatalog of the contents of your gdb?

And, try running the tools from ArcCatalog completely outside of an ArcMap session. With some tools - can't confirm this is one of them without digging way into the code - having layers in the map from different data sources that have the same names can cause the tools to point to the wrong feature class.

@LindaTedrow
Copy link

LindaTedrow commented Apr 9, 2021 via email

@LLeBlanc110
Copy link
Author

@ethoms-usgs I thought I could fix the problem by flipping the names around, since the tools allows for prefixes, but maybe not suffixes? So good news, the make topology tool works now, but I'm still getting the same error message for the validation tool. I built the geodatabase from scratch rather than using the tool, so I could've messed up a few things along the way.
image

Upon checking, I found that I allowed Null values in the DMU for HierarchyKey, could that be the problem?

Also, somewhat related, in building the gdb from scratch I realized the attribute field in OrientationPoints is now "StationsID" in the publication, formerly was "StationID" in the manuscript. The validate tool will flag this as an error if someone was building their gdb based on the pub. Not a big deal, just pointing it out. And lastly, for what's it worth, I've experienced the issue you describe about having ArcMap open and the validate tool pulling from another open geodatabase than the one I directed it to.

@ethoms-usgs
Copy link
Collaborator

The Validate Database tool does expect to be able to find a 'DescriptionOfMapUnits' table, with no prefixes or suffixes, so try removing the prefix. The Make Topology tool works with feature classes with prefixes (only -- no suffixes) because the intent is for it to be used to build topology not only in GeologicMap feature dataset, but CrossSection datasets as well, where ContactsAndFaults and MapUnitPolys do get named with prefixes.

In general, the tools do not expect to have to deal with prefixes like what you have used because of the idea that a GeMS database describes the geology of only one map, that is, a prefix that identifies a feature class as belonging to a particular gdb is redundant. We could consider re-writing the tools to always look for names in the way that Make Topology tool does, but the workaround for now is to not rename those required table names

@LLeBlanc110
Copy link
Author

Changing the DMU back to its original name fixed the issue and the tool ran. I understand the need to keep the names as is, I did it for clarity since I'm compiling 4 GeMS geodatabases in one map. Changing the names is easy enough, and I should've just changed the alias (duh). Thanks for the help, Evan!

@ethoms-usgs
Copy link
Collaborator

Yeah, I wondered if you were doing something like that!
Good to know.

@ethoms-usgs
Copy link
Collaborator

@LindaTedrow Yes! It is similar isn't it? I am still curious about the error you reported. I have continued the discussion over at the original issue

@ethoms-usgs ethoms-usgs reopened this Feb 14, 2022
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

3 participants