Re: [ldm-users] GOES-16 to GOES East switchover

Thanks Kevin for the info.

I tested the ADDE server and unfortunately G-16 data does not have
navigation frame... :
MAP: NO IMAGE OR NO NAVIGATION FOR FRAME

Christian

On Thu, Dec 14, 2017 at 9:36 PM, Kevin Baggett <kevinb@xxxxxxxxxxxxx> wrote:

> If you're using ADDE, Unidata has a server already set up for GOES-16 data
> access.  It's RTGOESR on lead.unidata.ucar.edu.
>
> Kevin
>
>
> On Wed, Dec 13, 2017 at 1:39 PM, Wojtowicz, David P Jr <
> davidw@xxxxxxxxxxxx> wrote:
>
>> I second the interest in a test dataset of the NetCDF format files.
>>  Probably already around somewhere, I haven’t had the time to hunt for it.
>>   So any pointers would also be appreciated.
>>
>>
>>
>> --david
>>
>>
>>
>> *From:* ldm-users-bounces@xxxxxxxxxxxxxxxx [mailto:ldm-users-bounces@unid
>> ata.ucar.edu] *On Behalf Of *Christian Pagé
>> *Sent:* Wednesday, December 13, 2017 2:32 PM
>> *To:* Pete Pokrandt <poker@xxxxxxxxxxxx>
>> *Cc:* support-idd@xxxxxxxxxxxxxxxx; Mike Zuranski <
>> zuranski@xxxxxxxxxxxxxxx>; ldm-users@xxxxxxxxxxxxxxxx
>>
>> *Subject:* Re: [ldm-users] GOES-16 to GOES East switchover
>>
>>
>>
>> Thanks very much Pete.
>>
>>
>>
>> Is there a test dataset (e.g. one day of data for example) we can use to
>> prepare the migration of our data processing?
>>
>>
>>
>> Christian
>>
>>
>>
>> On Wed, Dec 13, 2017 at 9:16 PM, Pete Pokrandt <poker@xxxxxxxxxxxx>
>> wrote:
>>
>> Ok, so the question that I posed to the NOAA contacts was:
>>
>>
>>
>> [pete]
>>
>> The question has come up on the Unidata LDM-Users mailing list as to
>> whether there are any plans to replace the GINI imagery that we currently
>> get for GOES-East over NOAAPORT with a similar product.
>>
>>
>>
>> Unidata is planning to make something available, but that will be via the
>> IDD on the internet, not NOAAPORT the satellite feed. IDD sites with slower
>> internet connections may not be able to keep up with these, but those with
>> a NOAAPORT dish, would be able to grab whatever comes in from that w/o
>> bandwidth restrictions.
>>
>>
>>
>> I am aware of the sectorized netcdf4 GOES16 products that will be coming
>> over NOAAPORT - as far as you know, are there any plans to also send out
>> GINI or AREA files? I doubt it, but just figured I'd check.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> The response, as I figured is that no, there will be no GINI or AREA
>> files coming over NOAAPORT for GOES 16 or any of the later GOES products,
>> only ever netcdf4. Specifically:
>>
>> [noaa]
>>
>> --------
>>
>> I am not sure what you mean by "replace". We do not have plans to
>> distribute GINI images for GOES16. The GINI format will not be used for the
>> new satellites. NESDIS has transitioned to netcdf4 for the GOES-R class of
>> satellites.
>>
>>
>>
>> On NOAAPORT, there are multiple channels. The current GINI images are on
>> the GOES channel (pid 102). This includes data for both GOES13 and GOES15.
>> We have been evaluating GOES16 data for the last few months on the new GRE
>> channel (pid 108). This data has been available for everyone to evaluate
>> and test with local software. Due to the increased data volume for the new
>> satellites, the East and West data will be separated. Once GOES-S/17 is
>> active, that data will be on the GRW channel (pid 107).
>>
>>
>>
>> So, after January 2, GOES-East data will only be available from GOES16 on
>> the GRE channel in netcdf4. Later in 2018, when GOES17 is operational, a
>> similar transition will take place for GOES-West. At that point, the GINI
>> format will no longer be used, after GOES15 is retired.
>>
>>
>>
>>
>>
>>
>>
>> So, if you are on a slow network connection and depend on NOAAPORT,
>> you'll need to adapt and use the netcdf4 data. There will be some probably
>> AREA format files sent out over the IDD by Unidata, but if that's more
>> bandwidth than you have, you'll need to be seective on what you request, or
>> work with the netcdf4 files.
>>
>>
>>
>>
>>
>> Pete
>>
>>
>>
>>
>>
>>
>>
>> --
>> 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 12:35 PM
>>
>>
>> *To:* Pete Pokrandt
>> *Cc:* Arthur A Person; ldm-users@xxxxxxxxxxxxxxxx;
>> support-idd@xxxxxxxxxxxxxxxx
>> *Subject:* Re: [ldm-users] GOES-16 to GOES East switchover
>>
>>
>>
>> On Wed, Dec 13, 2017 at 12:01 PM, Pete Pokrandt <poker@xxxxxxxxxxxx>
>> wrote:
>> > 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.
>>
>> That was my understanding, just figured it wouldn't hurt to make that
>> statement out loud.  We rely on NOAAPORT pretty heavily here.
>>
>>
>> > 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.
>>
>> Great, thank you very much.
>>
>> -Mike
>>
>>
>> ======================
>> Mike Zuranski
>> Meteorology Support Analyst
>> College of DuPage - Nexlab
>> Weather.cod.edu
>> ======================
>>
>>
>> >
>> >
>> > Pete
>> >
>> >
>> >
>> >
>> > --
>> > 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/
>>
>>
>> _______________________________________________
>> 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/
>>
>>
>>
>> _______________________________________________
>> 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/
>>
>
>
>
> _______________________________________________
> 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 listldm-users@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.
>
>
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
  • 2017 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: