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

RE: NEXRAD data feeds



Hi All,

Slight correction...

The FNEXRAD feed that has the 1Km nat'l mosaic is only the base
reflectivity product...We are exploring other products such as 1 hr
precip, 3 hr precip (but are not generating or distributing on a regular
basis currently)..but, the velocity products do not mosaic as exiting
velocities for one radar are approaching velocities for another.

So, as Tomislav stated, it may be best to get ALL radars for the level III
data so you have access to these other derived paramaters, and  use the
1km base ref as a starting point...i.e. let you know which radars may have
interesting events..

If/as we begin generating mosaics of the precip products, you may want to
cease the NNEXRAD feed..but I have no timeline currently for this.


The volume of this feed is approximately:


NNEXRAD
150-200 MB/hour..always dynamic, depending upon weather.

Please see:

http://my.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NNEXRAD+shemp.unidata.ucar.edu


and for FNEXRAD


25-35MB/hour

Please see:

http://my.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?FNEXRAD+shemp.unidata.ucar.edu


Hope this clears things up a bit..let me know if you have any questions.

Cheers,


Jeff
---------------------------------------------------------------------
Jeff Weber                                    address@hidden        :
Unidata Program Center                        PH:303-497-8676        :
University Corp for Atmospheric Research      3300 Mitchell Ln       :
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000  :
---------------------------------------------------------------------

On Thu, 9 Sep 2004, David Maidment wrote:

> Tomislav:
>
> Nexrad stage III is a mosaiced coverage of the US where the data
> from individual radar sites have already been merged.  I'm not sure
> if its possible to get a feed just of part of the country, and even
> if it is, rainfall phenomena dont' respect state boundaries too much.
> For example, somebody in Texas might well want to get a sense of
> what the impact of Hurricane Frances would have been on Texas if
> it had occured here rather than in Florida.
>
> David
>
>
> -----Original Message-----
> From: Tomislav Urban [mailto:address@hidden]
> Sent: Thursday, September 09, 2004 1:24 PM
> To: David Maidment; Jeff Weber; Ben Domenico
> Cc: address@hidden; Venkatesh Merwade
> Subject: RE: NEXRAD data feeds
>
>
> Jeff -
>
> OK, so we want the FNEXRAD and NNEXRAD feeds for now, (David - correct
> me if I'm wrong, but I assume we want to collect ALL the sites?)
>
> Can you provide a quick back of the envelope on how much data (per hour,
> day, week, or year, whatever is convenient)?  For the above for all
> sites?
>
> Thanks!
>
> - Tomislav
>
>
>
> -----Original Message-----
> From: David Maidment [mailto:address@hidden]
> Sent: Thursday, September 09, 2004 2:19 PM
> To: Jeff Weber; Ben Domenico
> Cc: address@hidden; Tomislav Urban; Venkatesh Merwade
> Subject: RE: NEXRAD data feeds
>
> Jeff:
>
> Wow!  I am glad I know somebody who knows about this stuff!
>
> Tomislav -- Jeff Weber is a friend of mine at Unidata who knows all the
> acronyms and is helping us interpret this stuff.  He says:
>
> "I suspect you would want the level III data as it more accurately
> delivers what I think you want ( 1 & 3 hour storm totals, and storm
> total precip)"
>
> And I think he is right.   Level II data is more accurate but requires a
> lot
> more site specific processing before we can actually get rainfall
> values. Lets start with the Level III stuff which is more directly
> usable.
>
> Jeff -- can you tell Tomislav how to select these data streams from the
> whole Nexrad feed?
>
> Appreciate your help.
>
> David
>
>
> -----Original Message-----
> From: Jeff Weber [mailto:address@hidden]
> Sent: Thursday, September 09, 2004 11:23 AM
> To: David Maidment; Ben Domenico
> Cc: address@hidden
> Subject: NEXRAD data feeds
>
>
> Hi David,
>
> Basically it breaks down like this:
>
> NNEXRAD
> FT27, NEXRAD
> NOAAport NEXRAD
>
> and
>
> NEXRD2
> FT28, CRAFT
> Reserved for CRAFT level 2 radar data distribution
>
>
> and
>
> FNEXRAD
> FT13, NMC
> NOAAPORT NEXRAD Floater
>
>
> [this is the feed that contains the 1km nat'l mosaic which is in GINI
> format...gridded]
>
>
> NNEXRAD is the level III (NIDS) data "products".
>
> These products are derived from the level II data.
>
> The NIDS products include:
>
> DPA     N0S     N0Z     N1R     N1V     N2S     N3S     NET     NVL
> N0R     N0V     N1P     N1S     N2R     N3R     NCR     NTP     NVW
>
>
> which translates to:
>
>
>     Base Relectivity
>     Composite Reflectity
>     Layer Composite Reflectivity
>     Echo Tops
>     Vertically Integrated Liquid
>     One-Hour Precipitation
>     Three-Hour Precipitation
>     Storm Total Precipitation
>     Hourly Digital Rainfall Array
>     Radial Velocity
>     Velocity Azimuth Display Wind
>     Free Text Message
>
>
> The level II data is volumetric and contains all tilts in its scan...but
> parameters such as 1 hr precip, are not represented. You can create your
> own algorithm to determine rain rates based upon reflectivity values.
>
>
>
>
> I suspect you would want the level III data as it more accurately
> delivers what I think you want ( 1 & 3 hour storm totals, and storm
> total precip)
>
> and also the floater FNEXRAD to get the 1 Km mosaic of base
> reflectivity.
>
>
> So in a nutshell
>
> FNEXRAD
>
> and
>
> NNEXRAD ( and a list of sites, or do you want ALL of them)
>
> Thoughts....
>
>
> Jeff
> ---------------------------------------------------------------------
> Jeff Weber                                    address@hidden        :
> Unidata Program Center                        PH:303-497-8676        :
> University Corp for Atmospheric Research      3300 Mitchell Ln       :
> http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000  :
> ---------------------------------------------------------------------
>
> On Thu, 9 Sep 2004, Unidata Support wrote:
>
> >
> > ------- Forwarded Message
> >
> > >To: General Support <address@hidden>
> > >From: Ben Domenico <address@hidden>
> > >Subject: RE: NexRad Data (fwd)
> > >Organization: UCAR/Unidata
> > >Keywords: 200409091630.i89GU7nK011179
> >
> > Hi,
> >
> > I'm forwarding this note from David Maidment to our support email
> > list, so we can get the mail into the tracking system and have the
> > proper experts respond.
> >
> > -- Ben
> >
> > ---------- Forwarded Message ----------
> > Date: Thursday, September 09, 2004 11:17 AM -0500
> > From: David Maidment <address@hidden>
> > To: Ben Domenico <address@hidden>
> > Subject: RE: NexRad Data
> >
> >
> > Ben:
> >
> > Can you help us to understand what we are dealing with concerning
> > Nexrad data feeds from
> > Unidata.   Tomislav is trying to build up a data collection at the
> Texas
> > Advanced Computation
> > Center of Nexrad information that we can use for flood analysis and
> > forecasting.   We are a
> > bit bewildered by the plethora of Nexrad products that you have.
> >
> > David
> >
> >
> >
> >
> > -----Original Message-----
> > From: Tomislav Urban [mailto:address@hidden]
> > Sent: Thursday, September 09, 2004 9:47 AM
> > To: David Maidment
> > Cc: address@hidden
> > Subject: NexRad Data
> >
> >
> >
> > David --
> >
> >
> >
> > I would need to know which data products we would like to include in
> > the TG collection.  This is the list provided by UniData, it seems
> > that there are 3 NexRad related streams:
> >
> >
> >
> > NNEXRAD
> >
> > FT27, NEXRAD
> >
> > NOAAport NEXRAD
> >
> >
> > NEXRD2
> >
> > FT28, CRAFT
> >
> > Reserved for CRAFT level 2 radar data distribution
> >
> >
> > NXRDSRC
> >
> > FT29
> >
> > Reserved for NCDC use for archiving NEXRAD level 2 data.
> >
> >
> >
> > Please let me know which would be most appropriate.  Thanks!
> >
> >
> >
> > Primary Name
> >
> > Alternate Names*
> >
> > Description
> >
> >
> > PPS
> >
> > FT0
> >
> > Public Products Service
> >
> > DDS
> >
> > FT1, DOMESTIC
> >
> > Domestic Data Service
> >
> > HDS
> >
> > FT2, HRS
> >
> > High resolution Data Service
> >
> >
> > IDS
> >
> > FT3, INTNL
> >
> > International Data Service
> >
> >
> > SPARE
> >
> > FT4
> >
> > Spare, available for IDD use.
> >
> >
> > UNIWISC
> >
> > MCIDAS, FT5
> >
> > Satellite imagery and derived products from the Unidata/Wisconsin
> > Broadcast
> >
> >
> > PCWS
> >
> > FT6, ACARS
> >
> > ACARS data, from commercial aircraft
> >
> >
> > FSL2
> >
> > FT7, PROFILER
> >
> > Wind profiler data from FSL
> >
> >
> > FSL3
> >
> > FT8
> >
> > Reserved for FSL use
> >
> >
> > FSL4
> >
> > FT9
> >
> > Reserved for FSL use
> >
> >
> > FSL5
> >
> > FT10
> >
> > Reserved for FSL use
> >
> >
> > AFOS
> >
> > FT11, NMC1, GPSSRC
> >
> > National Weather Service AFOS
> >
> >
> > NMC2
> >
> > FT12, NCEPH
> >
> > CONDUIT model data
> >
> >
> > FNEXRAD *
> >
> > FT13, NMC3
> >
> > NOAAPORT NEXRAD Floater
> >
> > NLDN
> >
> > FT14
> >
> > National Lighting Data Network
> >
> >
> > WSI
> >
> > FT15
> >
> > NIDS radar products
> >
> >
> > DIFAX
> >
> > FT16
> >
> > Unidata community-generated replacement for defunct DIFAX feed
> >
> >
> > FAA604
> >
> > FT17, FAA, 604
> >
> > FAA604 products for NWS use (private network), but available for IDD
> > use.
> >
> >
> > GPS
> >
> > FT18
> >
> > Reserved for use in SuomiNet
> >
> >
> > FNMOC *
> >
> > FT19, SEISMIC, NOGAPS
> >
> > NOGAPS and COAMP model data from FNMOC
> >
> > GEM
> >
> > FT20, CMC
> >
> > Canadian Meteorological Center GEM model outputs.
> >
> >
> > NIMAGE
> >
> > FT21, IMAGE
> >
> > NOAAport imagery (for future use)
> >
> >
> > NTEXT
> >
> > FT22, TEXT
> >
> > NOAAport text products (for future use)
> >
> >
> > NGRID
> >
> > FT23, GRID
> >
> > NOAAport gridded binary (GRIB, GRID) products (for future use)
> >
> >
> > NPOINT
> >
> > FT24, POINT, NBUFR, BUFR
> >
> > Reserved for NOAAport point products (for future use)
> >
> >
> > NGRAPH
> >
> > FT25, GRAPH
> >
> > NOAAport Redbook Graphics (for future use)
> >
> >
> > NOTHER
> >
> > FT26, OTHER
> >
> > Reserved for other NOAAport data (for future use)
> >
> >
> > NNEXRAD
> >
> > FT27, NEXRAD
> >
> > NOAAport NEXRAD
> >
> >
> > NEXRD2
> >
> > FT28, CRAFT
> >
> > Reserved for CRAFT level 2 radar data distribution
> >
> >
> > NXRDSRC
> >
> > FT29
> >
> > Reserved for NCDC use for archiving NEXRAD level 2 data.
> >
> > EXP
> >
> > FT30
> >
> > For testing, experiments, and transient or low-interest data streams
> >
> >
> > ANY
> >
> > FT0 | FT1 | FT2 | ... | FT31
> >
> > Predefined feed set name for any feed type
> >
> >
> > NONE
> >
> > -
> >
> > Predefined feed set name for no feed types (will not match anything)
> >
> >
> > DDPLUS
> >
> > FT0 | FT1
> >
> > Predefined feed set name for PPS or DDS.
> >
> >
> > WMO
> >
> > FT0 | FT1 | FT2 | FT3
> >
> > Predefined feed set name for PPS, DDS, HDS, or IDS.
> >
> >
> > UNIDATA
> >
> > FT0 | FT1 | FT2 | FT3 | FT5
> >
> > Predefined feed set name for PPS, DDS, HDS, IDS, or MCIDAS.
> >
> >
> > FSL
> >
> > FT6 | FT7 | FT8 | FT9 | FT10
> >
> > Predefined feed set name for PCWS, FSL2, FSL3, FSL4, or FSL5.
> >
> >
> > NMC
> >
> > FT11 | FT12 | FT13
> >
> > Predefined feed set name for AFOS, NMC2, or NMC3.
> >
> >
> > NPORT
> >
> > FT22 | FT23 | FT24 | FT25 | FT26
> >
> > Predefined feed set name for NTEXT, NGRID, NPOINT, NGRAPH, or NOTHER.
> >
> >
> >
> >
> >
> >
> > ---------- End Forwarded Message ----------
> >
> >
> >
> > --
> >
> ************************************************************************
> > Unidata User Support                                    UCAR Unidata
> > (303)497-8643                                                  P.O.
> > address@hidden                                   Boulder, CO
> >
> ------------------------------------------------------------------------
> > Unidata WWW Service
> > ----------------------------------------------------------------------
> > 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.
> >
> > ------- End of Forwarded Message
> >
>