Historical data in Seasons skin

[Jeff Allison]

I think I must be missing something obvious, but I can't figure out how to display data for a specific date in the Seasons skin. I can see statistics for the current day, and I can see how to bring up the NOAA reports, but how do I pull up statistics for yesterday or any arbitrary date? 

This is Seasons 5.0.2.

Thanks!

- Jeff

[Vince Skahan]

Weewx generates a variety of predefined static web pages when the reports periodically run.

If you want something much more generic that would let you pick ‘any’ date of your choosing then you’d have to write some custom code to make that happen…

[Jeff A. D.]

You could run a report for any date.  For instance

sudo weectl report run --date=2026-01-02 --time=00:00

would run a report for New Year's day of this year.

[Jeff Allison]

OK. Thanks for the input!

- Jeff

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/iIYvDOC5-Oo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/26991640-f2b8-46f8-a945-927af571fdbcn%40googlegroups.com.

[Vince Skahan]

Jeff perhaps I misinterpreted what you wanted. I was thinking you wanted some web based way to pick a date from a calendar picker or by entering a date in a form then clicking ok. That would need some code to enhance the skin.

Running weectl from the shell gets you ireports as of that specified date but when weewxd runs the normal reports the next time it’ll revert to current info.

[John Smith]

Jeff perhaps I misinterpreted what you wanted. I was thinking you wanted some web based way to pick a date from a calendar picker or by entering a date in a form then clicking ok. That would need some code to enhance the skin.

It would be more efficient to use a javascript graphing library like Highcharts and have it plot data instead of pre-rendering a lot of static graph images.

I believe this is the direction they went with the new Belchertown skin. It's just a matter of exposing suitable data and letting the browser do all rendering.

You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/d41d9d03-de03-4f61-8d0d-8e171fd95ceen%40googlegroups.com.

[Vince Skahan]

When Jeff asked about Seasons skin specifically and statistics I interpreted that to mean text key/value pairs ala the data on the left hand side of the Seasons skin.   So I was thinking some javascript addition to view a generated alternate statistics.inc file or the like.

But yes Belchertown original + the newer fork both let you scroll nicely in their graphs.  Unfortunately you can only scroll backward one item at a time which (to me) isn't what he was asking about.

[Jeff Allison]

Yeah, what I was looking for was something like what Weather Underground has. There you have a "Weather History" section that lets you select a date and it'll show the high/low/average for temperature, dew point, humidity, etc.

- Jeff

[Mks Mk]

Jeff

try this

https://github.com/glennmckechnie/weewx-wxobs

[jterr...@gmail.com]

Jeff,

You may also have a look at this skin : https://github.com/Daveiano/weewx-wdc

There is a demo here : https://www.weewx-hbt.de/

WIth this skin, you can enable the daily statistics - see the "Statistics" menu -  where you can see the data, charts and tables for each day.   WIth the daily statistics enabled, the very first run of the skin could take quite a long time, depending on the extent of your historical data, since the skin will have to generate all the daily, monthly and yearly pages. 

[Jeff Allison]

I’ll take a look at these. Thanks.

 

• Jeff

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/93906529-5af7-4397-b1e0-c547689666b6n%40googlegroups.com.

[Jimi Lawson]

This may/may not be of interest, with being in the UK I have no real use for the NOAA reports, although I upload my data to most of usual suspects I don't upload the NOAA reports anywhere. So I modified the NOAA reports to give me a history of my data. You can see my monthly/yearly records here <https://jlawson.co.uk/index.php/weather/weather-statistics>   use the select month/year buttons to view the records
Regards
Jimi

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/2b4701dd192b%24b6af1ac0%24240d5040%24%40gmail.com.

[Jeff Allison]

I do appreciate the input here. I am finding myself getting confused about handling multiple skins in WeeWx, so I’m going to pull back, dig into the documentation, and get a better handle on this.

 

• Jeff

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/53DA5BC7-2E49-4402-991D-569DB2597E14%40gmail.com.

[jterr...@gmail.com]

You can have several skins configured and active with weewx.

In that case, you will have to define a specific html  root folder for each skin.  

In weewx.conf, for each additional  skin enabled, you will have to ajust the "HTML_ROOT" parameter of the skin.

For instance, with both Seasons and Belchertown skins activated:

[StdReport]
   
    # Where the skins reside, relative to WEEWX_ROOT
    SKIN_ROOT = skins
   
    # Where the generated reports should go, relative to WEEWX_ROOT
    HTML_ROOT = public_html/weewx
   
    # The database binding indicates which data should be used in reports.
    data_binding = wx_binding
   
    # Whether to log a successful operation
    log_success = True
   
    # Whether to log an unsuccessful operation
    log_failure = True
   
    # Each of the following subsections defines a report that will be run.
    # See the customizing guide to change the units, plot types and line
    # colors, modify the fonts, display additional sensor data, and other
    # customizations. Many of those changes can be made here by overriding
    # parameters, or by modifying templates within the skin itself.
   
   
   
    [[SeasonsReport]]
        # The SeasonsReport uses the 'Seasons' skin, which contains the
        # images, templates and plots for the report.
        skin = Seasons
        enable = true
        lang = fr
        unit_system = metric

   [[Belchertown]]
        enable = true
        skin = Belchertown
        HTML_ROOT = public_html/weewx/belchertown

[Jeff Allison]

OK, so if you’re only using one skin, say Seasons, and you don’t have an HTML_ROOT option defined in the [[SeasonsReport]] section, then the Seasons report is going to dump its output into the generic HTML_ROOT as defined at the [StdReport] level. If I have multiple skins defined, then each needs its own HTML_ROOT. For Seasons I could set HTML_ROOT=/var/www/html/weewx/seasons. Then, from a user perspective, I’d access this report by going to http://<server>/weewx/seasons. Same for other reports.

 

Now if I do that and I don’t have any reports writing to the general HTML_ROOT (/var/www/html/weewx), then if I browse to http://<server>/weewx, I’m just going to get a listing of the various directories there. Is the idea that I handcraft some HTML to put in that directory as the index file that lists my supported skins with links to each? Or is there some way to have WeeWx manage that automatically?

 

Sorry for all the dumb questions. I truly appreciate the assistance here!

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/545766fb-006d-4f83-a314-5d81e62c80acn%40googlegroups.com.

[Vince Skahan]

Sure handcraft a file for the webserver docroot pointing to whatever you want. I do that here.