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

[IDD #MVE-554056]: LDM example pattern of '/ABI/' on NIMAGE webpage

Hi Daryl,

Sorry for the slow reply.  Yesterday kinda got away from me....

re:
> I'm reviewing your very, very, very helpful NIMAGE page here today:
> 
> https://www.unidata.ucar.edu/data/nimage.html
> 
> and notice LDM pattern examples like:
> 
> /data/ldm/pub/native/satellite/GOES/GOES16/ABI/FullDisk/Channel15/20190221/OR_ABI-L2-CMIPF-M6C15_G16_s20190521950170_e20190521950170_c20190521950170.nc
> 
> shown.  Is the "/ABI/" portion of that example right?  Based on what I am 
> seeing, it is more like "Products/CloudAndMoistureImagery" instead?

You are absolutely correct.  This mistake is undoubtedly a carryover from my
using the GOESR page

https://www.unidata.ucar.edu/data/goesr.html

as my original template when creating the NIMAGE page and then failing to
go back and correct the example LDM/IDD Product IDs to match the NIMAGE feed.

I believe that I have corrected all of the incorrect entries now, but please
let me know if I missed anything.

Thanks for reporting this!!

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: MVE-554056
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.