Fix names/units for variables on METAR netcdf files

Unidata / thredds

THREDDS Data Server v4.6

https://www.unidata.ucar.edu/software/tds/v4.6/index.html

265 stars 179 forks source link

Fix names/units for variables on METAR netcdf files #140

Open dopplershift opened 9 years ago

dopplershift commented 9 years ago

There are some curious issues in the netcdf files for METAR data on http://thredds.ucar.edu:

Names are not all CF-Compliant: e.g. inches_ALTIM, hectoPascal_ALTIM
The units on altimeter setting are 'inches'. This should be changed to udunits for 'in Hg'

Would be nice to make the new units compatible with MetPy/Siphon.

lesserwhirls commented 9 years ago

If you look in the idd/pqact/cdl directory, you will see where these are set (I think). Should be an easy fix without having to rework the decoders. I'll take a look and see.

Sean

On Sunday, June 21, 2015, Ryan May notifications@github.com wrote:

There are some curious issues in the netcdf files for METAR data on http://thredds.ucar.edu:

Names are not all CF-Compliant: e.g. inches_ALTIM, hectoPascal_ALTIM

The units on altimeter setting are 'inches'. This should be changed to udunits for 'in Hg'

Would be nice to make the new units compatible with MetPy/Siphon.

— Reply to this email directly or view it on GitHub https://github.com/Unidata/thredds/issues/140.

dopplershift commented 9 years ago

It's also odd that it calls these "altim" which I think means altimeter setting, but then it also calls them "pressure at station"; these are two completely different things.

dopplershift commented 9 years ago

More things I have noticed:

The data returned (at least in CSV) have the field time rather than date, as in NCSS grid as point.
String format for times is %Y-%m-%d %H:%M:%SZ--note the lack of a T in the middle
Times are returned with increasing date, but decreasing time

lesserwhirls commented 9 years ago

I wonder what they are called in the WMO or NWS decoding docs.

On Sunday, June 21, 2015, Ryan May notifications@github.com wrote:

It's also odd that it calls these "altim" which I think means altimeter setting, but then it also calls them "pressure at station"; these are two completely different things.

— Reply to this email directly or view it on GitHub https://github.com/Unidata/thredds/issues/140#issuecomment-113941714.

dopplershift commented 9 years ago

Also, wondering why BJC is the nearest station to 40, -105. Why no Boulder or Longmont obs?

lesserwhirls commented 9 years ago

The station list may not be up to date. It's hand maintained, I think.

On Sunday, June 21, 2015, Ryan May notifications@github.com wrote:

Also, wondering why BJC is the nearest station to 40, -105. Why no Boulder or Longmont obs?

— Reply to this email directly or view it on GitHub https://github.com/Unidata/thredds/issues/140#issuecomment-113950434.

JohnLCaron commented 8 years ago

reading metars from metar2nc bastard files. whats the long range fix here?

dopplershift commented 8 years ago

Long range fix captured in more appropriate venue on unidata/TDSConfig#2.