[All work](/work?type=work)

# TransitSync

TransitSync connected Google Calendar locations with Metlink route planning, keeping the travel problem close to the events that made the journey necessary.

[Routing service source](https://github.com/Slaymish/transitsync-routing)

Independent prototype development. Python, Flask, Google Calendar and Metlink routing.

![Original TransitSync project mark, combining a calendar and a bus above the project name.](https://cdn.sanity.io/images/qnuj1c4o/production/4d2bbf44b02e3b1956e97218ba8de210b42706d9-1024x1024.png?w=960\&q=80\&auto=format)

I worked on a planner for Wellington journeys that started from calendar events, as an event already had the destination and the time I needed to be there, which gave the routing a useful place to begin, with geocoding and nearby-stop lookup connecting the written address to the transit network behind the journey.

The app retrieved events and used a per-user routing service to connect their locations with transit plans, while the separate Python package handled geocoding, nearby stops and departure information.

The preserved version includes calendar integration and routing work, though the proposed multi-user rollout, scheduled syncing and realtime recalculation should be treated as development plans beyond that prototype.

The catalogue date follows the first preserved commit on 5 April 2025.

## Outcome

A calendar-linked routing prototype and a public Wellington transit package. The implementation is preserved separately from the proposed hosted product and its rollout plans.

[All work](/work?type=work)