Data Sources

The open feeds behind the demand surface

Mobvynt normalizes and fuses four public data streams your agency already operates. No proprietary location tracking, no video storage, no personally identifiable information collected or retained.

4 open data stream types
30s GTFS-RT refresh interval
0 PII records stored
Transit

GTFS & GTFS-RT

General Transit Feed Specification (static and real-time) is the foundation of the Mobvynt demand surface. Static GTFS provides the route, stop, and schedule skeleton; GTFS-RT adds live vehicle positions, trip updates, and service alerts at 30-second intervals.

  • GTFS 2.0 static: routes, stops, trips, stop_times, shapes, calendar
  • GTFS-RT: VehiclePositions, TripUpdates, ServiceAlerts feeds
  • Automatically detected from public GTFS sources or direct agency API
  • Historical boardings from AVL systems (where agency data share agreement exists)
ProtocolGTFS 2.0 / Protocol Buffers
Static refreshOn agency publish (typically weekly)
RT refresh30-second polling
CoverageAny agency publishing public GTFS
Bike-share

Bike-share GBFS

General Bikeshare Feed Specification (GBFS) provides dock status, vehicle availability, and trip origination data. Combined with transit demand, GBFS reveals first/last-mile connectivity patterns and modal substitution zones.

  • Station status: dock availability, charging status, vehicle count
  • Trip origination and destination aggregated at H3 resolution
  • Geofencing zones for dockless fleet area awareness
  • Compatible with all major shared mobility operators supporting GBFS 2.3
ProtocolGBFS 2.3 JSON feeds
Refresh15-second station status
Trip dataOrigin/destination aggregates (no individual)
PIINo user-level data retained
Traffic

Intersection Camera APIs

Aggregated vehicle and pedestrian counts from existing intersection camera systems via REST and NTCIP APIs. No video is stored or transmitted — only the counts your traffic management center already generates.

  • Vehicle volumes by movement (through, left, right) per 15-minute interval
  • Pedestrian volumes per crosswalk phase
  • Compatible with major ATMS platforms exposing NTCIP 1211 or REST count endpoints
  • No video footage transmitted or stored at any point
ProtocolsREST API / NTCIP 1211
Granularity15-minute count intervals
Data typeAggregated counts only
VideoNever stored or transmitted
Demographics

LEHD & ACS Census Data

Employment density (LEHD LODES 8) and commute pattern context (ACS 5-year estimates) provide the socioeconomic layer for equity analysis and demand interpretation. Used exclusively for spatial aggregation context — not individual record matching.

  • LEHD LODES 8: jobs by block group, industry sector, worker home location
  • ACS 5-year: commute mode, household income, vehicle availability by block group
  • Equity overlay: identifies Title VI protected populations in coverage gap zones
  • Annual refresh aligned with Census publication cycle
EmploymentLEHD LODES 8 (annual)
DemographicsACS 5-year estimates
Spatial unitBlock group → H3 resolution 8
UpdateAnnually on Census release

Connect your agency's data feeds

Most transit agencies can connect their public GTFS endpoint and see initial demand surface results within 30 minutes. Bike-share GBFS and camera API integrations are configured during onboarding.

Request a Demo