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.
Hi Carol, re: > I'm in the process of creating a new local dataset to process older GOES-16 > data. Greg showed me how to get the archived GOES-16 data, and the > filenames are in the following format. > > OR_ABI-L1b-RadF-M3C14_G16_s20182230100463_e20182230111229_c20182230111294.nc SSEC notes that this naming convention is what is used in NOAA CLASS or decoded from the GRB data stream using CSPP Geo. The McIDAS ADDE server _requires_ that GOES-R class satellite images be named using this form. re: > I originally thought these were in netCDF format, but Greg explained they > were the native format that should work in McIDAS. You are correct, these files are in netCDF4 format. SSEC added support for select netCDF4 format data files a couple of years ago. re: > In order to create a new dataset, I ran the following DSSERVE > > dsserve.k ADD MYDATA/GOESC14 AREA TYPE=IMAGE > DIRFILE='/mnt/satellite/restore/OR_ABI-L1b-RadF-M3C14*' The DSSERVE invocation should be: dsserve.k ADD MYDATA/GOESC14 ABIN TYPE=IMAGE DIRFILE="/mnt/satellite/restore/OR_ABI-L1b-RadF-M3C14*" NB: I recommend that you also include a comment in the dataset definition. Something like the following would be useful to those using the dataset down the road: dsserve.k ADD MYDATA/GOESC14 ABIN TYPE=IMAGE DIRFILE='/mnt/satellite/restore/OR_ABI-L1b-RadF-M3C14*' \"GOES-16 Full Disk Channel 14 re: > Next, I ran a quick IMGLIST. For reference, there are only 4 files included > in this DIRFILE reference which represents 24 hours of satellite data for > one channel. > > $imglist.k MYDATA/GOESC14.ALL > Image file directory listing for:MYDATA/GOESC14 > imglist.k: No images satisfy the selection criteria > imglist.k: done > > Any ideas how I'm running the dsserve incorrectly? The problem goes back to using the incorrect type in the DSSERVE command. The rest looks OK. re: > Could this be a permission issue? It is not likely, but you should always make sure that the set of images specified in the DIRFILE= regular expression are readable. re: > The files are owned by a different user, but the files > all have 644 permission. I tested this by changing the permissions to 755, > and that didn't work either. Rerun the DSSERVE command and all should be well :-) Aside: If you are uncertain of what type of a file you are working with, you could use the utility 'od' to dump out some values. For instance: od -c OR_ABI-L1b-RadF-M3C14_G16_s20182230100463_e20182230111229_c20182230111294.nc | less Even better, if you suspect that the file is in netCDF format, use the netCDF utility 'ncdump': ncdump -h OR_ABI-L1b-RadF-M3C14_G16_s20182230100463_e20182230111229_c20182230111294.nc 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: PBN-748877 Department: Support McIDAS 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.