[OSM-talk] ferry route speed

[Peter Miller]

Traditionally the GIS part (Where are the Stops? / What is the route?) is
managed separately from the schedules themselves. If we define the routes
and the stops in OSM then we should probably leave it to other systems to
handle the timetables (opentimetableservice?).

One handover bit that is worth including is the transport operator's own ID
for each Stop Point.

Google have a simple timetable transfer protocol which might be worth a
looking at.
http://code.google.com/transit/spec/transit_feed_specification.html

Mappers in San Francisco, Portland and a few other places might like to play
with some available schedules in this format.
http://code.google.com/p/googletransitdatafeed/wiki/PublicFeeds



Regards,



Peter 

> -----Original Message-----
> From: talk-bounces at openstreetmap.org [mailto:talk-
> bounces at openstreetmap.org] On Behalf Of Mark Williams
> Sent: 04 September 2008 06:55
> To: Kevin Ryan
> Cc: talk at openstreetmap.org; Gervase Markham
> Subject: [Spam] Re: [OSM-talk] ferry route speed
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Kevin Ryan wrote:
> > Should probably give some indication of the max and min.  Helsinki to
> > Tallinn can be done in about 40-45 minutes during the summer in the fast
> > ferries.  Winter time the fastest is about 4 hours.
> >
> > 2008/9/2 Gervase Markham <gerv-gmane at gerv.net>
> >
> >> Shaun McDonald wrote:
> >>> That low speed is far too low. When I was on the Holyhead to Dublin
> >>> ferries recently, my GPS was giving 45mph for the return journey, and
> >>> 25-30mph for the outward (different ferries, the return was the swift
> >>> fastcraft).
> >> Hmm. Perhaps we need maxcrossingtime and mincrossingtime.
> >>
> >> Gerv
> >>
> >>
> 
> Obviously, not all ferrries are the same. The low speed was indeed to
> account for loading time.
> 
> max & min is fine, but doesn't account for time of day / no ferry for 5
> hours.
> 
> Timetables can vary quite frequently.
> 
> I can't think of any way other than a link to the operator's URL that's
> going to allow this to actually, really, work for timings, so some sort
> of guide value is required - I do think this should be per route not
> generic, the average I alluded to earlier is in the nature of a fix
> because right now, I haven't seen an OSM-based router route on ferries
> at all, so a silly time is better than avoiding it altogether.
> 
> Mark
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFIv3g5JfMmcSPNh94RAsQTAJwKd4ptpImWMsaNTVL56d/yfTjPDQCeLd+M
> T4ahxf+pzvJ4El5XrrRzCGI=
> =OBx3
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk