Screwed-Up Corridors! Why?
This post is loosely-related to the last post re: Corridor model output failure. That was shown to be a result of invalid Base Map Control data source objects. Usually, duplicate/overlaid objects are the root-cause of the ugly corridor models output seen at times.
However, this issue appears to be the same (Since the output pretty much does the same squiggly/jiggly jumping back & forth between stationed increments) the cause of this anomaly is unrelated to Base Map Control data directly.
If one of your past projects contained corridors & profiles which appear 'damaged' in parts of the model, like in the sample image above, there is a new 'Use-Cases' page that describes what's causing this and how to fix it.
38 Views
Chris,
The repair is still a work in-progress. I've been considering 3 different approaches to a solution, one of which was David's suggestion.
Did David's 'Marker replacement' workaround resolve this issue in any other projects where this occurred?
-Nick