Data Specification Requirements:
- API (unspecified standard)
Required anonymized data: Company Name, Type of bicycle or e-scooter, Trip record number, Unique, hashed and persistent ID of the user, User Demographics as available, Trip duration, Trip distance, Trip waypoints to track the route, Start date, Start time, End date, End time, Start Location, End Location, Bicycle or e-scooter ID number)
Operator shall include any data regarding public complaints and response times, maintenance and repair activities, and incidents involving dockless mobility devices within the data that is sent to council every month.
Operator must have the capacity to provide council on request with real-time information on the entire fleet through a documented application program interface (API). The data to be published to the council API should include the following information in real time for every parked device:
a) Identification number
b) GPS Co-ordinates
c) Availability start date
d) Availability start time
e) Power level (if electric)
f) Date of last service
g) Time to next service
h) Service status
The Operator will support the General Bikeshare Feed Specification (GBFS), an open data standard for cycle share.
Public data reporting:
The Department of Planning Transport and Infrastructure may choose to integrate cycle share into Adelaide Metro’s Metro MATE Mobile app.