-
Notifications
You must be signed in to change notification settings - Fork 1
Data stored in the CROW Dashboard database
In this document you find information on what kind of information we store in the CROW database.
Shared mobility providers share a data feed.
We process the feed every 30 seconds using the importer script. We store this processed data in two different data stores:
- park_events
- trips
A park event: The period of time that a vehicle is in public space, not being rented.
In example:
- If a rental is ended and the vehicle is 'back' in public space, this is the begin datetime for the park event.
- If a rental starts for this specific vehicle, this is the end datetime of the park event.
See PROW for info on when a vehicle should be included in the feed. The data is the basis for the park events.
This is the data we store for every park event:
system_id varchar(255) Name of provider
bike_id varchar(255) Unique vehicle ID
location geometry Location
start_time timestamp Start time, i.e. 2019-06-17 11:21:44.535568
end_time timestamp End time
park_event_id integer Unique event ID
vehicle_type_id integer Vehicle type, i.e. cargo bike
A trip: The period of time that the vehicle has been out of public space, because it has been rented.
In example:
- If a rental starts, this is the begin datetime for the park event.
- If a rental ends and is back in public space, this is the end datetime of the park event.
This is the data we store for every trip:
system_id varchar(255) Name of provider
bike_id varchar(255) Unique vehicle ID
start_location geometry Start location
end_location geometry End location
start_time timestamp Start time, i.e. 2019-06-17 11:21:44.535568
end_time timestamp End time
trip_id integer Unique event ID
vehicle_type_id integer Vehicle type, i.e. cargo bike
These are the different types of supported vehicle types.
If you have any questions, feel free to email us at [email protected]