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

[LDM #JXO-344446]: Alaska profiler data

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 #JXO-344446]: Alaska profiler data
  • Date: Wed, 05 Feb 2020 13:21:59 -0700
Hi,

re:
> I work in the radar group at NOAA/PSD, here in Boulder, that feed wind
> profiler data to Unidata for the sites that we operate across the western
> U.S.

OK.

re:
> We are looking to ingest NWS-operated wind profiler data from sites
> in Alaska, and were informed by the NWS Radar Operations Center that those
> data are available on the FSL2 feed though Unidata.

The information provided to you by the NWS Radar Operations Center is
most likely using knowledge that has been out of date for several years.
The FSL2 feed used to contain all of the profilers that were in the old
national profiler network, but that network was dismantled quite some
time ago.

re:
> I have already
> verified that those data are not available through in-house LDM servers at
> GSD and MADIS, and was hoping that we could use a Unidata server to acquire
> them.

The only profiler data we are receiving is the set that is being provided
by NOAA/PSD.  A quick look at the Product IDs for this "test" feed does
not show any data from Alaska.

re:
> Since we currently acquire some NEXRAD3 products from
> idd.unidata.ucar.edu, I monitored the FSL2 feed on idd (via notifyme), but
> no products were listed.

Correct.

re:
> So, I'm assuming that we're currently not allowed
> to access that feedtype on idd or I'm monitoring the wrong server for that
> feedtype.  The LDM server that I'd like to use to acquire these data
> is 140.172.38.113

If we had the data, you would automatically be ALLOWed to REQUEST it, but,
unfortunately, we do not have the data you are looking for, sorry.

re:
> Thank you!

No worries.  I'm sorry that we couldn't be of more (any) help!

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: JXO-344446
Department: Support IDD
Priority: Normal
Status: Closed
===================
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.