>> That said, highway= implies that the object is a public or private way
>> (US terms, but usable by the public), except for highway=service and
>> highway=track.
>actually a highway=* is any kind of way, and access by the public
>might only be implied if no other access is tagged explicitly.
>Cheers,
>Martin
This is the problem in a nutshell. Implications, and bundling of values in a
key.
Let's say there is no such tag as highway=motorway.
Is a 'motorway' just - highway=primary[1]; access:private[2]; car=yes[3];
motorway=yes; lorry;yes; max_speed;x;
lanes:3; hardsholder:yes?
i.e. do you take an implied access[1], then void that applied access[2], then
state specific means of transport
to build up a motorway like description through multiple specific tags?[3]
now see the 'track issue' as this.
highway=track; access:private; foot=yes; horse;yes; (a hundred other
regulations;yes)
now just like the motorway being more than just tarmack for cars motorbikes. it
is 'a motorway' - a bundle of
rules and regulations. A package. And this needs to render as such. The
motorway example isn't a sort of
primary road. It is a 'motorway'. The bridlway on a track isn't a sort of
track. It is a bridlway. It can go
on a track.
So the aforementioned track tag combo is a 'bridleway'.
highway=track; highway=bridleway
not possible.
highway=track; designation=public bridleway
not rendering, and contradicted by what does render.
Ben
_______________________________________________
talk mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/talk
