OpenRoads Designer Tip: Symbology Management of GIS Features
With the evolution of OpenRoads software, recent versions like OpenRoads Designer 2024 now provide enhanced capabilities to connect directly to GIS data using Feature Services. This functionality, available through the Geospatial Context Tab, is a major step forward for organizations focused on OpenRoads data management solutions and BIM software support.
For teams delivering OpenRoads management services or Bentley software support, properly configuring and standardizing these connections is key to maintaining consistency, efficiency, and alignment with agency requirements.
How OpenRoads Designer Integrates GIS Feature Services
When you connect to a GIS Feature Service in OpenRoads Designer, the software:
- Queries GIS data directly into your active model
- Automatically generates elements on new Levels
- Assigns Element Templates based on Feature Service Layer names
This automated structure is especially valuable for organizations implementing OpenRoads software configuration and OpenRoads software implementation strategies.
Why Standardization Matters for CAD and BIM Managers
The default naming and structure are derived from:
- The Connection Name (defined when adding the Feature Service URL)
- The Layer Names from the GIS service
Without standardization, this can lead to inconsistent data organization across projects. However, for teams focused on:
- OpenRoads workflow optimization
- Custom CAD programming
- CAD management services
this presents an opportunity to enforce structured, repeatable standards.
By standardizing naming conventions and templates, CAD and BIM managers can:
- Align GIS data with agency standards
- Improve model organization and usability
- Reduce manual rework and errors

Best Practice: Standardizing Feature Service Connections
To ensure consistency across your organization, you should predefine Feature Services within your configuration.
Key Steps:
- Define Feature Service URLs
- Add services through the Feature Service Manager
- Assign a standardized Connection Name (instead of using publisher defaults)
- Store Services in Configuration
- Make services available at the:
- Organization level
- WorkSpace level
- WorkSet level
- Make services available at the:


Configuring Element Templates for GIS Data
Once your Connection Names are standardized, the next step is aligning Element Templates.
Recommended Approach:
- Create a Template Group for each Feature Service
- The group name should match the standardized Connection Name
- Create Element Templates for each GIS Layer used
Deployment Options:
- Store templates in a DGNLIB using:
MS_DGNLIBLISTMS_DGNLIBLIST_ELEMENTTEMPLATES
- Or distribute via an Element Templates XML file for import prior to querying GIS data

Benefits of a Standardized GIS Workflow in OpenRoads
By implementing these best practices, organizations can achieve:
- Improved data consistency across projects
- Faster GIS data integration
- Reduced manual cleanup and rework
- Better alignment with agency standards
The ability to connect directly to GIS data in OpenRoads Designer is a powerful feature—but without proper standardization, it can introduce inconsistency. By defining Connection Names and aligning Element Templates, organizations can fully leverage this functionality while maintaining control over their CAD and BIM environments.