Documente Academic
Documente Profesional
Documente Cultură
Best Practices
1
3/28/2014
Learning Objectives
Notes
• This guide is equally applicable for the MX, InRoads or
GEOPAK families of products.
• Utilizing OpenRoads technology, each product contains
the identical Bentley Civil toolset and identical workflow.
• However, the transitioning tasks may vary, so the
differences will be identified.
2
3/28/2014
Disclaimer
• Keep in mind that there is no ONE best practice.
• This presentation and associated guide presents
suggestions and best practices and it is the
responsibility of each organization to determine how the
Best Practices fits into your standard policies,
procedures and operations.
http://www.bentley.com/en-US/Promo/OpenRoads/OpenRoads+Technology+Resources.htm
3
3/28/2014
4
3/28/2014
2D or 3D?
Geometry Files
Best Practice Recommendations:
5
3/28/2014
Terrain Files
Best Practice Recommendations:
Survey Files
Best Practice Recommendations:
6
3/28/2014
2D and 3D Summary
7
3/28/2014
Reference Files
P
l
a
n
i
m
e
t
r
Terrain Models
i
c
s 3-D
3 D Models
Survey
Superelevation
8
3/28/2014
Workflow
• Just Reference the data you need.
• It is all file management
• The way you break files up depends on:
• Your organization
• The Project
• The amount of interactive change you want
Example #1
Alignment
Terrain
e a Topo
opo
#1
Alignment Alignment
#2 #3
9
3/28/2014
Example #2
Terrain Topo
p Alignments
g
Cross
Superelevation Corridors
Sections
Example #3
Superelevation Superelevation
Alignment #1 Alignment #2
#1 #2
10
3/28/2014
Limitations of References
11
3/28/2014
Reference Files
W k
Workspaces and
d
Resources
12
3/28/2014
• Bentley-Civil-Imperial
• Bentley-Civil-Metric
Bentley--Civil
Bentley Civil--Imperial
• Power Geopak
– C:\ProgramData\Bentley\PowerGEOPAK V8i (SELECTseries
3)\WorkSpace\Projects\Examples\Bentley-Civil-Imperial
• MicroStation
– C:\ProgramData\Bentley\MicroStation V8i
(SELECTseries)\WorkSpace\Projects\Examples\Bentley-Civil-
Imperial
• Common Standards
– C:\ProgramData\Bentley\Civil\Standards\8.11.9\en
13
3/28/2014
Civil Geometry
GPK
ALG
FIL
Importing Geometry
Limitations:
• Can
Can’tt import extremely complex geometry
geometry.
• Complex geometry may not be “ruled.”
• Can’t bring in profile only (must be associated with a chain).
• Can only import within a product.
14
3/28/2014
Exporting Geometry
• Manual or automatic
• Review what is exported
– Centerlines and Baselines
– Right of Way when needed for plats, parcels and other geometry
layouts
– Survey data needed for the GEOPAK export to drainage application
– Data needed for staking when using GEOPAK as the native
application
application.
ADVANTAGES DISADVANTAGES
Auto Export No additional steps are Inexperienced user create
required. unintended changes in the native
Process is fairly invisible to the database.
user. Not design file specific. Elements
Supports horizontal station p files react to
in copied
annotation. persistence.
Always “in sync”
15
3/28/2014
Native Databases:
XIN
DDB, SMD
PSS
Native Databases
Best Practice Recommendations:
• Exercise patience
patience, as there’s
there s more work to come
come…
• Link to your native database, watching for duplicate
names.
• Augment as needed for new features or items that are
currently not supported within the databases.
• Start with a few element templates and expand as
needed during test / pre-deployment.
16
3/28/2014
Element Templates
+ More capability than styles (i.e., material assignments)
+ Access to text styles
17
3/28/2014
Seed Files
Seed File Suggested Considerations…
• Set DGN File Civil Settings appropriately
• Set Default Drawing Scale
• Set default Snap Divisor to 1
• Turn off clip volume for all views in view attributes
• Delete unused fonts in keyin field
• Set default text style
• Attach
ttac de
default
au t ce
cell library
bay
• GEOPAK must change Civil Settings Station Equation to “By
Region” for auto annotate to function properly
• Turn off Camera View Attribute in 3D seed files
• Set GCS
36 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated
18
3/28/2014
• DGN files based on different GCS (where the GCS is defined within the
file) can be referenced and re-projected on-the-fly so the data is in sync.
• Interface with Google Earth and other widely available data regardless
of the source data GCS.
• MicroStation interface with GPS devices
devices.
• Created objects without additional steps needed for transformation /
reprojection.
19
3/28/2014
Material Assignments
• Material Assignments
20
3/28/2014
Material Assignments
21
3/28/2014
22