Hi All, I am now doubt going to start a bit of a conversation with this one. I came across the use of Highcharts on a Weather website today and it looks pretty neat. My first thought would be to generate Json data from Weewx and code up the client size which would be pretty straight forward.
I have reviewed the forums and see that both Json and plotting has been discussed. It looks like the Bee's Knees will be WeeRT and a new client front end (thread: Dynamic History Plots Using D3). What I am looking for is something that can be completed quite rapidly using Highcharts. It may not be the best, nor lightweight, nor fit everyone due to Highcharts licensing, but it will be something. The main part for discussion is how to get Json data out of Weewx. Option 1: Code up $all_values timebinder (or similar) and use Cheetah template engine. While this will work I am feeling it will not be as flexible as it needs. Option 2: Code up a new 'jsongenerator' which works similar to imagegenerator, borrowing its conf structure etc., but output is json data and not an image. I believe coding up a jsongenerator would be straightforward and would be happy to do. If so, we may need to think about the following. jsongenerator Q1: Will it be just raw data? jsongenerator Q2: Will a [head] or something be need to give information about the file? I am thinking start_ts, stop_ts, observations included.. (Any examples people have used? Any requirements?) jsongenerator Q3: For multiple observations in a file (like multiple on a plot), will it be a row collection of the observations? Or a collection of each observation? I think the former as this would be easy to put into client side charting applications. Then for the Skin, I would reduce the Current, Week, Month, Year down to one page and have a selection to choose what data to display in graphs. (Weewx would have output Json files for each). Not the most elegant but is a nice transition from the current 'standard' Skins into something client driven but not too fat or heavy (and not waiting for the 'new' world). Your thoughts. I intend to code up next weekend (unless otherwise convinced!). Regards Darryn
