patsmad

Route segments out-of-order after topology validation

Discussion created by patsmad on Jan 27, 2014
Latest reply on Jan 27, 2014 by rfairhur24
Hello,
We are experiencing a problem with our transportation database - in particular, the routing/geometry feature class...
After topology is validated, multi-part routes have their Parts thrown out-of-order. For example:

The route should run from 0 to 207.14, and the geometry measures are showing that it runs from 118.450 to 15.300.  The geometry parts are out of order as can be seen below:
�?� Parts 0 and 1 = 118.450 to 129.840
�?� Parts 2 and 3 = 135.510 to 174.058
�?� Parts 4 and 5 = 40.200 to 112.490
�?� Parts 6 and 7 = 174.047 to 207.140
�?� Parts 8 and 9 = 19.700 to 33.190
�?� Parts 10 and 11 = 0.000 to 15.300

Why would validating the topology on this (and pertaining) features cause the routing to get re-ordered?
I am using the default cluster tolerance to minimize the geometry shift that occurs from topology validation.

Is there anything that could be done to safeguard these routes or prevent this from happening?

(BTW, this happens in both an SDE environment and in  File Geodatabase environment)

Thanks!
Pat

Outcomes