Is your feature request related to a problem? Please describe.
Version 3.0 of GBFS will soon be released, and of course we would like to support it in lamassu.
Goal / high level use-case
The goal is to support both consuming and producing versions 2.x and 3.x. We will use https://github.com/entur/gbfs-mapper-java to map between the versions.
Describe the solution you'd like
There will be a full rewrite of https://github.com/entur/gbfs-loader-java as part of this effort. A likely API design is a separate callback for each version. We will likely rewrite the rest of the lamassu pipeline to be based on v3 model. I also want to change the feed caches so that we store string serialized json instead of kryo format, so that we reduce CPU and latency for serialization for data that does not need to be modified. We will probably need to add some metadata.
Is your feature request related to a problem? Please describe. Version 3.0 of GBFS will soon be released, and of course we would like to support it in lamassu.
Goal / high level use-case The goal is to support both consuming and producing versions 2.x and 3.x. We will use https://github.com/entur/gbfs-mapper-java to map between the versions.
Describe the solution you'd like There will be a full rewrite of https://github.com/entur/gbfs-loader-java as part of this effort. A likely API design is a separate callback for each version. We will likely rewrite the rest of the lamassu pipeline to be based on v3 model. I also want to change the feed caches so that we store string serialized json instead of kryo format, so that we reduce CPU and latency for serialization for data that does not need to be modified. We will probably need to add some metadata.