Construction Staking using Corridors.... (Trimble)
Whats your guys' opinion on using corridors for roadway staking vs creating an alignment. We had a training session on how to import the corridor that our engineers created in civil 3d, to TBC, then to our Trimble data collectors via Trimble link. It seemed very clunky and everytime you hit undo while performing the task in civil 3d the program had a fatal error and crashed out. There has to be a better way! Whats your workflow on using corridors or is it easier to just created alignment and profiles for everything?
Trimbles's staking to alignments and profiles, or to alignments and a DTM work well for me.
I have not used Civil3D corridors.
My experience is that, bringing data into Trimble from other sources, it is best to export the alignment and a road DTM as LandXML. Import them separately and go stake...
I would take our engineering plans and hand enter the corridor information into Trimble Business Center.
This did take some time, a 2 mile corridor with curb, gutter, and sidewalk may take me two weeks to enter the information and make checks.
One thing I did like, once I was finished, I knew everything about the plans, and made my checks to verify.
For staking, the corridors work well for everything, such as blue topping. You walk anywhere in the corridor prism, and you get cut or fills to finish grade.
I agree, get to know the plans completely before leaving the office.
Before data collectors and after data collectors, I would take the set of plans and a new field book and start at the beginning of any route or corridor survey and enter and draw the centerline and offset locations of everything for use in the field.
Using Carlson Surveyor1 I would enter the centerline alignment and grading plan complete with vertical curves and PI elevations to be able to compute the necessary information for any point on the project.
RPLS NE Texas
putting the C3d corridor into TSC3's/trimble access is a normal part of our office workflow. It is quite valuable and really speeds up things. With contractors now building jobs with automated machine guidance, we can rapidly check their work for compliance with the design. One great benefit is the DC provides accurate interpolations on curves between stations and between feature allowing for spot shots and spot checks anywhere on the design surface instantly and accurately.
The only complaint I have is that some errors can occur with the trimble roads import of the C3d corridor. This then requires editing of the .rxl which is best done in trimble access. I use the access emulator on my pc for this process. The amount of editing can be fairly minimal if the design corridor is built with all the links defined and there are no vertical components of any subassemblies.
I also never ever ever bring the corridor into TBC to view or edit. TBC will screw it up on both the import and export routines.
and there are no vertical components of any subassemblies.
Amen to that.
We use Civil3D, but SurvCE for surveying. Our methodology for stakeout is either to generate corridor points on selected features (like back of kerb, or offset from back of kerb, in which case we make a "point generator assembly"), or generate dynamic feature lines off the corridor then explode (yeehaa) them down to 3D polyline. Then import points or 3D polylines into SurvCE and go for gold on site. The trouble with both methods is that it isn't dynamic, so changes to the model don't update the points or 3D polylines. BTW, the ability to select corridor feature lines in Civil3D is vastly improved in V2017.