Just to be clear, Unidata has nothing to do with, and minimal if any input on
what goes over the NOAAPORT satellite. That's entirely NOAA/NCEP/NWS decided.
Through the Users committee, we do have some contacts, and they do ask our
input and we can make suggestions, but the final decision on what goes out over
NOAAPORT is theirs. I'll touch base with one of our contacts and ask if they
she knows of any plans to put anything other than the netcdf4 files on NOAAPORT.
Pete
<http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>--
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - poker@xxxxxxxxxxxx
________________________________
From: zuranski.wx@xxxxxxxxx <zuranski.wx@xxxxxxxxx> on behalf of Mike Zuranski
<zuranski@xxxxxxxxxxxxxxx>
Sent: Wednesday, December 13, 2017 11:56 AM
To: Pete Pokrandt
Cc: Arthur A Person; ldm-users@xxxxxxxxxxxxxxxx; support-idd@xxxxxxxxxxxxxxxx
Subject: Re: [ldm-users] GOES-16 to GOES East switchover
Hey Pete,
Thanks for the update.
re:
> Is anyone out there currently using the GINI imagery that comes in over
> NOAAPORT that could not use similar imagery if it came in in McIDAS AREA
> format instead?
We do use the GINI imagery, and would eventually need a replacement
for the GINICOMP imagery. I figured I'd have to mock something up
myself, but if AREA files came over NOAAPort we could use those. I'm
saying NOAAPort though because our internet bandwidth can get
congested at times, so if they come over internet only then I may
still end up making my own. My two cents anyways.
-Mike
======================
Mike Zuranski
Meteorology Support Analyst
College of DuPage - Nexlab
Weather.cod.edu
======================
On Wed, Dec 13, 2017 at 11:26 AM, Pete Pokrandt <poker@xxxxxxxxxxxx> wrote:
> Just a quick update on this. I checked in with Tom Yoksas at Unidata to make
> sure he had seen this. His response:
>
>
>
>> Is anything happening with AREA or GINI imagery for GOES16 after the
>> cutover?
>
> [Tom] Not yet. On my list of things to do is create some McIDAS scripts
> that will create sectors of the same coverages that are currently being sent
> as GINI images in NOAAPort. The format of the new sectors will not be GINI,
> however, but, rather AREA. Writing the same into the GINI format would
> entail creating a GINI output ADDE server or a converter from AREA to GINI.
> I am under the impression that the GREAT majority of Unidata sites that use
> the GINI imagery being distributed in NOAAPort could handle the same in
> AREA. Please let me know if you do not think that this is the case.
>
> > What idd data feed would you be making those available on?
>
> [Tom] I'm thinking the images would be put into NIMAGE or UNIWISC.
>
>
> So, the gist is that Unidata plans to make something available, probably
> some AREA files, but they probably won't be ready right at the cutover from
> GOES13 to GOES16.
>
> Is anyone out there currently using the GINI imagery that comes in over
> NOAAPORT that could not use similar imagery if it came in in McIDAS AREA
> format instead?
>
> Pete
>
>
>
> --
> Pete Pokrandt - Systems Programmer
> UW-Madison Dept of Atmospheric and Oceanic Sciences
> 608-262-3086 - poker@xxxxxxxxxxxx
>
>
>
> ________________________________
> From: ldm-users-bounces@xxxxxxxxxxxxxxxx
> <ldm-users-bounces@xxxxxxxxxxxxxxxx> on behalf of Arthur A Person
> <aap1@xxxxxxx>
> Sent: Tuesday, December 12, 2017 11:07 AM
> To: ldm-users@xxxxxxxxxxxxxxxx
> Subject: [ldm-users] GOES-16 to GOES East switchover
>
> Hi...
>
> With the imminent switchover from GOES-13 to GOES-16 as the GOES EAST
> operational satellite,
> does anyone know whether the Unidata McIDAS and GINI imagery will be
> affected at all, or will
> this changeover be transparent?
>
> Thanks... Art
>
> --
> Arthur A. Person
> Assistant Research Professor, System Administrator
> Penn State Department of Meteorology and Atmospheric Science
> email: aap1@xxxxxxx, phone: 814-863-1563
>
> _______________________________________________
> 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.
>
>
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/