Geotag Schema
When using the normalised schema, only geotagId will be returned.
| Field | Type | Optional | Description |
|---|---|---|---|
| geotagId | String | No | Unique identifier for geotag. |
| counterpartyName | String | No | Name of counterparty (brand). |
| counterpartyLabel | String | No | Name and short address of counterparty. |
| houseNumber | String | Yes | The building number. |
| street | String | Yes | Street the building is located on. |
| neighbourhood | String | Yes | Commonly a district within a town. |
| locality | String | Yes | City, town or village. |
| city | String | Yes | City. Can be the same value as locality. |
| county | String | Yes | County. Can be the same value as city. |
| region | String | Yes | Region. Can be the same value as county. |
| postcode | String | Yes | Postcode of geotag. We estimate this in the event it wasn’t provided by the data source we use by considering surrounding geotags that have a postcode. While the field is optional, it’s very rare we don’t return it. |
| latitude | Double | No | WGS84 latitude. |
| longitude | Double | No | WGS84 longitude. |
| counterpartyCategory | String | Yes | The level 3 category (industry). |
| postcodeEstimated | Boolean | No | True if we’ve estimated the postcode by considering surrounding geotags. |
| postcodeErrorKm | Float | Yes | If we’ve estimated the postcode, the distance the location is from the geotag we used to estimate the postcode. |
Updated about 2 months ago