[Talk-us] Best way to tag a campground/site?

[Thomas Colson]

It has been brought to my attention that our method of tagging campgrounds
runs afoul of OSM best practices:

 

http://www.openstreetmap.org/browse/changeset/17949565

 

Which begs the question: what is the best way to tag a campground that
serves multiple groups?

 

Most NPS Front Country campgrounds, and Forest Service as well, provide for
"car-camping" as well as RV Sites. Some also include group sites (10 or more
people not in an RV). 

 

We have been tagging them as such:

 

tourism <http://wiki.openstreetmap.org/wiki/Key:tourism?uselang=en>  =
camp_site;caravan_site

 

Options include

 

tourism <http://wiki.openstreetmap.org/wiki/Key:tourism?uselang=en>  =
camp_site

comments = also_caravan_site

 

but this will result in a very vocal and vigorous response from the RV crowd
as to why we're not using:

 

tourism <http://wiki.openstreetmap.org/wiki/Key:tourism?uselang=en>  =
caravan_site

comments = also_camp_site

 

Another option is to use two nodes, very near each other, one for each
camping "activity". Most campgrounds are divided into tent sites and RV
sites, but in MHO this is not the best way to tag these..?

 

If the intended end result is for  consumers of OSM data to be able to
"locate" a campground that best serves their needs (I'm sleeping in the
backseat of my car or a RV or in a horse trailer), what is the best scenario
here, when applied to 350+ NPS parks  (We want a consistent tagging)?

 

Just to complicate this, some Front Country campgrounds can also accommodate
horses, as well. 

 

http://wiki.openstreetmap.org/wiki/Semicolon#When_NOT_to_use_a_semi-colon_va
lue_separator suggest that most consumers of OSM data can't parse the
semi-colon, which I have a hard time believing: any decent renderer using
OSM data can use "like" statements. 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20130922/43d2a064/attachment.html>