Best Practice: How to Move Project Data from

Best Practice: How to Move Project Data
from SELECTseries 2 to SELECTseries 3
Presented by: Joe Waxmonsky PE, Bentley Civil
© 2014 Bentley Systems, Incorporated
Best Practice: How to Move
Project Data from SELECTseries 2
to SELECTseries 3
2 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Agenda
• File Types/Compatibility between SS2 and SS3
• Considerations
• Demo
3 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
4 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
5 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
The Preference Files
• DDB, PSS, and XIN are the Same Formats in OpenRoads
Environment
• Required in SELECTseries 3
• Dictates Drafting
– How it looks
– How is it annotated
6 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
“Link” from OpenRoads
• Create Feature Definition via Active XIN, PSS, & DDB File
• Creates an actual link back to the XIN, PSS, or DDB file
7 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Links
8 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
SS3 Tools that Access the XIN for Settings
• Create Cross Sections
• Annotate Cross Sections
• End Area Volumes & Mass Haul
• Cross Section Viewer
**All SS3 Products
9 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Best Practice
• Linking to your legacy style files is intended to be a ‘starting
point’ to help you get your feature definitions created
quickly.
Best practice is to do this once.
After the initial linking has been done, any structural
changes to the feature definition tree (new features,
renaming of features, etc.) should be made directly in the
DGN Lib.
Note: An exception would be changes to symbology or
annotation, which would be made in the legacy style file.
10 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
DGNLIB
“DGNlibs, they are your friend, it
the only way I can describe it”
11 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
What is no longer controlled by the XIN/DDB?
• Component Style(SS2) =Component Feature Definition(SS3)
12 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Creating Element Templates via
Export/Import
13 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Levels to Element Templates
• Added MVBA to convert levels to Element Templates by
creating a XML file.
– Manual Key-in Only
• C:\ProgramData\Bentley\PowerInRoads V8i (SELECTseries
3)\WorkSpace\Projects\Examples\Bentley-CivilMetric\dgnlib\SaveLevelsToElementTemplateXML.mvba
– Makes Proper Format XML file to import to Element Templates
– Level Name becomes Element Template Name
– All other settings are set to bylevel
14 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
The GPK/ALG/FIL Files
• Format is Unchanged
• Import to OpenRoads
– Supports only Clothoid Transitions
• Export from OpenRoads
15 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Auto Annotate
• If set to True, then the horizontal geometry element will be
annotated immediately whenever it is created or modified.
• If set to False, then annotation would not occur.
• Note: You MUST use a Native Style in order to produce
annotation, as the specifications for the annotation are based on
the native feature style.
16 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Auto Export
• If set to True, then any geometry elements created using
this feature will be automatically exported to the
appropriate legacy coordinate geometry database (FIL,
ALG, GPK).
• If set to False, then this export would not occur.
ALG
FIL
GPK
17 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
The TIN, Model, & DTM File
• Same Formats
• Import to a Terrain Model
– No Components
– No Features****
• Export to Terrain Model
– No Components
18 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
.ITL File
• Same Format
• Additions & Changes
– Removed Vertical Styles Constraints
– Superelevation Flags
– Naming
• Styles = Feature Definition
• Targets Renamed
19 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
IRD File
20 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Import Corridor from IRD File
21 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Import Corridor from IRD File
• Only one corridor at a time can be imported.
• An imported corridor’s baseline horizontal and profile
geometry must already exist in the design file or an attached
reference file.
• Imported corridors will always target the active terrain model,
but corridors may be imported without an active Terrain
Model.
• Superelevation point controls will be imported.
22 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Import Corridor from IRD File
• A corridor’s missing dependencies will be reported at the
time of import. The import can then be canceled or
continued without missing dependencies.
• Corridor objects that are missing a dependency will not be
imported.
– For example, if a point control is a corridor feature point control, the
corridor and the corridor feature must already exist. If they do not,
the point control will not be imported.
• In order for a Target Alias to be imported at least one of it’s
dependencies must exist in the design model. Missing
aliases will not be imported.
23 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Extra Notes
• All dependencies will be matched by name with objects in the
design model.
• When importing secondary alignments, the .alg that contains
the secondary alignment geometry must reside in the same
directory as the .ird.
24 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Consideration
• All Corridors do not need to be one DGN
• Referencing is KEY for BIG DATA
• Remember Dependencies within IRD
– Target Aliasing
– Corridor Point Controls
• Clipping Established after Import
• Style Constraints are “Heavy”
– Reference to Corridor after Import
• Feature Point Controls are not supported.
25 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Demo…
26 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
XSL IRD Dependency Report
• https://communities.bentley.com/products/road___site_desig
n/w/road_and_site_design__wiki/13636.report-on-corridordependencies-from-ird-file-before-running-import-irdcommand.aspx
27 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
Best Practice: How to Move
Project Data from SELECTseries 2
to SELECTseries 3
[email protected]
28 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Download Report