As a data consumer, +1 to the idea of highway=service,
service=escape_lane. This combo is enough information to avoid any
confusion about what the purpose of the way is, while also fitting
with existing common data/render schemes. To be absolutely safe with
regard to routing, an appropriate dissuas
I agree this should be highway=service, service=escape_lane.
Also note, if I'm thinking of the right thing, in the US this is usually
called a "runaway truck ramp". This phrase should appear in the feature
docuentation somewhere.
___
Tagging mailing lis
Eric,
The English version did say that at one point, as well, before it was
changed back to the current definition. Maybe the French one was copied
from it during that period.
Stephen
On 13 October 2012 04:49, Eric SIBERT wrote:
>
>> Indeed, as pointed out by Martin, I have to use lanes=1. I
2012/10/12 Martin Koppenhoefer :
> 2012/10/12 Eric SIBERT :
>> No. It would indicate that it can't be used by vehicles.
sorry, I got you wrong here, thought you wanted to exclude them (foot-bridge).
cheers,
Martin
___
Tagging mailing list
Tagging@open
2012/10/12 Eric SIBERT :
> No. It would indicate that it can't be used by vehicles.
if there are no legal restrictions one step or also 2 won't be an
unsurmountable obstacle for most vehicles.
cheers,
Martin
___
Tagging mailing list
Tagging@openstreet
you could use lanes=1 on the narrow parts.
Agree.
- a bridge or a raft with a bad link to the road/track i.e. a step at each
end of the bridge/raft. obstacle=unevenness ? or obstacle=step? For me
unevenness is to soft for what you describe.
split the way and put a short highway=steps, step
- a narrow bridge i.e. you can't cross a vehicle in opposite
direction. We may use width=* but it is difficult to get it
precisely. obstacle=narrowness
It's slightly offtopic, but wouldn't it be logical to use "car" as a non
accurate unit of length? So you can have a tag like "width=
Hi
In the UK local authorities are responsible for public rights of way. Paths,
bridleways etc. There are so called Best Value Performance Indicators (BVPI)
that require them to survey a certain % length of these each year to measure
the ease of use of the network.
Documentation and forms f
Maybe, but I think we shouldn't tag strips of road which are not intended for
driving in any way but for stopping as highway=service.
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap
I think we should work on making it easier to link to OSM from outside.
People can discuss which entities should and should not be a part of
the map as opposed to being part of an external database. The same
issue came up with regard to ferry schedules and whether they should
be included in the ma
On 12/10/2012 16:38, José Juan Sánchez del Arco wrote:
I have updated an old proposal, relating to highways, escape lanes for
trucks and cars alongside motorways to stop them. Please visit the
proposal page:
http://wiki.openstreetmap.org/wiki/Proposed_features/escape_lane
I think this is just a
Hi Tobias,
Am Freitag, 12. Oktober 2012, 13:13:47 schrieb Tobias Knerr:
> New players should indeed be treated the same as dominating platforms
> (see Flickr): If they want OSM integration, they should link to OSM, not
> the other way around.
well, except that linking to OSM is notoriously diffic
On 12/10/2012 09:57, Pieren wrote:
On Fri, Oct 12, 2012 at 10:15 AM, Simone Saviolo
wrote:
I think that contact info of an amenity (allow me to group shops,
restaurants, bars, and companies under that umbrella just for a minute)
should be considered all of equal importance.
They are amenities
2012/10/12 Eric Sibert :
> - a narrow bridge i.e. you can't cross a vehicle in opposite direction. We
> may use width=* but it is difficult to get it precisely. obstacle=narrowness
you could use lanes=1 on the narrow parts. "narrowness" is a very
relative concept and I wouldn't encourage you to u
2012/10/12 Eric Sibert
> - a narrow bridge i.e. you can't cross a vehicle in opposite direction. We
> may use width=* but it is difficult to get it precisely. obstacle=narrowness
>
It's slightly offtopic, but wouldn't it be logical to use "car" as a non
accurate unit of length? So you can have a
Hi,
During my last travel in Africa, I was thinking on how to map
obstacles on road. So I support your proposal but in a generalized
way, not only for pedestrian or bicycle. And I take the opportunity to
review what I observed:
- a narrow bridge i.e. you can't cross a vehicle in opposite
On 11.10.2012 20:52, Alexander wrote:
> I am trying to establish a standard for external links to various
> platforms (including but not only facbook, qype, foursquare etc.)
[...]
> I wouldn't like to limit the tagging to these dominating platforms. New
> players should be threaten equally. Maybe t
2012/10/12 Pieren
> On Fri, Oct 12, 2012 at 11:08 AM, Simone Saviolo
> wrote:
>
> > by that reasoning, we should remove all the bars, all the shops, all the
> > restaurants, all the companies, all the fuel stations, all the parking
> > information (a free parking may become a ticket-only parking
2012/10/12 Pieren :
> Read my post carefully. I'm not asking to remove anything. I'm saying
> that most of this information is quickly outdated in OSM and that
> other services like google are doing it better than us.
yes, others (like Apple) are doing worse ;-) Unfortunately neither of
them lets
2012/10/12 Pieren :
> On Fri, Oct 12, 2012 at 10:15 AM, Simone Saviolo
> wrote:
>
>> I think that contact info of an amenity (allow me to group shops,
>> restaurants, bars, and companies under that umbrella just for a minute)
>> should be considered all of equal importance.
>
> They are amenities
On Fri, Oct 12, 2012 at 11:08 AM, Simone Saviolo
wrote:
> by that reasoning, we should remove all the bars, all the shops, all the
> restaurants, all the companies, all the fuel stations, all the parking
> information (a free parking may become a ticket-only parking), all the names
> of the build
2012/10/12 Pieren
> On Fri, Oct 12, 2012 at 10:15 AM, Simone Saviolo
> wrote:
>
> > I think that contact info of an amenity (allow me to group shops,
> > restaurants, bars, and companies under that umbrella just for a minute)
> > should be considered all of equal importance.
>
> They are ameniti
On Fri, Oct 12, 2012 at 10:15 AM, Simone Saviolo
wrote:
> I think that contact info of an amenity (allow me to group shops,
> restaurants, bars, and companies under that umbrella just for a minute)
> should be considered all of equal importance.
They are amenities that stay for long time like po
2012/10/12 Eugene Alvin Villar
> However, I personally don't think your example of putting the URLs to
> a place's webpage on foursquare, Google+, Yelp, TripAdvisor, etc. is
> the way to go.
>
> OSM is not a link directory so adding many such links on the OSM
> database doesn't seem appropriate.
24 matches
Mail list logo