About MapMagpie
Why we're building one map for transit operations.
Magpies are famous for collecting the shiny bits. MapMagpie does the same for transit agencies: it gathers every schedule, live feed and vehicle position your vendors already produce and puts them on one map that the whole team can work from.
Why we started
Most agencies run their network across a handful of systems that don’t talk to each other: one for scheduling, one for AVL, one for passenger information, and a spreadsheet to reconcile them. Planners can’t easily see what actually ran, and dispatchers can’t easily see what was planned.
We think the answer isn’t another silo. It’s a map that speaks the standards the industry already shares, GTFS and GTFS-realtime, and keeps a complete record of everything that happened, so the plan and the reality finally sit side by side.
What we believe
- Your data is yours. Everything you put in comes back out, in open formats, whenever you want it.
- Standards over integrations. If your vendor publishes GTFS, MapMagpie already works with it.
- Built for the control room. Fast, clear and calm under pressure, on the screens operators really use.
- Accessible by default. We build towards WCAG 2.1 AA, because the tools public agencies use should be usable by everyone who works there.
Where we are
MapMagpie is early and working closely with a small number of agencies. If you’d like to help shape it, get in touch.