Which Vehicle Properties are essential to know about? #26
Replies: 4 comments 16 replies
-
|
Per the discussions, it seems the working group is leaning toward:
|
Beta Was this translation helpful? Give feedback.
-
|
I think we are in agreement on what vehicle properties are essential. Vehicle_id I dont think is essential based on comments but we do have it in our spec as an optional field which will still allow cities that have LPR or digital permits to require that information if needed. (Seattle would use this eventually) For vehicle_type I understand that we want to align with MDS but something we may want to consider is the Urban Freight Lab's Vehicle Typology and Activity Type classification methology. The methodology is outlined on pages 9-12 and Appendix A of the linked report. Seattle has been using this strategy for our parking studies with pretty good success. There are limitations if you want to classify activity types for private vehicles being used for commercial purposes but that could be an optional field? I also noticed that (I think) CDS doesn't have activity type in our Event's data. Should this be something that is included? |
Beta Was this translation helpful? Give feedback.
-
|
For passenger_transport | Picking up and/or dropping off of human passengers Possible additions include: emergency_use - includes ambulance, fire truck, police |
Beta Was this translation helpful? Give feedback.
-
|
Should we try to align Curbs API This also gets to (like activity types) how connected Curbs and Events are. Do they need to align? Will they be used to enforce activity at the curb, in which case they should align, or is that outside the scope for now? |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
CDS needs vehicle properties added. What properties need to be added? Is permit number needed (would be optional and sent only in company feed)? Already have vehicle length. Class? Loading side? Back ramp? Drones deployable? Etc.
How would these be added to the Events API? Currently vehicle_length is just a field in /events, but maybe instead it's an array of vehicle_properties in /events we define.
Already have vehicle_type and propulsion_type, like MDS. This would be an additional vehicle_properties object.
Beta Was this translation helpful? Give feedback.
All reactions