Export Topology Errors

TedCronin — Wed, 11 Jan 2012 00:16:35 GMT

Not sure if this goes here, or GDB, but you guys should get it, either way. This tool from the help says that: The names of each feature class are created by combining a user-defined base name appended with either PointsErrors, LineErrors, or PolygonErrors. Does that mean the layers are to be called Base Name + PointsErrors? I currently am seeing BaseName_point (line(poly)).

This table is pretty confusing, too. I am expecting to see at least an Origin, and if there are two layers an Origin and Destination. Currently, I am seeing if there is an Origin, there is no Destination, and vice versa. Also, very few Origin Classes. I have some NULL Object IDs, which seems like strange. Perhaps that doc can list more info for RuleType (http://resourcesbeta.arcgis.com/en/help/main/10.1/index.html#//00170000015w000000). So for esriTRTAreaAreaCoverEachOther, I am thinking there should be an Origin and a Destination, because this sounds like Must Cover Each Other, but with no doc, or explanation it makes it challenging. Doc also lists a Rule Description but the table does not have a Desc. isException (-1, or 0), HUH, doc says A value of 1 identifies the error as being an exception, problem is that there are no 1s, just -1s.

So, I am thinking that this tool just grabs what is "KNOWN", it does not validate, then export. If its dirty and never been validated, its not going to find anything. If it has been validated and is dirty it will find the errors.

I do like the premise of what this tool is trying to do, but not yet on the delivery. It will be very useful in our migration to the parcel fabric, and other reporting capabilities for our other non fabric layers.

Sounds like Yoda - esriTRTLineNoIntersectOrInteriorTouch

Another cool by product is you can potentially create a ROW from the errors for polys.

Re: Export Topology Errors

CraigGillgrass — Sun, 15 Jan 2012 12:50:16 GMT

Ted, most of the points you raise are resolved in Pre-release. Let us know if you see the same issues once you've had a chance to test it.

Re: Export Topology Errors

TedCronin — Sun, 15 Jan 2012 17:30:08 GMT

So, its gdb then. Looking forward to the next release and will do. Thank you for getting back to me, Craig.

Re: Export Topology Errors

TedCronin — Tue, 17 Jan 2012 16:16:08 GMT

I don't thank you enough Craig. You ( and a few others...) have been instrumental in the setup of our GIS since 9.2, so once again thank you for your continued assistance. Sorry for the dup on the Thanks, but it needed to be said.

topic Re: Export Topology Errors in Data Management Questions

Export Topology Errors

Re: Export Topology Errors

Re: Export Topology Errors

Re: Export Topology Errors