Compare Missouri demand evidence

REVIEW SNAPSHOT · not refreshing

Current data · Explicit review sample

Last collection attempt: Sep 26, 2026, 8:38 AM Central. Evidence evaluated at capture time.

All ten study areas in one place. This is a research coverage comparison, not a ranking of rides or investment returns. No verified area-wide Uber/Lyft/taxi totals are available in this view.

Owner current collection · Download observation worksheet

Three separate decisions

• Historical patterns: choose areas worth evaluating for parking.
• Upcoming activity: plan observation and possible staging windows.
• Actual operations: later compare requests, paid miles, empty miles and net contribution, subject to network rules.

“Not in this regional feed” does not mean no sources exist: existing airport, transit and venue checks appear above for signed-in owners. A recently collected source may still cover only part of the forecast horizon. Event windows cover up to 60 days; they are not comparable ride volumes. Multiple windows may belong to one event.

Low-cost observation pilot

1. Start with South County, St. Charles and O’Fallon. Pick one legal public observation spot per area; record the exact spot privately.
2. Before visiting, record the expected busy period, the reason and a source. Pair it with an ordinary period at the same spot, preferably the same weekday and clock time on another week.
3. Observe each period for 30 minutes. Aim for three paired visits per area as an exploratory first pass. Log weather, overlapping events, blocked curb access and visibility.
4. Count clearly identifiable taxi/rideshare pickups separately from unclassified passenger pickups. Do not infer app orders, collect plates, or track individual passengers. Keep missing counts blank; use zero only after a complete observation with none seen.
5. Compare only equally covered visits. A curbside count measures that spot and interval, not an entire area or total unmet demand. Repeated differences help select the next pilot; they do not establish causation.

Year-round historical activity

Facility encounters are not unique people, local residents, taxi trips or RoboGO customers. Categories can overlap; do not sum them or convert them into rides.

Context source: connected; last successful check Sep 26, 2026, 8:38 AM. Historical facility encounters, not unique people or ride demand; categories may overlap. Monthly recheck.

Year-round evidence still needed

Households without vehicles, employment concentrations, hotels, hospitals and transit usage can help explain ordinary activity. These need dated official sources, exact geography and uncertainty before being added as numbers. Census household retrieval currently requires an API key. Hotel and employment figures remain unverified for individual study areas. No estimates were invented.

When this can guide parking

Combine repeated observations with verified access, round-trip staging distance, rent and operating costs. Evaluate saved empty-mile costs separately from any additional ride contribution. Nearby cars are not guaranteed priority dispatch. Keep low/base/high assumptions until real operation validates them.