Re: [Tagging] Kerbs

2017-12-28 Thread Warin
There are many different kerb shapes http://www.playford.sa.gov.au/webdata/resources/files/SD%20100%20TYPICAL%20RESIDENTIAL%20KERB%20PROFILES.pdf https://en.wikipedia.org/wiki/Curb#Types_of_curb kerb:shape=* would be better as it suggests what is to be tagged*. * kerb=* is open to any use, kerb=

Re: [Tagging] Kerbs

2017-12-28 Thread Nick Bolten
That's a really great example of how it may make sense to separate out the idea of a 'curb ramp' from the curb interface. I might have to steal it! On Thu, Dec 28, 2017 at 3:12 PM Selfish Seahorse wrote: > On 28 December 2017 at 23:50, Nick Bolten wrote: > > With that said, I agree that there a

Re: [Tagging] Kerbs

2017-12-28 Thread Selfish Seahorse
On 28 December 2017 at 23:50, Nick Bolten wrote: > With that said, I agree that there are opportunities for improving `kerb` > tags. Here are some ideas to toss around: > > - `kerb=square` would seem to be as descriptive as `kerb=raised`, but more > clear. > > - `barrier=kerb` is sometimes used in

Re: [Tagging] Kerbs

2017-12-28 Thread Nick Bolten
> The question is: does it make sense to introduce another `kerb` value in order to differentiate between standard high kerbs and very high kerbs at public transport stops? If I understand the question right, it really comes down to what you consider to be a curb. Some transit stops have raised pl

Re: [Tagging] Kerbs

2017-12-28 Thread Selfish Seahorse
I agree that `kerb:height` is more useful than `kerb`. However, `kerb` seems to be a good starting point when mapping many kerbs and you can't measure them all yet, as it gives a rough information whether most wheelchair users can cross the street there or not. The question is: does it make sense

Re: [Tagging] Kerbs

2017-12-28 Thread Matej Lieskovský
I'd use "normal" or "regular", leaving "raised" for "above the norm". Both values are quite rare, but I guess that is because most will simply not tag it. Or (as the wiki discussion suggests) use kerb:height in cm. Looks like that wiki page could use updating... Matej Lieskovský On 28 December 2

Re: [Tagging] Kerbs

2017-12-28 Thread Nick Bolten
This kind of info is actually very relevant to all kinds of different pedestrians. There are manual wheelchair users with serious athleticism who are happy with moderate curbs, but can't do tall ones (due to physics - they'd tip before getting over), people with limited mobility who use walkers/can

Re: [Tagging] Kerbs

2017-12-28 Thread Selfish Seahorse
On 28 December 2017 at 20:29, Martin Koppenhoefer wrote: > I think it makes a difference to many wheelchair users or cyclists or > automobilists or most other vehicles and pedestrians whether the kerb is 12 > or 30 centimeters (assuming that meters was a typo, right?). > > Regarding the tag rai

Re: [Tagging] Kerbs

2017-12-28 Thread Graeme Fitzpatrick
On 29 December 2017 at 05:05, Selfish Seahorse wrote: it doesn't make a difference for wheelchair users if the kerb is 12 or > 30 metres high. > I think it would make a difference to everybody if the kerb is 30 metres high! :-) Thanks Graeme ___ Tagg

Re: [Tagging] Kerbs

2017-12-28 Thread Martin Koppenhoefer
sent from a phone > On 28. Dec 2017, at 20:05, Selfish Seahorse wrote: > > I think it makes sense to tag common high kerbs `kerb=raised` too, as > it doesn't make a difference for wheelchair users if the kerb is 12 or > 30 metres high. > > What is your opinion? I think it makes a difference

Re: [Tagging] Kerbs

2017-12-28 Thread Nick Bolten
kerb=raised is a bit subjective, but you can always add kerb:height when in doubt. Another way to look at it is as the shape at the interface: flush = straight on, lowered = approaching linearly at an angle, rolled = rounded, raised = square edge. On Thu, Dec 28, 2017, 12:15 PM Selfish Seahorse w

[Tagging] Kerbs

2017-12-28 Thread Selfish Seahorse
Hi There are conflicting informations on the wiki[^1] whether common high kerbs (example[^2]) can be tagged `kerb=raised` or if this tag is reserved for very high kerbs at public transport stops. [^1]: [^2]:

Re: [Tagging] Variable position

2017-12-28 Thread Matej Lieskovský
I respectfully disagree. The benches are there, quite probably within 10m of their location in the map. While this is abysmal accuracy, it is not entirely wrong. Isn't "there aren't any known benches here" a worse information than being 10m off? That same park has several stone benches that do no

Re: [Tagging] Variable position

2017-12-28 Thread marc marc
Le 28. 12. 17 à 11:05, Matej Lieskovský a écrit : > If we mark the object with a note: >  - an unaware data consumer will see the object with an inaccurate position your proposal has the same defect as those that create objects that do not exist (highway or building for example) and that add tag

Re: [Tagging] Variable position

2017-12-28 Thread Matej Lieskovský
I've thought about it and I believe the option with a note is better. If we tag it on the area: - an unaware data consumer will see just some strange tags - an informed data consumer will know "somewhere in there" If we mark the object with a note: - an unaware data consumer will see the objec