Quantcast
Channel: OpenRoads | OpenSite Forum - Recent Threads
Viewing all articles
Browse latest Browse all 15087

[OR] CR - Template point feature definitions and name overrides

$
0
0

The long and the short of this: In template processing, please allow any constructed point to assign the feature definition of the 3D linear segment that it is a member of.


My template was originally provided with a client's workspace. It was set up so that whether you're in cut or fill, the tie point name is overridden to, say, ConStakes-L and ConStakes-R. The usual way to handle cut and fill is to show cut ties and fill ties on a different level. The most obvious fix here is to go into the point properties and set cut tie points to use the cut feature definition. That didn't work. The way OpenRoads creates and processes these points is that the entire element is (in my case, at least) on the level indicating a fill tie condition. 

Moving forward on this project I plan to keep things as they are currently. Fixing it means I would need to recreate or at least revise terrain models from corridors. I don't want to go there. For future projects, I can think of other ways to handle this, such as having name overrides named ConStakes-F-L and ConStakes-C-L, etc. Meanwhile, there may be specific reasons you want to have a separate element that combines all of these slope stake lines. I guess there's always the option of adding one more point that's pegged to that tie point.

But might I suggest another way to handle this? The options as presented suggest that the feature definition is independent of the name override. This simply isn't true. So might it make sense to present this a different way to the user who is faced with this issue? Perhaps in the Active Template thing, give us a list of name overrides and the feature definition applied to that name.

But I guess this wouldn't really be unique to that template anyway; I think it's a corridor-wide thing, and this is probably true even if there are no name overrides for a given point that has the same name across template drops.

In case it is impossible to have a single segment of a greater chain to have different formatting, I do see that the user can at will assign formatting and even the feature definition. 


Viewing all articles
Browse latest Browse all 15087

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>