MobilityData/gbfs

Weekly Digest: No cut-off date, empty strings, Paris, etc

kospl opened this issue · 3 comments

kospl commented

Discussed in #601

Originally posted by richfab February 26, 2024
🗳️ Following the vote (0 vote in favor, 1 vote against), there will be no cut-off date to implement the v3.0-RC features at this time.

This gives you, producers and consumers, more time to implement the features that you’d like to see included in v3.0:

  • 🅿️ Geofencing made simple (#481) - Missing a consumer. Produced by Flamingo, TIER, Check and ENTUR.
  • 🕐 Opening hours format (#328) - Missing a consumer. Produced by Flamingo, TIER, Check)
  • ⌛ Timestamps format (#522) - Missing a consumer. Produced by ENTUR.
  • 💵 Pricing per mile (#546) - Missing a producer. Consumed by Transit App.
  • 🎟️ Reservation price (#457) - Missing a producer and consumer.

🙌 Protecting publishers and riders, reducing implementation costs, and improving the rider experience, are some of the many exciting benefits of GBFS v3.0. Read more.

Issue in discussion: #600 - REQUIRED Strings : should the spec say they MUST NOT be empty ("")?

🚲 I was in Paris last weekend and we definitely get a feeling of Amsterdam like city now! Paris bike lane usage doubled in one year (source in French).

🇫🇷 Speaking of Paris, I will be at the Autonomy Mobility World Expo on March 20-21. The topics covered will be shared mobility 2.0, MaaS, data, AI and mobility (program here). Write to me if you go, I’ll be happy to chat in person!

IMG_4143.MOV

kospl commented

oops

richfab commented

Hi @kospl, no worries! Have a good day :)

sven4all commented

We use 'Geofencing made simple' as a consumer in the dashboarddeelmobiliteit https://dashboarddeelmobiliteit.nl/.

https://github.com/Stichting-CROW/dd-importer-v2/blob/master/process/service_area.go

It's good to mention that we require our publishers to use the following global rules:

  • ride_start_allowed = false
  • ride_end_allowed = false
  • ride_through_allowed = true