Restriction mapping
Create and review mapped restrictions in the context of streets, basemaps and related records.
- Restriction mapping
- Lines and polygons
- Gazetteer support
- Revocations and amendments
- Public access options
- Data sharing
TRO workflows connected to spatial data
Traffic Regulation Orders depend on streets, restrictions, geometry, order schedules and public-facing information. Officers need to understand how lines, polygons, street data, basemaps, amendments and revocations relate to the same place on the ground.
eVO TRO brings those workflows into a browser-based mapping environment so councils and highways authorities can manage restriction data, review spatial context and prepare outputs for wider use.
What eVO TRO supports
Lines and polygons
Work with line-based and polygon-based restriction geometry where those data models are required.
Restriction styling
Use visual styles to make restrictions clearer for officers and public-facing map users.
Measuring and tracing tools
Use mapping tools to support tracing, measuring and reviewing restriction lengths.
Splitting and combining
Support workflows where restrictions need to be split, grouped or adjusted.
Revocations and amendments
Review affected restrictions and support amendment or revocation workflows where configured.
Gazetteer and street lookup
Use street and address context from local gazetteer data where configured.
OS basemap support
Work with OS basemaps and maintained mapping services where those are part of the deployment.
Public access options
Publish or share appropriate TRO information with public-facing services where implemented.
Data extracts and integration
Prepare outputs for colleagues, public portals or third-party systems using suitable data-sharing methods.
Mapping and editing tools
TRO work needs accurate map-led editing. eVO TRO mapping tools can help officers trace and edit restrictions, review restriction lengths and work with line or polygon geometry against configured basemaps.
Restriction styles can reflect the way restrictions appear on the street, which helps officers review what has been captured. Measuring tools can support review of restriction lengths and location. Street View integration can support review where configured, giving officers extra street-level context without turning it into the source of record.
Gazetteer and street data
Street and address context is important when managing Traffic Regulation Orders. Where configured, eVO TRO can work with local gazetteer data and hosted address or street services so users can search, locate and review records in context.
Local gazetteer context
Connect TRO workflows with street and address data that officers already use across the authority.
Mapping and data services
Use hosted basemaps, addressing and spatial data services alongside TRO workflows where appropriate.
Revocations and amendments
TRO teams need to understand which restrictions are affected by a proposed change. eVO TRO can support review of restrictions scheduled for revocation, help users understand affected features and support partial revocation workflows where configured.
The aim is to make change management clearer: what exists now, what is being amended, which records are affected and what information needs to be retained for the order process.
Public access and data sharing
TRO data often needs to be shared beyond the traffic orders team. Colleagues, public portals, consultation services or third-party systems may need appropriate views, outputs or data feeds.
Public-facing information
Publish appropriate TRO information through public-facing services where implemented.
Data sharing and integration
Plan extracts, feeds or integrations so TRO data can be used by other systems and services.
Relationship to Earthlight and eVO
eVO TRO uses StatMap's wider web mapping and eVO platform approach. That means Traffic Regulation Orders can sit alongside corporate GIS, spatial data services, gazetteer data and public-facing information.
For authorities reviewing wider GIS provision, TRO can be considered as part of the same platform conversation as Earthlight, hosted data services and other map-led workflows.
Migration, support and implementation
TRO implementation is often about data as much as software. Existing restrictions, order schedules, geometry, gazetteer links, public information and integration requirements all need to be understood before migration or go-live.
Data migration
Support review and migration of existing TRO data, geometry and related records.
Implementation planning
Plan configuration, data preparation, roles, outputs and integration points before launch.
Training
Help officers and administrators understand the workflows and tools they need to use.
Support desk
Provide a support route for product questions, issues and implementation help.
Product input
The migrated source material describes eVO TRO as having been developed with input from TRO practitioners, including cooperation with TRO experts from Doncaster Council. The important point for visitors is practical: the page is focused on the work highways teams need to do every day, from restriction mapping to amendments, public access and data sharing.
Related technical videos
TRO: Splitting, Cloning and Revoking
A practical eVO TRO demonstration covering how live orders can be split, cloned and revoked.
Discuss your TRO project
Talk to StatMap if you are reviewing TRO workflows, replacing a legacy system, improving restriction mapping or connecting TRO data with wider GIS and public-facing services.