[OSM-talk-be] roadsign plugin adapted for Belgium
Ben Laenen
benlaenen at gmail.com
Sun Feb 22 19:18:13 UTC 2015
On Sunday 22 February 2015 19:27:27 Sander Deryckere wrote:
> Another sign I found was a no-access sign, with a "uitgezonderd plaatselijk
> verkeer, fietsers en ruiters", then someone made the "fietsers" part
> invisible (put a blue tape on it), but underneath, there was yet another
> subsign saying "uitgezonderd bicycle_icon". And that while cyclists are
> always considered "local".
Shouldn't we have a proper discussion once about how we're going to translate
all the traffic signs in OSM tags? A lot of traffic signs have different variations
and if we just tag all of these under the same traffic_sign=* we're going to
lose a lot of information.
We really need to know how to handle things like:
* B15 (priority on next crossroad) with different lines
* C5+7+9+? combinations where different traffic signs are combined into one
* D1 and D3 (mandatory direction) with different arrows which don't have
separate names
* F45 and F45b (no exit, maybe except cyclists and pedestrians, maybe not on
all routes), with different ways how the roads are laid out.
* F91 with different traffic signs on each lane arrow (recursion anyone?)
* F99a/b/c with different icons for pedestrians, cyclists, horses, and in
reality variations are found with mopeds and even gocarts
* F103 for pedestrian roads with or without bicycle icon, other different
exceptions possible for loading or unloading
* and what about all the big destination signs that can have exotic layouts?
* bilingual traffic signs, how to map those?
* and of course our governments and city councils are sometimes very creative
with the traffic code...
So yeah, maybe start a wiki page so we can discuss possible implementations
for these issues?
Greetings
Ben
More information about the Talk-be
mailing list