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

[LDM #FIK-556169]: LDM - Acquiring a specific station

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: [LDM #FIK-556169]: LDM - Acquiring a specific station
  • Date: Wed, 07 Jun 2006 08:40:56 -0600
Hi Ben,

re:
> We are trying to get metar data for a specific station (KLGU)
> from the ldm feed, but so far my attempts have been unsuccessful.
> Here is the pqact.conf entry:
> IDS|DDPLUS  ^SAUS.. ... (..)(..) .*KLGU
> FILE    data/\2_KLGU.metar
> 
> We have another entry that just grabs all stations (ie we take off
> the ".*KLGU" part) and I see the KLGU station in the dump to that file.
> I am wondering if the problem is that this entry only works on the WMO
> header, and doesn't look into the "body" of the data.

Your surmise is exactly correct. The patterns you can specify in ldmd.conf
request and pqact.conf action lines _only_ act on product ID information.

The best/easiest way to test an action you want to include in your pqact.conf
processing is to use the LDM 'notifyme' utility to see if the pattern you
want to specify will match.  Here is  simple example that will show that
your pattern does not match anything:

<as 'ldm' on your LDM machine>
notifyme -vxl- -f ANY -o 10000 -p KLGU

The pattern specified ('-p KLGU') will match if KLGU is specified anywhere
in any product header that you receive.  If you let this 'notifyme' invocation
run for long enough, you will see that the pattern never matches.

What you likely want to do is find out which pattern will match the
product that contains METAR data for KLGU and then use it in your pqact.conf
action.  If you only want the KLGU METAR, then you would need to parse the
full product listing to extract the KLGU information.

There is, however, another and perhaps easier way to solve your problem:
use the McIDAS SFCRPT command and ask for KLGU METAR reports for the last
'n' hours.  Here is a quick example:

<as 'mcidas' or any user whose Unix account has been configured to run McIDAS>
cd $MCDATA
dataloc.k ADD RTWXTEXT webcat.gis.usu.edu
sfcrpt.k KLGU 24                           <- request KLGU METARS for the past
                                              24 hours

This should return a listing that looks something like:

KLGU 071351Z AUTO 33003KT 10SM CLR 17/11 A2997 RMK AO2
     SLP093 T01720106=
KLGU 071251Z AUTO 33005KT 10SM CLR 13/09 A2997 RMK AO2
     SLP094 T01330089=
KLGU 071251Z AUTO 33005KT 10SM CLR 13/09 A2997 RMK AO2
     SLP094 T01330089=
KLGU 071151Z AUTO 00000KT 10SM CLR 12/08 A2996 RMK AO2
     SLP091 T01220083 10228 20117 53006=
KLGU 071051Z AUTO 11005KT 10SM CLR 13/09 A2995 RMK AO2
     SLP086 T01280089=
KLGU 070951Z AUTO 03006KT 10SM CLR 14/10 A2994 RMK AO2
     SLP084 T01390100=
KLGU 070851Z AUTO 00000KT 10SM CLR 16/11 A2994 RMK AO2
     SLP082 T01560106 50003=
KLGU 070751Z AUTO 23004KT 10SM CLR 17/13 A2995 RMK AO2
     SLP085 T01670128=
KLGU 070651Z AUTO 00000KT 10SM CLR 19/11 A2994 RMK AO2
     SLP084 T01890111 403440083=
KLGU 070551Z AUTO 00000KT 10SM CLR 19/11 A2993 RMK AO2
     SLP080 T01940111 10333 20189 51006=
KLGU 070451Z AUTO 16010KT 10SM CLR 26/06 A2993 RMK AO2
     SLP075 T02560061=
KLGU 070351Z AUTO 15008KT 10SM CLR 25/10 A2992 RMK AO2
     SLP076 T02500100=
KLGU 070251Z AUTO 13004KT 10SM CLR 26/11 A2991 RMK AO2
     SLP076 T02610111 56006=
KLGU 070151Z AUTO 20003KT 10SM CLR 29/14 A2991 RMK AO2
     SLP077 T02890139=
KLGU 070051Z AUTO 00000KT 10SM CLR 32/06 A2991 RMK AO2
     SLP079 T03220056=
KLGU 062351Z AUTO 35004KT 10SM CLR 33/05 A2993 RMK AO2
     SLP086 T03280050 10344 20256 56019=
KLGU 062251Z AUTO 35004KT 10SM CLR 33/05 A2994 RMK AO2
     SLP087 T03280050=
KLGU 062151Z AUTO 00000KT 10SM CLR 32/04 A2997 RMK AO2
     SLP098 T03220044=
KLGU 062051Z AUTO 00000KT 10SM CLR 31/04 A2999 RMK AO2
     SLP107 T03110039 58018=
KLGU 061951Z AUTO VRB04KT 10SM CLR 29/04 A3001 RMK AO2
     SLP114 T02940044=
KLGU 061851Z AUTO 30005KT 10SM CLR 28/03 A3004 RMK AO2
     SLP125 T02780028=
KLGU 061751Z AUTO VRB04KT 10SM CLR 26/06 A3005 RMK AO2
     SLP132 T02560056 10256 20083 58006=
KLGU 061651Z AUTO 04005KT 10SM CLR 23/07 A3006 RMK AO2
     SLP137 T02330072=
KLGU 061551Z AUTO 00000KT 10SM CLR 20/07 A3008 RMK AO2
     SLP140 T02000067=
KLGU 061451Z AUTO 00000KT 10SM CLR 17/08 A3008 RMK AO2
     SLP138 T01720078 51005=
SFCRPT: Done

If you would like to pursue use of McIDAS to access things like
METAR data for KLGU, please open an new inquiry by sending an
email to 'address@hidden'.

> Thanks!

No worries.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: FIK-556169
Department: Support IDD
Priority: Normal
Status: Closed