Arnaud Delcasse fafa58daf1 | ||
---|---|---|
handler | ||
helpers | ||
interoperability | ||
servers | ||
storage | ||
tiles | ||
.gitignore | ||
README.md | ||
config.go | ||
go.mod | ||
go.sum | ||
main.go |
README.md
COOPGO Carpool Service
COOPGO Carpool Service is a carpool management microservice. It is part of the COOPGO Technical Platform and the base carpool component of COOPGO's RIDYGO application. It was redesigned from scratch to implement natively the new OCSS carpool standard and bring interoperability.
This is not a full featured carpooling application. There is no UI and it only implements basic carpooling functionalities (create and find, book journeys). The objective of this service is to be embedded in a bigger carpool or Mobility as a Service platform.
It provides a gRPC service to interact with other microservices, and an HTTP API to provide interoperability with external carpooling operators.
Technical architecture
Managing trips and journeys
Trips and journeys are managed through the provided gRPC service and stored in the database (MongoDB for the moment). They are stored in the database as GeoJSON feature collections with extra members defining the trips and journeys non-geographical parameters.
Tiles architecture and cache
To reduce dependencies on the chosen database, we decided to manage geographical calculations directly in our code instead of relying completely on MongoDB geographical features.
We use a tiles system to retrieve relevant journeys easily. Each tile is defined by :
- driver or passenger status of the journey
- date of the journey
- Tile ID in the tiles grid. The tiles grid is inspired by Valhalla https://github.com/Telenav/open-source-spec/blob/master/valhalla/doc/valhalla-tiles-basic.md. We use a level 0 grid
Journeys are stored in each relevant tile (where a departure, destination or part of the polyline enters the tile)
Search
Booking
OCSS standard
The OCSS standard is the new carpooling interoperability standard defined by the french carpooling ecosystem.
COOPGO Carpool Service implements all of this standard, except the messages endpoint which we think should be handled outside of this service, as different carpooling or MaaS applications may handle messaging differently.
Licence
COOPGP Carpool Service is released under the terms of the AGPL version 3 licence