Public Transit Schedule Encoding

For want of a schedule API from the Amsterdam public transit authority GVB, I came up with a simple encoding for one schedule, which is a combination of stop, route and direction. For example, to describe the entire ferry schedulefor Amsterdam Central Station to Buiksloterweg, you would need two endoded schedule objects (ESOs):

Public Transit Schedule Encoding

Backlink: http://oegeo.wordpress.com/2010/11/26/public-transit-schedule-encoding/

VeryFurryFerryFairy – A Case For Open Transit Data

I take the ferry from the center of Amsterdam to Noord, the part of the city on the far end of the IJ where I live, at lot. For cyclists and pedestrians, it is the only way to get from Noord to the city and vice versa. There is a total of five ferry routes, all with different schedules for weekdays, Saturdays and Sundays. One of the ferries operates on a round-the-clock schedule, the others cease service around midnight. Too much to remember even for the seasoned ferry traveler.

VeryFurryFerryFairy – A Case For Open Transit Data

Backlink: http://oegeo.wordpress.com/2010/11/26/veryfurryferryfairy-a-case-for-open-transit-data/

Google Transit Program and Mobile Transit apps – A Starting Point for public transit

No doubt many if not most of you are familiar with the Google Maps transit layers – this is a layer of data found in Google maps showing readers current/live public transit data and more. I can’t help to think  that in this day and age where the public, developers, industry and more are clamoring [...]

Google Transit Program and Mobile Transit apps – A Starting Point for public transit

Backlink: http://blog.gisuser.com/?p=8134