https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177en-USTelligent Community 12https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177Fri, 13 Sep 2013 08:37:53 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fJason Walshhttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsCurrent Revision posted to OpenRoads | OpenSite Wiki by Jason Walsh on 9/13/2013 8:37:53 AM<br /> <p><b><img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /></b></p> <table style="background-color:#dce5f0;width:500px;border:#dce5f0 0px solid;" border="0" align="left"> <tbody> <tr> <td style="text-align:right;"><b>&nbsp;</b></td> <td style="text-align:right;"><b>&nbsp;</b></td> <td></td> <td></td> </tr> <tr> <td style="text-align:right;"><b>&nbsp;</b></td> <td style="text-align:right;"><span style="font-size:medium;"><b>Applies To&nbsp;</b></span></td> <td></td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td></td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Product(s):</strong></td> <td>Bentley MX Products</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Version(s):</strong></td> <td></td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Environment:&nbsp;</strong></td> <td>N/A</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Area:&nbsp;</strong></td> <td>N/A</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Subarea:&nbsp;</strong></td> <td>N/A</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Original Author:</strong></td> <td>Bentley Technical Support Group</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td></td> <td></td> </tr> </tbody> </table> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <h1>Scope</h1> <p>This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX.</p> <p>&nbsp;</p> <h1>Introduction</h1> <p>Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings.</p> <p>With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option.</p> <p>Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment.</p> <p>&nbsp;</p> <h1>How the files are written</h1> <p>The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that &#39;best fits&#39; the alignment by generating a fixed float, float, float scenario in the resulting data file.</p> <p>Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX.</p> <p>&nbsp;</p> <h1>Data Output accuracy</h1> <p>Because the data output files are a &#39;best fit&#39; of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files.</p> <p>&nbsp;</p> <h1>Recommendations</h1> <p>To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places.&nbsp;</p> <p>To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy.</p> <p>Depending on the length of the alignment and the point interval specified, the genio data for the master string may be very extensive, which in some working methods may prove to be inconvenient. To avoid this, store only only the data for the geometry string, but immediately following the data add an EDIT 029 command to regenerate the master string from the geometry string.</p> <p>A more pragmatic&nbsp;approach&nbsp;- and still the most commonly used - is to generate the HALGN, HCUSP, VALGN, VERAT and VCUSP as required and run the input data file; then compare the resulting master and geometry strings with the original created in interactive alignment (either visually or using reporting tools) or simply check that the results are acceptable.&nbsp; For the vast majority of cases this method proves entirely satisfactory, and provides the advantage that simple changes to the alignment (changing value of an intermediate free curve in VALGN or VERAT, for example) can be made by directly modifying the data, enabling extremely quick iteratation to optimize a design.&nbsp; [Limitation: With this method is not suitable where interactive alignment has been used to store superelevation/cant points, as there is no linemode equivalent, and thus these points will be lost.&nbsp; Use genio&nbsp;data instead]</p> <p>&nbsp;</p> <h1>See Also</h1> <p><a href="/Products/w/Products__Wiki/product-technotes-and-faqs.aspx">Product TechNotes and FAQs</a></p> <p><a href="/Products/Road___Site_Design/w/Road_and_Site_Design__Wiki/mx-technotes-and-faqs.aspx">MX TechNotes And FAQs</a></p> <h1>External Links</h1> <p><a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/">Bentley Technical Support KnowledgeBase</a></p> <p><a title="LEARN Server" href="http://lms.bentley.com">Bentley LEARN Server</a></p> <h1>Comments or Corrections?</h1> <p>Bentley&#39;s Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU!</p> <p>&nbsp;</p> <div class="hr"></div> <p>&nbsp;&nbsp;&nbsp;</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: tn8282, Civil, MX, MXURBAN, TechNote, Data Files, TechNotes</div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/10Mon, 24 Jun 2013 12:29:19 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fElisabeth Pryhttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 10 posted to OpenRoads | OpenSite Wiki by Elisabeth Pry on 6/24/2013 12:29:19 PM<br /> <p><b><img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /></b></p> <table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0" align="left"> <tbody> <tr> <td style="text-align:right;"><b>&nbsp;</b></td> <td style="text-align:right;"><b>&nbsp;</b></td> <td></td> <td></td> </tr> <tr> <td style="text-align:right;"><b>&nbsp;</b></td> <td style="text-align:right;"><span style="font-size:medium;"><b>Applies To&nbsp;</b></span></td> <td></td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td></td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Product(s):</strong></td> <td>Bentley MX Products</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Version(s):</strong></td> <td></td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Environment:&nbsp;</strong></td> <td>N/A</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Area:&nbsp;</strong></td> <td>N/A</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Subarea:&nbsp;</strong></td> <td>N/A</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>Original Author:</strong></td> <td>Bentley Technical Support Group</td> <td></td> </tr> <tr> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td style="text-align:right;"><strong>&nbsp;</strong></td> <td></td> <td></td> </tr> </tbody> </table> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <h1>Scope</h1> <p>This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX.</p> <p>&nbsp;</p> <h1>Introduction</h1> <p>Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings.</p> <p>With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option.</p> <p>Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment.</p> <p>&nbsp;</p> <h1>How the files are written</h1> <p>The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that &#39;best fits&#39; the alignment by generating a fixed float, float, float scenario in the resulting data file.</p> <p>Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX.</p> <p>&nbsp;</p> <h1>Data Output accuracy</h1> <p>Because the data output files are a &#39;best fit&#39; of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files.</p> <p>&nbsp;</p> <h1>Recommendations</h1> <p>To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places.&nbsp;</p> <p>To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy.</p> <p>Depending on the length of the alignment and the point interval specified, the genio data for the master string may be very extensive, which in some working methods may prove to be inconvenient. To avoid this, store only only the data for the geometry string, but immediately following the data add an EDIT 029 command to regenerate the master string from the geometry string.</p> <p>A more pragmatic&nbsp;approach&nbsp;- and still the most commonly used - is to generate the HALGN, HCUSP, VALGN, VERAT and VCUSP as required and run the input data file; then compare the resulting master and geometry strings with the original created in interactive alignment (either visually or using reporting tools) or simply check that the results are acceptable.&nbsp; For the vast majority of cases this method proves entirely satisfactory, and provides the advantage that simple changes to the alignment (changing value of an intermediate free curve in VALGN or VERAT, for example) can be made by directly modifying the data, enabling extremely quick iteratation to optimize a design.&nbsp; [Limitation: With this method is not suitable where interactive alignment has been used to store superelevation/cant points, as there is no linemode equivalent, and thus these points will be lost.&nbsp; Use genio&nbsp;data instead]</p> <p>&nbsp;</p> <h1>See Also</h1> <p><a href="/Products/w/Products__Wiki/product-technotes-and-faqs.aspx">Product TechNotes and FAQs</a></p> <p><a href="/Products/Road___Site_Design/w/Road_and_Site_Design__Wiki/mx-technotes-and-faqs.aspx">MX TechNotes And FAQs</a></p> <h1>External Links</h1> <p><a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/">Bentley Technical Support KnowledgeBase</a></p> <p><a title="LEARN Server" href="http://lms.bentley.com">Bentley LEARN Server</a></p> <h1>Comments or Corrections?</h1> <p>Bentley&#39;s Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU!</p> <p>&nbsp;</p> <div class="hr"></div> <p>&nbsp;&nbsp;&nbsp;</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Civil, Data Files, MX, MXURBAN, TechNote, TechNotes, tn8282</div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/9Tue, 06 Nov 2012 19:13:03 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fJacquelyn Pettushttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 9 posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 11/6/2012 7:13:03 PM<br /> <p><a title="SELECT Services Online" href="http://selectservices.bentley.com/en-US"></a>&nbsp;&nbsp;<a href="http://selectservices.bentley.com/en-US"><img border="0" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="175" height="56" alt="" /></a></p> <h1>Document Information</h1> <blockquote> <p><strong>Document Type:</strong> TechNote &nbsp;</p> <p><strong>Product(s):</strong>&nbsp; Bentley MX Products</p> <p><strong>Version(s):</strong>&nbsp; All</p> <p><strong>Original Author:</strong> Bentley Technical Support Group</p> <p><strong>Legacy Document Number:</strong> 8282</p> </blockquote> <h1>Scope</h1> <p>This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX.</p> <p>&nbsp;</p> <h1>Introduction</h1> <p>Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings.</p> <p>With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option.</p> <p>Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment.</p> <p>&nbsp;</p> <h1>How the files are written</h1> <p>The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that &#39;best fits&#39; the alignment by generating a fixed float, float, float scenario in the resulting data file.</p> <p>Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX.</p> <p>&nbsp;</p> <h1>Data Output accuracy</h1> <p>Because the data output files are a &#39;best fit&#39; of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files.</p> <p>&nbsp;</p> <h1>Recommendations</h1> <p>To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places.&nbsp;</p> <p>To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy.</p> <p>Depending on the length of the alignment and the point interval specified, the genio data for the master string may be very extensive, which in some working methods may prove to be inconvenient. To avoid this, store only only the data for the geometry string, but immediately following the data add an EDIT 029 command to regenerate the master string from the geometry string.</p> <p>A more pragmatic&nbsp;approach&nbsp;- and still the most commonly used - is to generate the HALGN, HCUSP, VALGN, VERAT and VCUSP as required and run the input data file; then compare the resulting master and geometry strings with the original created in interactive alignment (either visually or using reporting tools) or simply check that the results are acceptable.&nbsp; For the vast majority of cases this method proves entirely satisfactory, and provides the advantage that simple changes to the alignment (changing value of an intermediate free curve in VALGN or VERAT, for example) can be made by directly modifying the data, enabling extremely quick iteratation to optimize a design.&nbsp; [Limitation: With this method is not suitable where interactive alignment has been used to store superelevation/cant points, as there is no linemode equivalent, and thus these points will be lost.&nbsp; Use genio&nbsp;data instead]</p> <p>&nbsp;</p> <h1>See Also</h1> <p><a href="/Products/w/Products__Wiki/product-technotes-and-faqs.aspx">Product TechNotes and FAQs</a></p> <p><a href="/Products/Road___Site_Design/w/Road_and_Site_Design__Wiki/mx-technotes-and-faqs.aspx">MX TechNotes And FAQs</a></p> <h1>External Links</h1> <p><a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/">Bentley Technical Support KnowledgeBase</a></p> <p><a title="LEARN Server" href="http://lms.bentley.com">Bentley LEARN Server</a></p> <h1>Comments or Corrections?</h1> <p>Bentley&#39;s Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU!</p> <p>&nbsp;</p> <div class="hr"></div> <p>&nbsp;&nbsp;&nbsp;</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Civil, Data Files, MX, MXURBAN, TechNote, TechNotes</div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/8Thu, 22 Jul 2010 18:50:49 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fElisa McGrawhttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 8 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 7/22/2010 6:50:49 PM<br /> <p><a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"></a>&nbsp;&nbsp;<a href="http://selectservices.bentley.com/en-US"><img height="56" width="175" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" border="0" alt="" /></a> </p> <h1>Document Information</h1> <blockquote> <p><strong>Document Type:</strong> TechNote &nbsp; </p> <p><strong>Product(s):</strong>&nbsp; Bentley MX Products </p> <p><strong>Version(s):</strong>&nbsp; All </p> <p><strong>Original Author:</strong> Bentley Technical Support Group </p> <p><strong>Legacy Document Number:</strong> 8282 </p> </blockquote> <h1>Scope</h1> <p>This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX. </p> <p>&nbsp; </p> <h1>Introduction</h1> <p>Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings. </p> <p>With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option. </p> <p>Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment. </p> <p>&nbsp; </p> <h1>How the files are written</h1> <p>The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that &#39;best fits&#39; the alignment by generating a fixed float, float, float scenario in the resulting data file. </p> <p>Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX. </p> <p>&nbsp; </p> <h1>Data Output accuracy</h1> <p>Because the data output files are a &#39;best fit&#39; of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files. </p> <p>&nbsp; </p> <h1>Recommendations</h1> <p>To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places.&nbsp; </p> <p>To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy. </p> <p>Depending on the length of the alignment and the point interval specified, the genio data for the master string may be very extensive, which in some working methods may prove to be inconvenient. To avoid this, store only only the data for the geometry string, but immediately following the data add an EDIT 029 command to regenerate the master string from the geometry string. </p> <p>A more pragmatic&nbsp;approach&nbsp;- and still the most commonly used - is to generate the HALGN, HCUSP, VALGN, VERAT and VCUSP as required and run the input data file; then compare the resulting master and geometry strings with the original created in interactive alignment (either visually or using reporting tools) or simply check that the results are acceptable.&nbsp; For the vast majority of cases this method proves entirely satisfactory, and provides the advantage that simple changes to the alignment (changing value of an intermediate free curve in VALGN or VERAT, for example) can be made by directly modifying the data, enabling extremely quick iteratation to optimize a design.&nbsp; [Limitation: With this method is not suitable where interactive alignment has been used to store superelevation/cant points, as there is no linemode equivalent, and thus these points will be lost.&nbsp; Use genio&nbsp;data instead] </p> <p>&nbsp; </p> <h1>See Also</h1> <p><a href="/Products/w/Products__Wiki/product-technotes-and-faqs.aspx">Product TechNotes and FAQs</a> </p> <p><a href="/Products/Road___Site_Design/w/Road_and_Site_Design__Wiki/mx-technotes-and-faqs.aspx">MX TechNotes And FAQs</a> </p> <h1>External Links</h1> <p><a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase">Bentley Technical Support KnowledgeBase</a></p> <p><a href="http://lms.bentley.com" title="LEARN Server">Bentley LEARN Server</a> </p> <h1>Comments or Corrections?</h1> <p>Bentley&#39;s Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU! </p> <p>&nbsp; </p> <div class="hr"></div> <p>&nbsp;&nbsp;&nbsp; </p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Civil, Data Files, MX, MXURBAN, TechNote, TechNotes</div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/7Thu, 24 Jun 2010 20:39:15 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fElisa McGrawhttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 7 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 6/24/2010 8:39:15 PM<br /> <p><a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"></a>&nbsp;&nbsp;<a href="http://selectservices.bentley.com/en-US"><img height="80" width="250" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" border="0" alt="" /></a> </p> <h1>Document Information</h1> <blockquote> <p><strong>Document Type:</strong> TechNote &nbsp; </p> <p><strong>Product(s):</strong>&nbsp; Bentley MX Products </p> <p><strong>Version(s):</strong>&nbsp; All </p> <p><strong>Original Author:</strong> Bentley Technical Support Group </p> <p><strong>Legacy Document Number:</strong> 8282 </p> </blockquote> <h1>Scope</h1> <p>This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX. </p> <p>&nbsp; </p> <h1>Introduction</h1> <p>Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings. </p> <p>With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option. </p> <p>Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment. </p> <p>&nbsp; </p> <h1>How the files are written</h1> <p>The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that &#39;best fits&#39; the alignment by generating a fixed float, float, float scenario in the resulting data file. </p> <p>Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX. </p> <p>&nbsp; </p> <h1>Data Output accuracy</h1> <p>Because the data output files are a &#39;best fit&#39; of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files. </p> <p>&nbsp; </p> <h1>Recommendations</h1> <p>To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places.&nbsp; </p> <p>To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy. </p> <p>Depending on the length of the alignment and the point interval specified, the genio data for the master string may be very extensive, which in some working methods may prove to be inconvenient. To avoid this, store only only the data for the geometry string, but immediately following the data add an EDIT 029 command to regenerate the master string from the geometry string. </p> <p>A more pragmatic&nbsp;approach&nbsp;- and still the most commonly used - is to generate the HALGN, HCUSP, VALGN, VERAT and VCUSP as required and run the input data file; then compare the resulting master and geometry strings with the original created in interactive alignment (either visually or using reporting tools) or simply check that the results are acceptable.&nbsp; For the vast majority of cases this method proves entirely satisfactory, and provides the advantage that simple changes to the alignment (changing value of an intermediate free curve in VALGN or VERAT, for example) can be made by directly modifying the data, enabling extremely quick iteratation to optimize a design.&nbsp; [Limitation: With this method is not suitable where interactive alignment has been used to store superelevation/cant points, as there is no linemode equivalent, and thus these points will be lost.&nbsp; Use genio&nbsp;data instead] </p> <p>&nbsp; </p> <h1>See Also</h1> <p><a href="/Products/w/Products__Wiki/product-technotes-and-faqs.aspx">Product TechNotes and FAQs</a> </p> <p><a href="/Products/Road___Site_Design/w/Road_and_Site_Design__Wiki/mx-technotes-and-faqs.aspx">MX TechNotes And FAQs</a> </p> <h1>External Links</h1> <p><a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase">Bentley Technical Support KnowledgeBase</a></p> <p><a href="http://lms.bentley.com" title="LEARN Server">Bentley LEARN Server</a> </p> <h1>Comments or Corrections?</h1> <p>Bentley&#39;s Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU! </p> <p>&nbsp; </p> <div class="hr"></div> <p>&nbsp;&nbsp;&nbsp; </p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Civil, Data Files, MX, MXURBAN, TechNote, TechNotes</div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/6Fri, 15 Jan 2010 08:56:26 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fJonathan Bridgehttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 6 posted to OpenRoads | OpenSite Wiki by Jonathan Bridge on 1/15/2010 8:56:26 AM<br /> <p> <a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"></a>&nbsp;&nbsp;<a href="http://selectservices.bentley.com/en-US"><img src="http://communities.bentley.com/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" border="0" width="250" height="80" /></a> </p> <h1>Document Information</h1> <blockquote> <p> <strong>Document Type:</strong> TechNote &nbsp; </p> <p> <strong>Product(s):</strong>&nbsp; Bentley MX Products </p> <p> <strong>Version(s):</strong>&nbsp; All </p> <p> <strong>Original Author:</strong> Bentley Technical Support Group </p> <p> <strong>Legacy Document Number:</strong> 8282 </p> </blockquote> <h1>Scope</h1> <p> This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX. </p> <p> &nbsp; </p> <h1>Introduction</h1> <p> Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings. </p> <p> With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option. </p> <p> Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment. </p> <p> &nbsp; </p> <h1>How the files are written</h1> <p> The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that 'best fits' the alignment by generating a fixed float, float, float scenario in the resulting data file. </p> <p> Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX. </p> <p> &nbsp; </p> <h1>Data Output accuracy</h1> <p> Because the data output files are a 'best fit' of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files. </p> <p> &nbsp; </p> <h1>Recommendations</h1> <p> To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places.&nbsp; </p> <p> To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy. </p> <p> Depending on the length of the alignment and the point interval specified, the genio data for the master string may be very extensive, which in some working methods may prove to be inconvenient. To avoid this, store only only the data for the geometry string, but immediately following the data add an EDIT 029 command to regenerate the master string from the geometry string. </p> <p> A more pragmatic&nbsp;approach&nbsp;- and still the most commonly used - is to generate the HALGN, HCUSP, VALGN, VERAT and VCUSP as required and run the input data file; then compare the resulting master and geometry strings with the original created in interactive alignment (either visually or using reporting tools) or simply check that the results are acceptable.&nbsp; For the vast majority of cases this method proves entirely satisfactory, and provides the advantage that simple changes to the alignment (changing value of an intermediate free curve in VALGN or VERAT, for example) can be made by directly modifying the data, enabling extremely quick iteratation to optimize a design.&nbsp; [Limitation: With this method is not suitable where interactive alignment has been used to store superelevation/cant points, as there is no linemode equivalent, and thus these points will be lost.&nbsp; Use genio&nbsp;data instead] </p> <p> &nbsp; </p> <h1>See Also</h1> <p> <a href="/Products/w/Products__Wiki/product-technotes-and-faqs.aspx">Product TechNotes and FAQs</a> </p> <p> <a href="/Products/Road___Site_Design/w/Road_and_Site_Design__Wiki/mx-technotes-and-faqs.aspx">MX TechNotes And FAQs</a> </p> <h1>External Links</h1><a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase">Bentley Technical Support KnowledgeBase</a> <p> <a href="http://lms.bentley.com" title="LEARN Server">Bentley LEARN Server</a> </p> <h1>Comments or Corrections?</h1> <p> Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU! </p> <p> &nbsp; </p> <div class="hr"> </div> <p> &nbsp;&nbsp;&nbsp; </p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Civil, Data Files, MX, MXURBAN, TechNote, TechNotes</div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/5Fri, 15 Jan 2010 08:53:54 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fJonathan Bridgehttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 5 posted to OpenRoads | OpenSite Wiki by Jonathan Bridge on 1/15/2010 8:53:54 AM<br /> <p> <a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"></a>&nbsp;&nbsp;<a href="http://selectservices.bentley.com/en-US"><img src="http://communities.bentley.com/files/storage/363/17560/TSG%20Logo.bmp" border="0" width="250" height="80" /></a> </p> <h1>Document Information</h1> <blockquote> <p> <strong>Document Type:</strong> TechNote &nbsp; </p> <p> <strong>Product(s):</strong>&nbsp; Bentley MX Products </p> <p> <strong>Version(s):</strong>&nbsp; All </p> <p> <strong>Original Author:</strong> Bentley Technical Support Group </p> <p> <strong>Legacy Document Number:</strong> 8282 </p> </blockquote> <h1>Scope</h1> <p> This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX. </p> <p> &nbsp; </p> <h1>Introduction</h1> <p> Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings. </p> <p> With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option. </p> <p> Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment. </p> <p> &nbsp; </p> <h1>How the files are written</h1> <p> The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that 'best fits' the alignment by generating a fixed float, float, float scenario in the resulting data file. </p> <p> Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX. </p> <p> &nbsp; </p> <h1>Data Output accuracy</h1> <p> Because the data output files are a 'best fit' of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files. </p> <p> &nbsp; </p> <h1>Recommendations</h1> <p> To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places.&nbsp; </p> <p> To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy. </p> <p> Depending on the length of the alignment and the point interval specified, the genio data for the master string may be very extensive, which in some working methods may prove to be inconvenient. To avoid this, store only only the data for the geometry string, but immediately following the data add an EDIT 029 command to regenerate the master string from the geometry string. </p> <p> A more pragmatic&nbsp;approach&nbsp;is to generate the HALGN, HCUSP, VALGN, VERAT and VCUSP as required; then run the input data file; then compare the resulting master and geometry strings with the original created in interactive alignment (there are a number of ways this can be done) or simply check that the results are acceptable.&nbsp; For the vast majority of cases this method proves entirely satisfactory, and provides the advantage that simple changes to the alignment (changing value of an intermediate free curve in VALGN or VERAT, for example) can often be made by directly modifying the data, enabling extremely quick iteratation to optimize a design.&nbsp; [Limitation: With this method is not suitable where interactive alignment has been used to store superelevation/cant points, as there is no linemode equivalent, and thus these points will be lost.&nbsp; Use genio&nbsp;data instead] </p> <h1>See Also</h1> <p> [[Product TechNotes and FAQs]] </p> <p> [[MX TechNotes And FAQs]] </p> <h1>External Links</h1><a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase">Bentley Technical Support KnowledgeBase</a> <p> <a href="http://lms.bentley.com" title="LEARN Server">Bentley LEARN Server</a> </p> <h1>Comments or Corrections?</h1> <p> Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU! </p> <p> &nbsp; </p> <div class="hr"> </div> <p> &nbsp;&nbsp;&nbsp; </p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: <tags></tags></div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/4Tue, 04 Nov 2008 18:30:39 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fElisa McGrawhttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 4 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 11/4/2008 6:30:39 PM<br /> <p> <a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"></a>&nbsp;&nbsp;<a href="http://selectservices.bentley.com/en-US"><img src="http://communities.bentley.com/files/storage/363/17560/TSG%20Logo.bmp" border="0" width="250" height="80" /></a> </p> <h1>Document Information</h1> <blockquote> <p> <strong>Document Type:</strong> TechNote &nbsp; </p> <p> <strong>Product(s):</strong>&nbsp; Bentley MX Products </p> <p> <strong>Version(s):</strong>&nbsp; All </p> <p> <strong>Original Author:</strong> Bentley Technical Support Group </p> <p> <strong>Legacy Document Number:</strong> 8282 </p> </blockquote> <h1>Scope</h1> <p> This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX. </p> <p> &nbsp; </p> <h1>Introduction</h1> <p> Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings. </p> <p> With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option. </p> <p> Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment. </p> <p> &nbsp; </p> <h1>How the files are written</h1> <p> The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that 'best fits' the alignment by generating a fixed float, float, float scenario in the resulting data file. </p> <p> Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX. </p> <p> &nbsp; </p> <h1>Data Output accuracy</h1> <p> Because the data output files are a 'best fit' of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files. </p> <p> &nbsp; </p> <h1>Recommendations</h1> <p> To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places. </p> <p> To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy. </p> <h1>See Also</h1> <p> [[Product TechNotes and FAQs]] </p> <p> [[MX TechNotes And FAQs]] </p> <h1>External Links</h1><a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase">Bentley Technical Support KnowledgeBase</a> <p> <a href="http://lms.bentley.com" title="LEARN Server">Bentley LEARN Server</a> </p> <h1>Comments or Corrections?</h1> <p> Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU! </p> <p> &nbsp; </p> <div class="hr"> </div> <p> &nbsp; &nbsp; </p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: <tags></tags></div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/3Thu, 30 Oct 2008 13:44:36 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fElisa McGrawhttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 3 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 10/30/2008 1:44:36 PM<br /> <p> <a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"></a>&nbsp;&nbsp;<a href="http://selectservices.bentley.com/en-US"><img src="http://communities.bentley.com/files/storage/363/17560/TSG%20Logo.bmp" border="0" width="250" height="80" /></a> </p> <h1>Document Information</h1> <blockquote> <p> <strong>Document Type:</strong> TechNote &nbsp; </p> <p> <strong>Product(s):</strong>&nbsp; Bentley MX Products </p> <p> <strong>Version(s):</strong>&nbsp; All </p> <p> <strong>Original Author:</strong> Bentley Technical Support Group </p> </blockquote> <h1>Scope</h1> <p> This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX. </p> <p> &nbsp; </p> <h1><strong>Introduction</strong></h1> <p> Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings. </p> <p> With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option. </p> <p> Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment. </p> <p> &nbsp; </p> <h1><strong>How the files are written</strong></h1> <p> The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that 'best fits' the alignment by generating a fixed float, float, float scenario in the resulting data file. </p> <p> Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX. </p> <p> &nbsp; </p> <h1><strong>Data Output accuracy</strong></h1> <p> Because the data output files are a 'best fit' of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files. </p> <p> &nbsp; </p> <h1><strong>Recommendations</strong></h1> <p> To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places. </p> <p> To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy. </p> <h1>See Also</h1> <p> [[Product TechNotes and FAQs]] </p> <p> [[MX TechNotes And FAQs]] </p> <h1>External Links</h1><a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase">Bentley Technical Support KnowledgeBase</a> <p> <a href="http://lms.bentley.com" title="LEARN Server">Bentley LEARN Server</a> </p> <h1>Comments or Corrections?</h1> <p> Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU! </p> <p> &nbsp; </p> <div class="hr"> </div> <p> &nbsp; &nbsp; </p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: <tags></tags></div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/2Tue, 21 Oct 2008 21:20:59 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fElisa McGrawhttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 2 posted to OpenRoads | OpenSite Wiki by Elisa McGraw on 10/21/2008 9:20:59 PM<br /> <p> <a href="http://selectservices.bentley.com/en-US/" target="_blank"><img src="/photos/select_server_under_construction-gallery/images/10802/500x159.aspx" border="0" alt="Bentley Technical Support Group" title="Bentley Technical Support Group" width="250" /></a> </p> <h1>Document Information</h1> <blockquote> <p> <strong>Document Type:</strong> TechNote &nbsp; </p> <p> <strong>Product(s):</strong>&nbsp; Bentley MX Products </p> <p> <strong>Version(s):</strong>&nbsp; All </p> <p> <strong>Original Author:</strong> Bentley Technical Support Group </p> </blockquote> <h1>Scope</h1> <p> <strong> </strong>This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX. </p> <p> &nbsp; </p> <h1><strong>Introduction</strong></h1> <p> <strong> </strong>Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings. </p> <p> With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option. </p> <p> Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment. </p> <p> &nbsp; </p> <h1><strong>How the files are written</strong></h1> <p> <strong> </strong>The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that 'best fits' the alignment by generating a fixed float, float, float scenario in the resulting data file. </p> <p> Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX. </p> <p> &nbsp; </p> <h1><strong>Data Output accuracy</strong></h1> <p> <strong> </strong>Because the data output files are a 'best fit' of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files. </p> <p> &nbsp; </p> <h1><strong>Recommendations</strong></h1> <p> <strong> </strong>To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places. </p> <p> To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy. </p> <h1>See Also</h1> <p> [[Product TechNotes and FAQs]] </p> <p> [[MX TechNotes And FAQs]] </p> <h1>External Links</h1><a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase">Bentley Technical Support KnowledgeBase</a> <p> <a href="http://lms.bentley.com" title="LEARN Server">Bentley LEARN Server</a> </p> <h1>Comments or Corrections?</h1> <p> Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this &quot;Comments or Corrections?&quot; section. THANK YOU! </p> <p> &nbsp; </p> <div class="hr"> </div> <p> &nbsp; &nbsp; </p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: <tags></tags></div> https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177/revision/1Tue, 01 Jul 2008 08:24:57 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3bacf97c-00ca-4831-9502-c9eb40a3677fDave Bentleyhttps://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/3177/3177#commentsRevision 1 posted to OpenRoads | OpenSite Wiki by Dave Bentley on 7/1/2008 8:24:57 AM<br /> <table border="0" cellspacing="0" cellpadding="2" width="631" id="Table7"> <tbody> <tr> <td width="150" valign="top"><strong>Product:</strong></td> <td>Bentley MX </td> </tr> <tr> <td width="150" valign="top"><strong>Date Added:</strong></td> <td>July 1, 2008</td> </tr> </tbody> </table> &nbsp; <p> <strong>Scope<br /> </strong>This paper applies to the creation of Alignment data output files from the Interactive Alignment options within MX. </p> <p> <strong>Introduction<br /> </strong>Prior to the creation of the Interactive Alignment options; Major options HALGN, HCUSP, VALGN, VERAT and VCUSP were used to generate design alignments. These were ASCII files that allowed geometry definition and when processed by MOSS (MX) they created Master and Geometry Strings. </p> <p> With the evolution of interactive graphics there was a demand to be able to design alignments graphically and hence the creation of the Interactive Alignment option. </p> <p> Since the creation of Interactive Alignment in 1990, users have been able to regenerate the alignments generated in Interactive Alignment by outputting an ASCII file from within Interactive Alignment. This creates a copy of the alignment in HALGN, VALGN and VERAT format to be used as a backup copy of their alignment. </p> <p> <strong>How the files are written<br /> </strong>The HALGN, VALGN and VERAT files analyze the completed alignment created in the Interactive Alignment option and then create a data file that 'best fits' the alignment by generating a fixed float, float, float scenario in the resulting data file. </p> <p> Historically users have used these files as backup copies of their alignments so that they can create their entire design with a series of input files. Those users with experience of how the HALGN, VALGN and VERAT files are coded can also use them to make minor amendments to the geometry of the alignment and then re input the file to update the Master and Geometry string in MX. </p> <p> <strong>Data Output accuracy<br /> </strong>Because the data output files are a 'best fit' of the alignments generated in Interactive Alignment and they often cannot be stored to a sufficient accuracy in the data file, different iteration calculations can be made when the data output files are re-input into MX. This can lead to small discrepancies in the data between the original alignment and that generated by the data output files. </p> <p> <strong>Recommendations<br /> </strong>To create a true and accurate record of a master and geometry string created in Interactive Alignment users must make a GENIO file record of the alignment. This will store the alignment to double precision i.e. to 17 decimal places. </p> <p> To enable users to do this an option to generate a GENIO file at the data output stage in Interactive Alignment will be created at MX V2.5. This GENIO data file can subsequently be input into MX with other input files to recreate the entire design. If a user wants to amend a previously created alignment this must be done with the editing tools within Interactive Alignment to maintain alignment accuracy. </p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: <tags></tags></div>