Talk:Key:incline/Archive 1
Jump to navigation
Jump to search
don't use highway tag
please don't use highway tag for an incline--I suggest using:
- incline = [up|down] (it's not a good idea to change the direction of a way if the way is for example a oneway)
- incline_steep = <number, default %>
please see my comment on Talk:Proposed features/Incline - I just don't have the time to start another proposal (anybody wants to? You're welcome :) -- Schusch 23:26, 14 December 2008 (UTC)
up/down
There are some situations (e.g. steps) where you simply want to specify whether a way goes up or down and don't have precise percentages available. What do people think about using non-numeric inclines such as incline=up and incline=down for that? Using the same key seems natural because you will never use both: As soon as you know that it's a 10% incline, you don't need the vague incline=up anymore. --Tordanik 13:11, 2 April 2009 (UTC)
- How about the same method that always works: Estimate the incline percentage and leave a FIXME=incline estimated?! Lulu-Ann
- Well, that works, too, but it's not machine readable. An application that reads incline=50% + FIXME=incline estimated will assume an incline of 50% (that can easily be quite wrong) and ignore the FIXME tag. Whether that matters depends on the accuracy of my estimate. I could, for example, add up/down values for most steps in my area from memory, but I'm unable to even roughly estimate incline without going there. --Tordanik 16:37, 3 April 2009 (UTC)
- Of course it is not machine-readable in all cases, and of course an estimation is not readable by a person in a wheelchair. It's a "maybe you can go there", and the FIXME tag is the easiest way do make someone go there soon and check it.
- If you need a standard value for estimation use 7%. 6% is the maximum that is recommended for German streets for wheelchair use, so any routing for wheelchairs will not use the route. --Lulu-Ann 07:30, 6 April 2009 (UTC)
- I'm not suggesting to use incline=up for "normal" roads anyway. I'd use it for features such as steps where most renderings/applications are not really interested in exact inclines, but simply want to know which of the two possible "up" directions applies. Floor plans etc. are much more likely to contain that information (as arrows or similar rendering) than an exact percentage value. --Tordanik 12:48, 6 April 2009 (UTC)
- Well, that works, too, but it's not machine readable. An application that reads incline=50% + FIXME=incline estimated will assume an incline of 50% (that can easily be quite wrong) and ignore the FIXME tag. Whether that matters depends on the accuracy of my estimate. I could, for example, add up/down values for most steps in my area from memory, but I'm unable to even roughly estimate incline without going there. --Tordanik 16:37, 3 April 2009 (UTC)
- A way to indicate incline direction period is a good idea. Looking at any piece of OSM data, this is something that simply cannot be estimated, and it also proves useful for other ways, such as steps. The obvious solution is to use a mechanism similar to oneway=*. Circeus 19:44, 21 April 2009 (UTC)
- I'm also in favor of using incline=up and incline=down because it is much easier to add (you need to think less) and so would be much more popular than a concrete % or ° number, which furthermore could lead to edit wars of people changing around numbers... Maybe however I think we should have a seperate key for up/down instead of using incline. Often an easy solution is best. The value wether a way goes up or down is of imminent importance for mtb autorouting. As the difficulty is given by other tags, knowing whether a way goes up or down is all that is needed. Exact % or ° are not.--Extremecarver 11:40, 1 June 2009 (UTC)
- Without percentage this tag is useless for wheelchair users. --Lulu-Ann 09:10, 2 June 2009 (UTC)
- People knowing percentage can add it later. But wheelchair users won't be using paths in mountain settings that swindle up or down with 15-25° anyhow.
- The case of wheelchair acessibility is in fact simpler than what you think: there are specific equipment for them (such as an incline ramp added to facilitate the passage over steps). The incline may still be steep (more than 30%) but this won't be a problem for just a single step. Longer ramps with smaller incline angles (possibly with intermediary flat sections) are needed for more steps.
- But along streets, there's little that can be done, except having larger footways and keeping some flat sections (even if this means a bit steeper angles elsewhere) to limit efforts and allow resting, or allowing the footway to "zigzag" without haing to go to the area used by vehicles. When a ramp is not possible, there are elevators.
- When such equipement is present, we can safely ignore tagging the rest: it's important ten that the map displays these equipments intended for making the place accessible. Only in absence of equipement, we must be more careful for inclines of more than about 5% in narrow footways, and we must tag the presence of steps. — Verdy_p (talk) 17:30, 29 May 2015 (UTC)
- People knowing percentage can add it later. But wheelchair users won't be using paths in mountain settings that swindle up or down with 15-25° anyhow.
- Without percentage this tag is useless for wheelchair users. --Lulu-Ann 09:10, 2 June 2009 (UTC)