Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.0.1 (build 4023) - 16 May 2024
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V4 release 4.0.1 (build 4023) - 16 May 2024
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
METEOalarm warnings
Moderator: saratogaWX
-
- Posts: 1830
- Joined: Sat 17 Dec 2011 11:55 am
- Weather Station: Davis Vantage Pro2
- Operating System: Windows 11 x64
- Location: Dorset - UK
- Contact:
METEOalarm warnings
Hi
I installed the METEOalarm script, and got it working. We're under a yellow, so it shows just fine
I did test with a UK code that doesn't currently have a warning, just to check, but I got "Name not available for Name not available for"
https://warehamwx.co.uk/wxadvisory.php
Have I missed out on a setting somewhere?
I installed the METEOalarm script, and got it working. We're under a yellow, so it shows just fine
I did test with a UK code that doesn't currently have a warning, just to check, but I got "Name not available for Name not available for"
https://warehamwx.co.uk/wxadvisory.php
Have I missed out on a setting somewhere?
- saratogaWX
- Posts: 1211
- Joined: Wed 06 May 2009 5:02 am
- Weather Station: Davis Vantage Pro Plus
- Operating System: Windows 10 Professional
- Location: Saratoga, CA, USA
- Contact:
Re: METEOalarm warnings
Maybe not a setting, but a file?
Make sure you have the current meteoalarm-geocode-aliases.php and meteoalarm-codenames.json files in the same directory as get-meteoalarm-warning-inc.php script.
They're available at https://github.com/ktrue/Meteoalarm-warning
What was the code you tried that returned "undefined name"?
BTW.. the current version of the script does not handle countries that have switched to polygon-only alerts (ones that no longer include EMMA_IDs in the alerts). I'll have an update (thanks to Wim van der Kuil/PWSdashboard) later in the month of January, 2024.
Make sure you have the current meteoalarm-geocode-aliases.php and meteoalarm-codenames.json files in the same directory as get-meteoalarm-warning-inc.php script.
They're available at https://github.com/ktrue/Meteoalarm-warning
What was the code you tried that returned "undefined name"?
BTW.. the current version of the script does not handle countries that have switched to polygon-only alerts (ones that no longer include EMMA_IDs in the alerts). I'll have an update (thanks to Wim van der Kuil/PWSdashboard) later in the month of January, 2024.
-
- Posts: 1830
- Joined: Sat 17 Dec 2011 11:55 am
- Weather Station: Davis Vantage Pro2
- Operating System: Windows 11 x64
- Location: Dorset - UK
- Contact:
Re: METEOalarm warnings
I tried UK215
I have the latest geocode and codename files in the correct file.
I get that undefined name on any county that isn't under a warning.
I have the latest geocode and codename files in the correct file.
I get that undefined name on any county that isn't under a warning.
- saratogaWX
- Posts: 1211
- Joined: Wed 06 May 2009 5:02 am
- Weather Station: Davis Vantage Pro Plus
- Operating System: Windows 10 Professional
- Location: Saratoga, CA, USA
- Contact:
Re: METEOalarm warnings
You seem to have the scripts in the ./wxadvisory/ subdirectory. In get-meteoalarm-warning-inc.php you have
unless you have a ./wxadvisory/wxadvisory/ drectory, you probably should use
instead to store the pages in the same directory.
Code: Select all
$alarm_area = 'UK239'; # leave unset-- the $SITE['EUwarnings'] will configure it.
$cacheFileDir = './wxadvisory/';
Code: Select all
$alarm_area = 'UK239'; # leave unset-- the $SITE['EUwarnings'] will configure it.
$cacheFileDir = './';
-
- Posts: 1830
- Joined: Sat 17 Dec 2011 11:55 am
- Weather Station: Davis Vantage Pro2
- Operating System: Windows 11 x64
- Location: Dorset - UK
- Contact:
Re: METEOalarm warnings
All the pages are in the same directory: /wxadvisory/
I wanted it like that, so that all files are kept tidy. There are no errors in regards to file paths.
In any case, using ./ still gives the same "Name not available for Name not available for"
I wanted it like that, so that all files are kept tidy. There are no errors in regards to file paths.
In any case, using ./ still gives the same "Name not available for Name not available for"
- saratogaWX
- Posts: 1211
- Joined: Wed 06 May 2009 5:02 am
- Weather Station: Davis Vantage Pro Plus
- Operating System: Windows 10 Professional
- Location: Saratoga, CA, USA
- Contact:
Re: METEOalarm warnings
Excellent! What was the final fix you used?
-
- Posts: 1830
- Joined: Sat 17 Dec 2011 11:55 am
- Weather Station: Davis Vantage Pro2
- Operating System: Windows 11 x64
- Location: Dorset - UK
- Contact:
Re: METEOalarm warnings
I should've worded it different.. no bugs to fix, I just set it so that the cache files are in their own directory and the php and json files are in the root directory with my advisory page.
I didn't want the cache files to be in the root directory and so I was overthinking it.
Apologies Ken.
Thanks for a great script though!
I didn't want the cache files to be in the root directory and so I was overthinking it.
Apologies Ken.
Thanks for a great script though!
- saratogaWX
- Posts: 1211
- Joined: Wed 06 May 2009 5:02 am
- Weather Station: Davis Vantage Pro Plus
- Operating System: Windows 10 Professional
- Location: Saratoga, CA, USA
- Contact:
Re: METEOalarm warnings
The thanks really go to Wim van der Kuil for his script which he graciously allowed me to adapt for the Saratoga templates. He and I have had a great mutual code sharing for years now. He did the heavy lifting and continues to monitor the somewhat quirky meteoalarm.org data feeds.
The major change coming up is that some countries are adopting alerting by polygon coordinates only and so some major code changes are in progress to support both EMMA_ID and polygon alerting.
Have a Happy, healthy, and prosperous New Year!
The major change coming up is that some countries are adopting alerting by polygon coordinates only and so some major code changes are in progress to support both EMMA_ID and polygon alerting.
Have a Happy, healthy, and prosperous New Year!