[Tagging] access on both area and highway

[Nathan Case]

I'd imagine if there are no conditional restrictions on the way, then 
this would allow routing on the way regardless of any conditional on the 
area itself.

I could imagine the same sort of situation where a footpath runs through 
a private residential estate/hotel/amenity but the footpath is open to 
the general public (such as "public rights of way" in the UK). Though, 
in your case, I doubt many routers cater specifically for dog walkers!

I guess what might be useful is some conditional access value like 
"paths_only" or "keep_to_path", i.e. dog = leashed + 
dog:conditional=keep_to_path @ (May-Aug), but I doubt that would 
supported by any data consumers (and I'm not sure if user-made values 
are encouraged in the conditional access scheme).

I think I would:

- Tag path ways with dog = leashed

- Tag the islet area with dog = leashed + dog:conditional=no @ (May-Aug)

Hope that's helpful.


On 28/03/2022 17:09, Niels Elgaard Larsen wrote:
> The wiki has a section about ways and areas
> https://wiki.openstreetmap.org/wiki/Key:access#Nodes.2C_ways_and_areas
> It talks about whether to tag on ways OR areas.
>
> But can I put access restrictions with the same keys both on an area 
> and ways inside the area, and how are they prioritized?
>
>
> On The Amager Strandpark Islet
> https://www.openstreetmap.org/way/23013534
> From May to August dogs are only allowed leashed on paths and not on 
> the beaches, etc.
>
> So I would like to tag
> dog=leashed on the paths
> and
> dog=leashed,dog:conditional=no@(Sep-Mar) on the islet
>
> But does that make sense? I.e., can I assume that consumers would not 
> apply the dog:conditional on the paths.
> Or would:
>
> dog=leashed on the paths
> and
> dog=no,dog:conditional=leashed@(Apt-Aug) on the islet
>
> be interpreted differently?
>
>
> Anyway, this should be clarified on the wiki.
>