-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Better OpenChargeMap support #273
Comments
Thanks! Yes, we should investigate whether these details are available through the OCM API (probably yes) and then map them to the existing internal data structure or add extra fields. |
These are already included, see the screenshot below:
will add it in the next update: c5714c8
Yeah, that is possible but a bit more work to implement in the UI. Currently we only show fault reports, other comments are not displayed. Let's divide it into a separate issue -> #277
will hide deleted chargers in the next update: fab66d1 |
Hey,
Assuming it's possible, it would be nice if EVMap displayed more info when using OpenChargeMap as data source.
Some entries have information about parking restrictions, notes about how we can pay for the charger, a link to the charger's website where we can see the real time status/prices, etc. For example, OCM-235945:
They also support comments, which can be useful when looking for feedback about the charger/location. Perhaps some "tab" to display the comments/photos could be created (similar to plugshare, zapmap, etc)?
Some status are also not correctly displayed by EVMap. For example, OCM-237231 is a duplicated entry/doesn't exist and is marked as "Operational Status: Removed (Duplicate Listing)". OCM displays this:
While EVMap displays the charger as if it's working:
I don't know if it's because the entry is "Removed (Duplicate Listing)", but the charger itself is "Operational"? Maybe they should sites marked as duplicated, but since the quality of the data will sometimes be like this, I think it's a good idea to handle it better.
The text was updated successfully, but these errors were encountered: