Data Sources and Attribution
The destination catalogue of the Content API (places, the destination hierarchy and the hotel counts per destination returned by search-destination, places and hotels/by-destination) combines Bundleport and supplier content with the open data below. We credit each source here as its licence requires.
Sources
| Data | Source | Licence | How we use it |
|---|---|---|---|
| Place names, coordinates and administrative codes | GeoNames | CC BY 4.0 | Base of the place catalogue and of its administrative hierarchy. |
| Administrative boundaries | © OpenStreetMap contributors, Overture Maps Foundation | ODbL 1.0 | Used internally to determine which administrative area contains a city. Boundary geometry is not served. |
| Administrative boundaries, same release | geoBoundaries; Esri Community Maps contributors; Land Information New Zealand (LINZ) | CC BY 4.0 | As above. |
| Identifier crosswalk | Wikidata | CC0 1.0 | Links boundary releases to GeoNames areas. No attribution required; credited for transparency. |
Changes made
- GeoNames: names and codes are matched to supplier destinations, deduplicated and completed with Bundleport data.
- Boundaries: matched to GeoNames administrative areas and used only to compute which area contains each city. The boundaries themselves are not redistributed; responses carry Bundleport place identifiers and names, not boundary data.
Release in use
| Country | Boundary release | Loaded |
|---|---|---|
| Spain | divisions 2026-09-23.1 | 2026-10-03 |
This table is updated when a boundary release is loaded for a new country or replaced. Each release's sources and licences are those listed by its publisher.
Credit line
© OpenStreetMap contributors, Overture Maps Foundation; GeoNames; geoBoundaries, Esri Community Maps contributors, LINZ (CC BY 4.0).