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

[IDD #YBK-937568]: GOES-16 L2 products

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: [IDD #YBK-937568]: GOES-16 L2 products
  • Date: Tue, 27 Apr 2021 16:40:37 -0600
Hi Rick,

re:
> I have not worked on updating the script, but have another question.

OK.

re:
> William Stratka has requested a netcdf file prior to the restitch.  Is
> this possible? We are not using restitch.

Yes.

To be clear:

- the restitching process is _only_ for the SCMI imagery as
  the SCMI products are the only imagery that are distributed in
  NOAAPort as tiles

  One needs to stitch together the tiles to create a full scene,
  and that is what our restitching process does after the NOAAPort
  broadcast headers and footers are stripped off to leave the
  "bare" netcdf4 file.

- the other Level 2 imagery (I say other since the SCMI images
  are also Level 2 products) in NOAAPort are sent in individual files
  but a broadcast header and footer are glued onto the netCDF4
  product

  The only thing that the processing that I shared with you
  does for the non-SCMI Lever2 imagery is strip off the NOAAPort
  broadcast (binary) header and (binary) footer.  The result
  of the stripping is a "bare" netcdf4 file that can be used
  directly by any netCDF4-enabled application

- if one wants to work directly with the Level 2 products that are
  sent in NOAAPort, they are still available in the NOTHER feed

  A site can setup FILEing of these products directly to disk,
  and then the end-user will need to strip off the NOAAPort
  broadcast header and footers in order to use the underlying
  netCDF4 file.

I hope that this helps!

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: YBK-937568
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.