What data is available?

What feature types are available in OS NGD API – Tiles?

Basemap (ngd-base)

The following table details the OS NGD datasets that were used to create the OS NGD API – Tiles basemap. The result is a detailed OS basemap that combines OS Open Zoomstack and OS NGD data.

Theme	Collection	Feature Type(s)
Buildings	Building Features	Building Part
Geographical Names	Named Features	Named Point
Land	Land Features	Land, Land Point, Landform, Landform Line
Land Use	Land Use Features	Site
Structures	Structure Features	Compound Structure, Structure, Structure Line
Transport	Transport Features	Cartographic Rail Detail, Rail, Road Line, Road Track or Path
	Transport Network	Path, Path Link, Road
Water	Water Features	Inter Tidal Line, Tidal Boundary, Water, Water Point
	Water Network	Water Link, Water Link Set, Water Node

Find out more about the hierarchy of OS NGD data here.

Data overlays

The following table details the OS NGD datasets that can be used as overlays to the basemap to add additional information:

Theme	Collection	Feature Type(s)	Collection ID
Administrative and Statistical Units	Boundaries	Boundary High Water Mark, Ceremonial County, Country, Devolved Parliament Constituency, Devolved Parliament Electoral Region, Electoral Division, GLA Assembly Constituency, Historic County, Historic European Region, Lower Tier Local Authority, Parish Or Community, Polling District, Region, Regional Authority, Upper Tier Local Authority, Ward, Westminster Constituency	asu-bdy
Transport	Transport Network	Railway Link, Railway Link Set, Railway Node	trn-ntwk-railway
Water	Water Features	River Basin District Catchment, Waterbody Catchment	wtr-ctch

Attribution available in OS NGD API – Tiles

The following attribution is available as part of OS NGD API – Tiles:

CollectionID	Layer(s)	Available Attribution
ngd-base	All	osid, description, name1_text (only applicable to the Named Point, Site and Water Link Set layers), designatedname1_text (only applicable to the Road layer), versionavailablefromdate
asu-bdy	All	osid, description, name1_text (only applicable to the Country layer), name2_text, pollingdistrictid (only applicable to the Polling District layer), versionavailablefromdate
trn-ntwk-railway	Railway Link	osid, description, railwayuse, operationalstatus, physicallevel, name1_text, versionavailablefromdate
	Railway Node	osid, description, versionavailablefromdate
	Railway Link Set	osid, name1_text, name2_text, versionavailablefromdate
wtr-ctch	Waterbody Catchment	osid, waterbodyname_text, waterbodycategory, versionavailablefromdate
	River Basin District Catchment	osid, riverbasindistrictname, versionavailablefromdate

The map features do not contain every OS NGD feature type, nor the complete list of attribution available within the feature types that are included; we have purposefully only selected feature types and a subset of attribution from them that are useful for visualisation as this keeps the tiles lightweight and quick to render.

The inclusion of unique identifiers (IDs), where available, allows you to cross-reference with the full product, for example, with OS NGD API – Features. Find out more about OS NGD unique identifiers.

Update Frequency

Collection ID	Update Frequency
ngd-base	Weekly
asu-bdy	Biannually
trn-ntwk-railway	Monthly
wtr-ctch	Updated as and when updates are received from the authoritative bodies

Although OS NGD API – Tiles will be updated weekly, the data updates are based on the set currency of the OS NGD collections (for example, the Structure Features Collection currency is daily, whereas the Water Network Collection currency is monthly).

Collections

A collection in OS NGD API - Tiles references OS NGD Feature Type grouping. Feature types have their own data model and specifications which are not commonly shared with other feature types.

GET a list of all OS NGD Collections by using the below endpoint:

Retrieve the list of geospatial data collections available from this service.

GEThttps://api.os.uk/maps/vector/ngd/ota/v1/collections

Response

200400404405406500504

The collections of (mostly geospatial) data available from this API. The dataset contains one or more collections. This resource provides information about and access to the collections. The response contains the list of collections. Each collection is accessible via one or more OGC API set of specifications, for which a link to relevant accessible resources, e.g. /collections/{collectionId}/(items, coverage, map, tiles...) is provided, with the corresponding relation type, as well as key information about the collection. This information includes:

• a local identifier for the collection that is unique for the dataset;
• a list of coordinate reference systems (CRS) in which data may be returned by the server. The first CRS is the default coordinate reference system (the default is always WGS 84 with axis order longitude/latitude);
• an optional title and description for the collection;
• an optional extent that can be used to provide an indication of the spatial and temporal extent of the collection - typically derived from the data;
• for collections accessible via the Features or Records API, an optional indicator about the type of the items in the collection (the default value, if the indicator is not provided, is 'feature').

Body

application/jsontext/html

links*array of link (object)

collections*array of collectionInfo (object)

Request

JavaScriptCurl

const response = await fetch('https://api.os.uk/maps/vector/ngd/ota/v1/collections', {
    method: 'GET',
    headers: {},
});
const data = await response.json();

Response

{
  "links": [
    {
      "href": "http://data.example.com/buildingpart/123",
      "rel": "alternate",
      "type": "application/geo+json",
      "templated": false,
      "varBase": "/ogcapi/vars/",
      "hreflang": "en",
      "title": "Building Part"
    }
  ],
  "collections": [
    {
      "id": "buildingpart",
      "title": "Building Part",
      "description": "Polygon feature representing a building.",
      "links": [
        {
          "href": "http://data.example.org/collections/buildingpart",
          "rel": "self",
          "type": "application/json",
          "title": "Building Part"
        }
      ],
      "extent": {
        "spatial": {
          "bbox": [
            [
              -180,
              -90,
              180,
              90
            ]
          ],
          "crs": "http://www.opengis.net/def/crs/EPSG/0/3857"
        }
      }
    }
  ]
}