Re: [OSM-talk] Help - how to get rid of wrong image in wiki?

2018-12-19 Thread Paul Norman
On 2018-12-19 11:25 p.m., Maarten Deen wrote: And the image is not entirely wrong, it's an example of a reversible oneway street. https://en.wikipedia.org/wiki/Lions_Gate_Bridge The Lions Gate Bridge and Stanley Park causeway are not one-way. The middle lane switches direction, but there is

Re: [OSM-talk] Help - how to get rid of wrong image in wiki?

2018-12-19 Thread Maarten Deen
On 2018-12-19 22:30, Richard wrote: the example image in https://wiki.openstreetmap.org/wiki/Tag:oneway%3Dreversible is clearly wrong but aparently isn't mentioned referenced anywhere in the source of the page. Am I blind? Does it perhaps come from https://wiki.openstreetmap.org/wiki/Item:Q57

[OSM-talk] Help - how to get rid of wrong image in wiki?

2018-12-19 Thread Richard
Hi, the example image in https://wiki.openstreetmap.org/wiki/Tag:oneway%3Dreversible is clearly wrong but aparently isn't mentioned referenced anywhere in the source of the page. Am I blind? Does it perhaps come from https://wiki.openstreetmap.org/wiki/Item:Q5736 ?? How the hell can I get rid

Re: [OSM-talk] Grab using OSM Data for route preview

2018-12-19 Thread Christoph Hormann
On Wednesday 19 December 2018, Martin Koppenhoefer wrote: > > bist Du nicht im advisory board? Hast Du mind 1 Eur bezahlt? > Kommt mir unwahrscheinlich vor ;-) Oder bringe ich da was > durcheinander? I am on the AB because the FOSSGIS sent me there (and neither i not the FOSSGIS paid anything

Re: [OSM-talk] Grab using OSM Data for route preview

2018-12-19 Thread Martin Koppenhoefer
Am Mi., 19. Dez. 2018 um 11:28 Uhr schrieb Simon Poole : > Please get your quotes correct. mea culpa, they must have changed something in the UI :o ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Grab using OSM Data for route preview

2018-12-19 Thread Simon Poole
Please get your quotes correct. On 19.12.2018 10:51, Martin Koppenhoefer wrote: > Hallo Christoph, > > bist Du nicht im advisory board? Hast Du mind 1 Eur bezahlt? Kommt mir > unwahrscheinlich vor ;-) > Oder bringe ich da was durcheinander? > > Gruß, Martin > > sent from a phone > >> On 19.

[OSM-talk] Insufficient map attribution by global players, WAS Re: Grab using OSM Data for route preview

2018-12-19 Thread Martin Koppenhoefer
sending again sent from a phone > On 19. Dec 2018, at 09:33, Ervin Malicdem wrote: > > But still, the issue remains that when the community does not care about > these violations, then we are prone to such instance over and over. I wholeheartedly agree, people traditionally had not to fear

Re: [OSM-talk] Grab using OSM Data for route preview

2018-12-19 Thread Martin Koppenhoefer
Hallo Christoph, bist Du nicht im advisory board? Hast Du mind 1 Eur bezahlt? Kommt mir unwahrscheinlich vor ;-) Oder bringe ich da was durcheinander? Gruß, Martin sent from a phone > On 19. Dec 2018, at 10:42, Simon Poole wrote: > > A seat on the advisory board requires at least a "gol

Re: [OSM-talk] Grab using OSM Data for route preview

2018-12-19 Thread Simon Poole
The LWG has added a work item for 2019 to update the guidance on attribution. The major part of the existing texts were written in the ramp up to the licence change in 2012 and are now over 6 years old.  Lots of things have changed massively since then, be it the scope of OSM usage, to what kind o

Re: [OSM-talk] Grab using OSM Data for route preview

2018-12-19 Thread Frederik Ramm
Hi, On 19.12.2018 09:33, Ervin Malicdem wrote: > I just hoped before they were given a seat as part of OSMF's ADVISORY > board, these issues had been handled. 500 euros seems to clear all that > history so soon. A seat on the advisory board requires at least a "gold" level membership which costs

Re: [OSM-talk] Grab using OSM Data for route preview

2018-12-19 Thread Ervin Malicdem
They have been known NOT to attribute OSM since over 4 years back. [1] Unfortunately, our community leaders back then is more assertive in other ways than those who potentially violate the attribution guidelines. They were notified but instead of replying back for a resolution, they ceased using t