Skip to content
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

Realtime data: Reject matching if candidate charger is closer to another known charging site #243

Open
johan12345 opened this issue Oct 11, 2022 · 0 comments

Comments

@johan12345
Copy link
Collaborator

johan12345 commented Oct 11, 2022

For this charging station, EVMap is currently showing realtime data that actually belongs to a different station a bit less than 150 meters away: https://www.goingelectric.de/stromtankstellen/Deutschland/Ruesselsheim-am-Main/Karolingerring-Karolingerring-51A/68190/

This is because this station is missing in the EnBW data, and the other station has the same combination of plugs and is close enough that the matching algorithm still considers it as valid.

As the other station also exists in GoingElectric, we could pass the AvailabilityDetector algorithm a list of nearby charging sites and use that list to reject candidate chargers from the realtime data source that are close enough to the site we are looking for, but actually closer to a different site.

To make sure that the list of nearby charging sites passed to the algorithm is from a large enough radius, we would need to make sure that the bounding box in which we load chargers is never smaller than the matching radius of the AvailabilityDetector.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant