Proposed features/Checkpoint for Tourism

From OpenStreetMap Wiki
Jump to navigation Jump to search
Status: Approved (active)
Proposed by: Herrbert74
Tagging: checkpoint=hiking or cycling
Applies to: nodearearelation
Definition: Hiking (or cycling) checkpoints are important for validation of completion on long distance walking (and cycling) routes.

Rendered as: a stamp
Drafted on: 2011-07-15
RFC start: 2011-07-15
Vote start: 2011-07-30
Vote end: 2011-08-13


Define a tag for point of interests where a hiker or cyclist can validate the reach of a checkpoint.


The participants (usually hikers completing a long distance hiking route) have to validate the completion of the tour at the reach of every checkpoint. They can do this usually with dating and stamping of the appropriate box in their personal completion brochure. It is needed to stamp at every checkpoint. If this is not possible, it is accepted the stamp of the closest place to the route which is not marked in the brochure. The checkpoints can be located in pubs or shops in the villages, on railway stations usually in the ticket offices, but many times they are in the forest in their standard boxes equipped on trees or on the fences of forester’s lodges. The checkpoints are permanently placed on their locations. They are not transitional objects placed there for a race, etc.

Usually the hikers have to start or finish a trip at a checkpoint. So they have to stamp twice at same checkpoint: at the finish of a section and at the start of the next section if these are in two different date.

It is very useful to see the checkpoint on your GPS unit, if you use one.


A course is a permanent tour that is organised by an organisation. It can consist of one or several trails, routes, walks or only of checkpoints. An organisation can start many of these, e.g. the Hungarian Rambler's Association have more than a hundred listed on their website. You can start to complete a course by buying its brochure or registerig at their website and completing it by validating all the checkpoints by electronic means, stamping or by writing down a code. At the end you usually receive a badge or similar reward. There are two types of courses:

  1. Most courses have a designated route
    • For an example, see the Wikipedia page on El Camino de Santiago. On the right, you can see the stamps.
    • Another example is 'The validation of the completion' section on the Wikipedia page of the Countrywide Blue Tour in Hungary.
    • The individual trails on can be considered as a Hiking Course.
  2. There are also courses that require visiting all checkpoints in any order from any direction, like all the castles and springs of a mountain range. So there is no required route, hence the use of course to avoid confusion.


Checkpoint type

Tag Description
checkpoint:type=stamp A stamping point.
checkpoint:type=code A sign on a tree or on a building to write down.
checkpoint:type=electronic An electronic device used with a timing tag.


  • course=value is the name of the hiking or cycling course.

Other tags

  • name=value is used only to describe the place, e.g. name of the building, pub, mountain, etc.
  • description=value is used only to translate the name of the course to different languages.
  • url=value is a url to the course and the organisation.


course=Országos Kéktúra
operator=Magyar Természetbarát Szövetség
description:en=Countrywide Blue Tour

Or on a pub on El Camino:

name=John Bull Pub
course=El Camino de Santiago
operator=Junta de Galicia
description:en=Way of St. James

Example on

name=Princes Risborough 
course=The Ridgeway

Applies to


Areas (buildings)

Relation (multipolygon buildings)


No rendering on street maps.

On special interest maps for hikers, a stamp.


Please use the discussion page.


Voting is open until 2011-08-13. Please vote with {{vote|yes}} or {{vote|no}} and sign with ~~~~. If you oppose, please put your reason on the comments page and not in this voting chapter.

  • I approve this proposal I approve this proposal. --Herrbert74 15:27, 30 July 2011 (BST)
  • I approve this proposal I approve this proposal. -- Al3xius 12:28, 31 July 2011 (BST)
  • I approve this proposal I approve this proposal. for permanent checkpoints. For checkpoints active within an event please consider a role in a relation — see the discussion page. --Surly 21:34, 31 July 2011 (BST)
  • I mostly approve this proposal. The hiking/cycling split is guaranteed to cause problems for combined hiking/cycling routes. Suggest tourism=checkpoint instead. I don't think there's any fundamental distinction between a "cycling checkpoint" and a "hiking checkpoint" - whatever distinction there is will be made by the relation, not the checkpoint itself. Stevage 02:57, 1 August 2011 (BST)
    • I changed the tagging from tourism=checkpoint for a reason. Please refer to the tagging mailing list. I'm not aware of any checkpoint where the hikers and bikers share the same checkpoints. If there are such examples, I'm sure that the cyclers are OK with checkpoint=hiking.
  • I approve oppose this proposal. I like its idea, but not the tagging: 1) This should be within tourism=*, e.g. tourism=checkpoint as suggested by Stevage. 2) description=* should not be misused for translations of other tags. A relation may indeed be a better place to define name=*, name:en etc of the course, and which checkpoints belong to it. 3) url=* should be replaced with website=*. --Fkv 05:40, 1 August 2011 (BST)
    • 1)See above 2)OK, I will change the tagging from description to course in the final wiki version 3)URL is the right choice, as mostly the website is only the oerator's website, and there are subpages to the course. Like in 2 of 3 of the above examples. For example in Hungary only url applies.
  • I approve this proposal I approve this proposal. Hunsly 13:05, 1 August 2011 (BST)
  • I approve this proposal I approve this proposal. Kempelen 20:36, 1 August 2011 (BST)
  • I approve this proposal I approve this proposal.Szp 11:01, 8 August 2011 (BST)
  • I approve this proposal I approve this proposal.--grin 10:59, 9 August 2011 (BST)
  • I approve this proposal I approve this proposal. --higa4 04:15, 13 August 2011 (BST)