GMPTE GTFS Schedule Data

[Christopher Osborne]

Hello there OpenDataGMers

To help the community develop more transport applications, we have
released a GTFS export of the GMPTE schedule data on the DataGM site:

http://datagm.org.uk/package/gmpte-gtfs-schedule-data

This is a mostly untested GTFS export of the schedule data released by
GMPTE. We know there are a few bugs in there, we have detected: 192
partial duplicate Metrolink journeys and 452 partial duplicate bus
journeys in the source data, and the date ranges are not reliable.
This is not suitable for a publicly released app, but will give you
what you need to so start prototyping.

I thought we'd throw this one out to the ODM group, see if there's any
demand, and then work out what fits with the community without
committing ourselves to anything right now. For starters we have
released this one-off export and will consult with GMPTE to see what
their views are on the matter.

I'd like to repeat that we're not committing to anything just yet, but
exploring possibilities from having the data in a more accessible
format. All of the open source trip planners etc that I've seen are
GTFS based so I believe it should push things forward a great deal.

Have fun making things and let us know what you do with the data!

[aph]

Thanks Chris.

I was doing my own conversion but one route at a time (see
https://groups.google.com/group/opendatamanchester/t/c4bb9f78f32ae132?hl=en).
A full set is probably more useful.

I did manage to validate your data (using
http://code.google.com/p/googletransitdatafeed/wiki/FeedValidator)
and there are a few errors which are probably down the source data
rather than
the conversion. Some errors identified include

1. Timetravel detected where arrival time is before the departure time
2. Too fast travel where the time between two timing points is deemed
too short such
that the speed is unbelievable (e.g. 500 Km/h)

Will have a play with your data and see whether I can do something
useful with it!

Regards

Anthony

On Mar 4, 11:28 am, Christopher Osborne <chris.gai...@gmail.com>
wrote:

[Christopher Osborne]

Hi Anthony

We did see a few errors in the source data, particularly to do with date ranges. Let me know what you come up with.

[Christopher Osborne]

We have just uploaded a new version, where the stop_id's now match ATCO Codes. This will match with other regional datasets as they become available in the future.