From Street Reality to Strategic Intelligence

Behind every overcrowded matatu and hand-painted route sign lies critical transit intelligence. Our platform captures this data with precision and speed, creating the GTFS feeds, datasets, and strategic insights that transform how cities move.

RouteLab's Field Ops: the day's researchers on a live map, with an attention list of who is late, missed or unconfirmed
In the office · Field Ops
Observer confirming a researcher has arrived at Ramses Square and may start the survey
In the field · Observer

The problem

Why transit data is hard to get right

The network isn't written down

In most paratransit cities no one holds a list of routes, stops or terminals. Before anyone can plan, the network has to be found on the street.

Field data that won't hold up

Surveys started in the wrong place or at the wrong time, and records lost on the way back, surface weeks later in cleaning — too late to collect again.

Large teams, no overview

Dozens of researchers coordinated over chat groups and spreadsheets: no one can see who is where, who is late, or what is left to collect.

How a programme runs

From plan to network model, in one system

Five stages, each with the screens that do the work.

  1. 01

    Plan

    Coverage targets by route and time, and a dispatch planner that flags overloaded days and impossible orders before anyone leaves.

    • Coverage targets per route and interval
    • A day plan per researcher
    • Warnings before the day starts
    The dispatch planner's day view: each researcher's assignments against the remaining coverage
    Coverage targets by route and time interval
  2. 02

    Collect

    Observer, the field app: guided surveys that start only at the right place and time, and keep every record offline.

    • Surveys open on arrival
    • Every stop, boarding and departure
    • Nothing lost without signal
    An onboard trip in progress in Observer, with its stops on the map and the passenger tally
    Observer confirming a researcher has arrived at Ramses Square and may start the survey
  3. 03

    Monitor

    Field Ops shows every researcher on a live map, and who is late, at risk or missing — while it can still be fixed.

    • An attention list, ranked
    • A case's full story
    • Replay a researcher's track
    Field Ops with a case open: the researcher, the window and what is wrong
    Field Ops investigate mode: a researcher's track played back on the map
  4. 04

    Validate

    Every onboard trip is reviewed — its trace, its stops — and accepted or rejected before it reaches you.

    • Trace and stops side by side
    • Accept or reject, with a reason
    • Map-matched to the road network
    An onboard trip open for review: its trace, stops and passenger counts
    Onboard traces map-matched to the road network, trip by trip
  5. 05

    Deliver

    A network model of routes, terminals and stops, with headways from frequency surveys and origin–destination flows from onboard surveys.

    • Routes, terminals and stops
    • Headway distributions
    • Origin–destination flows
    The network model: routes, terminals and stops on the map
    Origin–destination analytics: the OD matrix and its flow map
The dispatch planner's day view: each researcher's assignments against the remaining coverage
Coverage targets by route and time interval
An onboard trip in progress in Observer, with its stops on the map and the passenger tally
Observer confirming a researcher has arrived at Ramses Square and may start the survey
Field Ops with a case open: the researcher, the window and what is wrong
Field Ops investigate mode: a researcher's track played back on the map
An onboard trip open for review: its trace, stops and passenger counts
Onboard traces map-matched to the road network, trip by trip
The network model: routes, terminals and stops on the map
Origin–destination analytics: the OD matrix and its flow map
  1. The dispatch planner's day view: each researcher's assignments against the remaining coverage
    01

    Plan

    Coverage targets by route and time, and a dispatch planner that flags overloaded days and impossible orders before anyone leaves.

  2. An onboard trip in progress in Observer, with its stops on the map and the passenger tally
    02

    Collect

    Observer, the field app: guided surveys that start only at the right place and time, and keep every record offline.

  3. Field Ops with a case open: the researcher, the window and what is wrong
    03

    Monitor

    Field Ops shows every researcher on a live map, and who is late, at risk or missing — while it can still be fixed.

  4. An onboard trip open for review: its trace, stops and passenger counts
    04

    Validate

    Every onboard trip is reviewed — its trace, its stops — and accepted or rejected before it reaches you.

  5. The network model: routes, terminals and stops on the map
    05

    Deliver

    A network model of routes, terminals and stops, with headways from frequency surveys and origin–destination flows from onboard surveys.

Observer, the field app

Field data you can trust — checked where it is collected

  • At the right place

    A survey starts at its terminal — or not at all.

  • At the right time

    Every observation carries a time you can rely on.

  • Nothing lost

    Built for places with no signal.

  • Every record accountable

    Know who recorded what — and review it.

See how Observer enforces it →

Built and used by

RouteLab is the system Transport for Cairo built and uses to run its own surveys — supported by the engineers who build it.

Run your next survey programme on RouteLab

Start in the app, or tell us about your project and we'll walk you through it.