update due to change to https by NOAA for metar downloads

new update of WD
or use direct
http://www.weather-display.com/downloadfiles/cronmetardownload.zip

(only affected if you have set to use http for the metar download)

Great timing, thanks Brian.

Thanks, Brian.

Hi, I take it that you just down load, & then open it into WD ?.

many thanks.

teal.

Hi

Yes download the zip fil and unzip. Move the file to your weather display folder.

Hi, thanks for just making sure cheers.

teal.

My METAR data stopped working in early February, presumably caused by this change. I’m running the latest build of WD which already has this updated .exe file from the ZIP file mentioned in this thread.

I’m still am not getting the custom field %weatherreport% populated from the downloaded METAR for observed weather reading. The only files now available for download for my three METAR sites are TAF files. I’ve gone through every possible combination of check boxes in WD to make this work, including it is is a TAF metar. I use the custom %weatherreport% in wxlocal30.html and it’s the 37th entry in the array and it’s now just a null value.

Is there a different custom field we’re now supposed to use or some combination of settings?

I’m using KSEA.TAF, KBFI.TAF, and KPAE .TAF and have KSEA.TAF set as the Use this metar as icon/icon conditions. I also tried entering this as .TXT extensions even though the downloaded files are .TAF. Settings I’ve also tried adjusting:

  • Use the metar to update wd’s main weather condition report
  • Save as a .txt file as well as a .met file
  • It is a ASOS/SYNOP metar
  • It is a taf metar

are you sure you have the latest cronmetardownload.exe version?
what is the modified date/time on that file?
try grabbing it from
http://www.weather-display.com/downloadfiles/cronmetardownload.zip

The one in c:\wdisplay is actually newer: 2/5/2019 8:10 AM. The one in the ZIP is 2/4/2019 11:10 AM. Both same size. I’ve copied over the one from ZIP just to be sure.

The TAF files are downloading, but wx30.html still getting a null value for %weatherreport%.

I am not sure why the metar is not downloading for you when it is for me and others
what windows version?

Unfortunately, it’s not just me. Another site I help with has the same issue with metars from a different part of the US. We both broke in early February.

Both on Windows 10 Pro
Microsoft Windows [Version 10.0.17763.253]

Weather Display
10-37S Build 90 -12 Feb 2019

To be clear, we’re getting TAF files downloaded, but that’s it.

Can you verify which check boxes should be set on the METAR Downloads tab to process these coming down as TAF?

And should we specificy KXXX.txt or KXXX.taf for the station IDs?

Thanks!

testing here
I get
151: HTTP protocol error. 404 Not Found.
https://aviationweather.gov/adds/dataserver_current/httpparam?datasource=tafs&requestType=retrieve&format=xml&mostRecentForEachStation=true&hoursBeforeNow=2&stationString=KSEA
Downloading TAF:https://aviationweather.gov/adds/dataserver_current/httpparam?datasource=tafs&requestType=retrieve&format=xml&mostRecentForEachStation=true&hoursBeforeNow=2&stationString=KSEA
Downloading to :C:\wdisplayprogram\metar\KSEA.taf

I’m not seeing the 151 error. Those links open fine for me directly in a Chrome browser. What WD is putting in the metar folder is a .taf file (KSEA.taf):

Contents:
KSEA 171747Z 1718/1824 19003KT P6SM BKN015 OVC020 FM171900 VRB03KT P6SM BKN020 OVC060 FM172100 34006KT P6SM SCT025 BKN040 FM180000 35003KT P6SM SCT025 BKN040 FM180700 11004KT P6SM SCT015 BKN030 FM181200 11004KT P6SM SCT010 BKN025 FM182100 23004KT P6SM SCT025 OVC060

ops
I had put in the list KSEA.TAF instead of KSEA.TXT
now it works
*** version Metar Download vers 2.0

Next file HTTP metar station download
https://tgftp.nws.noaa.gov/data/observations/metar/decoded/KSEA.TXT
Downloading to :C:\wdisplayprogram\metar\KSEA.met
final download setting=C:\wdisplayprogram\metar\KSEA.met
Doing metar download now
Attempting to connect to server.
OK
Socket connection established.
Starting secure channel handshake.
Enabling TLS versions: TLS1.2 TLS1.1 TLS1.0
Cipher Suites:
TLS_KRB5_EXPORT_WITH_RC2_CBC_40_MD5 (0x002a);
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c);
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b);
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030);
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f);
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f);
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e);
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024);
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023);
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028);
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027);
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a);
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009);
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014);
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013);
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d);
TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c);
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d);
TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c);
TLS_RSA_WITH_AES_256_CBC_SHA (0x0035);
TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
Sending 174 bytes of handshake data.
Receiving 1330 bytes of handshake data.
Receiving 2048 bytes of handshake data.
Receiving 802 bytes of handshake data.
Selected TLS Version: TLS1.2
Selected Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
Receiving 342 bytes of handshake data.
Sending 126 handshake bytes.
Receiving 51 bytes of handshake data.
OK
OU=Domain Control Validated, CN=dev.ncep.noaa.gov
C=US, S=Arizona, L=Scottsdale, O=“GoDaddy.com, Inc.”, OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Negotiated SSL parameters: Protocol: TLS1.2 Cipher: AES Cipher strength: 256 Hash: SHA384 Hash strength: 0 Key exchange: ECDH Ephemeral RSA Key exchange strength: 256
OK
Connected
OK
OK
https://aviationweather.gov/adds/dataserver_current/httpparam?datasource=tafs&requestType=retrieve&format=xml&mostRecentForEachStation=true&hoursBeforeNow=2&stationString=KSEA
Downloading TAF:https://aviationweather.gov/adds/dataserver_current/httpparam?datasource=tafs&requestType=retrieve&format=xml&mostRecentForEachStation=true&hoursBeforeNow=2&stationString=KSEA
Downloading to :C:\wdisplayprogram\metar\KSEA.taf
Doing TAF metar download now
Attempting to connect to server.
OK
Socket connection established.
Starting secure channel handshake.
Enabling TLS versions: TLS1.2 TLS1.1 TLS1.0
Cipher Suites:
TLS_KRB5_EXPORT_WITH_RC2_CBC_40_MD5 (0x002a);
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c);
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b);
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030);
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f);
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f);
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e);
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024);
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023);
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028);
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027);
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a);
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009);
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014);
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013);
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d);
TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c);
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d);
TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c);
TLS_RSA_WITH_AES_256_CBC_SHA (0x0035);
TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
Sending 175 bytes of handshake data.
Receiving 2048 bytes of handshake data.
Receiving 2007 bytes of handshake data.
Sending 126 handshake bytes.
Receiving 242 bytes of handshake data.
OK
C=US, S=Maryland, L=College Park, O=National Oceanic and Atmospheric Administration NOAA, CN=weather.gov
C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA
Negotiated SSL parameters: Protocol: TLS1.2 Cipher: AES Cipher strength: 256 Hash: SHA384 Hash strength: 0 Key exchange: ECDH Ephemeral RSA Key exchange strength: 256
OK
Connected
OK
OK
Finished downloading metars

what shows in your metardownloadlog.txt

[ul]Looks like something might have finally triggered it. This time when I clicked test, I got .txt, .met, and .taf files for KSEA, KBFI, and KRNT. wx30.html is now getting the observation condition.

On the METAR Downloads tab, I’ve got these entries:
KRNT.TXT
KBFI.TXT
KSEA.TXT
Use this metar for local sky/icon conditions: KSEA.TXT

Checked:

  • Use the metar to update WD’s main weather condition report
  • Save as a .txt file as well as a .met file
  • It is an ASOS/SYNOP metar
    [li]It is a TAF metar[/li][/ul]

The log file is attached.

Thanks, Brian. I’ll see if it keeps updating.


metardownloadlog.txt (13.1 KB)

Well, worked for a few hours, but now I’m getting “-T” for the %weatherreport% field.

Where it’s getting that from the KSEA METAR, beats me:
SEATTLE-TACOMA INTERNATIONAL AIRPORT , WA, United States (KSEA) 47-27N 122-19W 136M
Feb 17, 2019 - 07:53 PM EST / 2019.02.18 0053 UTC
Wind: from the NNE (020 degrees) at 3 MPH (3 KT):0
Visibility: 10 mile(s):0
Sky conditions: mostly cloudy
Temperature: 42.1 F (5.6 C)
Dew Point: 32.0 F (0.0 C)
Relative Humidity: 67%
Pressure (altimeter): 30.23 in. Hg (1023 hPa)
ob: KSEA 180053Z 02003KT 10SM BKN035 06/00 A3023 RMK AO2 SLP247 T00560000
cycle: 1

Just to close this out, I now have it working again for all three METAR locations and the %currentreport% custom field. While trying to get the TAF downloads to work and was only getting TAD files, I had selected the It is a TAF METAR check box which was messing things up. All good now.