Which robot corridors are busiest with transit?
Transit-stop density varies more than fiftyfold across the tracked corridors. LA West Side is the densest at 2,737 measured OpenStreetMap transit stops, so a delivery robot there shares the sidewalk constantly with waiting and moving transit riders. Atlanta reads lowest at 27 stops, but that is almost certainly OSM under-tagging rather than a true absence: MARTA runs a large network the open map has not fully captured. The honest read is that transit density is a real sidewalk-crowding signal where the open data is complete, and a data-coverage caveat where it is not.
Every figure is measured from OpenStreetMap transit-stop tags. How we verify.
Transit stops, ranked densest first
| Detail | Basis | ||
|---|---|---|---|
| LA West Side | 2,737 | 2,737 OSM transit stops. Highest transit density. | Measured |
| Chicago | 949 | 949 OSM transit stops. CTA+Metra. | Measured |
| SF Core | 727 | 727 OSM transit stops. Muni+BART. | Measured |
| Dallas-Fort Worth | 511 | 511 OSM transit stops. DART. | Measured |
| Miami | 448 | 448 OSM transit stops. Metrobus+Metrorail. | Measured |
| Austin | 288 | 288 OSM transit stops. CapMetro. | Measured |
| Alexandria, VA | 185 | 185 OSM transit stops. DASH+Metrobus+WMATA. | Measured |
| Phoenix | 90 | 90 OSM transit stops. Valley Metro. Low density = car-dependent. | Measured |
| Atlanta | 27 | 27 OSM transit stops. LOWEST. MARTA under-tagged in OSM. | Measured |
Source: OpenStreetMap via Overpass API (transit-stop tags). Counts reflect OSM coverage, which is complete in some metros and under-tagged in others.
Why a low count is a coverage caveat, not a finding
OpenStreetMap is community-tagged, so a corridor with a large real transit network can still show few stops if local mappers have not tagged them. Atlanta at 27 is the clear example: its rail and bus network is large, so the low count is an open-data gap, not a quiet street. Where OSM coverage is complete, the density figure is a real signal of how much a robot shares the sidewalk with transit riders.
Related verified answers
Browse the registryAll verified answers
Every transit-stop count is measured from OpenStreetMap transit tags via the Overpass API and carries the Measured basis. OSM is community-tagged, so a low count can reflect under-tagging rather than a true low, which is stated on every affected row. These are measured-from-open-data facts, not reviewed DEPLOY registry records, so none carries the registry verified chip. How we verify
Related answers
Which robot corridors have the best connectivity?
The measured mobile connectivity scoreboard across the same corridors.
Read article →
Which robot corridors have the most data?
The open-data coverage scorecard, transit density included.
Read article →
How steep are robot delivery corridors?
Measured corridor grade across the same nine corridors.
Read article →
Compare
canonical URL: /which-robot-corridors-are-busiest-with-transit · machine-readable mirror: /which-robot-corridors-are-busiest-with-transit.md