[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDFDecoders #MHV-467373]: metar2nc.new1 error

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDFDecoders #MHV-467373]: metar2nc.new1 error
  • Date: Thu, 16 Dec 2010 11:16:51 -0700
Art,

There were a couple minor things causing problems, your samplemetar.dat had an 
unexpected CR at the end of file and the -c flag needs to be used if the data 
is over a day old. The -c flag was implemented because so much data was coming 
in with the wrong time stamps, ie in the future or months ago. Your test file 
did bring up an interesting case, WRKTTU key was found. I've never seen this 
before and the METARs in that bulletin seem to be non-US. Do you know anything 
about WRKTTU key? Also the station IDs were not in GEMPAK Metar file, so I'm 
going to start keeping a record of unknown stations and then add them to the 
cdl file. A side note, if a station is not in the cdl then it's skipped because 
the lat/lon description information is not known. 

%  metar2nc.new1 -c metar.cdl.new1 data 201012 < samplemetar.dat

I'm attaching metar2nc.new1 that accommodates the problems.

Robb...

Ticket Details
===================
Ticket ID: MHV-467373
Department: Support netCDF Decoders
Priority: Normal
Status: Open

Attachment: metar2nc.new1
Description: Binary data