Re: [Tagging] Time is now: tag ALL traffic signs in OSM

It is interesting your petition. My point of view is , even the meaning of two traffic signs in differents places would be the same, it would be different traffic signs. In some countries there are other codes for the road marks (but with the same meaning) so they aren't the same traffic sign so

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

Hello, I think that tagging all traffic sign is very usefull. I hope having one day an app that automates photo-sign-osm process. Mainly because it is the easy way to detect signaling changes. The proposal is interesting but the key side should be improved. It would be useful to be compatible

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

As the proposal is evolutioning in a ways I can't manage (for example because I don't know how to build the models in Kendzi3D with relations or at the style) I wish all of you could afford ways and help with specific examples,models , scripts,code in the wiki proposal or the github, for example.

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

For those who wonder how useful the trafic sign and associated stuff can be, this 5 years old article can give some hints https://www.theatlantic.com/technology/archive/2012/09/how-google-builds-its-maps-and-what-it-means-for-the-future-of-everything/261913/ Google seems to use street view

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On Mon, May 22, 2017 at 12:40 PM, Tobias Knerr wrote: > On 21.05.2017 22:23, yo paseopor wrote: > > As you can see in http://imgur.com/gallery/SgE90 with Kendzi3D JOSM > > plugin you can locate the traffic signs belonging to a way. > > Of course it's always possible to

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On Sun, May 21, 2017 at 1:46 PM, Mark Wagner wrote: > Warning signs are something that data consumers could certainly make > use of, but we need some way of explicitly coding which direction of > which road they apply to. > This sounds like a problem that can be handled

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 21.05.2017 22:23, yo paseopor wrote: > As you can see in http://imgur.com/gallery/SgE90 with Kendzi3D JOSM > plugin you can locate the traffic signs belonging to a way. Of course it's always possible to guess a place next to the road, but even with your proposed side=* tagging, that's not

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

Hi all Le 21 mai 2017 21:25, "yo paseopor" a écrit : Node could be in a way. Way has a direction We can use forward and backward keys, and also side=right/left/both to orient the traffic_sign. I don't support this because signs are often beside the road and not "on" it.

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 2017-05-22 07:46, Marc Gemis wrote: > As for the useage of the data: inventory for towns so they know how > many signs of a particular type are found within the town limits. > Newspapers could use it in "there are X number of signs that need to > be replaced for this new law". Couldn't they

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

As for the forward, backward on nodes. Did you read the discussion on stop signs on the mailing list ? Several people were opposed to it. This seems to be a slightly different way of tagging direction signs. There is also [1], which is visualized by [2] and partially supported by e.g. OsmAnd and

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

Javbw > On May 21, 2017, at 10:36 PM, Colin Smale wrote: > > WHY are we storing traffic signs in OSM? - scene render - completeness (shows that someone has mapped the area very closely) - possible use for warnings - "color" information - welcome to FooBar / FooBar

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 2017-05-21 22:23, yo paseopor wrote: > On Sun, May 21, 2017 at 9:47 PM, Tobias Knerr wrote: > >> I also find it useful to know the exact traffic sign combinations that >> the other tags are derived from, as ambiguities in tagging can cause >> that information to be

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On Sun, May 21, 2017 at 9:47 PM, Tobias Knerr wrote: > On 21.05.2017 14:05, Colin Smale wrote: > > So, in simple language, WHY do we put traffic signs into > > OSM? > > The use case I'm interested in is having the location of the physical > object available, e.g. for 3D

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 21.05.2017 14:05, Colin Smale wrote: > So, in simple language, WHY do we put traffic signs into > OSM? The use case I'm interested in is having the location of the physical object available, e.g. for 3D rendering. This is also why I'm in favour of placing signs in their actual on-the-ground

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On Sun, May 21, 2017 at 8:46 PM, Mark Wagner wrote: > On Sun, 21 May 2017 22:23:12 +0900 > John Willis wrote: > > > > Warning signs - not restriction signs - such as stop ahead, curve > > ahead, falling rock, animals, etc do present a chance for the > >

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 05/21/2017 07:35 AM, Martin Koppenhoefer wrote: > > 2017-05-21 14:05 GMT+02:00 Colin Smale >: > > WHY do we put traffic signs into OSM? > > > > I do it because in the past in many occassions I have found the maxspeed > I had

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On Sun, 21 May 2017 22:23:12 +0900 John Willis wrote: > > Warning signs - not restriction signs - such as stop ahead, curve > ahead, falling rock, animals, etc do present a chance for the > presence of the sign's node to offer a notice to whatever is parsing > the way Data and

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 2017-05-21 15:14, Martin Koppenhoefer wrote: > 2017-05-21 15:09 GMT+02:00 Colin Smale : > >> Basically only d) is related to functionality for the consumer of the data - >> a/b/c are about the OSM-internal process of how we get there. If we don't >> have some view of

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

Javbw > On May 21, 2017, at 8:36 PM, Martin Koppenhoefer > wrote: > > IMHO this linking is done by spatial proximity (and sign orientation). In > reality there are no more indications to where a sign applies than their > proximity and orientation. There is no other

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

2017-05-21 15:09 GMT+02:00 Colin Smale : > Basically only d) is related to functionality for the consumer of the data > - a/b/c are about the OSM-internal process of how we get there. If we don't > have some view of what we want to get out of OSM, then any discussion about

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 2017-05-21 14:35, Martin Koppenhoefer wrote: > 2017-05-21 14:05 GMT+02:00 Colin Smale : > >> WHY do we put traffic signs into OSM? > > I do it because in the past in many occassions I have found the maxspeed I > had mapped, later destroyed by mappers who had merged

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

2017-05-21 14:05 GMT+02:00 Colin Smale : > WHY do we put traffic signs into OSM? I do it because in the past in many occassions I have found the maxspeed I had mapped, later destroyed by mappers who had merged the ways with different maxspeeds back into one way, and I

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 2017-05-21 13:36, Martin Koppenhoefer wrote: > 2017-05-21 13:15 GMT+02:00 Colin Smale : > this can depend on legislation. Usually the end of the restriction should be > signed (or the restriction will already have indications when it will end/to > where it applies,

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

2017-05-21 13:15 GMT+02:00 Colin Smale : > What about the effect on a way or polygon to which the sign actually does > apply? > this will be tagged as we have always done. E.g. a footpath sign: highway=footway. A maxspeed sign? maxspeed=, source:maxspeed=sign, etc. >

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

On 2017-05-21 12:36, Martin Koppenhoefer wrote: > 2017-05-20 11:26 GMT+02:00 yo paseopor : > >> What do you think? > > I'm only using this for cases where I find it important (mostly for other > mappers to understand, where an observation of a sign was made, so they can

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

> On May 21, 2017, at 7:36 PM, Martin Koppenhoefer > wrote: > > I am in favor though to tag the signs as signs (i.e. a node on the position > of the sign) and NOT using sign tags for the interpretation (i.e. the > supposed effect on a way or polygon to which the

Re: [Tagging] Time is now: tag ALL traffic signs in OSM

2017-05-20 11:26 GMT+02:00 yo paseopor : > What do you think? I'm only using this for cases where I find it important (mostly for other mappers to understand, where an observation of a sign was made, so they can better understand the tags of the effects, i.e. from where

[Tagging] Time is now: tag ALL traffic signs in OSM

As you know Mapillary has released a layer with the results of their recognition system of traffic signs to JOSM and iD (I wish OSC will do the same soon) . This means now we have a reliable and open (CC) source to map traffic signs in a easy and complete way inside OSM (instead of the