Import Rustpunt rest areas for hiking and cycling

From OpenStreetMap Wiki
Jump to navigation Jump to search

(work in progress)

Import into OSM of special rest-areas for hikers and cyclists.

Latest edit: 2022-10-30 Peter Elderson: layout and text improvements


A semi- automated import is proposed of ca 630 special rest area’s for hikers and cyclists to take a break, branded as “Rustpunt”. A Rustpunt always includes an outside seating area with BYO permission, and self_service coffee/drinks/snacks/sweets, and water, access to toilets and a shelter.

The tagging specs and the proposed workflow are presented first. See below for details and explanations.


Import the new Rustpunt objects as nodes tagged

  • amenity=cafe
  • self_service=only
  • outdoor_seating=only
  • name=name from dataset
  • website=url from dataset
  • ref:Rustpunt=p_id from url from dataset
  • brand:website=
  • fixme=resurvey
  • source=
  • source:date=2022-11


  1. The dataset will be split up by region and assigned to mappers living in the region. This will amount to 50-60 rustpunt locations per region. The import will be done region by region, after initial verification that the locations match the addresses.
  2. Before import, the location of each node will be verified and where necessary moved (off-line, of course), to ensure that it matches the address on the website.
  3. At import, each location is marked with fixme=resurvey, aimed to set the exact location at the address.
  4. After import, resurvey is required. At resurvey, it is up to the mapper to pick the exact spot for the node (the address itself, or a shed, barn or garden, a shelter, the sign, the seating area), and to add further detail such as a description, additional nodes for picnic tables/toilets/bins/bicycle stands etc. Or map it as an area. PS1. The operator knows and visits all the locations repeatedly, so detailed reports by the operator will be seen as survey. Imported Rustpunt nodes which are relocated more than 6m by a mapper after survey, will be reported back to the operator, for verification and correction. PS2. It is up to the regional import mappers to (partially or fully) perform the survey at step 2, if it can be done without slowing down the entire operation.
  5. Maintenance of the data: We will receive new and changed data from the operator, about twice per year without asking. In the meantime, we can also freely use the current datasets found on the Rustpunt website . The comparison of existing OSM data against the dataset is done using scripts by user emvee and the results are shared on the Dutch OSM forum. The maintenance will be done manually; no further automated edits are proposed.

Planning and progress

A target completion date for the import operation of 2022-12-31 seems achievable. We will start as soon as the Dutch community is in majority ok with it. Progress will be reported here.

2022-10-29 Green light. Started assigning regions. Announcing to international community.


Background details and considerations


In Nederland, some 630 locations are present under the reserved title “Rustpunt”. The title is assigned by a non-commercial operator called They are areas sporting outdoor seating where you can BYO, limited self_service items such as coffee, tea, soda and snacks, and access to a shelter and toilets. There may be other facilities such as air and electricity for bikes and mobile devices, drinking_water, waste bins, playground, bicycle stands. The sites are recognizable by a very notable sign at or to the entrance, but most areas are themselves hidden from sight so you really have to enter to see the exact layout, which has a wide variation.

The operator/issuer is “” and we have permission to use the dataset they have provided to the Dutch OSM community. We can get current data any time we want.

Following the import a periodical update dataset (additions, removals and attribute updates including possible name change or relocation) will be provided by the operator. This is *not* part of any automated edit, but will help maintain the quality of the data in OSM manually.

Rustpunt objects (nodes and polygons)  already existing in OSM have been tracked and checked, and will be excluded from the import. Where the dataset differs from OSM, the operator has been notified and together we will manually correct the data at both sides. 7 Rustpunt objects no longer existing as Rustpunt (™) have been removed from OSM (or retagged, is they still exist but the Rustpunt permission has been revoked).

The new Rustpunt objects will be imported as a node representing a self_service cafe with outdoor seating only, tagged with the official Rustpunt name + the official Rustpunt website page URL for the object, their unique poi number (p_id) + amenity=cafe + self_service=only + outdoor_seating=only. We will add source=[operator URL] and source:date=2022-10 or 2022-11 and fixme=resurvey (after survey to be replaced with survey:date=[date])

After import, all the objects will be checked for correctness and, if necessary, surveyed and refined. The after-import check is part of this proposal; later surveys depend on mapper findings. We plan the surveys, but not what will be done by the mappers. The workflow will be directed by fixme tags


The operator/issuer is “” and we have explicit permission to use the dataset they have provided to the Dutch OSM community. We can get current data any time we want. Updates of the dataset will be sent to us every half year without asking. This will trigger us to compare-and-update.


These resting areas with self-service of refreshments are very welcome to hikers and cyclists, and having them on the map or searchable as POIs is a vast improvement, that is, if we have them all, and if it’s are reasonably reliable that they still exist.

Spontaneous mapping during several years has yielded some 50 of these rest areas mapped, 7 of which no longer existed, according to the operator who assigns the right to call it a Rustpunt. (2022-10-20 These have been removed from OSM.)

The tags can differ. Most are tagged as amenity=cafe, and most have the word ‘rustpunt’ in one of the tags e.g. name=*, website=*, note=*. Checking and retagging already mapped nodes/areas is *not*  part of this import spec. (2022-10-24 As a side benefit, the exact locations have been checked by the Rustpunt operator and, if >6m off, are corrected in OSM as well as on the Rustpunt website).


The operator has granted us the use of the data of all the Rustpunt locations, which is provided though the website and, if a different format or special attributes are required, by mail. The operator would like feedback from OSM about differences, and offers to provide a half-yearly actual dataset in return, without us asking. Changes to the locations and attributes on the website are reflected without delay in the available export files.

The permission is recorded on the OSM wiki contributors page.

The data encompasses:

  • lat and lon
  • Name (Official name of the Rustpunt)
  • Address (street, city/municipality, postal code), address of the owner
  • URL of the subwebsite for the Rustpunt, format<p_id>

The address will not be tagged. It will be used for check-up to verify the location before the upload is done.

The subwebsite of the poi gives details and often pictures of the Rustpunt, and a map with a pin at the right spot near the address. Part of the URL is the unique poi-Id, which can be used in the future as a unique link between OSM and the source data.

Assessment of the data items in a record (row in the table)

The name is somewhat arbitrarily assigned, sometimes the word ‘Rustpunt’ is included, sometimes not; it may be the surname of the owner, or the name of a camping, or a house name, or a fantasy name. The name on the road is often not the same as in the data. For us, any name is fine, though it is not suitable as a unique key.

The owner’s address we think should not be in OSM. It cannot be seen at the spot, you would have to explore to find it. Providing the URL also provides access to the addres on the site.

The URL of the Rustpunt’s page on the site is unique, because the unique p_id is there. The p_Id of a Rustpunt remains the same over time.

The lat and lon are a mixed story. We don’t know exactly how they are defined, it looks like they have simply pointed at a map. For the Rustpunt objects mapped in OSM the comparison shows exact matches, near matches and a few not-so-near matches (e.g. 250m off because of a relocation). OSM mappers regularly locate the Rustpunt itself some 30 meters off, compared to, and so far OSM has been more precise than the operator. One location was very far off, this has been corrected on both sides, but it shows errors can occur. The near matches can be e.g. 100m, which on a farmer’s grounds can be the result of relocation from the front to the back. This means that before the import, the locations need to be verified to at least be at the given address.

Comparing and processing the data

The comparison of existing OSM data against the dataset is done using QGIS and scripts by user emvee and the results are shared on the Dutch OSM forum.

OSM data is retrieved using an overpass query based on earlier tagging consensus. The comparison against the dataset will generate three lists:

  1. Removals: the object exists in OSM but not in the current dataset
  2. Matches: the object exists in both OSM and the dataset
  3. Additions: the object exist only in the dataset, not in OSM

Lists 1 and 2 are checked and handled manually. Changes in geolocation will be reported back to the operator, who will then enter the OSM geolocation into his database.

List 3 is processed as explained in this document.

After receiving an update dataset, the same comparison is run again. The expected result is that lists 1 and 3 may have a few entries, while list 2 (matches) contains nearly all the Rustpunt locations with near-exact (<6m) geolocations.

Tagging discussion results

A few years back, there was a consensus in the Dutch OSM community to map the Rustpunt areas as an area or a node with the main tag  amenity=cafe.

Some of the locations do resemble an enclosed self service cafe, there is an inside where you help yourself to cafe and snacks and pay, and there is an outside where you sit, drink and eat. Other locations are more like an open picnic area where -if weather permits- a table is put out with thermoses, paper cups and a box for the coins.

And very few of them have been mapped as a special Rustpunt over the past years.

That’s why the issue was raised again. Turns out that there is importable data, which means decide on the tags.

Viable suggestions were:

  1. highway=rest_area with name=*, self_service=yes, cafe=yes and other toggle tags; the existing definition of rest_area needs to be slightly adapted to encompass non-motorized uses.
  2. tourism=picnic_area with self_service=yes
  3. stick to amenity=cafe even though it’s often not a cafe;
  4. both amenity=cafe and tourism=picnic_area on the same node or polygon.
  5. Map all parts separately: picnic_tables or benches, picnic_area, cafe room, toilets, shelter.
  6. The latest idea is to use amenity=cafe and include self_service=only and outdoor_seating=only.

Current discussion (Dutch)