31 St & Broadway

7c7a39bb-e70b-88b1-ae44-215a292a5280 · relocation

Accepted · confidence MediumModel: mr_8a9483

Distance moved

21 m

Capacity change

? → 35

Pre-window trips

77,564

Match confidence

99%

Pre 2024-07-31 20:00 EDT → 2025-07-30 20:00 EDT

Post 2025-08-30 20:00 EDT → 2026-06-29 20:00 EDT

Before (2024-08-01 – 2025-07-31)

After (2025-08-31 – 2026-06-30)

Neighbor redistribution

Net redistribution ≈ +45 trips

Neighbor	Distance	Observed post	Model pred.	Naive baseline	Residual (model)	Residual (naive)
31 Ave & 30 St epumsppfzjh5	305 m	114.47	98.4	303.6	-16.1	+189.2
31 Ave & 34 St pjmeryzyv6ac	389 m	125.2	110.8	110.8	-14.4	-14.4
Crescent St & Broadway wlhnljxdxtev	320 m	146.27	132.1	132.1	-14.2	-14.2
34 St & 35 Ave e6xfd6ghz6ng	582 m	47.9	56.4	56.4	+8.5	+8.5
Broadway & 31 St sdjmzkjpi5tn · moved station	21 m	213.65	205.3	0.0	-8.4	-213.7
23 St & 31 Ave 57j4vyvwhfup	581 m	69.53	63.3	63.3	-6.2	-6.2
35 St & 34 Ave wispuc4gqyvk	458 m	50.05	55.3	55.3	+5.3	+5.3
35 St & Broadway m6tra5k3x3tf	320 m	77.22	81.9	81.9	+4.7	+4.7
34 Ave & 31 St k3yf64bxzq2r	322 m	58.71	54.6	54.6	-4.1	-4.1
31 Ave & Crescent St rbjg6rox22fx	429 m	85.5	84.7	84.7	-0.8	-0.8
Crescent St & 34 Ave p6imam36drq6	463 m	67.92	68.3	68.3	+0.4	+0.4

Sources

Pre & post trip data: Citi Bike tripdata S3 bucket
Station identity reconciliation: nyc.citibike_simulator_stations_master (canonical & legacy IDs)
Model prediction table: nyc.citibike_simulator_relocation_neighbor_predictions (model_run mr_8a9483)

Detected from ingest run: #94

Download event CSV How the model is evaluated

Methodology and known gaps

This tool is a Concourse research artifact. Not a permit or approval.

What this tool does

Estimates how relocating or resizing a Citi Bike station would affect ridership and rebalancing across a small neighborhood of stations, using public GBFS and S3 trip data.

What this tool does not do

This is not a NYC DOT approval, a Lyft operations tool, or a rebalancing dispatcher. It cannot see rebalancing truck routes, suppressed demand, or pricing history.

Four public-data gaps

Rebalancing truck logs are internal to Lyft.
The product infers rebalancing burden from inventory dynamics, not from observed truck routes. Rebalancing truck movements are not observed and would attenuate these effects in practice.
Suppressed demand (app searches without a trip) is internal to Lyft.
App searches that do not result in a completed trip are not in the public data. Suppressed demand is not observed here.
2019-05 to 2023-06 station-status archive gap.
No public station-status archive covers 2019-05 to 2023-06. Empty/full risk is trained on the OpenBus 2015-2019 window and live GBFS polling from ingest go-live forward. No continuity claim is made across the gap.
Pricing and promotions history is unobserved.
Pricing and promotions history is not observed. It is a confounder that may explain some observed demand shifts.