Hi all,
It appears someone has figured out G16 and GEMPAK:
https://satelliteliaisonblog.com/tag/goes-16/
At any rate, I too, would like to see the NIMAGE feed EAST-CONUS with the
previous products offerred by G13. All of my GEMPAK satellite scripts are
currently broken.
vg
On Fri, Jan 12, 2018 at 3:07 PM, Tom Yoksas <yoksas@xxxxxxxx> wrote:
> Hi Phil, Rodrigo, and fellow gembudians,
>
> On 01/12/2018 07:38 AM, Phil Birnie wrote:
>
>> Thanks for all of the feedback, all. - same Tom, would be interested but
>> we understand that this is a big undertaking. Same as Rodrigo — for us,
>> just the ability to produce VIS, IR and WV imagery would be fine as we
>> disseminate a few products to the general public and for internal
>> instructional purposes.
>>
>
> This past Monday, January 8, I replaced the GOES-13 image content in
> Unidata-Wisconsin (IDD feed type UNIWISC aka MCIDAS) GOES-East sectors
> with similar bands from GOES-16. In order to provide an impact-free
> transition, I left the images labeling as being from GOES-13. Since the
> images are being created by McIDAS remapping (IMGREMP) of GOES-16 Full
> Disk imagery into existing GOES-13 sectors, the navigation for the
> images is still that for GVAR, not the Fixed Grid projection of GOES-16.
> GEMPAK, McIDAS, IDV, McIDAS-V and presumably AWIPS users should be able to
> use these images with no changes to their setup (i.e., no adjustments
> to GEMPAK tables, etc.).
>
> I view the remapping of GOES-16 imagery into GVAR sectors as being a
> stop gap measure designed to lessen the impact of GOES-13 being
> turned off. I want to open a full discussion with LDM/IDD
> consumers of satellite imagery for what the next steps should be:
> e.g., send out select bands from the GOES-16 SCMI imagery that
> is being distributed in NOAAPort; create image sectors that match
> the spatial extents for the GOES-13 imagery that was sent in NOAAPort
> in GINI format, etc.
>
> Some questions to be answered before we proceed with the creation of
> new image content using GOES-16 data are:
>
> - does GEMPAK support the Fixed Grid projection used in all GOES-16
> GRB images?
>
> I _think_ the answer to this is no, Fixed Grid is not supported in
> GEMPAK, but I am not sure. If it is not, new image sectors can
> be remapped into a projection that GEMPAK supports.
>
> - which bands would GEMPAK users like to see in the new content?
>
> Recall that GVAR GOES platforms have 5 imager channels (bands),
> while GOES-R has 16 ABI channels.
>
> - do GEMPAK users need to be able to extract valid calibrations
> from the imagery (e.g., TEMPerature for IR bands and Albedo/
> reflectance from VISible bands)?
>
> If yes, this may mean that non-GOES-16 calibration information
> will need to be added to the new image sectors.
>
> - what LDM/IDD datastream should these image sectors be sent in?
>
> Comment(s):
>
> - creation of image sectors that are usable by GEMPAK is not
> a daunting task ** as long as the output format for the
> new sectors is McIDAS AREA **
>
> Creation of new sectors in GINI format would require new program
> development while creation in AREA format simply requires the
> creation of scripts that run appropriate McIDAS commands.
>
> Your input is important. Please let us know what option would be
> best for your operations!
>
> Cheers,
>
> Tom
>
> From: Rodrigo Mathias <rodrigowind.meteoro@xxxxxxxxx> <mailto:
>> rodrigowind.meteoro@xxxxxxxxx>
>> Reply: Rodrigo Mathias <rodrigowind.meteoro@xxxxxxxxx> <mailto:
>> rodrigowind.meteoro@xxxxxxxxx>
>> Date: January 11, 2018 at 9:12:04 PM
>> To: gembud@xxxxxxxxxxxxxxxx <gembud@xxxxxxxxxxxxxxxx> <mailto:
>> gembud@xxxxxxxxxxxxxxxx>
>> Subject: [gembud] Fwd: 20180111: Displaying GOES-16 Data
>>
>> Hi Tom!
>>>
>>> We are very interested in GOES-16 on Gempak. We have been trying to
>>> migrate to AWIPS II, but it is not possible yet and we use GOES daily on
>>> Gempak for maritime forecasts in Brazil. We are worried about the coming
>>> end of GOES-13 imagery. It is not necessary all the products and channels,
>>> but the enough of basic IR, VIS and WV imagery.
>>>
>>> Regards,
>>> Rodrigo
>>>
>>> ---------- Mensagem encaminhada ----------
>>> De: "Tom Yoksas" <>
>>> Data: 11 de jan de 2018 6:50 PM
>>> Assunto: [gembud] 20180111: Displaying GOES-16 Data
>>> Para: "Mullenax, Robert R. (WFF-820.0)[ORBITAL SCIENCES CORPORATION]" <
>>> robert.r.mullenax@xxxxxxxx <mailto:robert.r.mullenax@xxxxxxxx>>, "Devin
>>> Eyre" <Devin.Eyre@xxxxxxxxxxxx <mailto:Devin.Eyre@xxxxxxxxxxxx>>, "Phil
>>> Birnie" <me@xxxxxxxxxxxxxx <mailto:me@xxxxxxxxxxxxxx>>, "
>>> gembud@xxxxxxxxxxxxxxxx <mailto:gembud@xxxxxxxxxxxxxxxx>" <
>>> gembud@xxxxxxxxxxxxxxxx <mailto:gembud@xxxxxxxxxxxxxxxx>>
>>> Cc:
>>>
>>> Hi Guys,
>>>
>>> On 01/11/2018 01:40 PM, Mullenax, Robert R. (WFF-820.0)[ORBITAL
>>> SCIENCES CORPORATION] wrote:
>>>
>>> I was going to try that when I return from the Ice, wasn't
>>> sure it would work.
>>>
>>>
>>> This brings up a good question in my mind: does GEMPAK support the
>>> Fixed
>>> Grid projection that is used for all products distributed in the GRB
>>> (GOES ReBroadcast)? If not, McIDAS can remap the images into
>>> projections supported by GEMPAK, but this would entail some loss of
>>> information.
>>>
>>> re:
>>>
>>> What is AWS?
>>>
>>>
>>> Amazon Web Services - Amazon's cloud. All GOES-16 data has been
>>> moved
>>> up to AWS since the satellite was turned on.
>>>
>>> If anyone is not on the ldm-users email list, please be aware that we
>>> are distributing ALL of the GOES-16 imagery and products we are
>>> receiving here in UCAR. The imagery and products are under the DIFAX
>>> feed type, but this will be renamed to SATELLITE in an upcoming
>>> LDM release (while keeping DIFAX as a secondary name, of course).
>>>
>>> A much bigger question for the community as a whole is if there is
>>> a desire for us (Unidata) to distribute GOES-16 imagery in a format
>>> that is readily usable by GEMPAK (e.g., AREA, NOT GINI!)? If the
>>> answer is yes, what sectors are of interest (NB: not all bands!!).
>>> We have been discussing using McIDAS to turn the NOAAPort-delivered
>>> SCMI netCDF4 images into McIDAS AREAs and providing them in a
>>> satellite image based feed type like UNIWISC, NIMAGE, or possibly
>>> SATELLITE.
>>>
>>> Cheers,
>>>
>>> Tom
>>>
>>> ------------------------------------------------------------
>>> ------------
>>> *From:* Devin Eyre [Devin.Eyre@xxxxxxxxxxxx
>>> <mailto:Devin.Eyre@xxxxxxxxxxxx>]
>>> *Sent:* Thursday, January 11, 2018 2:27 PM
>>> *To:* Mullenax, Robert R. (WFF-820.0)[ORBITAL SCIENCES
>>> CORPORATION]; Phil Birnie; gembud@xxxxxxxxxxxxxxxx
>>> <mailto:gembud@xxxxxxxxxxxxxxxx>
>>> *Subject:* Re: [gembud] Displaying GOES-16 Data
>>>
>>> Using mcidas, you can make area files using the GOES-16 netcdf
>>> files, if you use the data that's on AWS.
>>>
>>> ------------------------------------------------------------
>>> ------------
>>> *From:* gembud-bounces@xxxxxxxxxxxxxxxx
>>> <mailto:gembud-bounces@xxxxxxxxxxxxxxxx>
>>> <gembud-bounces@xxxxxxxxxxxxxxxx
>>> <mailto:gembud-bounces@xxxxxxxxxxxxxxxx>> on behalf of
>>> Mullenax, Robert R. (WFF-820.0)[ORBITAL SCIENCES CORPORATION]
>>> <robert.r.mullenax@xxxxxxxx <mailto:robert.r.mullenax@xxxxxxxx>>
>>> *Sent:* Thursday, January 11, 2018 2:22 PM
>>> *To:* Phil Birnie; gembud@xxxxxxxxxxxxxxxx
>>> <mailto:gembud@xxxxxxxxxxxxxxxx>
>>> *Subject:* Re: [gembud] Displaying GOES-16 Data
>>> Display of GOES-16 isn't supported in GEMPAK according to the
>>> link Unidata sent out the other day. Only McIDAS-X, McIDAS-V,
>>> IDV, and AWIPS2.
>>>
>>> It is something I will have to tackle here in a few weeks
>>> myself as we haven't moved to AWIPS2. I would assume that with
>>> GEMPAK not being developed anymore at NCEP (AFAIK) that it
>>> would be difficult for Unidata to tackle that likely big task,
>>> but maybe Michael can chime in on that.
>>>
>>>
>>> Regards,
>>> Robert Mullenax
>>>
>>>
>>>
>>> Please note new email address: robert.r.mullenax@xxxxxxxx
>>> <mailto:robert.r.mullenax@xxxxxxxx>
>>> Robert Mullenax
>>> Senior Principal Meteorologist, Orbital ATK/CSBF
>>> 1510 E. FM 3224
>>> Palestine, Texas 75802
>>> 903-723-8037 <tel:903-723-8037>
>>> robert.r.mullenax@xxxxxxxx <mailto:robert.r.mullenax@xxxxxxxx>
>>> ------------------------------------------------------------
>>> ------------
>>> *From:* gembud-bounces@xxxxxxxxxxxxxxxx
>>> <mailto:gembud-bounces@xxxxxxxxxxxxxxxx>
>>> [gembud-bounces@xxxxxxxxxxxxxxxx
>>> <mailto:gembud-bounces@xxxxxxxxxxxxxxxx>] on behalf of Phil
>>> Birnie [me@xxxxxxxxxxxxxx <mailto:me@xxxxxxxxxxxxxx>]
>>> *Sent:* Thursday, January 11, 2018 12:13 PM
>>> *To:* gembud@xxxxxxxxxxxxxxxx <mailto:gembud@xxxxxxxxxxxxxxxx>
>>> *Subject:* [gembud] Displaying GOES-16 Data
>>>
>>> Hi Gembuds,
>>>
>>> I am successfully ingesting the GOES-16 data but am having
>>> difficulty displaying it. I’m assuming I probably have to run
>>> it through (or perhaps create) some kind of decoder. Has
>>> anyone had success that might be able to provide a few pointers?
>>>
>>> Thanks!
>>>
>>> - Phil Birnie
>>> Ohio State University, Dept of Geography Volunteer
>>>
>>>
>>> _______________________________________________
>>> NOTE: All exchanges posted to Unidata maintained email lists are
>>> recorded in the Unidata inquiry tracking system and made publicly
>>> available through the web. Users who post to any of the lists we
>>> maintain are reminded to remove any personal information that
>>> they
>>> do not want to be made public.
>>>
>>>
>>> gembud mailing list
>>> gembud@xxxxxxxxxxxxxxxx <mailto:gembud@xxxxxxxxxxxxxxxx>
>>> For list information or to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/mailing_lists/
>>> <http://www.unidata.ucar.edu/mailing_lists/>
>>>
>>>
>>> --
>>> +-----------------------------------------------------------
>>> -----------+
>>> * Tom Yoksas UCAR Unidata Program *
>>> * (303) 497-8642 <tel:%28303%29%20497-8642> (last resort) P.O.
>>> Box 3000 *
>>> * yoksas@xxxxxxxx <mailto:yoksas@xxxxxxxx> Boulder, CO
>>> 80307 *
>>> * Unidata WWW Service http://www.unidata.ucar.edu/ *
>>> +-----------------------------------------------------------
>>> -----------+
>>>
>>> _______________________________________________
>>> NOTE: All exchanges posted to Unidata maintained email lists are
>>> recorded in the Unidata inquiry tracking system and made publicly
>>> available through the web. Users who post to any of the lists we
>>> maintain are reminded to remove any personal information that they
>>> do not want to be made public.
>>>
>>>
>>> gembud mailing list
>>> gembud@xxxxxxxxxxxxxxxx <mailto:gembud@xxxxxxxxxxxxxxxx>
>>> For list information or to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/mailing_lists/
>>> <http://www.unidata.ucar.edu/mailing_lists/>
>>>
>>>
>>> _______________________________________________
>>> NOTE: All exchanges posted to Unidata maintained email lists are
>>> recorded in the Unidata inquiry tracking system and made publicly
>>> available through the web. Users who post to any of the lists we
>>> maintain are reminded to remove any personal information that they
>>> do not want to be made public.
>>>
>>>
>>> gembud mailing list
>>> gembud@xxxxxxxxxxxxxxxx
>>> For list information or to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/mailing_lists/
>>>
>>
>>
>> _______________________________________________
>> NOTE: All exchanges posted to Unidata maintained email lists are
>> recorded in the Unidata inquiry tracking system and made publicly
>> available through the web. Users who post to any of the lists we
>> maintain are reminded to remove any personal information that they
>> do not want to be made public.
>>
>>
>> gembud mailing list
>> gembud@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> http://www.unidata.ucar.edu/mailing_lists/
>>
>>
> --
> +----------------------------------------------------------------------+
> * Tom Yoksas UCAR Unidata Program *
> * (303) 497-8642 (last resort) P.O. Box 3000 *
> * yoksas@xxxxxxxx Boulder, CO 80307 *
> * Unidata WWW Service http://www.unidata.ucar.edu/ *
> +----------------------------------------------------------------------+
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> gembud mailing list
> gembud@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
--
Vittorio (Victor) A. Gensini
Assistant Professor
Davis Hall Room 118
Department of Geographic and Atmospheric Sciences
Northern Illinois University
DeKalb, IL 60115
vgensini@xxxxxxx
