Trimble Business Center

Sure - the help system also provides some direction here but here goes anyway

1. Road Name - This is the name of the Road in the RXL File when you read it in Access
2. Surface - Which surface do you want to export to RXL format
3. Horizontal Alignment - Which alignment do you want to use in the creation of the RXL file
4. Vertical Alignment - will default to the first Vertivcal Alignment - if you have multiple Vertical Alignments on the same Horizontal Alignment Pick the one you want to use
5. Begin Station - Typically the start of the alignment but can be anywhere if you only want part of the road
6. End Station - Typically the End of the alignment but again can be anywhere along the alignment if you only want a part of the road
7. Left Offset / Right Offset - typically enter a value larger than the max width of the road, but if you only want the Pavement for example put in a Left and Right Offset to limit the width of the RXL Sections. This reduces the width of the road that you can stake out etc.
8. File Name - The file that you want to create .RXL

Now the trickier parts

1. File Version - leave it at the default - mine shows 6.4 from v5.1 of TBC
2. Template Generate Method - you have options here
   1. Control Point Method - this will generate "Sections" in the RXL everywhere where there is at least one point in the source model. SInce most corridors are generated using Sections this is a good option to pick as it will use all of the sections that you were given rather than trying to interpolate between sections i.e. if your source data had points at say 25' intervals - this will use those 25' intervals.
   2. Sample Interval - Typically I would only use this approach if I am starting with a TIN model and no breaklines - this lets you sample at say 1' intervals and then it will compare the sections it creates against each adjacent section to see if the sections are varying by more than your input tolerance value and it will throw out sections that are within the tolerance and keep those outside the tolerance.
3. Adjust for Arc / chord offset - when you slice a cross section from a TIN Model, the TIN sides are basically chords that cut across the original curved linework (in curve sections of the road) - there will always be an Arc to Chord offset - depending onthe radius of the curve and the interval ofthe data that value can be Large or small - either way it is an error in the data - that if you stake it in the field at the chord location you will be off by the Arc to Chord separation (inside the true location when the chord is on the inside (centerline side of the curve) and outside the curve when the chord is on the outside of the line (non centerline side of the line). This setting allows you to adjust the computed sectional nodes for this offset using the Radius of the curve and the offset of the two ends of the chord (which should be on the line itself - giving you a more accurate result which is better for staking.
4. Sideslope Element Generate Method - again you have options here and which you choose depends somewhat on what data you are working with. If you have a TBC Corridor Model you will likely have sideslopes at the Left and Right end of the cross sections. If you import data you will have strings / breaklines that represent the features - however in this case TBC doesnt know that String A represents the Daylight Line and is in fact one end of the sideslope - so you have to tell the software what to do. Also if you are starting with just a TIN model, again the TIN doesn't state which Triangles represent the sideslope so again instruct TBC what to do.
   1. None - this stops TBC from adding any additional sideslope to your data - if it is a TBC corridor with Sidelsopes you will be OK, if it is a string model or a TIN model you likely don't want to select this option.
   2. Append - if you select Append - you are adding your own sideslopes to the model - you only get to add one simple sideslope for cut and one for fill. The Cut Sideslope can have a horizontal ditch and a sideslope. This will be appended to the left and right side end points of what you have selected as the model you are converting. If your model has sideslope ties, then I would remove them (the sideslope instructions in the Templates or the strings that represent the ties and ditch lines) if you are going to use this option. ie the model should go as far as the Hinge points and stop and then your defined sideslopes for Cut and Fill will be attached to the hinge points (edges of the model).
   3. Replace - this allows you to replace the last elements left and right of your computed sections with the sideslopes that you define (rather than appending them. Bear in mind that when modeling the sideslopes from Strings, you may have more than one triangle side on the side slope (creating 2 or more segments in the section) so this may or may not work as well as you hope (again depends on your data) - if you have strings, this can also have the same issue so be careful especially if you are using a Sample Interval rather than Control Point Method (which by default should only have one triangle side on the side slope at the control point location (if the source data is clean and good).
5. Left String Match Pattern - this allows you to enter a Regular Expression to define the naming of strings used to define the Daylight lines. Some software products use defaults like MX / Moss uses INT (regular expression ^INT) for its "Intersection Strings" so you can find those in the model if you have some kind of consistent naming - I rarely use this function.
6. Sideslope Element Code - this is similar to above - use the Feature Code to find the Daylight Lines - if you leave 5 and 6 blank then it defaults to using Last Segment Left and Right.
7. Cut Slope % - this is used if you use replace or Append in (4) above. If you enter 25% that would be a 4:1 slope.
8. Cut Ditch Width - if the Hinge point / stake location is above the Hinge Point (A Cut Condition) then a Ditch of this width will be placed first before the sideslope element - this has the effect of pushing out the daylight line by at least the ditch width.
9. Fill Slope - Enter the Fill Slope that you want in % i.e. a 4:1 slope would be 25%
10. Horizontal Alignment Station Interval - this is just for Access users and sets the default stake interval for the device when the RXL file is read. It has no effect on the generation of the RXL file from TBC other than a header record in the file for Access to set the Navigation Interval

You can try reading back your data into TBC as a check to see what you get. While maybe not 100% perfect it will at least show you areas where the output did not work for some reason and the sections at least should match your start point. 

RXL and Access are Geospatial Products - I hope that this helps, however if you still have data problems, you really need to discuss with your Geospatial Dealer or Geospatial Business Unit and chase that through the Geospatial Forum as I have no influence over their development and we do not use RXL format on the Civil Engineering and Construction side of the business. I am happy to try and assist so far, and can point you in the right direction (I hope) - but there is a point where you need to go to the team that takes care of this format and workflow. 

If you did build a Corridor Model in TBC from the plans, then you would use the Trimble Access Road RXL Templates method of Export rather than from Surface or Alignment.

If you have the Strings / Breaklines, some people comment that they have more success with the Trimble Access Road Strings method than with RXL files. In that case your strings should really only have meaningful 4 character names as the names are truncated to 4 characters (that is an MX GENIO Format Limit) which this is using as a format for Access exchange.

Hope that is OK - let me know if this helps.

Alan

Sure - the help system also provides some direction here but here goes anyway

1. Road Name - This is the name of the Road in the RXL File when you read it in Access
2. Surface - Which surface do you want to export to RXL format
3. Horizontal Alignment - Which alignment do you want to use in the creation of the RXL file
4. Vertical Alignment - will default to the first Vertivcal Alignment - if you have multiple Vertical Alignments on the same Horizontal Alignment Pick the one you want to use
5. Begin Station - Typically the start of the alignment but can be anywhere if you only want part of the road
6. End Station - Typically the End of the alignment but again can be anywhere along the alignment if you only want a part of the road
7. Left Offset / Right Offset - typically enter a value larger than the max width of the road, but if you only want the Pavement for example put in a Left and Right Offset to limit the width of the RXL Sections. This reduces the width of the road that you can stake out etc.
8. File Name - The file that you want to create .RXL

Now the trickier parts

1. File Version - leave it at the default - mine shows 6.4 from v5.1 of TBC
2. Template Generate Method - you have options here
   1. Control Point Method - this will generate "Sections" in the RXL everywhere where there is at least one point in the source model. SInce most corridors are generated using Sections this is a good option to pick as it will use all of the sections that you were given rather than trying to interpolate between sections i.e. if your source data had points at say 25' intervals - this will use those 25' intervals.
   2. Sample Interval - Typically I would only use this approach if I am starting with a TIN model and no breaklines - this lets you sample at say 1' intervals and then it will compare the sections it creates against each adjacent section to see if the sections are varying by more than your input tolerance value and it will throw out sections that are within the tolerance and keep those outside the tolerance.
3. Adjust for Arc / chord offset - when you slice a cross section from a TIN Model, the TIN sides are basically chords that cut across the original curved linework (in curve sections of the road) - there will always be an Arc to Chord offset - depending onthe radius of the curve and the interval ofthe data that value can be Large or small - either way it is an error in the data - that if you stake it in the field at the chord location you will be off by the Arc to Chord separation (inside the true location when the chord is on the inside (centerline side of the curve) and outside the curve when the chord is on the outside of the line (non centerline side of the line). This setting allows you to adjust the computed sectional nodes for this offset using the Radius of the curve and the offset of the two ends of the chord (which should be on the line itself - giving you a more accurate result which is better for staking.
4. Sideslope Element Generate Method - again you have options here and which you choose depends somewhat on what data you are working with. If you have a TBC Corridor Model you will likely have sideslopes at the Left and Right end of the cross sections. If you import data you will have strings / breaklines that represent the features - however in this case TBC doesnt know that String A represents the Daylight Line and is in fact one end of the sideslope - so you have to tell the software what to do. Also if you are starting with just a TIN model, again the TIN doesn't state which Triangles represent the sideslope so again instruct TBC what to do.
   1. None - this stops TBC from adding any additional sideslope to your data - if it is a TBC corridor with Sidelsopes you will be OK, if it is a string model or a TIN model you likely don't want to select this option.
   2. Append - if you select Append - you are adding your own sideslopes to the model - you only get to add one simple sideslope for cut and one for fill. The Cut Sideslope can have a horizontal ditch and a sideslope. This will be appended to the left and right side end points of what you have selected as the model you are converting. If your model has sideslope ties, then I would remove them (the sideslope instructions in the Templates or the strings that represent the ties and ditch lines) if you are going to use this option. ie the model should go as far as the Hinge points and stop and then your defined sideslopes for Cut and Fill will be attached to the hinge points (edges of the model).
   3. Replace - this allows you to replace the last elements left and right of your computed sections with the sideslopes that you define (rather than appending them. Bear in mind that when modeling the sideslopes from Strings, you may have more than one triangle side on the side slope (creating 2 or more segments in the section) so this may or may not work as well as you hope (again depends on your data) - if you have strings, this can also have the same issue so be careful especially if you are using a Sample Interval rather than Control Point Method (which by default should only have one triangle side on the side slope at the control point location (if the source data is clean and good).
5. Left String Match Pattern - this allows you to enter a Regular Expression to define the naming of strings used to define the Daylight lines. Some software products use defaults like MX / Moss uses INT (regular expression ^INT) for its "Intersection Strings" so you can find those in the model if you have some kind of consistent naming - I rarely use this function.
6. Sideslope Element Code - this is similar to above - use the Feature Code to find the Daylight Lines - if you leave 5 and 6 blank then it defaults to using Last Segment Left and Right.
7. Cut Slope % - this is used if you use replace or Append in (4) above. If you enter 25% that would be a 4:1 slope.
8. Cut Ditch Width - if the Hinge point / stake location is above the Hinge Point (A Cut Condition) then a Ditch of this width will be placed first before the sideslope element - this has the effect of pushing out the daylight line by at least the ditch width.
9. Fill Slope - Enter the Fill Slope that you want in % i.e. a 4:1 slope would be 25%
10. Horizontal Alignment Station Interval - this is just for Access users and sets the default stake interval for the device when the RXL file is read. It has no effect on the generation of the RXL file from TBC other than a header record in the file for Access to set the Navigation Interval

You can try reading back your data into TBC as a check to see what you get. While maybe not 100% perfect it will at least show you areas where the output did not work for some reason and the sections at least should match your start point. 

RXL and Access are Geospatial Products - I hope that this helps, however if you still have data problems, you really need to discuss with your Geospatial Dealer or Geospatial Business Unit and chase that through the Geospatial Forum as I have no influence over their development and we do not use RXL format on the Civil Engineering and Construction side of the business. I am happy to try and assist so far, and can point you in the right direction (I hope) - but there is a point where you need to go to the team that takes care of this format and workflow. 

If you did build a Corridor Model in TBC from the plans, then you would use the Trimble Access Road RXL Templates method of Export rather than from Surface or Alignment.

If you have the Strings / Breaklines, some people comment that they have more success with the Trimble Access Road Strings method than with RXL files. In that case your strings should really only have meaningful 4 character names as the names are truncated to 4 characters (that is an MX GENIO Format Limit) which this is using as a format for Access exchange.

Hope that is OK - let me know if this helps.

Alan

Sure - the help system also provides some direction here but here goes anyway

1. Road Name - This is the name of the Road in the RXL File when you read it in Access
2. Surface - Which surface do you want to export to RXL format
3. Horizontal Alignment - Which alignment do you want to use in the creation of the RXL file
4. Vertical Alignment - will default to the first Vertivcal Alignment - if you have multiple Vertical Alignments on the same Horizontal Alignment Pick the one you want to use
5. Begin Station - Typically the start of the alignment but can be anywhere if you only want part of the road
6. End Station - Typically the End of the alignment but again can be anywhere along the alignment if you only want a part of the road
7. Left Offset / Right Offset - typically enter a value larger than the max width of the road, but if you only want the Pavement for example put in a Left and Right Offset to limit the width of the RXL Sections. This reduces the width of the road that you can stake out etc.
8. File Name - The file that you want to create .RXL

Now the trickier parts

1. File Version - leave it at the default - mine shows 6.4 from v5.1 of TBC
2. Template Generate Method - you have options here
   1. Control Point Method - this will generate "Sections" in the RXL everywhere where there is at least one point in the source model. SInce most corridors are generated using Sections this is a good option to pick as it will use all of the sections that you were given rather than trying to interpolate between sections i.e. if your source data had points at say 25' intervals - this will use those 25' intervals.
   2. Sample Interval - Typically I would only use this approach if I am starting with a TIN model and no breaklines - this lets you sample at say 1' intervals and then it will compare the sections it creates against each adjacent section to see if the sections are varying by more than your input tolerance value and it will throw out sections that are within the tolerance and keep those outside the tolerance.
3. Adjust for Arc / chord offset - when you slice a cross section from a TIN Model, the TIN sides are basically chords that cut across the original curved linework (in curve sections of the road) - there will always be an Arc to Chord offset - depending onthe radius of the curve and the interval ofthe data that value can be Large or small - either way it is an error in the data - that if you stake it in the field at the chord location you will be off by the Arc to Chord separation (inside the true location when the chord is on the inside (centerline side of the curve) and outside the curve when the chord is on the outside of the line (non centerline side of the line). This setting allows you to adjust the computed sectional nodes for this offset using the Radius of the curve and the offset of the two ends of the chord (which should be on the line itself - giving you a more accurate result which is better for staking.
4. Sideslope Element Generate Method - again you have options here and which you choose depends somewhat on what data you are working with. If you have a TBC Corridor Model you will likely have sideslopes at the Left and Right end of the cross sections. If you import data you will have strings / breaklines that represent the features - however in this case TBC doesnt know that String A represents the Daylight Line and is in fact one end of the sideslope - so you have to tell the software what to do. Also if you are starting with just a TIN model, again the TIN doesn't state which Triangles represent the sideslope so again instruct TBC what to do.
   1. None - this stops TBC from adding any additional sideslope to your data - if it is a TBC corridor with Sidelsopes you will be OK, if it is a string model or a TIN model you likely don't want to select this option.
   2. Append - if you select Append - you are adding your own sideslopes to the model - you only get to add one simple sideslope for cut and one for fill. The Cut Sideslope can have a horizontal ditch and a sideslope. This will be appended to the left and right side end points of what you have selected as the model you are converting. If your model has sideslope ties, then I would remove them (the sideslope instructions in the Templates or the strings that represent the ties and ditch lines) if you are going to use this option. ie the model should go as far as the Hinge points and stop and then your defined sideslopes for Cut and Fill will be attached to the hinge points (edges of the model).
   3. Replace - this allows you to replace the last elements left and right of your computed sections with the sideslopes that you define (rather than appending them. Bear in mind that when modeling the sideslopes from Strings, you may have more than one triangle side on the side slope (creating 2 or more segments in the section) so this may or may not work as well as you hope (again depends on your data) - if you have strings, this can also have the same issue so be careful especially if you are using a Sample Interval rather than Control Point Method (which by default should only have one triangle side on the side slope at the control point location (if the source data is clean and good).
5. Left String Match Pattern - this allows you to enter a Regular Expression to define the naming of strings used to define the Daylight lines. Some software products use defaults like MX / Moss uses INT (regular expression ^INT) for its "Intersection Strings" so you can find those in the model if you have some kind of consistent naming - I rarely use this function.
6. Sideslope Element Code - this is similar to above - use the Feature Code to find the Daylight Lines - if you leave 5 and 6 blank then it defaults to using Last Segment Left and Right.
7. Cut Slope % - this is used if you use replace or Append in (4) above. If you enter 25% that would be a 4:1 slope.
8. Cut Ditch Width - if the Hinge point / stake location is above the Hinge Point (A Cut Condition) then a Ditch of this width will be placed first before the sideslope element - this has the effect of pushing out the daylight line by at least the ditch width.
9. Fill Slope - Enter the Fill Slope that you want in % i.e. a 4:1 slope would be 25%
10. Horizontal Alignment Station Interval - this is just for Access users and sets the default stake interval for the device when the RXL file is read. It has no effect on the generation of the RXL file from TBC other than a header record in the file for Access to set the Navigation Interval

You can try reading back your data into TBC as a check to see what you get. While maybe not 100% perfect it will at least show you areas where the output did not work for some reason and the sections at least should match your start point. 

RXL and Access are Geospatial Products - I hope that this helps, however if you still have data problems, you really need to discuss with your Geospatial Dealer or Geospatial Business Unit and chase that through the Geospatial Forum as I have no influence over their development and we do not use RXL format on the Civil Engineering and Construction side of the business. I am happy to try and assist so far, and can point you in the right direction (I hope) - but there is a point where you need to go to the team that takes care of this format and workflow. 

If you did build a Corridor Model in TBC from the plans, then you would use the Trimble Access Road RXL Templates method of Export rather than from Surface or Alignment.

If you have the Strings / Breaklines, some people comment that they have more success with the Trimble Access Road Strings method than with RXL files. In that case your strings should really only have meaningful 4 character names as the names are truncated to 4 characters (that is an MX GENIO Format Limit) which this is using as a format for Access exchange.

Hope that is OK - let me know if this helps.

Alan

Sure - the help system also provides some direction here but here goes anyway

1. Road Name - This is the name of the Road in the RXL File when you read it in Access
2. Surface - Which surface do you want to export to RXL format
3. Horizontal Alignment - Which alignment do you want to use in the creation of the RXL file
4. Vertical Alignment - will default to the first Vertivcal Alignment - if you have multiple Vertical Alignments on the same Horizontal Alignment Pick the one you want to use
5. Begin Station - Typically the start of the alignment but can be anywhere if you only want part of the road
6. End Station - Typically the End of the alignment but again can be anywhere along the alignment if you only want a part of the road
7. Left Offset / Right Offset - typically enter a value larger than the max width of the road, but if you only want the Pavement for example put in a Left and Right Offset to limit the width of the RXL Sections. This reduces the width of the road that you can stake out etc.
8. File Name - The file that you want to create .RXL

Now the trickier parts

1. File Version - leave it at the default - mine shows 6.4 from v5.1 of TBC
2. Template Generate Method - you have options here
   1. Control Point Method - this will generate "Sections" in the RXL everywhere where there is at least one point in the source model. SInce most corridors are generated using Sections this is a good option to pick as it will use all of the sections that you were given rather than trying to interpolate between sections i.e. if your source data had points at say 25' intervals - this will use those 25' intervals.
   2. Sample Interval - Typically I would only use this approach if I am starting with a TIN model and no breaklines - this lets you sample at say 1' intervals and then it will compare the sections it creates against each adjacent section to see if the sections are varying by more than your input tolerance value and it will throw out sections that are within the tolerance and keep those outside the tolerance.
3. Adjust for Arc / chord offset - when you slice a cross section from a TIN Model, the TIN sides are basically chords that cut across the original curved linework (in curve sections of the road) - there will always be an Arc to Chord offset - depending onthe radius of the curve and the interval ofthe data that value can be Large or small - either way it is an error in the data - that if you stake it in the field at the chord location you will be off by the Arc to Chord separation (inside the true location when the chord is on the inside (centerline side of the curve) and outside the curve when the chord is on the outside of the line (non centerline side of the line). This setting allows you to adjust the computed sectional nodes for this offset using the Radius of the curve and the offset of the two ends of the chord (which should be on the line itself - giving you a more accurate result which is better for staking.
4. Sideslope Element Generate Method - again you have options here and which you choose depends somewhat on what data you are working with. If you have a TBC Corridor Model you will likely have sideslopes at the Left and Right end of the cross sections. If you import data you will have strings / breaklines that represent the features - however in this case TBC doesnt know that String A represents the Daylight Line and is in fact one end of the sideslope - so you have to tell the software what to do. Also if you are starting with just a TIN model, again the TIN doesn't state which Triangles represent the sideslope so again instruct TBC what to do.
   1. None - this stops TBC from adding any additional sideslope to your data - if it is a TBC corridor with Sidelsopes you will be OK, if it is a string model or a TIN model you likely don't want to select this option.
   2. Append - if you select Append - you are adding your own sideslopes to the model - you only get to add one simple sideslope for cut and one for fill. The Cut Sideslope can have a horizontal ditch and a sideslope. This will be appended to the left and right side end points of what you have selected as the model you are converting. If your model has sideslope ties, then I would remove them (the sideslope instructions in the Templates or the strings that represent the ties and ditch lines) if you are going to use this option. ie the model should go as far as the Hinge points and stop and then your defined sideslopes for Cut and Fill will be attached to the hinge points (edges of the model).
   3. Replace - this allows you to replace the last elements left and right of your computed sections with the sideslopes that you define (rather than appending them. Bear in mind that when modeling the sideslopes from Strings, you may have more than one triangle side on the side slope (creating 2 or more segments in the section) so this may or may not work as well as you hope (again depends on your data) - if you have strings, this can also have the same issue so be careful especially if you are using a Sample Interval rather than Control Point Method (which by default should only have one triangle side on the side slope at the control point location (if the source data is clean and good).
5. Left String Match Pattern - this allows you to enter a Regular Expression to define the naming of strings used to define the Daylight lines. Some software products use defaults like MX / Moss uses INT (regular expression ^INT) for its "Intersection Strings" so you can find those in the model if you have some kind of consistent naming - I rarely use this function.
6. Sideslope Element Code - this is similar to above - use the Feature Code to find the Daylight Lines - if you leave 5 and 6 blank then it defaults to using Last Segment Left and Right.
7. Cut Slope % - this is used if you use replace or Append in (4) above. If you enter 25% that would be a 4:1 slope.
8. Cut Ditch Width - if the Hinge point / stake location is above the Hinge Point (A Cut Condition) then a Ditch of this width will be placed first before the sideslope element - this has the effect of pushing out the daylight line by at least the ditch width.
9. Fill Slope - Enter the Fill Slope that you want in % i.e. a 4:1 slope would be 25%
10. Horizontal Alignment Station Interval - this is just for Access users and sets the default stake interval for the device when the RXL file is read. It has no effect on the generation of the RXL file from TBC other than a header record in the file for Access to set the Navigation Interval

You can try reading back your data into TBC as a check to see what you get. While maybe not 100% perfect it will at least show you areas where the output did not work for some reason and the sections at least should match your start point. 

RXL and Access are Geospatial Products - I hope that this helps, however if you still have data problems, you really need to discuss with your Geospatial Dealer or Geospatial Business Unit and chase that through the Geospatial Forum as I have no influence over their development and we do not use RXL format on the Civil Engineering and Construction side of the business. I am happy to try and assist so far, and can point you in the right direction (I hope) - but there is a point where you need to go to the team that takes care of this format and workflow. 

If you did build a Corridor Model in TBC from the plans, then you would use the Trimble Access Road RXL Templates method of Export rather than from Surface or Alignment.

If you have the Strings / Breaklines, some people comment that they have more success with the Trimble Access Road Strings method than with RXL files. In that case your strings should really only have meaningful 4 character names as the names are truncated to 4 characters (that is an MX GENIO Format Limit) which this is using as a format for Access exchange.

Hope that is OK - let me know if this helps.

Alan