I have a project with a single 18.1 mile alignment and profile. Upon trying to make simple profile adjustments, I notice lots of spinning and not responding for a long period of time when trying to edit with either the table editor or graphically. The alignment will update to changes, but only with painfully long periods of waiting in between each click while the software responds.
I think this alignment is too much for the software to process in a manageable way. Does anyone know the recommendations for maximum alignment length?
I think I may need to split this alignment up into segments like my corridors are. The corridors for this project are split up into 4 corridors; 4.5 miles each, although they process alright, I wonder if I am pushing the limitations of this software. Are there maximum corridor length recommendations?
I use OpenRoads Desinger 2019 Release 2.
Properties indicate: V.10.12.0.56
While I don't have a lot of experience with ORD yet, I have seen recommendations of 1 mile max. for the best performance. Since ORD is capable of working with reference file design data, I would expect that managing a number of alignment segments wouldn't be any harder than managing a mainline with ramps and cross streets.
Splitting up the data can have other benefits as well - including the ability to let more than one person work on a project at a time. For an 18 mile project, that might be a good thing.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
We've noticed that clearing the active profile if you are planning to make lots of PVI updates has helped stability a lot. Additionally, after some trial and error, if you add more than 20 PVI's in a given session, ORD tends to get mad at you. So I'll add them in bunches, close the software, and re-open, saving frequently. Profile edits have resulted in the most software crashes then anything if I had to guess. I haven't reliably reproduced the 20-PVI assumption, so I haven't submitted an SR, but it seems relatively consistent. (See also: My thread in the Ideas Forum for additional support for spline/graphic grade). We don't have anything that's 18 miles, but we have several alignments that are over ~4 and I've had to add hundreds of PVI's to those. My success rate has...not been great and I've had a lot of crashes and restarts.We are currently using 20R1.
Answer Verified By: Jennifer Longmore
Hi JenniferFrom our experience, the right hardware goes a long way in determining what a workable length is. We have a 60km long route that we split into three 20km (12.5mi) sections and that works okay on a gaming laptop with 16GB ram, i7 CPU, SSD, and an nVidia GTX 1060.
What also goes a very long way is separating your workflow into reference dgns rather than trying to combine them as a simple change to the vertical alignment results in reprocessing of the corridor. We use separate dgns for: terrain model, baseline geometry, superelevations, corridor (which can be further split into layerworks and end conditions), and point controls. The biggest speed improvement we noticed was separating the corridor dgn into roadworks and end conditions.
The size of your terrain model also plays a part - it seems as if the current coding interrogates the whole terrain model when finding intercepts for end conditions. I think that should be looked at again.
I hope this helps!
Kind Regards
If you are working in the file where you have the corridor, don't forget to release corridor rules when you edit the profile to avoid processing the corridor at each change.
It applies also when you add many point controls, parametric constraints, ...
We also separate our files in this manner.