The EToN version used in the EToN data. Not applicable to Incident and TM dataIdentifies the Highway Authority area in which the data is located.Identifies the Highway Authority area in which the data is located.Road name and location of the EntityThe Permit status of the EToN works. Only relevant to EToN works where the works is on a permitable USRN
"The works Activity. Relevant to EToN data"
The code for EntityWorksActivityCurrent status of Entity, e.g. "Advanced planning".Identifies the system in which the Item data content was createdIdentifies the system in which the Entity data content was createdIdentifier for the entity in the originating systemIdentifier for the item in the originating systemDeep link to Entity on roadworks.orgDeep link to Item on roadworks.orgIndicates if the Entity is cancelledIndicates if the Item is cancelledA flag to identify if the works has been confirmed. An EToN works, and a TM works associated with an EToN works is considered CONFIRMED unless: 1) When an EToN roadworks' start date has passed but no confirmed works start alert has
been receieved from the LHA 2) When an EToN roadworks' end date has passed and the works is still in it's grace period, but still considered active as no confirmed works stop alert has been received from the LHA All other TM works and Incidents are
considered CONFIRMED
A flag to identify if the works has been confirmed. An EToN works, and a TM works associated with an EToN works is considered CONFIRMED unless: 1) When an EToN roadworks' start date has passed but no confirmed works start alert has
been receieved from the LHA 2) When an EToN roadworks' end date has passed and the works is still in it's grace period, but still considered active as no confirmed works stop alert has been received from the LHA All other TM works and Incidents are
considered CONFIRMED
The direction of the travel where the Item occursThe name of the road on which the Entity lies.The name of the road on which the item lies.Comma delimited list of USRNs corresponding to Entity geometry USRN stands for Unique Street Reference Number. A USRN identifies a street segment in the UK Natonal Street Gazetteer
Comma delimited list of USRNs corresponding to Item geometry USRN stands for Unique Street Reference Number. A USRN identifies a street segment in the UK Natonal Street Gazetteer
The organisation responsible for the traffic disruption. Identifies the organisation source of the data. The name of the Local Authority/Utility/National Highways Agency from whom the data was sourced. Please refer to an authoritative list
here.
The Responsible Organisation's Section ID. This is an EToN field. This is an official DfT code associated with the Publisher's SWA_ORG_REF. Ref: http://www.thensg.org.uk/iansg/link.htm?legacy=true&nwid=20026
Identifies the organisation source of the dataA textual description for the eCollection/@IDID identifying a collection of Entities. Grouping by this field will generate a list of all Entities belonging to a collection such as a major road scheme. For a majority of the roadworks data this reference code is the same format
as the SourceReference field. Where an EToN ProjectID is present it is encoded as the EntityCollectionID. For Incidents this data will be Null
Description of "parent" EntityEntity Short DescriptionEnd datetime of "parent" EntityStart datetime of "parent" EntityEnd datetime of "child" Item. This value is mandatory as where it is missing from the source data it is derived from the Entity.Start datetime of "child" Item. This value is mandatory as where it is missing from the source data it is derived from the Entity.Array of start and end datetimes when Entity is active. AKA Enforcement Pattern.Array of start and end datetimes when Item is active. AKA Enforcement PatternRoad name and location of the ItemItem Short DescriptionDatetime when the data was last updated within roadworks.orgThe reference used by the originating system from which the data was sourced. For roadworks this is the Eton works reference.Identifies the organisation from which the data is sourced. The name of the Local Authority/Utility/National Highways Agency or third party from whom the data was sourced.
Identifies the organisation from which the data is sourced. The name of the Local Authority/Utility/National Highways Agency or third party from whom the data was sourced.
The Entity's Datasource Section ID. This is an official DfT code associated with the Publisher's SWA_ORG_REF. Ref: http://www.thensg.org.uk/iansg/link.htm?legacy=true&nwid=20026
Identifies the organisation from which the data is sourced. The name of the Local Authority/Utility/National Highways Agency or third party from whom the data was sourced.
Identifies the organisation from which the data is sourced. The name of the Local Authority/Utility/National Highways Agency or third party from whom the data was sourced.
The Entity's Datasource Section ID. This is an official DfT code associated with the Publisher's SWA_ORG_REF. Ref: http://www.thensg.org.uk/iansg/link.htm?legacy=true&nwid=20026
The name of the Contractor. i.e who is carrying out the work.Indicates whether the works will close the footwayThe EToN notice sequence numberThe last EToN Notification Type received See https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/181675/eton-6-technical-specification.pdf for details
The EToN works categoryThe EToN parking suspensions flagThe EToN outgoing flagthe EToN Permit Condition descriptionIs there out of hours working? An EToN fieldThe Reinstatement Categories that apply to the road on which the works are being carried out. EToN onlyThe Traffic Sensitive information that applies to the road on whicih the works are being carried out. EToN onlyIf true then the reverse route of the TM diversion route plan appliesThe speed limit in mph (if any) on the TM ItemThe weight restriction in tonnes (if any) that applies to the TM ItemBoolean flag to say the date is estimated or exact. This value is mandatory as where it is missing from the source data it is derived from the Entity (please see "derived" field)..Boolean flag to say the date is derived from its parent Entity. False indicates the date is present in the source data.Point coordinate of Entity locationA delimited list of coords that represent the user defined way points in a route. Ie: the points along the route explicitly defined by the user when digitising their route on the map.A delimited list of coords that represent the user defined way points in a route. Ie: the points along the route explicitly defined by the user when digitising their route on the map.Entity line geometry is described in WKT. Longitude and latitude and vertices are space delimited.
Item line geometry is described in WKT. Longitude and latitude and vertices are space delimited.
Entity polygon geometry is described in WKT. Longitude and latitude and vertices are space delimited. The last vertex in a polygon is always the start and first vertex in the string.Item polygon geometry is described in WKT. Longitude and latitude and vertices are space delimited. The last vertex in a polygon is always the start and first vertex in the string.Entity From/To route geometry is described in WKT. Longitude and latitude and vertices are space delimited. The last vertex in a polygon is always the start and first vertex in the string.Entity From/To route geometry is described in WKT. Longitude and latitude and vertices are space delimited. The last vertex in a polygon is always the start and first vertex in the string.Item From/To data is described in WKT. Longitude and latitude and vertices are space delimited. The last vertex in a polygon is always the start and first vertex in the string.Item From/To data is described in WKT. Longitude and latitude and vertices are space delimited. The last vertex in a polygon is always the start and first vertex in the string.Traffic Management Code - only applies to EToN roadworks.Currently only accepts coordinates in BNG.
The maximum area for the box is 25.000 square kilometersIndicates whether the point location has been derived by Elgin. False indicates that the location was present in the source data.Estimated impact on road traffic of EntityThe top level category of "parent" Entity (can be thought of as the "Cause" or "Consequence")The category of "parent" Entity (can be thought of as the "Cause")Items is the root element for REST implimentationsEntities is the root element for REST implimentationsDatetime when the data row was createdA checksum derived from the data fields of the individual feed.ID of "parent" Entity. Both EntityID and ItemID are persistently unique in their own right. Because the 2-level hierarchy is flattened Entity information will be passed through for each Item record – and consequently the EntityID is
repeated in the XMLID of traffic management Item. Persistently uniqueID of traffic management Item. Persistently uniqueA checksum derived from the data fields of the individual feed.Datetime when the data row was createdA checksum derived from the data fields of the individual feed.ID of "parent" Entity. Both EntityID and ItemID are persistently unique in their own right. Because the 2-level hierarchy is flattened Entity information will be passed through for each Item record – and consequently the EntityID is
repeated in the XML