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

Schema redesign #28

Open
stefanpernpaintner opened this issue Jul 10, 2023 · 2 comments
Open

Schema redesign #28

stefanpernpaintner opened this issue Jul 10, 2023 · 2 comments

Comments

@stefanpernpaintner
Copy link
Collaborator

Schema redesign: Idea was to have one flat table with rows containing all attributes of a charging station (including address + basic charging attributes). Current design with 3 tables doesn't make sense (1:1 relationships) and complicates the whole process

@LarsHaferkampEON
Copy link
Contributor

For the initial merging of charging properties and address data, the 3 tables helped a bit, i.e. now it's chosen which table/object (address, charging) from which source to prefer.
But in the end we should compare attribute by attribute when merging, which is a bit more effort.

@mjmader
Copy link
Collaborator

mjmader commented Feb 2, 2024

We should consider #30 though, our data model currently does not support charge points, while original datasets are structured this way (even the row based BNA and FRGOV data)

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

No branches or pull requests

3 participants