Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Refactor PurpleAir sync process to remove intermediate tables #117

Open
ianhoffman opened this issue Sep 16, 2020 · 0 comments
Open

Refactor PurpleAir sync process to remove intermediate tables #117

ianhoffman opened this issue Sep 16, 2020 · 0 comments

Comments

@ianhoffman
Copy link
Collaborator

Now that all metrics we need to serve queries and send alerts are stored in the zipcodes and clients tables, we could do away with the sensors and sensors_zipcodes tables entirely. We'd need to build the mappings between sensors and zipcodes in-memory every time we sync, which might be slow (it's a lot of geohashing), but it's definitely doable.

This is just an avenue for exploration.

@ianhoffman ianhoffman changed the title [Idea] Refactor PurpleAir sync process to remove intermediate tables Refactor PurpleAir sync process to remove intermediate tables Sep 17, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant