[Tagging] Tagging of pitches within a campsite

Bryce Nesbitt bryce2 at obviously.com
Wed Apr 29 21:57:35 UTC 2015

Ok, lets see if we can land this.
Existing practice varies:

tourism=camp_site + name=<pitch number>
tourism=camp_site + ref=<pitch number>
tourism=camp_site + addr:unit=<pitch number>
tourism=camp_site + addr:housenumber=<pitch number>
camp_site=pitch + name=<pitch number>
camp_site=pitch + ref=<pitch number>
camp_site=pitch + addr:unit=<pitch number>
camp_site=pitch+ addr:housenumber=<pitch number>
camp_site=<pitch number>
tourism=caravan_site + name=<pitch number>

building=cabin + ref=<number>

name=<pitch number>

ref=<pitch number>

There's a lot of activity in the "camp_site" namespace:

camp_site:water (412)
camp_site:parking (333)

The least disruptive tagging seems to be;

tourism=camp_site (for the site) or tourism=caravan_site

addr:unit=<pitch number>

Tagging that avoids the namespace is:

tourism=camp_site (for the site) or tourism=caravan_site

<amenity>=yes/no   (e.g. drinking_water=yes).
addr:unit=<pitch number>

If the community is willing to mechanically retag, it could be:



addr:housenumber=<pitch number>

I chose *addr:housenumber* because that's perfectly set up for routers.  If
a router can find a camp ground mapped as an area,
it should be able to find the number inside.  It's also unrealistic at this
time to expect osm-carto to render ref addr:unit or other names.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20150429/3d17a5fd/attachment.html>

More information about the Tagging mailing list