I found these “system data” pages and S3 buckets for other Lyft Bike systems (starting from [lyft.com/bikes](https://www.lyft.com/bikes)): - [SF](https://www.lyft.com/bikes/bay-wheels/more): [`s3://baywheels-data`](https://baywheels-data.s3.amazonaws.com/index.html) - [Portland](https://biketownpdx.com/system-data): [`s3://biketown-tripdata-public`](https://biketown-tripdata-public.s3.amazonaws.com/index.html) - [Chicago](https://divvybikes.com/system-data): [`s3://divvy-tripdata`](https://divvy-tripdata.s3.amazonaws.com/index.html) - [Columbus](https://cogobikeshare.com/system-data): [`s3://cogo-sys-data`](https://cogo-sys-data.s3.amazonaws.com/index.html) - [DC](https://ride.capitalbikeshare.com/system-data): [`s3://capitalbikeshare-data`](https://capitalbikeshare-data.s3.amazonaws.com/index.html) - [MPLS](https://niceridemn.com/system-data): [`s3://niceride-data`](https://niceride-data.s3.amazonaws.com/index.html) - [NYC](https://citibikenyc.com/system-data): [`s3://tripdata`](https://tripdata.s3.amazonaws.com/index.html) - Denver: couldn’t find the actual site like those above, just [lyft.com/bikes/denver-co](https://www.lyft.com/bikes/denver-co) They look relatively similar in structure to NYC's site/bucket, so it might be cool to point ctbk.dev at some of them…
I found these “system data” pages and S3 buckets for other Lyft Bike systems (starting from lyft.com/bikes):
s3://baywheels-datas3://biketown-tripdata-publics3://divvy-tripdatas3://cogo-sys-datas3://capitalbikeshare-datas3://niceride-datas3://tripdataThey look relatively similar in structure to NYC's site/bucket, so it might be cool to point ctbk.dev at some of them…