Proposal talk:Advanced checkpoints

Conflicts with current use of Key:checkpoint

Unfortunately, using checkpoint=* in this new way would conflict with the currently approved meaning of the tag: checkpoint=hiking or checkpoint=cycling for checkpoints along hiking or cycling courses:

Key:checkpoint - original proposal (approved): Proposed_features/Checkpoint_for_Tourism

Taginfo: https://taginfo.openstreetmap.org/keys/checkpoint

I'd suggest changing your proposal to use a different key, perhaps militarycheckpoint=* or checkpoint:military=* --Jeisenbe (talk)

It isn't problem. Let it be military_checkpoint=*. --Otavva (talk) 15:48, 1 May 2019 (UTC)

Other values?

You've suggested values of "war" and "border" for the types of military checkpoints. It might not be possible to map military checkpoints in war zones, because the positions change frequently, and we try to map at least semi-permanent features.

There may also be checkpoints at other military facilities, perhaps near a military base or training area. How would these be tagged? --Jeisenbe (talk) 13:36, 1 May 2019 (UTC)

You're mostly right about war checkpoints. But there are not only quickly changeable checkpoints. Many of the war checkpoints are built with heavy machinery (for example big blocks transporting), and they are more permanent then small are. I think we can map them easily. When we know nothing about checkpoint, except that it is checkpoint, we can map it just military=military_checkpoint. This tag can be used by many not important checkpoints (military entrances, or something else). --Otavva (talk) 15:48, 1 May 2019 (UTC)