nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Topology Error 138

TimWitt2

Hey everybody!

I tried to create a topology for two line features and use the "Must Not Intersect With" rule. Once I create the topology and try to validate it, I receive the following error.

Anybody came across this yet and figured out how to solve it?

Thanks,

Tim

Najděte více příspěvků označených jako

Accepted answers

RebeccaStrauch__GISP

You could write a script to change the current extent and then use Validate Topology—Help | ArcGIS Desktop

grab the full extent X/y, then break it into four extents. Zoom. Run the topology on current extent, move to next, etc.

All comments

TimWitt2

This might be the only way. Thanks!

RebeccaStrauch__GISP

You could write a script to change the current extent and then use Validate Topology—Help | ArcGIS Desktop

grab the full extent X/y, then break it into four extents. Zoom. Run the topology on current extent, move to next, etc.

TimWitt2

Yes, I saw this discussion, but I hoped I wouldn't have to do the validation in smaller pieces.

I am using a fgdb for my topology.

RebeccaStrauch__GISP

I'm not sure that this will help, but there was another (not checked as resolved) thread https://community.esri.com/thread/164974

that at suggested trying a smaller geographic extent...have you tried that? Also, make sure they are in the same coordinate/reference system and extent.

I knwo now back in the 9.4 (turned into 10.1) days, we could not validate our topology no matter how we "broke it down", but I don't remember if gave a code or just crashed. That did have to do with the size of the data OR possibly the extent east/west (over the 180), even if we weren't validating over the line. We could do about 95% (different extents, different order, etc.) but the last portion would not work. That was fixed before the 10.1 release. We were using ArcSDE SQL.

Are te you using Enterprise SDE or a a fgdb or personal? Maybe you are hitting a limit? I think topology checking produces a lot of data behind the scenes.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.