Am 04.10.2013 21:47, schrieb Richard Fairhurst:
John F. Eldredge wrote:
That brings up an issue for routing in general, not
just cycle-routing. The routing algorithm needs
to take into account the day of the week, and what
time it will be when you reach a point with time-
dependent
Am 04.10.2013 00:05, schrieb Martin Koppenhoefer:
maybe you can use service_times? It uses the opening_hours syntax and I
invented it originally for churches, but it might fit here as well ;-)
+1
we should stick to one syntax if possible and the opening_hours' syntax
already includes all
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
Subject: Re: [Tagging] Ferry frequency
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
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
Subject: Re: [Tagging] Ferry frequency
Thanks all - some great
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
I'd like to tag approximate ferry frequency in OSM. It's important for
routing: something that runs every 10 minutes is likely to be useful for
routing purposes; something that runs once a day, less so.
Before I go ahead and JFDI, has anyone done this / seen this done, and
if so, what tags
2013/10/3 Richard Fairhurst rich...@systemed.net
I'd like to tag approximate ferry frequency in OSM. It's important for
routing: something that runs every 10 minutes is likely to be useful for
routing purposes; something that runs once a day, less so.
Before I go ahead and JFDI, has anyone
I use frequency=6 for 6 buses per hour as a tag on a bus route relation.
And journeys=3 for 3 services a day.
Interpreting such tags is always likely to be context-sensitive
Richard
On Thu, Oct 3, 2013 at 10:31 PM, Richard Fairhurst rich...@systemed.netwrote:
I'd like to tag approximate
Yes, that is how I use it - frequency if there's 1/hour or better, journeys
if it's less than that.
On Thu, Oct 3, 2013 at 11:35 PM, John F. Eldredge j...@jfeldredge.comwrote:
Richard Mann richard.mann.westoxf...@gmail.com wrote:
I use frequency=6 for 6 buses per hour as a tag on a bus route
I have been talking about this on the transit mailing list[1]. I formed a
tag that gives us a number of journeys in any given period. It is very
flexible, and can be simple and complex.
For example, if we want to say there are 3 journeys a day, we would simply
have:
public_transport:frequency=d3
20 matches
Mail list logo
