[OSM-talk] How to tag lanes, not ways, was: Deprecating the use of Tag:highway=stop in favour of Key:stop
Peter Childs
pchilds at bcs.org
Sun Aug 30 09:13:09 BST 2009
2009/8/30 John Smith <deltafoxtrot256 at gmail.com>:
> 2009/8/30 Anthony <osm at inbox.org>:
>> <way id=....>
>> <nd ref=.../>
>> <tag .../>
>> <tag .../>
>> <tag k='lanes' v='2' />
>> <tag k='lanedirection' v='backward;forward'>
>> <tag k='maxspeed' v='130;110' />
>> </way>
>
> That solution would fail to allow us to attach nodes to individual lanes.
>
> This is just another hack to try and accomodate the existing framework
> and I think it's a bad idea to try and cram multiple values into a
> single keypair.
>
> We need a proper solution to do this properly, at some point OSM is
> going to need to move to more micro mapping, lanes isn't really a
> micro mapping issue, it's a subset of a way issue and we should treat
> it as such.
>
Another reason this is a bad idea, is that its difficult to access,
search index and process. I think lanes need there own records, like
ways, nodes and relations.
We needs some way to map thinks like the pavement having 3 steps in it
where the road is flat, and this is likly to be difficult to push
chairs and wheel chairs and hence they need to cross the road to avoid
the steps..... (Currently they are all on the same way and splitting
it just gets more and more difficult to get reasonable accuracy and
scale (Too much on top of each other). I'm not even sure I like the
way we currently map dual carriageways.
Peter.
More information about the talk
mailing list