Docs · Analysis tools · Rider propensity

Rider propensity Free

A nationwide Demand Dots map layer that surfaces likely transit demand — population most likely to ride and the jobs they could be commuting to — as dots rendered directly on the basemap. Use it to spot under-served demand pockets when sketching a new route or sizing a flex zone.

GTFS·X editor with the Demand Dots layer enabled, showing colored dots representing high-propensity population and jobs across the Bozeman area.
Demand Dots overlaid on the demo feed. Blue dots: high-propensity adults. Orange dots: jobs. Gray dots: other adults. One dot represents five people (or five jobs).

Where to find it

Demand Dots is a basemap layer toggle, not a sidebar panel. Open the basemap control on the top-right of the map (the small square icon below the zoom controls) and check the Demand Dots box. The dots appear at every zoom level; they're most legible from neighborhood-scale (zoom ~12) to corridor-scale (zoom ~15).

Basemap control panel in the GTFS·X editor showing a Demand Dots checkbox.
The basemap control with the Demand Dots checkbox. Toggling it doesn't change the underlying basemap style — it adds the dot layer on top.

What the dots show

The layer renders three categories of dots, each at a one-dot-equals-five-units density:

The layer is nationwide: every state, plus DC. Alaska and Puerto Rico render the population layers (blue and gray) but not jobs, because LODES isn't published for those jurisdictions.

How to use it

What it isn't

This is a propensity layer, not a ridership forecast. Demand Dots tells you where transit-inclined population and jobs concentrate. It does not predict how many people will ride your route, how that ridership splits by trip purpose, or how it responds to frequency, fare, or competing modes. If your decision needs an actual ridership estimate, you need a ridership model (regional travel demand, direct demand, sketch elasticity) — not this layer. Agencies have spent real money on real mistakes by treating a propensity heatmap as a forecast; don't.

Methodology

Limits

See also