Those are what I meant with sub-signs that often require free text input.
But even that free text (next to the naming of the sign) can be horrible.
And not only in Belgium. Just take a look at this:
http://wiki.openstreetmap.org/wiki/File:Conditional-access-bicycle-and-delivery.jpg
When you read
I added those Type signs to the plugin, and I fully agree with you about
the spanking! I called them Type_XX_often_something_extra
They're a pain and forced me to become somewhat creative...
Jo
2015-02-11 17:44 GMT+01:00 Glenn Plas :
> What are we going to do about Type-* subsigns ? That is t
For the direction of the sign, it would be nice to be able to use a
'virtual' node, then JOSM could calculate the bearing automatically. Maybe
somebody should create a ticket so this becomes possible for all nodes
which have direction.
How is this solved when 2 signs are on the same pole? Or 3 (th
What are we going to do about Type-* subsigns ? That is the official
designation, I mapped a few but they apply to several variations. I
tried waiting until someone else brings them up.
I'm talking about those:
http://www.wegcode.be/wetteksten/secties/mb/mb-111076/868-hs2art13
Type IV for exa
Hi Sander,
Thank you for having a look at it! You are right. The plugin code itself
needs to be changed to accomodate the remarks at the start of your message.
traffic_sign should go on the selected node
and the effects of the sign should go on the selected ways
The way it works now, you'd have
I tried it a bit, and I do have some concerns with both the mapping plugin
and the style JOSM uses.
First, I think that a traffic sign should only have tags like
traffic_sign=BE:C21[7]
and no tags like
maxweight=7
Those legal implications of traffic signs should stay on way segments IMO.
So th
