Identifying Change in the Network

Use cases

• Identify which features change and how that affects other information related to it.

• Identify physical change to the road network.

• Identify roads under construction and affects on service provision.

Steps to Success: Identifying Change in the Operational State of a Street

• Common attribute is across all features

• Gives the reason why a feature has changed using these values

Considerations When Adding Your Own Data to OS MasterMap Highways

1. Back up your data.

2. Use feature validation data set (FVDS) to check which features are affected and how (TOID value and UPDATE, INSERT or DELETION).

3. Connect data to either TOID or USRN as this are persistent with a finite life cycle.

4. Further useful information:

   • BeginLifespanVersion – gives date of when the object was inserted or changed in the data

   • Validfrom – data when the custodian entered the data into LSG (Street records)

Things to Note: Data Captured Against OS MasterMap ITN Layer is Easily Transferred Over to OS MasterMap Highways

• TOIDS are persistent across both products and have not changed

• Data linked to ITN using TOID should link to Highways

• FVDS can be used to identify where a reference may have changed

Steps to Success: Identifying Change in the Operational State of a Street

• Operational State – indicates the construction status of the street

• Streets – all values are permitted, default is open

• RoadLink – Operational status defaults to open, although may occasionally be under construction

• Special designations table – provides additional information and can be linked directly to Street by USRN.

Code List: OperationalStateValue