• Author / Uploaded
• Santosh Rai

Citation preview

3/28/2014

OpenRoads Best Practices Bob Rolle, Civil Application Engineer © 2014 Bentley Systems, Incorporated

Best Practices • This presentation teaches many of the best practices discovered by the Bentley team during the Open Roads d l development, t bbeta t program andd th the llastt year off use. For F allll Bentley Civil users.

2 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

1

3/28/2014

Learning Objectives After this session you will be able: • use the best practice for the use of reference files in various types of projects. • select the most appropriate file type (2D or 3D) for various components. • understand the general use of native databases moving f forward d iin SELECT series i 3

3 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

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.

4 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

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.

5 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Best Practices Documentation

http://www.bentley.com/en-US/Promo/OpenRoads/OpenRoads+Technology+Resources.htm

6 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

3

3/28/2014

7 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

8 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

4

3/28/2014

2D or 3D?

9 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Geometry Files Best Practice Recommendations: .

• Store horizontal geometry in 2-D DGN models. • Name your profiles based on rules from native products.

10 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

5

3/28/2014

Terrain Files Best Practice Recommendations: .

Store terrains in 3-D DGN models. If stored in 2-D model, a 3-D model is automatically created.

11 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Survey Files Best Practice Recommendations: .

• Store survey data in 3-D DGN models. • Flatten if needed for 2-D downstream uses.

12 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

6

3/28/2014

Corridor Modeling Files Best Practice Recommendations: Start with 2D Model. . •

Modeling creates both 2D and 3D elements

•

Isolate the 2D elements from 3D elements; separation makes easier picking of elements / components

13 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

2D and 3D Summary

14 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

7

3/28/2014

Reference Files

15 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

DGN Based Objects P l a n i m e t r i c s

Geometry

Terrain Models 3-D 3 D Models Survey

Superelevation 16 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

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

17 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Example #1

Terrain e a

Topo opo

Alignment #2

Alignment #1

Alignment #3

• Alignment files include: Alignments, Super, corridors, etc.

18 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

9

3/28/2014

Example #2 Terrain

Topo p

Alignments g

Superelevation

Corridors

Cross Sections

• Alignment files include: Alignments, Super, corridors, etc.

19 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Example #3 Terrain #1

Terrain #2

Topo #1

Topo #2

Alignment #1

Alignment #2

Superelevation #1

Superelevation #2

Corridor #1

Corridor #2

Cross Section #1

Cross Section #2

• Everything is broken up into individual files

20 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

10

3/28/2014

Do I Have to Use Reference Files? • No, reference files are NOT required. – Simple project. – Preservation / rehabilitation projects. – Individual designer or very small work team. – Utilize models within a single file in lieu of referencing separate files.

• Base reference file usage on workflow / workteams, rather than size of project. • Excellent to provide granularity to projects.

21 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Limitations of References • Profiles must reside in same file as associated geometry • Supers can be in their own file and referenced to corridor corridor, but assignment must be from corridor file. • Edit handlers / manipulators only available in active file. – Activate – Exchange

22 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

11

3/28/2014

Reference Files Best Practice Recommendations: – Separate geometry for working with large work teams. – Separate corridors into areas of interest. – Use an all_geometry.dgn, all_corridor.dgn, etc. so users don’t have to search to find data. – Be “Nesting” aware to capture wanted data, but not duplicates of data. – Attach by relative paths so folders can be moved. – Careful when detaching as you may leave orphan objects.

23 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

W k Workspaces and d Resources

24 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

12

3/28/2014

Delivered Civil Workspaces • Bentley-Civil-Imperial • Bentley-Civil-Metric

25 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

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-CivilImperial

• Common Standards – C:\ProgramData\Bentley\Civil\Standards\8.11.9\en

26 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

13

3/28/2014

Civil Geometry GPK ALG FIL

27 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

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.

28 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

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.

• Keep in mind limitations in native products, i.e., naming of elements. 29 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

ADVANTAGES Auto Export No additional steps are required. Process is fairly invisible to the user. Supports horizontal station annotation. Always “in sync” Manual Export

Choose exactly which elements are exported Does not depend on feature setting.

DISADVANTAGES Inexperienced user create unintended changes in the native database. Not design file specific. Elements p files react to in copied persistence.

Requires extra step to export. Snap-shot in time; subsequent changes h require i an additional dditi l export. Auto annotation is not supported.

30 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

15

3/28/2014

Native Databases: XIN DDB, SMD PSS

31 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

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.

32 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

16

3/28/2014

Element Templates

+ +

More capability than styles (i.e., material assignments)

-

Can’t handle stationing and other specialized annotation

Access to text styles

Can’tt handle quantities / pay item data Can

33 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Create Element Templates Best Practice Recommendations:

34 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

17

3/28/2014

Changes in Native Databases Best Practices Recommendations: Do NOT delete feature definitions and start over. Just link again •

New items are added.

•

Existing items remain intact.

•

Changes in symbology are updated updated.

Users’ existing element need to be edited to force symbology redraw.

35 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

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

GEOGRAPHIC COORDINATE SYSTEMS (GCS) Historically, GCS were infrequently used, however, there are now numerous advantages to setting the GCS in your DGN fil files: • 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.

37 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

GEOGRAPHIC COORDINATE SYSTEMS (GCS) • The best practice for setting GCS in seed files is based on the number of GCS systems used by your organization. i ti If th the organization i ti utilizes tili a single i l system, t then it should be set in the seed file. • If your organization utilizes several systems, you would have to set up one for each system thereby increasing the number of seed files. In this case you may not want to set the GCS

38 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

19

3/28/2014

Design Standards - Review horizontal and vertical Design Standards – validate local standards

39 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

Material Assignments • Material Assignments – Can be set per DGN Level • One material per level

– Can be set per Element Template • Allows for different materials on same level (i.e. Level Name = Pavement)

– Important for adequate 3D Model visualization

40 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

20

3/28/2014

Material Assignments • Material Assignments using Element Templates Æ“Best Æ Best Practice Practice”

41 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

User Preferences Settings Location • Do not attempt to locate your SS2 version of your MicroStation UPF (User Preference File) to the same folder f ld as your SS3 UPF location. l ti This Thi will ill cause UPF corruption when switching between versions.

42 | WWW.BENTLEY.COM | © 2014 Bentley Systems, Incorporated

21

3/28/2014

OpenRoads Best Practices Bob Rolle, Civil Application Engineer © 2014 Bentley Systems, Incorporated

22