In Namibia, some walking paths in national and private reserves are accessible only with a guide.
What would be the appropriate way to tag them?
access=no + guided=yes?
In Namibia, some walking paths in national and private reserves are accessible only with a guide.
What would be the appropriate way to tag them?
access=no + guided=yes?
access=no means nobody is allowed to use it. What you want is access=private
In the case mentioned above, wouldnât it be closer to âaccess=permitâ?
If someone who normally does not have access rights is required to obtain separate clearance or can enter only when accompanied by an authorized person, it seems closer to âpermitâ.
In addition, the accompanying tag âguided=yesâ strikes me as quite an ingenious idea.
I hadnât thought of that before, but I think it is a very fitting tag for places that can only be accessed when accompanied by a guide.
I would say so, even under the original definition that required the permit to be âroutinely grantedâ. I disagree with that constraint, but this case even seems to satisfy it.
We already have guide=*, which sounds very similar. For example, some but not all tourism=museum and tourism=gallery offer guided tours. Unfortunately, the tagging scheme doesnât seem to distinguish between tour guides merely being available and tour guides being required (such as at the Vatican Museum).
You could duck tag it as guided=only
The guide=* tag mostly seems to be used for the type of guide thatâs available. It might not be a good idea to mix the information whether a guide is required into the same tag.
The question is about paths where an ordinary person cannot get a permit. They have to take a guided tour or a guide. The guides are getting a permission. Sometimes as a result of being employed by the reserve.
Sure, itâs just that parallel guide=* and guided=* keys might be confusing. I know we have some similar close calls, like community_adopted=* versus community_adopter=*, but they were part of the same tagging scheme. If we consider the Vatican Museum example I gave, no one would consider it a private museum â not with such crowds inside and lines outside. So access=private would be misleading even if guided=only would be accurate.
I figure that an ordinary person can get a permit by accompanying a tour guide. But permit already suffers from enough confusion without overloading more nuances onto it.
It occurs to me that we already have a solution for this on campgrounds. If you can only camp as part of a group, thatâs group_only=yes. If you canât just decide to use the facility on your own without registering somehow, thatâs impromptu=no. The fact that a guide is involved could be supervised=yes. Admittedly three tags for this single requirement seems a bit much, but it would probably avoid stretching access tags behind their intended meanings.
I agree that adding another access value is a stretch. Therefore, the suggestion was to use an additional tag. The combination of access=private + guided=yes is simple and clear. It would provide an exception similar to the combination of access=private +foot=yes.
supervised=yes seems to be applicable also to ordinary unguided walks in places like the US national parks, where âthere is a person who supervises the placeâ in the form of the park rangers.
Would mappers and data consumers reliably interpret this combination to mean private access except for a guide? Or would we ever need to tag private access even with a guide?
I would caution against establishing guided=* as a new mode of transportation alongside foot=*, which is essentially what youâre suggesting by drawing an analogy to foot=* overriding access=*. This is orthogonal to the mode of transportation. After all, some guided trails are walkable, while others are only traveled on horseback. As long as we rely on access keys to clarify highway=path, this could be a significant source of ambiguity.
it also sounds like fee=yes or (toll=yes?) would be applicable
guided would not apply only to walking. Similarly, there are tracks that can be driven only with a guide.
What would the combination highway=path access=private foot=yes guided=only mean for private vehicles or the public on foot? It feels like multiple moving parts that need to be glued together somehowâŠ
That means whatever the combination highway=path access=private foot=yes means (I couldnât figure out whatâs the role of foot=yes given highway=path), and that the use requires a guide.
We seem to be in agreement that guided is not another means of transportation. I suggest we treat it similar to fee and lit - as an additional attribute of the element.
BTW, I was proposing guided=yes rather than guided=only.
How about foot=guided? So guided would not become a means of transport but a refinement of what kind of transport by foot is allowed?
Would escorted=only help, or make it even worse?
Only uses I can see are âescortâ in regard to brothels & attraction:minheight:escorted, which isnât that far off what weâre talking about in needing to have somebody with you.
âEscortâ does sound more directly relevant than âguideâ when it comes to the right of access. For example, some tunnels require hazmat trucks to pull over and arrange for an escort before proceeding. Meanwhile, Iâve been on plenty of self-guided tours through parks. Maybe this is splitting hairs though.
I think the requirement to follow an escort or guide should correspond to the value required or only. Otherwise, yes just says that an escort or guide is available. We donât need to make this distinction with tolls, because thereâs no such thing as an optional toll. Precedent includes reservation=required and membership=required, with plenty of existing usage.
If the value really needs to be yes or no for some reason, then guide_required=* has some scant use.
I like it!
Yeah, why not use access=guided | Tags | OpenStreetMap Taginfo as the access value itself? Then if it differs by mode of transport, the usual applies and you tag vehicle=guided or foot=private, etc.
=permit is already bad enough. There needs to be more justification than having an idea to invent another another access=*
This doesnât explain whoâs allowed to use it with guides. Eg the requirement may be =permit , then you have a conflict.
There are already toll= , group_only= , reservation= , and membership=
Yes, guided would answer the question, âCould someone help me once Iâm there?â Access tags are about answering the question, âMay I access the feature in the first place?â If youâre telling me about a trail I know nothing about and say that I need a guide to go there, do I need to pay for a guide? Must they be a particular guide? Is the guide program restricted to members of a particular group, or to groups wanting to go there?