-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature-Request] Field for EVSE-ID #231
Comments
Our data model does have an Operators Reference data field per connection but in reality when people are submitting data manually they don't know it and can't supply it. We do support imports from OCPI locations data feeds but very few networks provide those to us. |
I would suggest to add an additional data field for the EVSE-ID, so you can be sure that this specific ID is in this field (if it is filled). I think this is important for using OCM data with other services that use this ID for identifying charging stations. I do not enter the EVSE-ID in submissions because I would not have expected that this is the right field for it. EVSE-ID is not an operator reference but an reference that is unique across all operators. |
@SnejPro thanks, we'll consider that for inclusion. I think we would need a revision to our model for the EVSE and connector grouping, our listings are mainly per site rather than per EVSE and connection info can refer to one unit or multiple units at that site. |
Maybe that's a chance to improve the data model in general and add some fields that could be useful. Additionally: A field for the EVSE-ID would allow mass imports (e.g. from official charing station registers). |
In the EU, there is a standardized system for identifying charging points: The EVSE-ID (https://evseid.eu)
This is a unique identifier for charging stations AND every single charging point.
I think this ID should be implemented in the OCM-datamodel and maybe even mandatory for future charging stations submitted to OCM.
The text was updated successfully, but these errors were encountered: