Building Access Location
Last updated
Was this helpful?
Last updated
Was this helpful?
Feature which has a point geometry and represents the locations where pedestrians and / or vehicles can enter or exit a building.
This page details upcoming data that will be provided for the new Building Access Location Feature Type in the OS NGD from the end of March 2025 to give you early insight. Data schema version 1.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
The earliest date on which you can request a one-off snapshot of a date in the past for data in this feature type is 25 March 2025.
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
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
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
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
The type of change that generated a new version of the feature.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Code List Name: changetypevalue
Max Length: 50
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.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
Geometry Type: Point
The date on which the latest evidence was gathered to make an update if required. For example, the date of a field visit or the date of imagery capture.
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
Date when the geometry 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
The capture method describes how the Building Access Location attributes were created, for example, via Field Survey.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Code List Name: capturemethodvalue
Max Length: 25
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0
The OS NGD theme to which the feature belongs.
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Code List Name: themevalue
Max Length: 40
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.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
Code List Name: buildingaccesslocationdescriptionvalue
Max Length: 25
OS NGD API – Features Filterable: No
OS Select+Build Filterable: No
Data Schema Version: 1.0
A description of the method(s) of access normally utilised at the Building Access Location (for example, Pedestrian).
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Code List Name: accessmodevalue
Max Length: 25
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: Yes
Data Schema Version: 1.0
A description of the principal access function at the Building Access Location (for example, Private or Public).
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Code List Name: accesspurposevalue
Max Length: 15
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: Yes
Data Schema Version: 1.0
An indicator of possible accessibility obstruction(s) at the Building Access Location (for example, Ramp or Step).
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Code List Name: accessobstructionvalue
Max Length: 20
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: No
Data Schema Version: 1.0
An indicator of the relative location of the Building Access Location with respect to surface level upon approach to the Building Access Location (for example, Above Surface Level).
Data Types: String (GeoJSON), String (GPKG), String (CSV)
Nullable: false
Code List Name: accesslevelvalue
Max Length: 20
OS NGD API – Features Filterable: Yes
OS Select+Build Filterable: Yes
Data Schema Version: 1.0
The date on which the latest evidence was gathered to make an update if required. For example, the date of a field visit or the date of imagery capture.
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
Date when the access 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
Identifier of the Building associated with the Building Access Location.
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
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 OS NGD Resources GitHub repository.
For instructions on loading CSV files, see the Getting Started with CSV guide.