On Jul 18, 2014, at 6:19 PM, Paul Johnson wrote:
> I actively dislike lanes=* on oneway=no situations, except as a checksum,
> because you're forcing renderers to make assumptions about placement and
> directionality: if it's two way, tag lanes:forward and lanes:backward, and
> use placement:*=* as appropriate.
>
I thought I'd read up on all the stuff I needed to tag lanes=*,
lanes:forward=*, lanes:backward=*, turn:lanes=*, turn:lanes:forward=*,
turn:lanes:backward=*, etc. But I totally missed the existence of placement:*=*
Probably because I wasn't looking for it when searching for how to tag lanes
and because there is no link to the placement:*=* proposal page from the
turn:*=* page in the wiki. Do any data consumers (map renderers, navigation
displays, etc.) use this key?
Learn something new everyday and it pays to subscribe to the mailing lists.
Regarding Scout, I leave data turned off 99% of the time so any of the
navigation tools that need to access servers don't work for me. That said, when
I was playing around with the user interface and display seemed nice, intuitive
and easy to use.
_______________________________________________
Talk-us mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-us
