Last updated
Was this helpful?
Last updated
Was this helpful?
This page details upcoming data that will be provided for the Site Access Location Feature Type in the OS NGD from the end of March 2025 to give you early insight. Data schema version 2.0 for this feature type is currently not available through the live access services. The information on this page is as accurate as possible, but is subject to change before launch.
Feature which has a point geometry and represents the locations where pedestrians and / or vehicles can enter or exit a site.
The earliest and latest dates on which you can request a one-off snapshot of a date in the past for the data schema versions available for this feature type are detailed in the following table:
Please see for more information about versioning in the OS NGD Land Use Theme.
The following sub-sections provide details about the attributes included with this feature type, their data types in the different output formats, and other important metadata about them.
Primary identifier for the feature. The OSID is a Globally Unique Identifier (GUID) and requires no centralised authority to ensure uniqueness. Note that the same OSID can occur in more than one feature type when a single feature is represented multiple times in the OS NGD.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Max Length: 36
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Topographic identifier (TOID) of the feature, as published in the OS MasterMap suite of products.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: true
Max Length: 20
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Date when the version was last updated.
Data Types: String (GeoJSON), Date (GPKG), Date (CSV)
Nullable: false
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The date this version of the feature became the latest version.
Data Types: String (GeoJSON), DateTime (GPKG), DateTime (CSV)
Nullable: false
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The date this version of the feature was superseded by an update or ceased to exist.
Data Types: String (GeoJSON), DateTime (GPKG), DateTime (CSV)
Nullable: true
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The type of change that generated a new version of the feature.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Max Length: 50
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
A single descriptive value intended for a quick understanding of what the feature represents.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Max Length: 15
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Geometry for the feature.
Data Types: Geometry (GeoJSON), Geometry (GPKG), WKT (CSV)
Nullable: false
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Geometry Type: Point
The date on which the latest evidence was gathered to make an update if required. For example the date of collection by a surveyor or third party information received.
Data Types: String (GeoJSON), Date (GPKG), Date (CSV)
Nullable: true
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
Indication of the method used to capture or produce the data.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: true
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 2.0
Date when the attribute was last updated.
Data Types: String (GeoJSON), Date (GPKG), Date (CSV)
Nullable: false
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The source organisation who provided the data.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: true
Max Length: 50
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0
The OS NGD theme to which this feature belongs.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Max Length: 40
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The organisation that provided the information.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: true
Max Length: 50
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0
This attribute was called accesstype in data schema version 1.0, and was renamed access_mode from version 2.0 onward.
A description of the method(s) of access normally utilised at the Site Access Location (for example, Pedestrian).
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Max Length: 25
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: Yes
Data Schema Version: 2.0
A description of the principal access function at the Site Access Location (for example, Private or Public).
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: true
Max Length: 15
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: Yes
Data Schema Version: 2.0
This attribute was called accesstype_evidencedate in data schema version 1.0, and was renamed access_evidencedate from version 2.0 onward.
The date on which the latest evidence was gathered to make an update if required. For example, the date of collection by a surveyor or third party information received.
Data Types: String (GeoJSON), Date (GPKG), Date (CSV)
Nullable: true
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 2.0
This attribute was called accesstype_updatedate in data schema version 1.0, and was renamed access_updatedate from version 2.0 onward.
Date when the attribute was last updated.
Data Types: String (GeoJSON), Date (GPKG), Date (CSV)
Nullable: false
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
This attribute was called siteid in data schema version 1.0, and was renamed accessedsiteid from version 2.0 onward.
The unique identifier (OSID) of the site feature to which the SiteAccessLocation feature relates.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Max Length: 36
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0, 2.0
The unique identifier (OSID) of the related SiteRoutingPoint feature.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: true
Max Length: 36
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0
The OS NGD network that the feature is accessed from (for example, Road Network).
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: true
Max Length: 20
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 2.0
This attribute was called roadnodeid in data schema version 1.0, and was renamed accessednetworknodeid from version 2.0 onward.
The unique identifier (OSID) of the network node that represents the point on that network that provides access to the Site Access Location feature.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: true
Max Length: 36
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 2.0
The straight line measure between the accessednetworknodeid and the location of the access feature.
Data Types: Number(GeoJSON), Float (GPKG), Real (CSV)
Nullable: true
Precision: 5
Scale: 1
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 2.0
Code List Name:
Code List Name:
Code List Name:
Code List Name:
Code List Name:
Code List Name:
From 25 April 2023, this value has no longer been populated. As part of a data enhancement programme in late Spring 2023, all Site Routing Point features were recreated as and therefore network references are now recorded and captured as in data schema version 1.0 of Site Access Locations.
See also for more information.
Code List Name:
1.0
03 October 2022
Ongoing
2.0
27 March 2025
Ongoing
Loading OS NGD CSV files into databases
Comma-separated values (CSV) file format is universally supported for easy ingestion into all major database products. Before loading OS NGD data contained in CSV files into a database, it is necessary to create relevant tables. Data definition language (DDL) statements for PostgreSQL, SQL Server and Oracle can be accessed in our .
For instructions on loading CSV files, see the guide.