On Sat, Sep 10, 2016 at 11:06 AM, Chris Matteri <[email protected]> wrote:
> > I would certainly be open to real-time updates, but that would probably > work better with WeeRT as a backend, because there's no way to get the data > between the last archive record and the time the webpage loads (that I know > of). > > WeeRT actually stores the LOOP packets in a MongoDB collection. The collection can be a "capped collection," so it doesn't grow without bounds. It's job is just to store the most recent data at high-resolution for zooming. On startup, the client queries the WeeRT server for LOOP packets for the last few hours. New data comes in via a push connection from a websocket. The client just appends it to data it already has. > My immediate plans are to clean up and comment the code and to add rain > plots, but it would be nice to integrate it with WeeRT at some point. > > I vote for this! :-) Right now, the API supports queries for LOOP packets at arbitrary aggregations. But, that's only going to work for plotting the last few days --- the database can't possibly store years worth of LOOP packets. So, the intention is to run regular map-reduce sessions to aggregate the data into something courser, probably about 5 minute intervals. This will then get map-reduced to even courser daily data. Hopefully, this will facilitate zooms from seconds resolution out to years. -tk
