[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[McIDAS #RWL-811432]: 20081004: bad lat/lon for Tuscon upper air data in MD file
- To: dmurray@xxxxxxxxxxxxxxxx
- Subject: [McIDAS #RWL-811432]: 20081004: bad lat/lon for Tuscon upper air data in MD file
- From: "Unidata McIDAS Support" <support-mcidas@xxxxxxxxxxxxxxxx>
- Date: Sat, 04 Oct 2008 17:54:38 -0600
- Delivered-to: support-mcidas@unidata.ucar.edu by laraine.unidata.ucar.edu (Postfix) with ESMTP id D28ADCB18F; Sat, 4 Oct 2008 17:54:38 -0600 (MDT) id B2E4662900; Sat, 4 Oct 2008 17:54:38 -0600 (MDT)
Hi Don,
re:
> I'm looking at the upper air data and found that the lat/lon
> for the Tuscon, AZ station (72274) is bad. STNLIST shows:
>
> chico.unidata.ucar.edu: stnlist.k 72274
> IDN ID Station Name Data Types ST CO LAT LON ELE
> ----- ----- -------------------- ----------------- -- -- ---------- ---------- ----
> 72274 KTUS Tucson M 36RT EG AZ US 32:07:53 110:57:19 805
> 72274 KTWC Tuscon R AZ US -213906:21:44 -213906:21:44 0
> Number of stations listed: 2
> stnlist.k: Done
>
> It looks like getting rid of the second entry would fix this.
>
> In the latest MD file, 72274 is in column 11.
>
> I've coded around this (trying to do a barnes analysis) for now.
I assumed that this would be easy to override by making an appropriate entry
in the STNDB.SITE file, but I have not yet been able to get this to work.
As soon as I do, I will update the STNDB.SITE file in the McIDAS v2007/2008
distributions and cut new addenda.
Cheers,
Tom
--
****************************************************************************
Unidata User Support UCAR Unidata Program
(303) 497-8642 P.O. Box 3000
support@xxxxxxxxxxxxxxxx Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage http://www.unidata.ucar.edu
****************************************************************************
Ticket Details
===================
Ticket ID: RWL-811432
Department: Support McIDAS
Priority: Normal
Status: Closed