Currently SQLite3 is used for generating KML and map view. A separate dashboard_data_model maintains data for generating the dashboard view, and yet another bespoke datatype maintains the history for the azimuth map. At the very least the dashboard and KML/map views should use the same data source; differences in data expiry lead to discrepancies between the two views, and it adds unnecessary complication and processing load to maintain and prune separate data sources.
The structure of the DB should probably be changed to add separate views used to generate appropriate presentations instead of using complex queries for dashboard_data_model etc.
Currently SQLite3 is used for generating KML and map view. A separate dashboard_data_model maintains data for generating the dashboard view, and yet another bespoke datatype maintains the history for the azimuth map. At the very least the dashboard and KML/map views should use the same data source; differences in data expiry lead to discrepancies between the two views, and it adds unnecessary complication and processing load to maintain and prune separate data sources.
The structure of the DB should probably be changed to add separate views used to generate appropriate presentations instead of using complex queries for dashboard_data_model etc.