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

[GEMPAK #KDY-987248]: GOES16 netcdf files

Hi Laura,

re:
> we succesfully displayed the data with the source you provided.

Very good.

re:
> Answering
> what you asked, we are getting the data from two sources. The L1b is from
> the GRB station, and the L2-CMIP is from Amazon.

OK, thanks.  We know that the ABI GRB imagery does not work in either
GEMPAK or AWIPS.  I was not aware that there was CMIP imagery being
uploaded to AWS, but I caught a hint of its existence via a comment
made by another user.

re:
> One idea we came up to (but certainly we have to dig a little more into it)
> is how to convert the L1b from GRB into files so that GEMPAK can read them.
> Is it possible?

Well, it is only software after all, so anything is possible :-)
In all seriousness, someone is converting GRB L1b imagery to the Sectorized
CMI format being sent in NOAAPort, so someone somewhere knows now to
do the conversion.  I don't know where that conversion is being done,
but my guess is that it is someone at Harris or Raytheon.

re:
> The second and more important for us is that the only projection that
> GEMPAK allows with this TDS files is the geostationary one. We use GEMPAK
> in different ways and we need to reproject the satellite images. We can do
> this with other datasets such as model data but that option is gray and not
> available when we load GOES data. Even further, if we load the model and
> the satellite data in the same display, it reprojects the model to the
> geostationary projection. Is it possible to display the satellite data in
> other projections?

I'm not aware that GEMPAK has the capability of reprojecting any image
imagery.  It can, as you note, overlay other types of data like model
output on top of the satellite image projections that it supports.

I know that McIDAS-X, McIDAS-V and the IDV can do this kind of
re-projection and MetPy should be able to do it also (via CartoPy).

re:
> It seems that we would have to save the ABI data in the
> projection we want it to be displayed but that is tightly related to the
> first question, how do we convert the files we have to a format that GEMPAK
> can read.

If you have McIDAS-X, you could setup conversions of the ABI imagery
you want to use into one of its supported projections and save the
imagery in an AREA file.  If GEMPAK has support for imagery in the
projection you want (I am not an expert in this, sorry), then it
should work.

You may want to subscribe to the address@hidden email
list that we maintain and post your question there:

https://www.unidata.ucar.edu/support/index.html#mailinglists

re:
> And also, is it possible to reproject the TDS CMIP data to other
> projection and then load it?

Packages like McIDAS-X have the built in capability to re-project satellite
imagery into a number of other projections.  The VisAD library that is a
cornerstone of the software used in the IDV and McIDAS-V can also do this
kind of reprojection.  I believe that MetPy can also be used to re-project
satellite imagery (via the CartoPy package (spelling?)), but this is
very slow as I understand it.  Whether or not any of these projections
is supported by GEMPAK for imagery is dependent on the projection that
you want to use.

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: KDY-987248
Department: Support GEMPAK
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.