This project is in an urban area. Here is a Corridor with a lot of point controls and arches. In the Properties of the Feature Definition of the Corridor the Densify Horizontal is On. With the Arches this is a good way to increase the detail at curves and point controls.
The Value of the Densify Horizontal is very low (now 0.01). This causes a lot of intervals which makes the model slow (see image):
If I want to edit the Densify Value, the box is grey:
Is it possible to edit this value?
With kind regards,
Louis van Amerongen
According to the online Help, 0.01 is the default value when nothing is set in the config variable, see https://docs.bentley.com/LiveContent/web/OpenRail%20Designer-v8/en/GUID-155A20EE-881B-4EA8-8EA8-74C53F6FA95C.html
Edit: the above information is from OpenRail, but I assume it also works in ORD.
Thanks Jan and Chris,
Jan, I changed the variable but unfortunately the text stays grey.
Now my work-method is to make two Feature Defintitions for Corridors. One where the Densify Horizontal variable is set to true and one where it is set to false. The last one is used when working on the project, the first one is used for the final version.
Regards Louis
I think changing the variable will not show in the text. The only way to test if it has any effect, is to use it in a model when setting the variable to different values. At the moment on my pc the variable is set to 0.02, but if you set it to something like 1 or 2, it's effect should be visible in the model.I'm not able to try it myself at this moment, otherwise I would to make sure it works.
Hi,
So do we know if this has been logged as a defect (greyed out options)? Surely we should be able to set different values for different corridor feature definitions.
Regards,
Mariusz
OpenRoads Designer 2022 R1
I would think that it would (and believe it does) adopt the stroking points of the parent baseline geometry?
Mark
OpenRoads Designer 2023 | Microstation 2023.2 | ProjectWise 2023
Hi Mark,
Corridors doesn't seem to adopt the stroking from the parents base line, i.e. it follows the greyed out global stroking values which makes it inflexible.
I think, you may be referring to linear templates which do follow the stroking setting of their base geometry and linear templates do not have separate stroking setting.
The whole point in using stroking on corridors is to optimize number of points on components meshes / locations of templates (i.e. less on straights at the same interval setting).
Also, you may want to have denser / more detailed pavement edge definition and footpath meshes within junction than on mainline alignment hence the need for separate settings for the base geometries.
In the example below the edge geometry that follows tight R=3m corner radius has horizontal density set to 0.001 but the corridor follows the predefined 0.02 value (as per CIVIL_DEFAULT_CURVE_STROKING set in the workspace)
I know it is more of a workaround, but you can always add an extra template drop using the same template but with a smaller drop interval. That way you could mimic the densify you want to use in a tight curve.