New 2.3 lyft feeds

[ArashMansouri]

We're updating the systems.csv files with Lyft's brand new 2.3 GBFS feeds.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ ArashMansouri
❌ Mitch Vars

---

Mitch Vars seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[futuretap]

@ArashMansouri are you from Lyft? I noticed that in some feeds (Denver, Portland), the last_reported field of the stations in station_status.json is months ago. Is the status information really that old? That would mean the feeds are unusable.

Also, I noticed that the Lyft Washington, DC feed lists vehicle types "1" and "2" in the station_status feed that are not defined in the vehicle_types feed. I assume that this feed is scooter-only and should not include stations at all?

[ArashMansouri]

@ArashMansouri are you from Lyft? I noticed that in some feeds (Denver, Portland), the last_reported field of the stations in station_status.json is months ago. Is the status information really that old? That would mean the feeds are unusable.

Also, I noticed that the Lyft Washington, DC feed lists vehicle types "1" and "2" in the station_status feed that are not defined in the vehicle_types feed. I assume that this feed is scooter-only and should not include stations at all?

Hi Ortwin,

Thanks for calling these out. I do work for Lyft and I made a different PR for the update to system.csv so feel free to comment there. For the two points you mentioned, we'll look into this and apply fixes as needed. Thanks!

Arash

[futuretap]

Hi @ArashMansouri, thanks for fixing this issue. We encountered another issue with the Capital Bikeshare feed: In station_status, num_bikes_available is larger than the sum of all vehicle_types_available counts. Specifically, the vehicle_types_available counts are all 0. Also, is the overlap to the Lyft DC feed intentional? The Lyft feed contains the same stations as the CaBi feed, plus the scooter locations in free_bike_status.

[futuretap]

Hi @ArashMansouri the issue with the broken vehicle_types_available persists. Can you please look into this?