search

openmobilityfoundation / mobility-data-specification

A data standard to enable right-of-way regulation and two-way communication between mobility companies and local governments.
https://www.openmobilityfoundation.org/about-mds/
Other
685 stars 231 forks source link

Adopt additional parking facilities information #818

Open rwdbrooks opened 1 year ago

rwdbrooks commented 1 year ago

Is your feature request related to a problem? Please describe.

Yes. As more mobility providers add infrastructure in the ROW, the City of Minneapolis has been having challenges understanding where parking facilities are located and what their different features are.

We'd like mobility operators to regularly report where their parking facilities are so we can know where they are, what features/amenties they have and to be able to direct riders to those locations and create optional or required parking zones. The City would also share its parking infrastructure as well.

Additionally, as we add more and different parking facilities; racks, docks, hangars, etc. with various features; power, security, etc. we need to better track what capabilities and capacities these new facilities have for residents & users.

Describe the solution you'd like

We would like to add data fields and new variables that can capture the different data necessary to map and understand their locations and different features.

Is this a breaking change

Impacted Spec

For which spec is this feature being requested?

Describe alternatives you've considered

Receiving regular reports or maps from individual providers.

Additional context

rwdbrooks commented 1 year ago

Here are the fields and variables we've come up with to start. We've grouped them under Station Information, Station Location, Station Status, and Station Features to start. Some of these fields are included, but I wanted a full list to start.

Station Information

Station ID: Name: Operator: Station type

Secure

Permit #: Contact info: Station Usage (who can use it)

Rental methods

Station Location

Address: Cross-street: Property Owner

Station Attached (is it attached in the ground or not)

Ground type

Location Type

Station Status

Is Installed

Is Renting

Is Returning

Is stored in place (for seasonal removals)

Hours of operation: Capacity

Station Features

Electrified

Charging Capacity

Vehicle types it can serve

Vehicle types it can charge by vehicle type (or connector types)

schnuerle commented 1 year ago

Thanks Russ the details you provided in this issue are great.

It's an interesting idea. It seems we would need to allow:

  1. cities to publish this through Policy (which is part of Stops, but with not as many fields as you are suggesting), and
  2. allow operators to publish as well (which we don't have now, mostly because it's usually the cities who are the authority on this on stations in the right of way).

GBFS does have a way to for operators to publish, which has good information, but not all the fields you list: https://github.com/MobilityData/gbfs/blob/master/gbfs.md#station_informationjson

Some of your ideas overlap with ways of defining things at the curb with the CDS, and something we are thinking of expanding in the next release (like other curb area adjacent elements that facilitate or impede curb transactions: trees, utility box, bench, ramp, art, bike rack, planter, meter pay stations, signal cabinets, scooter parking. Specific focus on EV Charging in spec - status Active/Charging/Inactive, reliability, uptime).

So now others can chime in here, and the steering committee can look at this to bring to a future working group meeting as a topic too.

schnuerle commented 1 year ago

Some of these ideas like around publishing stops in Policy are discussed in #638 as well now.