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.
Michael, You can change the elevaltion in the station table used by the data decoder in $GEMTBL/stns. The elevation of 1615m seems correct based on the NCDC/USAF table ftp://ncardata.ucar.edu/datasets/ds900.0/data/1999.01 Steve Chiswell Unidata User Support On Fri, 6 Jul 2001, Michael E. Splitt wrote: > Steven, > > I run QC algorithms for the MesoWest program > (http://www.met.utah.edu/mesowest). > The algorithms were flagging data from YOHO PARK (in Canada). When I did > some > further troubleshooting, I found that the elevation for YOHO PARK is > listed as 60 meters. > The low elevation ended up being the cause for the flagging. I found the > following > metadata at: > > http://www.ldeo.columbia.edu/~dery/WVRTombstone.htm > > > LAT LON ELV > YOHO PARK CS WYL 71786 5127 11620 1615.0 > > From GEMPAK page: > > LAT LON ELV > WYL 71786 YOHO PARK (AUTO8) AB CN 5145 -11633 > 60 > > I believe the 1615 is likely much closer to the actual elevations... how > do you go > about making corrections to the station metadata? > > Cheers, > > Mike > > ****************************************************************************** > Michael E. Splitt > NOAA Cooperative Institute for Regional Prediction > UNIVERSITY OF UTAH > 155 South 1452 East Rm 480 > SALT LAKE CITY UT 84112-0190 > > Phone: (801) 585-1413 > Fax: (801) 581-4362 > Email: address@hidden > > >