In the initial design stages, divide each corridor into multiple regions. Create a separate region wherever the assembly changes, such as for lane widening or intersections. As the design gets more detailed, you can turn off regions you are not working in and experience faster rebuilds. In each region, set the assembly frequency and the section swath width to avoid loading the design with unnecessary data. For example, assemblies can be widely spaced along a straight roadway across flat terrain, and spaced more closely in regions with a lot of change.
Section swath width should be set to a value not much wider than the maximum corridor width between the daylight lines on each side. Avoid a swath width that takes in excessive amounts of the existing ground surface beyond the corridor.
Instead of creating one region for a long corridor, divide the corridor into multiple, smaller regions. For example, on a 5,000 meter corridor, create five regions, each of which is about 1,000 meters long. This reduces the processing load when rebuilding the corridor.
Set region targets after creating the regions. For example, when creating regions, leave the targets set to “None” and proceed with creating the regions. After the regions are created, set the targets on the regions. This reduces the processing load because processing the assembly insertion points (during region creation), and processing the setting of the assembly targets, are two separate operations instead of one.
Hide unneeded regions when editing corridors. For example, when editing a corridor that contains multiple regions, hide the regions that you are not editing. This results in faster system response time while editing a corridor region.