Guten Morgen,
Ich ging bisher davon aus, dass jeder irgendwie genutzte Wald als
landuse=forest getaggt wird. Der Tag natural=wood fuer nicht genutzten
Wald. Dabei ist schon das Wort Nutzung schwierig.
Nutzung kann ueber die reine Holzgewinnung hinausgehen (Schutzwald im
Gebirge, Gruene
To me, the word and tag landuse implies human intervention or intention;
people are using the land or area in a certain way. Natural implies
something hat exists in a state of nature, in other words, not made or
regulated by man. Regardless of prior usage, therefore, I tend to agree
with Werner.
Am 04.10.2013 08:24, schrieb Werner Poppele:
Waelder mit natural=wood sind nach meinem Verstaendnis Urwaelder,
Waelder im Hochgebirge oder Waelder in Nationalparks usw.
Dein Verständnis ist insofern richtig, als es der derzeit herrschenden
Interpretation entspricht, die vor Jahren mal auf eine
Am 04/ott/2013 um 13:18 schrieb Tobias Knerr o...@tobias-knerr.de:
die hier ist Wald und diese Fläche wird forstwirtschaftlich genutzt
voneinander entkoppelt. Früher mal war das der Fall, indem man für
ersteres natural=wood verwendet hat, und für letzteres landuse=forest
ergänzen(!)
Dne 4.10.2013 13:18, Tobias Knerr napsal(a):
Am 04.10.2013 08:24, schrieb Werner Poppele:
Waelder mit natural=wood sind nach meinem Verstaendnis Urwaelder,
Waelder im Hochgebirge oder Waelder in Nationalparks usw.
Dein Verständnis ist insofern richtig, als es der derzeit herrschenden
Thanks all - some great suggestions. To clarify, I'm not looking to put
detailed timetable information in (that properly belongs in a GTFS feed or
somesuch, not OSM), just a broad-brush indication to help routing engines.
Based on Richard M's and Janko's suggestions, I'm tempted to use:
Duration is also important and currently used by OSRM (although not on
relations yet), like http://www.openstreetmap.org/browse/way/176323421
Cheers,
Stefano
___
Tagging mailing list
Tagging@openstreetmap.org
sabas88 wrote:
Duration is also important and currently used by OSRM
Indeed. I actually edited duration out of my OSRM route profile because it
gave misleading results for cycling - the router would often head for the
nearest long-distance ferry, since ferries are often quicker than cycling,
2013/10/4 Richard Fairhurst rich...@systemed.net
To clarify, I'm not looking to put
detailed timetable information in (that properly belongs in a GTFS feed or
somesuch, not OSM), just a broad-brush indication to help routing engines.
That's the beauty of it, my proposed tag can be detailed,
Hi,
what about the headway tag?
This tag is already in use for more than 750 public transport routes (bus,
tram, subway).
The headway time is given in minutes. This is used for multiple departures per
hour and also for only one departure per day.
For only one departure per day a headway of 1440
Richard Fairhurst rich...@systemed.net wrote:
sabas88 wrote:
Duration is also important and currently used by OSRM
Indeed. I actually edited duration out of my OSRM route profile
because it
gave misleading results for cycling - the router would often head for
the
nearest long-distance
I've seen this tag the first time in Orlando bus routes. A mapper tagged all
bus routes there with this tag.
If you think headway is difficult to understand, what tag would you like to
prefer?
Temporary I thought about interval.
Frequency would be a bad solution because this is the reciprocal
On Fri, Oct 04, 2013 at 06:36:33PM +0200, Janko Mihelić wrote:
That said, I like the journeys=3/day, 5/hour. If we decide to go with it, I
can just replace my 3d and 5h with it.
I think that would be sensible. I would never be able to remember what
your notation meant without looking it up each
ael law_ence@ntlworld.com wrote:
On Fri, Oct 04, 2013 at 06:36:33PM +0200, Janko Mihelić wrote:
That said, I like the journeys=3/day, 5/hour. If we decide to go
with it, I
can just replace my 3d and 5h with it.
I think that would be sensible. I would never be able to remember what
Ah, do you mean the signalling headway, or the planning headway or the
operating headway?
:o)
service_interval=nnn would probably be more en-gb
On Fri, Oct 4, 2013 at 6:46 PM, SomeoneElse li...@mail.atownsend.org.ukwrote:
Tilo wrote:
what about the headway tag?
Perhaps a tag that's
One thing that you may also need to consider is that the timetables and
therefore number of journeys a day may depend on the month as there are often
summer and winter timetables.
Regards
Dudley
Date: Fri, 4 Oct 2013 07:28:26 -0700
From: rich...@systemed.net
To: Tagging@openstreetmap.org
If I may insert myself into the conversation. I looked at the
opening_hours syntax recently when learning about parking specifications.
http://wiki.openstreetmap.org/wiki/Key:opening_hours#Syntax
Something like that could be used to specify different frequencies with
time of year.
So it seems, that interval is the better term.
Of course the service headway is meant.
The tagging should be done with routes. Routes are operated on railway lines,
streets or waterways. Only railway lines have signaling headways, not routes.
Bus routes also don't have signaling headways.
If
Dear all,
For shops selling musical instruments, there are currently two tags in use:
shop=musical_instrument and shop=musical_instruments. The singular (1327)
is used nearly 10 times as much as the plural (126). I suggest to confirm
the current situation by formally accepting the tag that is
There are currently various tags for gambling-related shops and amenities
in use, including amenity=casino, shop=bookmaker, shop=betting,
shop=lottery, and shop=gambling. See here for an overview of usage
statistics:
http://wiki.openstreetmap.org/w/index.php?title=Proposed_features/gambling.
20 matches
Mail list logo
