ocpi-tariffs
ocpi-tariffs copied to clipboard
tandemdrive
OCPI tariff calculations
Currently consumers need to provide the timezone explicitly. We should be able to detect it from the country code.
It would be helpful if the `id` of the chosen tariff, and the associated `currency` would be provided in the `pricer::Report` type, currently the `currency` can be deduced using the...
Hello 👋 We are testing our own implementation against yours, and I noticed that the following text from the spec regarding cdr.charging_periods.tariff_id is ignored: > tariff_id > Unique identifier of...
It would be great if the tool could simplify tariffs by removing everything which has no effect. Example with price components which do nothing: ```json { "id": "EXAMPLE", "currency": "EUR",...
Generate human readable text from a JSON Tariff structure. We can try to follow the structure provided by OCPI (a tariff with elements which have dimensions with restrictions) and we...
We want to be sure that we can parse a real CDR correctly.
I removed the periodic outdated deps action that would fail the build, as this was too strict and got in the way of development sometimes. I would like to add...
If the "last_updated" date time of the tariff is after the start date time of the CDR then show a warning that the tariff maybe a newer version than the...
A tariff could contain restrictions based on reservations, these are currently not handled. Additionally a cdr could contain reservation time as a dimension and volume. It's not fully clear how...