Yet Another Forecaster
Posted: Sat 08 Sep 2012 12:17 am
For a few weeks now I've been testing an alternative method of calculating a 'local' forecast.
I feel it's now at the stage for others to evaluate/use/bag or whatever.
I've put the code in a .zip file here: http://weather.gktnet.com/public/weathe ... cripts.zip
This method uses a php version of Beteljuice's Zambretti Forecaster to do the work.
The forecaster is called at 12-hour intervals as a Windows scheduled task and produces a small text file, which can be easily imported for display in a web page.
My variant of the Zambretti code returns an array to the calling php containing a forecast number (0-26) followed by the forecast description.
The forecast number can then be used to display a graphic, such as Jacques' day/night forecast set, with the description being used as a caption etc.
Here is how the scripts work:
The task scheduler task runs forecast.vbs, which calls FCast.php, which in turn calls Zambretti.php
FCast.php then writes a file called FC.txt to disk.
The only critical part is setting up a scheduled task and setting paths in the files.
I would welcome any comments, criticisms, etc.
I feel it's now at the stage for others to evaluate/use/bag or whatever.
I've put the code in a .zip file here: http://weather.gktnet.com/public/weathe ... cripts.zip
This method uses a php version of Beteljuice's Zambretti Forecaster to do the work.
The forecaster is called at 12-hour intervals as a Windows scheduled task and produces a small text file, which can be easily imported for display in a web page.
My variant of the Zambretti code returns an array to the calling php containing a forecast number (0-26) followed by the forecast description.
The forecast number can then be used to display a graphic, such as Jacques' day/night forecast set, with the description being used as a caption etc.
Here is how the scripts work:
The task scheduler task runs forecast.vbs, which calls FCast.php, which in turn calls Zambretti.php
FCast.php then writes a file called FC.txt to disk.
The only critical part is setting up a scheduled task and setting paths in the files.
I would welcome any comments, criticisms, etc.