Trimble Business Center

(Backstory) I am hunting for the best option to be able to reuse my corridor build to perform stakeout operations in the field. Specifically i am attempting to cut out the need for my field guys from having to key in templates to perform slope staking operations. We are currently running TSC3s with Access and Roads. TSC7’s are not an option for me yet so i’m looking at the best options with the equipment we have. So far after reading a handful of Alan’s articles regarding the use of GENIO files, i think my best option will be exporting “Trimble Access road strings”. I have done some field testing and i can get the staking information i require including a handful of H/V offsets and the slope intercept. However, I’m having issues when exporting the corridor for my project.

When i perform the "Trimble Access Road Strings" export and re-import the new .crd file into TBC to check, the new alignment definition is changing one of my vertical curves from symmetrical to asymmetrical. Once asymmetrical, it gives a departure curve length the exact distance to the the next vertical curves VPC. Prior to exporting, the symmetrical curve is only 750 long, after the export it is reaching over 3000' to the next curve and removing tangent section of line. I also notice that the .crd definition is adding a grade break at the VPC of every symmetrical curve, i am unsure if there is significance to that as well. The remainder of the alignment is technically a match (even though additional definition) with exception to the asymmetrical curve.

Before

After

Are there any known limitations to this export that could cause this? Or possibly a flaw in my corridor build that the software doesn’t like? Any suggestions would be greatly appreciated.

Thanks,

Joe

I will feed that back to development Joe - you could also try out the RPS Moss Export TML function that we just wrapped up that has a dedicated function to output the MX Road String format for Access - that may assist you here - it also manages all the mapping of your coding to the 4 character codes that MX GENIO files requires - it maps them to a 4 character code. I will turn that on for a 7 day trial for you today - check it out using TML Status

Your trial is active for 7 days Joe

Alan

Thanks Alan,

I emailed you a link to the files in my Google Drive. I included the VCE and the resulting .crd. I've tried a handful of modifications to attempt to "fake" it out, including changing the curve to asymmetrical and just setting the front/back to the correct length with the same results. Thanks for the trial of the MX Moss, I'll give it a shot this weekend to see if i get different results.

UPDATE   Please also let development know that it is somehow related to the (2) VPIs being the same elevation. If i change the elevation of either VPI by 0.001', it appears to export correctly. If they have any feedback i would love to hear, even if it doesn't get fixed, i would be interested in knowing the cause so i can try to avoid it on future projects.

Thanks for the update - I have sent it in to support

Alan

On Sun, Apr 26, 2020, 10:38 AM jomelchiori@trimediaee.com <

UPDATE   Issue above still occurs in TBC 5.3. The changing of one VPI by .001' still works as a temporary work around. We have also encountered an issue, that if we have multiple vertical alignments are defined inside of the horizontal alignment, when exporting to the .crd file, in some instances, the master linestring will export one of the supporting profiles. This happens regardless of the definition of the surface being controlled by the primary alignment and profile in TBC.

As far as the 3D strings and the Side Slopes, the .crd works very well, most issues we are seeing tend to be related to the definition of master string. However, we are using this tool to provide slope stakes with h/v offsets to centerline so the master string is critical. 

Joe

The alignment has a property when there are multiple VALs that sets which

is the correct VAL to be using and that is used in the Corridor - can you

check that you set that Property on the alignment correctly before

exporting it.

Alan

On Wed, May 13, 2020 at 8:06 AM jomelchiori@trimediaee.com <

Hey Alan,

Here are the properties showing when i select the alignment, corridor, and corridor surface. All point to the correct profile.

The resulting Profile comes out as following;

below is the secondary profile being exported

Let me know if I'm checking the wrong setting location.

Thanks,

Joe

I will call you in the am to discuss Joe - easier on the phone

Alan

On Wed, May 13, 2020 at 2:58 PM jomelchiori@trimediaee.com <

Could we get the data to take a look at - Development will want to see it I am sure if they are to provide a fix for this

Alan