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.
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.
