Skip to content
Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Location Data

Communicating the location of proposed or executed contract delivery is important to many users of contracting data.

This extension introduces two properties at the items level to describe location:

  • deliveryAddress - a standard Address block which can be used to provide a postal address where services should be delivered.
  • deliveryLocation - a new block consisting of GeoJSON and Gazetteer entries to describe a wider range of locations to which the contract line item relates.

The locationGazetteers.csv codelist's Category column indicates whether the gazetteer has identifiers for the whole world ('Universal') or only some subset ('National' or 'Sub-National').


Below is an example of a geolocated item:

  "items": [
      "id": "item1",
      "description": "Ceremonial Trumpets for Oxford Town Hall",
      "classification": {
        "description": "Trumpets",
        "scheme": "CPV",
        "id": "37312100",
        "uri": ""
      "deliveryLocation": {
        "geometry": {
          "type": "Point",
          "coordinates": [51.751944, -1.257778]
        "gazetteer": {
          "scheme": "GEONAMES",
          "identifiers": ["2640729"]
        "description": "Central Oxford",
        "uri": ""
      "deliveryAddress": {
        "postalCode": "OX1 1BX",
        "countryName": "United Kingdom",
        "streetAddress": "Town Hall, St Aldate's",
        "region": "Oxfordshire",
        "locality": "Oxford"
      "unit": {
        "name": "Items",
        "value": {
          "currency": "GBP",
          "amount": 10000
      "quantity": 10

If the procurement related to the rebuilding of a road, then the item could also specify more complex geometries such as:

"deliveryLocation": {
  "geometry": {
    "type": "LineString",
    "coordinates": [ [ -1.256503402048622, 51.747792026616821 ], [ -1.256477837243949, 51.747500168748303 ], [ -1.256466773131763, 51.747365723021403 ], [ -1.256471969911729, 51.747246699996332 ], [ -1.256481860557471, 51.747182243160943 ], [ -1.256497618535434, 51.747079648666102 ] ]
  "gazetteer": {
    "scheme": "OSMW",
    "identifiers": ["27895985"]
  "description": "St Aldate's",
  "uri": ""

You can take the contents of the geometry object, excluding the geometry keyword, and plug this into any GeoJSON tool to see the shape that is described.


Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.



  • Correct the order of longitude and latitude in field descriptions to match the GeoJSON specification
  • Describe elevation or altitude values
  • Remove Sphinx directives from readme
  • Update extension.json for Extension Explorer


  • Disallow Location.geometry.coordinates from having null in its array of coordinates
  • Disallow Location.gazetteer.identifiers from having null in its array of strings
  • Correct name of locationGazetteers.csv codelist (was locationGazeteers.csv)
  • Allow Location.geometry and Location.gazetteer to be null
  • Add title and description to Location.gazetteer
  • Add description to Item.deliveryLocation, Item.deliveryAddress
  • Add geometryType.csv codelist for Location.geometry.type
  • List codelists in extension.json
  • Add tests and tidy code
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.