Re: [OSM-talk] HDYC, login requirement and "privacy"

2017-05-07 Thread Christoph Hormann
On Sunday 07 May 2017, Frederik Ramm wrote: > > It is a common issue in OSM (and elsewhere) for people to use the > status quo as a reason. "Admin boundaries are not visible on the > ground and they are mapped, THEREFORE I can also map everything else > that is not visible on the ground" - no! And

Re: [OSM-talk] HDYC, login requirement and "privacy"

2017-05-07 Thread Frederik Ramm
Hi, On 07.05.2017 22:54, Nicolás Alvarez wrote: > Yet I don't know of any such platform that has rules on how such > metadata can be used, and I don't see anyone here arguing that we need > rules on the use of mailing list archive metadata. One thing at a time. Pascal's request for identifying yo

Re: [OSM-talk] HDYC, login requirement and "privacy"

2017-05-07 Thread Nicolás Alvarez
2017-05-05 6:59 GMT-03:00 Frederik Ramm : > Today, if you are looking for a job and you're being interviewed by a > potential employer, the potential employer could say: "I can see from > OpenStreetMap that you've been editing a lot during the day in your last > job. Did you not have any work to do

Re: [OSM-talk] HDYC, login requirement and "privacy"

2017-05-07 Thread moltonel
On 4 May 2017 22:33:47 IST, Frederik Ramm wrote: >It doesn't matter that anyone can sign up and then view that data; we >can at least make people promise to only use the data for project >internal use when they sign up. While I'm not looking forward to having to login to use various tools, I

Re: [OSM-talk] Revisiting traffic control and traffic calming

2017-05-07 Thread Jo
2017-05-07 9:30 GMT+02:00 Paul Johnson : > On Sun, May 7, 2017 at 2:25 AM, Jo wrote: > >> What about a type=traffic_sign relation? >> >> Where traffic_sign could be stop, give_way, parking >> > > I was thinking the typical highway=* tags for highway=stop, > highway=traffic_signals and highway=giv

Re: [OSM-talk] Revisiting traffic control and traffic calming

2017-05-07 Thread Paul Johnson
On Sun, May 7, 2017 at 2:25 AM, Jo wrote: > What about a type=traffic_sign relation? > > Where traffic_sign could be stop, give_way, parking > I was thinking the typical highway=* tags for highway=stop, highway=traffic_signals and highway=give_way. > In case of a stop sign, we could include th

Re: [OSM-talk] Revisiting traffic control and traffic calming

2017-05-07 Thread Jo
What about a type=traffic_sign relation? Where traffic_sign could be stop, give_way, parking. We can put a traffic_sign tag on nodes, where they get the country_code:specific_national_code like BE:C1. Several traffic signs can have an effect on several ways and nodes of the road network, so we co

Re: [OSM-talk] Revisiting traffic control and traffic calming

2017-05-07 Thread Paul Johnson
On Sun, May 7, 2017 at 2:12 AM, Nicolás Alvarez wrote: > > Do you know of a case where you would have a traffic calming device > only affecting one direction, but not already have a reason to map > each road direction as a separate way? > Somewhat commonly. Oklahoma and Texas have a strong tende

Re: [OSM-talk] Revisiting traffic control and traffic calming

2017-05-07 Thread Nicolás Alvarez
2017-05-07 3:57 GMT-03:00 Paul Johnson : > I think it's time that we seriously reconsider how stop signs, yield signs > and traffic calming devices are handled in all but the most simple (all > approaches to the affected node apply) cases. This largely after having a > protracted discussion with o

[OSM-talk] Revisiting traffic control and traffic calming

2017-05-07 Thread Paul Johnson
I think it's time that we seriously reconsider how stop signs, yield signs and traffic calming devices are handled in all but the most simple (all approaches to the affected node apply) cases. This largely after having a protracted discussion with one person about nodes lacking direction and this