-
Notifications
You must be signed in to change notification settings - Fork 3
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
Using hashed lat/long for BNA's source_id leads to error #30
Comments
mjmader
changed the title
Using hased lat/long for BNA's source_id leads to error
Using hahsed lat/long for BNA's source_id leads to error
Jul 11, 2023
cs-dieter-kling
changed the title
Using hahsed lat/long for BNA's source_id leads to error
Using hashed lat/long for BNA's source_id leads to error
Nov 10, 2023
Actually the problem is that the rows of the BNA data (and also FR data btw) have changed over time to resemble charge points of charging stations, rather than just a charging station per row. |
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the source_id value for BNA's charging stations is filled with the has value over lat/long. This leads to the situation that some charging stations have the same hash value because they have the same lat/long values set (most likely by error) and this in turn leads to the fact that some stations cannot be imported because of a unique key constraint error (source_id has to be unique)
I think we should generate the hash over all attributes of the BNA's charging station to avoid the described situation
The text was updated successfully, but these errors were encountered: