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] rail routes and stations (rail question 1)

2017-05-19 17:48 GMT+02:00 Michael Reichert : > As a railway mapper, I must admit that there is no tag to indicate that > a station with railway=station is a passenger-only station. The opposite > is possible to tag, use railway=yard. > Looking at the wiki definition, it

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] Australian Solar Challenge Race

2017-05-19 15:21 GMT+02:00 Tijmen Stam : > I think we should NOT tag these kinds of one-off routes, with no visible > trace on the ground. I am not sure about this Australian one, but sometimes there will actually be "traces on the ground", also after the event. E.g. the

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

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

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

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

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] rail routes and stations (rail question 1)

+1 to improved tagging for railways and happy to help! Bjoern On Sun, 21 May 2017 at 13:11, Martin Koppenhoefer wrote: > > 2017-05-19 17:48 GMT+02:00 Michael Reichert : > >> As a railway mapper, I must admit that there is no tag to indicate that >> a

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

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] Australian Solar Challenge Race

On 21-05-17 14:27, Martin Koppenhoefer wrote: 2017-05-19 15:21 GMT+02:00 Tijmen Stam >: I think we should NOT tag these kinds of one-off routes, with no visible trace on the ground. I am not sure about this Australian one, but

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

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

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 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 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, 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 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