You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tariffs may contain date and time restrictions, these are in local time zone. All the timestamps on the session and charging periods are in UTC. In order to compare the timestamps with the restrictions in the Tariffs we need to know what the local timezone is. This is present on the Location object but NOT on the CDR Location. This means that the CDR does not contain all the information form the Location that is needed to calculate the costs.
Time zone can be derived from the coordinates but that would force every OCPI implementation to depend on such a service.
I suggest, perhaps a bit late in the game, that Time zone from the Location object is included in the CDR Location.
The text was updated successfully, but these errors were encountered:
Tariffs may contain date and time restrictions, these are in local time zone. All the timestamps on the session and charging periods are in UTC. In order to compare the timestamps with the restrictions in the Tariffs we need to know what the local timezone is. This is present on the Location object but NOT on the CDR Location. This means that the CDR does not contain all the information form the Location that is needed to calculate the costs.
Time zone can be derived from the coordinates but that would force every OCPI implementation to depend on such a service.
I suggest, perhaps a bit late in the game, that Time zone from the Location object is included in the CDR Location.
The text was updated successfully, but these errors were encountered: