PMS 6.0 Release Notes ¶

Overview ¶

For the most part, the 6.0 release concerned with:

Facilitating the digitising of an Active Travel Infrastructure (ATI) edge network by advanced users though an expanded Missing Edges Module
Facilitating Road Schedule Editors in Local Authorities in capturing ATI routes though a redesign of the Segments Module
Framing the categorisation of Segments in the 1993 Roads Act
The addition on an ATI Features Module
The addition of ATI specific Project Types to the Projects Module
The addition of new Materials and Lane References relevant to the capture of ATI Works.
The addition of Open Street Map data as vector (WFS) layers for use within the advanced Missing Edges Module (only visible to Missing Edge Resolvers)
The addition of and ATI Surveys layer which will house vector lines from on-the-ground surveys carried out by Local Authorities

Note

The advanced missing edge functionality added to the system under this release is subject to the allocation of a specific User Role called the Missing Edge Resolver role. The Missing Edges form and functionality will continue as normal for the vast majority of users with the Road Schedule Editor role.

In addition to this we have:

Under PMS 5.5 we upgraded MapServer to the newest version 8. This version of MapServer comes with, among other things, initial OGC API support. Under the 6.0 development, this has been configured for use by users of the PMS.
Added an icon to the Coordinate Center Tool
Applied group editing functionality to some data grids
Applied a full road network update to PRIME2’s 2022 Q1 release
Streamlined the process for updating the PRIME2 network
Made various improvements to some grids in terms of layout and filters available
Added search functionality to the layer tree
Redesigned the PMS documentation
Create 154 new browser tests to test the newly developed functionality

User Stories ¶

Data Imports¶

#1.1 PRIME2 lower class way polygons WMS ¶

PMS edges data is imported from OSi’s PRIME2 product. To date, only line data has been imported. In March 2017, all class 6 and higher way lines were removed from Prime2. This data is currently only available as Polygons and as such, has not been available in the PMS.

This development was concerned with creating a WMS layer from PRIME2 class 6 to 10 road polygons to be used by LGMA users as a reference for adding missing edges.

The layer is available in the Network folder as Ways (PRIME2).

#1.2 Import latest line data from PRIME2 (not already in network edges) into missing edges ¶

Compass has been aligning the PMS with PRIME2 for a number of years. The normal process has been to recalculate edge and segment level data where it meets new PRIME2 road data, attempt automatic fixes and carry out manual fixes when necessary. This can be complex and time-consuming and therefore has tended to happen once a year at most.

This user story is concerned with developing an internal process for importing “New” PRIME2 data into PMS on a more regular basis. “New” data is any data that is not currently stored in PMS but also does not force the alteration or recalculation of data already stored i.e. data that does not cross intersect the current network.

#1.3 Create OSM data selection layers and grids ¶

OpenStreetMap is a free, editable map of the whole world that is being built by volunteers largely from scratch. As such it is a potential source of Active Travel line work that can be added to Missing Edges.

This development was concerned with a once-off process of bulk importing OSM data to the PMS database, data that will be made available to RMO data digitizers as WFS and WMS layers.

The grids for these layers contain an editable field which Missing Edge Resolvers can use to mark up data for bulk import into the missing edges layer. Alternatively, the missing edges tracing tool can be used to add edges directly to missing edges.

Note

These layers are only visible to users with the new Missing Edges Resolver user role.

#1.4 Create survey tool data selection layers and grids ¶

The RMO is in the process of developing a survey tool that will allow users to walk routes and capture line data via GPS. The intention is to roll this tool out to local authorities so they can capture ATI routes on the ground.

This development was concerned with the processing and importation of this data to the PMS database using Python, and the subsequent creation of layers and grids with the same functionality as OSM layers i.e. can be traced to missing edges or marked for import to missing edges via an editable grid.

#1.5 Full Road Network Update to Prime2 2022Q1 ¶

Under #1.2 Import latest line data from PRIME2 (not already in network edges) into missing edges we developed a process for importing Prime2 to network edges that do not require manual integration. 92% of changes have been imported under this user story.

This user story is concerned with completing the import of the 2022 Q1 Prime2 dataset i.e. manually resolving the remaining 8% of changes.

Missing Edges Tool with Network Editing Functionality¶

#2.1 User role for missing edges resolver ¶

A new role was be created for users who can resolve missing edges. This role is required to allow a separation of concerns between Missing Edge Data Digitizers and Missing Edge Data Resolvers.

#2.2 Add reviewing functionality to missing edges module ¶

This user story was concerned with how the new functionality developed for the missing edges module will be presented to users with the Missing Edge Data Resolver role.

This functionality includes:

A Combined Network Edges/ Missing Edges vector layer used for snapping newly created edges to PRIME2 edges
A Combined Network Nodes/ Missing Nodes vector layer used for snapping newly created nodes to PRIME2 nodes
Adding a series of check boxes and free text inputs to the Missing Edges form to aid work flow
Updating the UI to show current connectivity of edges and nodes
Developing functionality to allow forms from different modules to be accessed from a single grid
Updates to the missing edges grid
Allow users to open missing edge forms by clicking on map features (lines)

#2.3 Resolve missing edges within the PMS WEB application ¶

Prior to this release, users of PMS did not have the ability to directly edit missing edges in the PMS browser application. Missing edges were added to PMS by users in the local authorities via the current missing edges module. The quality of these user drawn edges varies greatly, where often they are indicative rather than exacting.

The pre 6.0 process for deciding which user entered missing edges should be imported into network edges was manual (using excel files), cumbersome and error prone, and only occured in line with PRIME2 updates, that is, once or twice a year.

This user story was concerned with the backend process required in giving users with certain privileges the ability to resolve i.e. snap and/or reshape (by moving vertices and/or splitting lines), missing edges within the PMS browser application. Coupled with a streamlined internal (Compass) process for importing missing edges, this development has greatly speed up the process of adding user-entered missing edges to the network proper.

Going forward, Missing Edges marked as ‘Resolved’ will be automatically imported to Network Edges on a weekly basis.

#2.4 Streamline process of adding resolved missing edges to the PMS road network ¶

To date, the importing of PRIME2 data to PMS has been both complex and lengthy, primarily due to the fact that the import process requires the recalculation of the survey and location data that sits on top of the Road Schedule.

Now, once the missing edge resolution process is complete, and because missing edges will not “break” the current network, we are in a position to import these edges using a streamlined process and at more regular intervals

#2.5 Mark user entered edges for deletion from network edges ¶

With the advent of the advanced missing edges tool, users at the RMO are afforded the ability to add to network edges on a needs-must basis, including being able to tag segments as ‘proposed’. Its noted that user-added edges could prove to have been inaccurate at the time of the original import to network edges, that geometries will be hit and miss in the initial phases of planned construction and the urgency to get info on the system. Therefore, a process was required for RMO users to mark edges for deletion from network edges so they can be redrawn/reshaped in missing edges and subsequently radded to edges proper.

Edges marked for deletion will be processed along with imports through a weekly automated process.

ATI: Segments and ATI Features¶

#3.1 Segment form and grid updates ¶

This developments applied to the Segments module were concerned with:

The addition of new attributes fields that align the categorisation of segments with the Roads Act ‘93
The addition of Active Travel classifications for segments
The application of new business rules to support the categorisation of segments with the Roads Act ‘93 and to better represent the flow in which attributes should be applied to segments.
A redesign of the form layout to facilitate all of the above

See the Segments - Road Details Tab page for more information on how the new logic is applied.

#3.2 ATI data capture module ¶

This module allows users to use a linear referencing tool to mark parts of the road network as active travel infrastructure by selecting a stretch along road centrelines and applying an offset.

The Usage Classification of Roadway is defined as ‘that portion of a road which is provided primarily for the use of vehicles’ [1]. A Roadway therefore can contain a Cycle Track, that can either form a part of the Roadway (inside the curb) or can sit just off the Roadway. Though not technically part of the Roadway, the ATI Usage Classifications of Footway and Combined Footway Cycle Track, will often run parallel to the Roadway.

To this end, and so to avoid over-complicating the underlying network, in cases where the ATI to be created is intrinsically linked to the Roadway, users can derive the ATI from the Roadway centerline by applying an offset.

All Active Travel Segments, be they formed of their own centrelines and created as Segments proper, or be they derived from a Roadway centerline, are represented in a new ‘ATI Segments & Features’ map layer with an associated grid.

See the ATI Features page for more information on how to create derived ATI.

ATI: Projects¶

Prior to 6.0, users could create Cycleway and Footway projects via the Projects module in the Pavement Management System. These project types were limited in scope in that they did not allow users to capture works details.

Now in PMS 6.0, users can capture ATI projects with all the detail previously afforded to Pavement projects.

Please refer to the Projects documentation page for more details.

#4.2 Add a new construction method of “New Construction” (with new Intervention and Treatment Category)¶

Users detailing works for cycleway or footway projects, can now select a construction method of “New Construction”. When ‘New Construction’ is chosen the value displayed for Intervention Type and Treatment will be ‘NC’.

#4.3 Update materials schema ¶

New materials and material designations are required to facilitate the addition of a works grid to ATI projects. The values of some existing materials were also updated.

#4.4 Calculate HasATI for projects and add to grid ¶

Users of the PMS can filter the Projects layer by Project Type to show Active Travel projects created using the ATI project forms. However, Pavement projects may also contain elements of Active Travel. Prior to PMS 6.0, no method existed for displaying these in the PMS.

In the works grid of Pavement projects, distinct sections along the Project’s width can be differentiated in the Lane Details panel of the Add Section form. In his form, users can add details for up to 8 lanes. All lanes can be attributed with the same values or individual lanes can be attributed with specific values. This development added a fixed list of Lane Reference values in a dropdown. The current Lane Reference free text box was retained and renamed Lane Description. For existing Projects, we carried out an exercise to map the current free text Lane reference values to the new fixed list of the Lane Reference values.

On saving a project a new value of HasATI is stored in the PMS database. The criteria for setting HasATI to true are as follows:

The project was created using the ATI Project from
The project has been marked up with at least one lane which utilises a Lane Reference value that is specific to Active Travel.
The project utilises the Active Travel Funding Source.

This value can then be used to filter the Projects layer and grid so users can view Active Travel projects or projects with Active Travel elements, in isolation. Where the project is a Pavement Project created on a Roadway segment rather than on a distinct ATI segment, users can turn on the ATI Features layer to see where the Active Travel elements sit in relation to the segment.

#4.6 Add a new project type for pavement projects of ‘Non-Public’¶

In line with the development to allow users of the PMS to create road segments with a road ‘Status’ of ‘non-public, a need arose to also allow users to define Projects as Non-Public Pavement Projects. These projects conform to a new phase logic.

#4.8 Addition of a Project Category ¶

Prior to PMS 6.0, the project category as set on the project form was a static value that exists without any relationship to project level objects in the PMS database i.e. the project type. It was formed by taking a hard-coded prefix value and appending the project year.

This development was concerned with storing the new project category values and creating a relationship with project types.

Reserve Items & Task Orders¶

#5.1 Reserve Item: End-user documentation (wms/wfs)¶

End-user documentation displaying WMS/WFS metadata was added here.

#5.2 End-user documentation (admin panel)¶

End-user documentation on the PMS Management Tool was added here.

#5.3 Reserve Item: Develop OGC API within PMS mapping services for reporting ¶

The RMO are unable to consume MapRoad PMS data directly from data business analytics services e.g. Power BI, AGOL. Prior to 6.0, to prepare analytical reports in business analytics services the RMO were required to export excel workbooks from MapRoad PMS bowser and import these static reports to data models built-in business analytics services. This process had to be repeated each time the model needs to be updated.

Under PMS 5.5 we upgraded MapServer to Version 8. This version of MapServer comes with, among other things, initial OGC API support. Under the 6.0 development, this has been configured for use by users of the PMS.

Please refer to the OGC API documentation page for more details on how to access the PMS data via this API.

#5.4 Reserve Item: Add Icon to Coordinate Center Tool ¶

Prior to 6.0, when users enter coordinates to the coordinate tool, the map centres on this point but a reference icon was not added. This development was concerned with adding this icon.

#5.5 Allow Full Grid Exports to Excel ¶

Prior to PMS 6.0, Excel exports were generated in the browser. Exporting an entire grid required users to turn off paging which sometimes caused the request to time out. This development was concerned with moving the export process away from the browser and generating the excels on the server instead.