Chess Me Outside

Open data

Open data

Some of the monuments on the map come from OpenStreetMap. This page says which ones, under what licence, and where to get the same rows as a file.

What comes from OpenStreetMap

The viewpoints, trail markers and peaks in the national parks and city forests we cover, and the public chess boards across the Netherlands, are read from OpenStreetMap. Each of those monuments carries © OpenStreetMap on its own card in the app; the full credit is © OpenStreetMap contributors.

The monuments come from Wikidata, which publishes under CC0, and the clubs and boards people send in through this site are recorded by us. Neither is OpenStreetMap data; the dumps below hold none of their rows, only a reference where an OpenStreetMap feature was merged into one of them.

The base map is not OpenStreetMap either: it is Apple Maps on iOS and Google Maps on Android.

The town, village and neighbourhood names on this website's live map come from OpenStreetMap as well.

The licence

OpenStreetMap data is published under the Open Database Licence 1.0 (ODbL). We use it under that licence and offer our copy under the same one. The licence asks three things of us: name the source, offer the derived database as a machine-readable file, and put no technical barrier between the data and the people who want it that the file does not get round. The app needs an account; this page is how the data stays reachable without one.

OpenStreetMap copyright ODbL 1.0 licence text

The files

Every row we take from OpenStreetMap, with the links between them, split one file per region. Each is regenerated after that region's import and committed with the app, and the production map's Dutch rows are seeded from this same set.

open-data/osm/index.json

  • index.json lists every region with its row count and the SHA-256 of its dump, so a copy of any one region can be checked against it without downloading the rest.
  • Each region's rows are at open-data/osm/<region>.ndjson.gz: one JSON object per line, gzip-compressed. <region>.manifest.json sits beside it and repeats that region's own row count, licence, attribution and SHA-256.
  • Fields, in order: sourceRef (the OpenStreetMap element as type/id), kind, role, region, name, cityLabel, lat, lon, attribution, duplicateOf, duplicatedBy.
  • kind is one of viewpoint, trail-marker, landmark (a peak or an observation tower) or chess-board.
  • The live map's town and village names are served under the same licence at map/places/<country>/<tile>.json, one file per square degree: longitude_latitude of its south-west corner, each place as x, y, rank and name. Neighbourhoods and hamlets sit beside them as <tile>.local.json, rank 4. Each country's manifest.json there names the licence, the source and the fetch date.
  • duplicateOf names the monument this row was merged into when two monuments on the map turned out to be the same thing within 17 metres, as source/reference: osm/node/123 for another OpenStreetMap feature, or wikidata/Q123 when the surviving row comes from Wikidata and so is not in this file. Both are our decisions about OpenStreetMap data, which is why they travel with it.

Nothing about players is in it: no accounts, no captures, no faction colours, no ratings.

If something is wrong

A monument that should not be on the map, a board that is gone, a name that is off: mail support@chessmeoutside.com. A correction to OpenStreetMap itself belongs on openstreetmap.org, where the next import picks it up.