Amit, I followed your model for creating a new route feature class with non-overlapping primary routes. I have discovered that this new feature classes m-values do not match the network it was derived from along all parts of a route. Smaller routes may match up in their entirety but longer routes my drift. In other words, the min and max m-values are fine, but the m-vales between the two networks my not match between the min and max m-values. The appended data in the network template feature class matches exactly, but after running the create routes geoprocessing tool from the MMin and MMax values the error is introduced. I may be able to eliminate the error by: taking the original network and running feature vertices to points, then locate features along routes on the output, then make route event layer, then add xy coordinates, then run delete identical based on routeid and xy coordinates, as well as, delete all points where RID does not match ROUTEID, and then finally use those points to calibrate the new primary routes network. This seems a bit convoluted and the processing time will take a couple of days. Any thoughts? Thank you, Justin.
... View more
