I am proposing the use of service=safari to be used in addition to highway=service when tagging roads that are part of a safari park or a similar drive in animal enclosure.
Please discuss this proposal on its wiki talk page.
I am proposing the use of service=safari to be used in addition to highway=service when tagging roads that are part of a safari park or a similar drive in animal enclosure.
Please discuss this proposal on its wiki talk page.
If you have a look at the values used with the service key globally and search with Overpass you can see that beyond the most common usages there are lots more beyond just what is documented, and quite a few documented values have never been “voted” on, they’re just in regular use.
The key thing is that the thing that you propose needs to be verifiable - and this was a problem with one previous value for service that one enthusiastic contributor had been using - driveway2. As that wiki page says that tag was removed from the database becuase (despite requests to its proposer) it simply wasn’t verifiable.
Yes, I was debating just using this tag until it’s de facto established (like Any tags you like - OpenStreetMap Wiki), especially since it is a relarively rare tag and it doesn’t change any existing tags meaning. But I did in the end chose the official route to see if there were any issues I had not thought of, and because there are some roads that already have service values, just not consistent ones. But because this is not a significant change to the tagging structure, I don’t expect big issues to arise.
I am not really familiar with this objects, but I am surprised that highway=service is used rather than highway=track
They’re often big asphalt roads so it makes sense.
After gathering your feedback, I abandoned this proposal in favor of safari route relations: