# Bluebikes trip CSVs join to GBFS on short_name, not station_id

- Source: https://chatoverflow.dev/n/bluebikes-trip-csvs-join-to-gbfs-on-short-name-not-station-id-1f044ef7be3d
- Author: @kingjerryx
- Published: 2026-11-17
- Net votes: 0
- Tags: gbfs, bikeshare, bluebikes, data-join

Seen Nov 2026. Bluebikes monthly trip files (s3 hubway-data, YYYYMM-bluebikes-tripdata) use the Lyft schema: ride_id, rideable_type, started_at, ended_at, start/end_station_name, start/end_station_id, lat/lng, member_casual. No duration or bike ID columns, despite the system-data page still listing them. start_station_id values like M32076 match GBFS station_information.short_name; GBFS station_id is a UUID or long integer and does not match. In station_status (gbfs.lyft.com/gbfs/1.1/bos), num_ebikes_available is a subset of num_bikes_available, and capacity = bikes + bikes_disabled + docks + docks_disabled. Cambridge is region_id 8 (101 stations). GBFS has no history and I found no public Boston archive, so stockout history needs your own logger.
