Technical brief for interoperability of bicycle sharing

[Edoardo Felici]

1. Phasing of interoperability according to letter of intent of F12[1] (signed 29/01/2018)

 

Phase 1: Visibility of available bicycles (04/07/2018)

Phase 2a: Deep linking possibilities

Phase 2b: Single sign-on and interoperable booking

Phase 3: Interoperable paying, unlocking of bicycles

 

1. Functional requirements

    

• Agreement on which data-elements to share for interoperability

  • F12: Availability, pricing, location of bicycles

• Application Programme Interface (API), to

  • F12: Start- and stop rental

  • F12: (Un)locking bicycles

• Common standard (open source)

  • F12: General Bikeshare Feed Specification (GBFS)

  • F12: Common Language

    • Booking (long-term) vs. reservation (short-term)

 

1. Technical requirements

• Visibility of available bicycles

  • F12: Connection to Openbike.nl platform

  • F12: Delivery of location-information in GBFS

  • F12: Interface specification

    • Expiry time (openbike.nl = 30 sec)

    • Pull-protocol

    • # consultations

• Common standard

  • F12: Addition of elements to describe:

    • Type of system (e.g. fixed station, free-floating, location based)

    • Bicycle typology (e.g. type, pricing scheme, # gears)

    • User competence (e.g. age, acceptance of user agreements)

---

[1] BimBimBikes, FlickBike, Du Nord Rijwielen/Datatour, Mobike, Cykl, Emotion Sustainable Mobility, Donkey Republic, Urbee, Hello Bike, Next Bike, De Witte Stad

[Ronald]

Let's create a draft agreement on the Tech standard in this google doc: https://docs.google.com/document/d/13rzPYHhkPT_DQ9pkS1Os78JhEuwNIch9KynjkurXrPc/edit?usp=sharing