You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
ianhoffman
changed the title
[Idea] Refactor PurpleAir sync process to remove intermediate tables
Refactor PurpleAir sync process to remove intermediate tables
Sep 17, 2020
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.
The text was updated successfully, but these errors were encountered: