https://community.esri.com/t5/arcgis-pro-ideas/topology-access-with-arcpy/idi-p/939936 <P>When running basic topology checks it would be nice to be able to script exceptions. If I set a no dangles rule on a road network every cul-de-sac will be an error. If it was possible to take that error point, search for features in a set distance to decide if its actually a dangle or just the end of a road, and mark as exception it would be great. No pseudo nodes has the same issue. There are all sorts of reasons for pseudo nodes in a road network such as name, ownership, surface type, or speed limit changes that all are reasons for a non intersection break in the line that could be resolved by comparing attributes between offending features and automatically marking them as exceptions.</P> Thu, 02 Nov 2023 21:23:49 GMT ChrisMathers1 2023-11-02T21:23:49Z https://community.esri.com/t5/arcgis-pro-ideas/topology-access-with-arcpy/idi-p/939936 <P>When running basic topology checks it would be nice to be able to script exceptions. If I set a no dangles rule on a road network every cul-de-sac will be an error. If it was possible to take that error point, search for features in a set distance to decide if its actually a dangle or just the end of a road, and mark as exception it would be great. No pseudo nodes has the same issue. There are all sorts of reasons for pseudo nodes in a road network such as name, ownership, surface type, or speed limit changes that all are reasons for a non intersection break in the line that could be resolved by comparing attributes between offending features and automatically marking them as exceptions.</P> Thu, 02 Nov 2023 21:23:49 GMT https://community.esri.com/t5/arcgis-pro-ideas/topology-access-with-arcpy/idi-p/939936 ChrisMathers1 2023-11-02T21:23:49Z