if you use the weathermap (mesomap) function in build 81 and use metar data on that, then that will stop working
(that is now changed to the new URL in the latest WD update)
Thanks for the replies Niko and Brian. Remember now there is a setting that can be changed but really need to go ahead and make the upgrade. Will do that in a couple of days when the weather settles down.
there is something strange going on
if I do a new setup with the latest version of WD and setup to use a metar, it sets to use the new server
and that works on a test update
but I restart WD , then its like what you are seeing
interestingly a new setup with build 81 which is using the older server , still works
in any case I would say you are going to have to update to the latest version (where I can fix the glitch on that it works the first time but not after restart)
I see whats wrong
it because of the different URL, WD then does not know its a metar station via the URL in the list
which is something that can not be fixed in build 81
but I have fixed that in the latest .zip update of WD
Hi Brian
that’s what I suspected with build 81
last time I ran an updated version the created web map had the info in the wrong places, was ok within WD. That was several months ago.
Will have to get round to testing again with the latest zip
Will this effect the NWS Alerts scripting as well… We are under many watches/warnings (T-Stroms) and nothing is showing. The alert script worked yesterday … today nothing.
I was having trouble with Alerts yesterday and had to change the http:// to https:// to get the script to work.
I have a customized Saratoga script and depending on how the alert file is retrieved it may have to be updated to support SSL (https). I think I had to change the cURL function by adding: curl_setopt($ch,CURLOPT_SSL_VERIFYPEER, false).
You are correct… the NWS changed to ALL https:// urls now, as they promised to do some time ago. I was just caught off guard and Ken caught it and resolved the issue in his scripts. I went through mine as made the correction and all is working now.