Geopak OpenRoads VBA to Move Cross Section Cells

Now that I'm using OpenRoads regularly on projects, every time I need to cut cross sections from a corridor, the cross section cells and proposed elements are cut into a new sheet model and (depending on the changes that have taken place) many of the cell origins can end up being in a new location than they were previously.  This wouldn’t be a big deal if it weren’t for the level of additional detail that we need to add to our cross sections after they are generated.

Our workflow used to be like this:

1)      Process existing ground cross sections

2)      Process proposed cross sections at a specified interval (this would run on top of existing ground elements and reuse the same cells)

3)      Add in cross sections at culverts (these used to just be just added off to the right of the other cross sections)

4)      Add in cross section labels by many different tools (Corridor Modeler VBA, Criteria, Cross Section Labeler, Ancillary Data, and manual)

5)      Draw on and label Geology layers

6)      Cut to sheets

When the design progressed to the next stage, the workflow only required deleting the proposed elements drawn in steps 2 & 3 and some of the labeling.  We had the ability to just reprocess the proposed elements back onto the existing cross section cells and update some of the labeling.  Our sheets usually didn’t even need to be recut.

In the new workflow, the initial process seems to be very similar:

1)      Process existing and proposed elements to cross section cells

2)      When the design includes culvert sections, reprocess all existing and proposed elements to cross section cells again (and again every time a culvert is changed)

3)      Add in cross section labels by many different tools (Corridor Modeler Annotation, Criteria, Cross Section Labeler, Ancillary Data, and manual)

4)      Draw on and label Geology layers (mostly manually generated layers and not from terrains)

5)      Cut to sheets

The problem is when we get to the next stage & make several design revisions, we have to start all the way back over and cut sections into a new model.  We have tried attaching the old cross section files as references so that we can copy back in all of the old labels, annotations, and geology layers.  We have found that many times (due to design changes that raise or lower ditches and other elements) the origins of the cross section cells have new elevations and the labeling and Geology layers don’t come in exactly where they were before.  On most projects, it may not be a big deal to fix the ones that are different. On a 10 mile project with sections every 50’ you’re talking about checking and fixing 1056 main line cross sections manually (then you have to fix all the side roads and frontage roads).  Then someone else has to verify that everything is correct again for quality control.

We have been holding off on developing our own solution for this problem in the hopes that it would be fixed in a future release.  Since the issue still persists in OpenRoads SS4, we find it necessary to come up with some kind of a fix.  Before I go spending a large amount of time, I wanted to check to see if there are already any solutions to this (either in place or in development).  I’m certain that a VBA could be written (fairly easily) that could handle this type of thing.  I envision that it could work with a form like this:

Here would be the workflow:

1)      User kicks off the VBA from the file containing the new cross sections (and a pop up should ask to confirm that it’s being run from the new cross section file before starting up).

2)      User picks the GPK job number, which populates the Chain text box

3)      User types in (or uses the browse button) to pick the file containing the old sections

4)      User picks OK-

a.       The old file and current file are scanned to make sure they both have cells for the selected chain (if not, pop up stops operation)

b.      The old file is scanned and a temporary file is generated that logs the Station, X, Y, & elevation at the origin of all the cells in the file

c.       The new file is scanned and steps through each cross section.  If the station existed in the old file it compares the cell origins & elevations to the old file and moves it, if different, so that the elevations & origins line up

d.      Temporary log file deleted, process complete dialog is displayed