MapScale data is licensed, not owned. Displaying the credit is a condition of that licence — here is exactly what to show and where.

What you’ll achieve

You know which credit each endpoint requires, where it has to appear, and how MapScale hands it to you in every response.

What MapScale licenses, and from whom

Maps, tiles, static images, search, geocoding and routing are built on OpenStreetMap, licensed under the Open Database License (ODbL 1.0). Any produced work you make from them — a rendered map, an exported image, a list of search results shown to a user — must carry a notice that it contains OpenStreetMap data.

Administrative boundaries (used by admin-area lookups and by the admin fields on reverse geocoding) come from the Common Operational Dataset — Administrative Boundaries for Thailand, sourced from the Royal Thai Survey Department, published by UN OCHA on HDX under CC BY 3.0 IGO. That licence requires the creator, the source and the licence itself to be credited wherever the data appears.

World outlines in the basemap come from Natural Earth, which is public domain. We credit it as a courtesy; you are not obliged to.

Interactive maps

A MapScale style ships the credit on its sources, so MapLibre GL renders the attribution control for you. Do not hide, cover or remove it — it must stay legible at mobile sizes and above custom overlays. Collapsing it behind an “i” toggle is acceptable; deleting it is not.

If you build your own control, reproduce the credit exactly as it comes from the style, with the links intact.

The credit a Thailand map must display

<!-- Rendered by MapLibre's attribution control from the style. -->
<div class="maplibregl-ctrl-attrib-inner">
  <a href="https://www.openstreetmap.org/copyright">© OpenStreetMap contributors</a>
  (<a href="https://opendatacommons.org/licenses/odbl/1-0/">ODbL 1.0</a>) ·
  <a href="https://www.naturalearthdata.com/about/terms-of-use/">Natural Earth</a>
</div>

Static maps and exports

Every image from the Static Maps API arrives with the credit rendered into the pixels along its bottom edge. That is deliberate: the image travels into emails, PDFs and social cards where no attribution control exists, so the credit has to travel with it.

Do not crop it off. If your layout has to crop or composite the image, place an equivalent, legible credit immediately next to the map.

API responses hand you the credit

Every JSON response includes an attribution string ready to display, plus an attributions array carrying each source, its link, its licence and the licence URL if you would rather build your own markup. Use them — they always reflect the datasets that actually produced that response, so a reverse-geocode result correctly credits both OpenStreetMap and COD-AB while a routing result credits only OpenStreetMap.

Binary responses (vector tiles, static PNGs) cannot carry JSON, so they carry an RFC 8288 Link header pointing at each licence deed instead.

Example 1 — admin-areas reverse lookup, Siam Paragon

GET /v1/admin-areas/reverse?point=100.5018,13.7563

{
  "subdistrict": { "id": 1, "name": "Pathum Wan" },
  "district":    { "id": 2, "name": "Pathum Wan District" },
  "province":    { "id": 3, "name": "Bangkok" },
  "country":     { "id": 4, "name": "Thailand" },
  "attribution": "Boundaries: RTSD / UN OCHA COD-AB (CC BY 3.0 IGO)",
  "attributions": [
    {
      "text": "Boundaries: RTSD / UN OCHA COD-AB",
      "url": "https://data.humdata.org/dataset/cod-ab-tha",
      "license": "CC BY 3.0 IGO",
      "licenseUrl": "https://creativecommons.org/licenses/by/3.0/igo/"
    }
  ]
}

A second response, a different point

Same endpoint, a different coordinate — the credit is identical because the licences behind it don't change, but the resolved administrative names do.

Example 2 — admin-areas reverse lookup, Thonglor

GET /v1/admin-areas/reverse?point=100.5348,13.7466

{
  "subdistrict": { "id": 5, "name": "Khlong Tan Nuea" },
  "district":    { "id": 6, "name": "Watthana District" },
  "province":    { "id": 3, "name": "Bangkok" },
  "country":     { "id": 4, "name": "Thailand" },
  "attribution": "Boundaries: RTSD / UN OCHA COD-AB (CC BY 3.0 IGO)",
  "attributions": [
    {
      "text": "Boundaries: RTSD / UN OCHA COD-AB",
      "url": "https://data.humdata.org/dataset/cod-ab-tha",
      "license": "CC BY 3.0 IGO",
      "licenseUrl": "https://creativecommons.org/licenses/by/3.0/igo/"
    }
  ]
}

Your own data layers

MapScale attribution covers MapScale data only. Anything you draw on top — your own geometry, a third-party dataset, another provider's imagery — needs whatever credit its own licence demands, alongside ours.

Next stepRender your first map →

Attribution