OS NGD API – Tiles Technical Specification provides an overview of the endpoints available, as well as the parameters that can be used with each endpoint. The Technical Specification is intended to be used bycustomers who want to integrate with the API.
Click into each endpoint to learn more.
Retrieve the OS NGD API – Tiles landing page for this service.
GEThttps://api.os.uk/maps/vector/ngd/ota/v1/
Response
The landing page provides links to the API definition (link relation service-desc, in this case path /api), to the Conformance declaration (path /conformance, link relation conformance), and to the Collections of geospatial data (path /collections, link relation data).
Body
titleThe title of the API.
While a title is not required, implementors are strongly advised to include one.
Example: "OS NGD API"
descriptionstring
Example: "Ordnance Survey National Geographic Database API."
attributionattribution for the API
The attribution should be short and intended for presentation to a user, for example, in a corner of a map. Parts of the text can be links to other resources if additional information is needed. The string can include HTML markup.
links*array of link (object)
Request
Response
Root level properties of a style specify the map's layers, tile sources and other resources, and default values for the initial camera position when not specified elsewhere.
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
links*array of link (object)
collections*array of collectionInfo (object)
Request
Response
Retrieve the description of a collection available from this service.
Information about a particular collection of (mostly geospatial) data available from this API. The 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 contained in the response, 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
id*string
identifier of the collection used, for example, in URIs
Example: "buildingpart"
titlestring
human readable title of the collection
Example: "Building Part"
descriptionstring
a description of the data in the collection
Example: "Polygon feature representing a building."
links*array of link (object)
extentExtent with Uniform Additional Dimensions Schema
The extent module only addresses spatial and temporal extents. This module extends extent by specifying how
intervals and crs properties can be used to specify additional geometries.
Request
Response
Retrieve the definition of the specified tiling scheme (tile matrix set)
Reference to a Tile Matrix Set on an offical source for Tile Matrix Sets such as the OGC NA definition server (http://www.opengis.net/def/tms/). Required if the tile matrix set is registered on an open official source.