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

20041006: NEXRAD station elevations in McIDAS STNLIST (cont.)

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: 20041006: NEXRAD station elevations in McIDAS STNLIST (cont.)
  • Date: Wed, 06 Oct 2004 19:20:45 -0600
>From: McIDAS Help Desk <address@hidden>
>Organization: SSEC
>Keywords: 200410061525.i96FOxUF010647 McIDAS STNDB NEXRAD elevations

Hi Becky,

re: constant 1.26 ratio

>Good catch! I talked to Todd, who is the one responsible for creating
>the STNDB.CORE file. He looked into it, and we get our elevation
>information from the NWS. Of course, we get the elevation in feet and
>convert it to meters. Whoever wrote the script had put an error
>in the conversion equation. It was multiplying the elevation by .3848,
>instead of by .3048.

Ah Ha, and .3848/.3048 = 1.26! :-)

>Todd is redoing the station database now with the
>correct conversion.

Super!

>Let me know if you need the new STNDB.CORE file, or if you can wait
>until a future fastrack.

I would like to have it sooner rather than later since I have been
planning a addendum for Unidata McIDAS users.

>Thanks; See you in a couple weeks (for the IDV seminar).

See you in Boulder soon!

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.