1 / 30

Terramodel Version 10.60

Terramodel Version 10.60. Please view in slide show mode !. Introduction to Updated Features. Information Sources. Customers www.trimble.com website Dealers www.trimble.com Products A-Z, Terramodel Construction Partners Trimble Connected Community Trimble SPS Site – Resources tab.

trina
Télécharger la présentation

Terramodel Version 10.60

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. TerramodelVersion 10.60 Please view in slide show mode !

  2. Introduction to Updated Features

  3. Information Sources • Customers • www.trimble.com website • Dealers • www.trimble.com • Products A-Z, Terramodel • Construction Partners • Trimble Connected Community • Trimble SPS Site – Resources tab

  4. Additional Informational Resources • Release Notes • The release notes can be found in English athttp://www.trimble.com/terramodel_ts.asp?Nav=Collection-19852 • Product Bulletin • A product bulletin is available on Partners athttp://constructionpartners.trimble.com/frame.asp?Page=/GetFile.asp?File=File-380296/newsletter.htm

  5. Main Focus Areas for v10.60 • The primary focus of the Terramodel v10.60 release is to continue to enhance the road modeling capabilities of the software and further develop the interface with SCS900 for site measurement and stakeout operations. • This release follows on from the development of the Road Job Workflow Guide in Terramodel v10.50 • The benefits of this development are • Users can now quickly and easily build road models and output accurate surface models (complete with linework) of road finished grade and subgrade surfaces • Surfaces can be visualized in 3D and contoured to check for surface integrity • Traditional surface to surface volumes can be carried out • Accurate surfaces with guidance linework can be quickly passed into GCS900 for grade control operations or to SCS900 for site positioning operations. • Complex ramps and interchanges can be modeled more rapidly and more accurately using the new commands.

  6. RoadDTM CommandEnhancements

  7. An Approximation of Terramodel’s Parametric Roadway Model • The RoadDTM command is used to create a DTM surface representation of a Terramodel road job • The road job is a parametric roadway model, which can exactly define the finished surface and subgrade surfaces at any location along the road • The surface created by the RoadDTM command is an approximation of a particular portion of that parametric roadway model • It may represent the finished surface or a particular subgrade

  8. The DTM Surface’s Character • The DTM surface is composed of discrete points and connecting breaklines • The points are formed in a cross-sectionally oriented manner • Roadway features, such as the edge of pavement, are represented by straight breakline segments connecting the appropriate points on adjacent cross-sections • The breaklines only approximate the true geometry of the feature that they represent • The accuracy of that approximation depends on the frequency with which those data points are spaced and on the curvilinearity of the roadway • The objective is to achieve a sufficiently accurate approximation, without generating a model that is unnecessarily dense, and perhaps too large to function well

  9. Uses for the DTM Surface • Some of the more common reasons to form the DTM surface approximation of a roadway are… • To facilitate the generation of contours • To perform 3D visualization of the roadway • To enable the creation of cut/fill maps • To create accurate models at ramps and interchanges • Additionally, some GCS900 and SCS900 users may elect to employ the DTM surface for grading and staking operations, as opposed to using the parametric road job • These operations typically require assurance that the inherent approximations are accurate enough to suffice in meeting their needs • The new enhancements help address that need

  10. Breakline Approximation Tolerance-Based DTM Optimization • Helps assure that breakline approximations of roadway features do not, at any location, deviate from the true feature by a dimension in excess of a user specified tolerance • Eliminates user responsibility for creating xlines everywhere that surface data is desired • Automatically determines cross-section placement • Varies the spacing of cross-sections depending on the degree of curvilinearity of the alignment • Considers both horizontal and vertical curvature as well as widening and superelevation. • Picks up some key roadway feature transition points • Continues to create data on cross-sections indicated by user placed xlines, if present.

  11. Example – Curves in HAL & VAL • In this plan view example, the cross-section spacing is influenced by both horizontal and vertical curves, as well as superelevation transitions and daylight line formation • The cross-sections can be seen to be more closely spaced as the spiral curve tightens • They tend to be more equally spaced along the arc • The cross-sections found within the tangent section are the result of vertical curves, superelevation transitions and daylight line formation

  12. Example – Curves in HAL Only • In this example, the road’s vertical alignment is a horizontal line with no curves • The spacing of cross-sections in the model is influenced only by the horizontal arc and spirals • Note the variable spacing as the spirals tighten • Note the constant spacing along the arc • Note the absence of cross-sections within the tangents • Note the cross-sections at the TS, SC, CS and ST points • This represents the minimum amount of data needed to achieve the specified breakline approximation tolerance

  13. Example – Curves in VAL Only • In this example, the road’s horizontal alignment is a straight line • The spacing of cross-sections in this surface model is influenced only by a parabolic vertical curve and by the formation of the daylight line

  14. How do they do it? • So, after considering these simplified examples, an explanation is in order as to how these results are achieved • Actually it is quite simple and intuitive • The changes to the user interface also provide the user with considerable flexibility

  15. User Interface Changes • The controls shown above have been added to the Road DTM Settings dialog box • You can specify that DTM cross-sections be computed at xlines that you have created and/or at a specified interval • If you elect to specify an interval, you can then opt to thin the cross-sections based on a tolerance • That tolerance indicates the maximum dimension at which the breakline approximation of a roadway feature can deviate from the true alignment of that feature • In this example the user has designated that cross-sections be computed at 1 foot intervals, but then that their numbers be thinned with the condition that every feature’s breakline not deviate more than 0.02 feet from the actual feature

  16. The Initial Pass • Based on those settings, Terramodel will initially create a surface with cross-sectional data located… • At every xline that you have created • At key transitional points on every feature • At every 1 foot interval along the road • That would be quite a dense surface model • So, Terramodel will then eliminate cross-sections that are unnecessary in maintaining the specified tolerance • That process is referred to as thinning computed cross-sections

  17. Thinning Cross-Sections • A second pass will evaluate each cross-section that was generated based on the specified interval • If, as a result of deleting that cross-section, the breakline approximation of every roadway feature in that region is found to be within the stated tolerance, the cross-section is deleted and that same test is then applied to the next cross-section • One by one, cross-sections are deleted until one of the approximated roadway features fails to meet the tolerance, at which point that cross-section is reinstated • The evaluation then resumes with the next cross-section • The result is that only enough of the incidental cross-sections are retained, as needed to achieve the specified breakline approximation accuracy tolerance • Cross-sections based on xlines or feature transitional points are not deleted in the thinning process

  18. Cross-Section Thinning Caveats • Note that the process employed is described as “thinning computed cross-sections” • In establishing the interval, it must be small enough to achieve the specified tolerance everywhere • If it is not, cross-sections will not be deleted, but they will not be added either • The objective is to liberally specify an interval that is certainly small enough to achieve the tolerance, and then let Terramodel discard the data that is not needed

  19. Former Settings Retained • In the preceding examples, breaklines were formed across the cross-section points • Doing so suited the discussion in which we were looking at the locations of the cross-section oriented data points • You can still of course form the model with breaklines only along the roadway features, as in this example • The resulting graphics can effectively be used to form an SCS900 background map, making the roadway features evident when the design is based on a road job

  20. SCS900 Integration

  21. 2D and 3D Alignment Staking • SCS900 v2.42 currently supports designs containing Terramodel project files that contain one or more road jobs (parametric roadway models). • The main alignment associated with a road job can contain a horizontal alignment and one or more vertical alignments, as required to accommodate roads • Terramodel provides tools to create an SCS900 design containing such a roadway model • The road job provides a mechanism in which complex 3D alignments can be defined and sent to SCS900 as a part of a roadway model • Now, at version 10.60, Terramodel can prepare an SCS900 design in the form of a road job containing an alignment alone • That capability provides a means of sending a complex alignment to SCS900, even if it does not actually represent a roadway, as there is no longer a need for the road job to contain data other than the alignment

  22. SCS900 Alignment Only Staking • HAL only • User can specify Station, Offset and define an absolute elevation (if required) to stakeout • HAL / VAL only • User can specify a Station and Offset to stakeout along with • A vertical difference to the computed Z at the VAL • An absolute elevation value • A cross slope % or ratio that computes Z at the offset location • User can also stake a road sideslope from a computed station, offset and defined elevation location in cases where a complete cross section is not available.

  23. Road Jobs with Alignments Only • A road job can be created with nothing more than a horizontal alignment (HAL) • That enables you to send a 2D alignment to SCS900 that has established stationing, optional station equations, and which can support spiral curves • The road job can contain a 3D alignment, consisting of a HAL and a vertical alignment (VAL) • That 3D alignment can therefore employ parabolic vertical curves • A road job containing only a 2D alignment might be used to stake out in preparation for clearing and grubbing operations • A road job might be used to represent the 3D alignment of a pipeline or a railway

  24. Road Jobs with Alignments Only • This feature exploits SCS900’s current support for the Terramodel road job, in order to accommodate alignment properties & geometric features that cannot be represented within a DXF file • The DXF file format does not support named objects, spiral or parabolic curves, stationing, or station equations • Both Terramodel v10.60 and Trimble Business Center – Heavy Construction Edition v1.20 can now create SCS900 designs of this nature

  25. OmniStar Control Points • SCS900 can now properly distinguish between a typical control point file and a special OmniStar control point file • Both files are located in the site folder within the SCS900 synchronizer folder structure • Both employ a filename extension of .csv • Terramodel now enables you to create or update a control points file for a site, when it already contains one related to OmniStar control points

  26. Alignment Dependent Surfaces • Version 1.20 of the Trimble Business Center – Heavy Construction Edition (TBC-HCE) software provides for the optional formation of surfaces that are dependent on an alignment object • The surfaces are triangulated in a manner that is more consistent with normal expectations associated with roadway surfaces • Without going into detail here, the effect of this option is illustrated in the following slide, taken from a similar introduction to TBC-HCE v1.20

  27. Example Surface Wireframes Normally Linked Surface Comparison Alignment Dependent Surface

  28. Alignment Dependent Surfaces • That topic is addressed in more detail within the above noted introductory presentation entitled:Introduction - Trimble Business Center-HCE - v1.20.ppt • It can be found at :http://www.trimble.com/tbc-hce_ts.asp?Nav=Collection-51339

  29. Implications for Terramodel Users • Terramodel does not support the creation of alignment dependent surfaces • However, when such a surface is created in TBC-HCE and associated with a roadway alignment as part of an SCS900 design. . . • The Terramodel project file that is employed on the site controller will accommodate the intended surface linking • The resulting surface used in the field will match that found within TBC-HCE • The road job as viewed from within roadway model editors will correctly reflect the alignment based surface • Terramodel users may need to recognize that this circumstance is addressed by placing the surface data within Terramodel’s view 8, where the coordinates are station and offset based • However, there are no supported operations enabling Terramodel itself to work with that data, such as viewing the surface in plan or 3D view, generating contours, etc.

  30. Questions / Discussion

More Related