Alex Demisch

SFMTA's [On-Street Car Share Program](https://www.sfmta.com/projects/street-shared-vehicle-parking-permit-program) dedicates curb spaces for car share vehicles. These are for the round-trip car share model where the vehicle is picked up and dropped off at...

I like Option 2 here because it puts all the GPS breadcrumb/telemetry data all in one /telemetry endpoint. When I'm thinking about the passenger services work, this is a good...

### Comparison to SFMTA Taxi Trips & Telemetry API I'm listing below fields from SFMTA's current [Taxi Trips & Telemetry API](https://sfmta-my.sharepoint.com/:b:/p/alex_demisch/EdbqLwh7apJIiOdXzOTkf0cB6KlnNGV-pBYRin35f1Tn8w?e=kRo5rg) and, where applicable, suggestions on how they could be...

Just flagging that SFMTA’s Taxi API contains two endpoints: Trips and Telemetry. It took me a bit to get a copy of the Telemetry spec, and I just updated my...

SFMTA staff have reviewed the feature-modes-passenger-services feature branch and compared it to the latest version of the SFMTA taxi spec. We have the following general thoughts and specific fields in...

I agree that start trip geography makes sense for now. As my SFMTA colleagues and I start to work with the data, we might have other opinions, but that can...

Since SFMTA is interested in trips taken on adaptive scooters, we added `adaptive_scooters` as a `special_group_type` in our implementation. Since there may be similar interest in adaptive scooters in other...

Adding provider_id as a field in the CSV would be helpful since data from multiple providers is very likely to be combined.

Thank you @schnuerle . I agree with you that each taxi company can get a MDS provider_id. In the SFMTA spec, there are two fields like provider_id, but they refer...

> This could be a chance to add a `curb_zone_id` optional field to trip attributes, that specifies if a trip ends in one of your defined CDS curb zones. You...