Jim - there is a github repository that attempts to keep up-to-date with
ICAO codes:
https://github.com/ip2location/ip2location-iata-icao
It is for the ip2location project, but I have found ICAO codes there
sometimes when I cannot find them on more official sources such as WMO or
NWS.
*Stonie Cooper, PhD*
Software Engineer III
NSF Unidata Program Center
University Corporation for Atmospheric Research
*I acknowledge that the land I live and work on is the traditional home of
The **Chahiksichahiks (**Pawnee), The **Umoⁿhoⁿ (**Omaha), and The **Jiwere
(**Otoe).*
On Tue, Oct 22, 2024 at 1:05 PM Weber, Jim via ldm-users <
ldm-users@xxxxxxxxxxxxxxxx> wrote:
> Just to double check…I believe this entry has everything covered. Would I
> be correct in that?
>
>
>
>
>
> WMO ^S[AP].... .... ([0-3][0-9])([0-2][0-9])
>
>
>
>
>
> Also, while we are on this topic, does anyone know where there might be a
> master list of METAR station identifiers to provide the station name, city,
> and hopefully a lat/lon?
>
>
>
>
>
>
>
> *Jim Weber*
>
> jim.weber@xxxxxxx <jim.weber@xxxxxxxxx>
>
> Certified Broadcast Meteorologist
>
> FOX 13 News
>
> WTVT - TV
>
> 3213 West Kennedy Blvd.
>
> Tampa, Florida 33609
>
> Phone 813-870-9657
>
>
>
> *From:* ldm-users <ldm-users-bounces@xxxxxxxxxxxxxxxx> *On Behalf Of *Gilbert
> Sebenste via ldm-users
> *Sent:* Monday, October 21, 2024 6:26 PM
> *To:* Mike Zuranski <zuranski.wx@xxxxxxxxx>
> *Cc:* LDM <ldm-users@xxxxxxxxxxxxxxxx>; NOAAPORT <
> noaaport@xxxxxxxxxxxxxxxx>
> *Subject:* Re: [ldm-users] Changes to METAR data over SBN
>
>
>
> This should also be the direct feed from the FAA, as that is what they use.
>
>
>
> Not only will this decrease METAR latency by several minutes for some
> domestic METARs, but this will also allow for new METARs that the FAA sends
> to be available immediately after activation.
>
>
>
> But note that this applies to KWBC METARS. Military observations on KAWN
> will still need to have to be accounted for. I would just grab anything SA*
> or SP* for WMO header capture, and then you likely don't have to worry
> about any changes in the future.
>
>
>
> Gilbert
>
>
>
> On Oct 21, 2024, at 1:39 PM, Mike Zuranski <zuranski.wx@xxxxxxxxx> wrote:
>
>
>
> Howdy all,
>
>
>
> I just saw this come across and given its significance I wanted to draw
> attention to it here. Seems that in December the process AND product
> headers for transmitting METAR and SPECIals will change. Depending on your
> REQUESTS and PQACTS this could be impactful.
>
>
>
> Subject: Addition of SAUS99 and SPUS99 Text Products to
> Satellite Broadcast Network (SBN) and Removal of the SAUS70, 80
>
> and 90 Counterparts on or about December 11, 2024
>
>
>
> The NWS National Centers for Environmental Prediction (NCEP)
> Central Operations (NCO) creates routine collectives of
> observational METAR data in SAUS70 KWBC, SAUS80 KWBC, SAUS90
> KWBC and their counterparts for Special observations SPUS70,
> SPUS80 and SPUS90. These collectives require manual
> intervention to add METAR stations to them. These are then
> distributed over the SBN. Another product, SAUS99 KWBC, and the
> Special observation counterpart SPUS99 KWBC contain any METAR
> observation received every minute. Delivering SAUS99 and SPUS99
> over the SBN rather than the aforementioned collectives will
> provide more observational data and more timely data to users of
> the SBN.
>
>
>
> The replacement with SAUS99 and SPUS99 is expected to occur on
> or about 1200 Coordinated Universal Time (UTC) December 11,
> 2024. If a Critical Weather Day has been issued, this change
> will be postponed until 1200 UTC on the next non-Critical
>
> Weather Day.
>
>
>
> Users that are receiving and utilizing SAUS70 KWBC, SPUS70 KWBC,
>
> SAUS80 KWBC, SPUS80 KWBC, SAUS90 KWBC or SPUS90 KWBC must ensure
>
> they can also receive SAUS99 KWBC and SPUS99 KWBC.
>
>
>
>
> https://www.weather.gov/media/notification/pdf_2023_24/scn24-99_add_saus99_to_sbn.pdf
> <https://urldefense.com/v3/__https:/www.weather.gov/media/notification/pdf_2023_24/scn24-99_add_saus99_to_sbn.pdf__;!!PxibshUo2Yr_Ta5B!zJrqu0Ootm-nbvY4YhVTLAymMbvzZNdPGDVp8oowROeF1Z413Gva3BncRgPfPTnaFvru14Hdpzd9hz7CggP88tUBNw$>
>
>
>
>
>
> Best,
>
> -Mike
>
>
>
> --
>
> - Mike Zuranski
>
> ----------------------------------
>
> Disclaimer: Thoughts, opinions and all general nonsenses are those of
> myself and in no way reflect the views or positions of any other person or
> entity.
>
> _______________________________________________
> 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:
> https://www.unidata.ucar.edu/mailing_lists/
> <https://urldefense.com/v3/__https:/www.unidata.ucar.edu/mailing_lists/__;!!PxibshUo2Yr_Ta5B!zJrqu0Ootm-nbvY4YhVTLAymMbvzZNdPGDVp8oowROeF1Z413Gva3BncRgPfPTnaFvru14Hdpzd9hz7CggO9npJ8kg$>
>
>
>
> This message and its attachments may contain legally privileged or
> confidential information. It is intended solely for the named addressee(s).
> If you are not an addressee indicated in this message (or responsible for
> delivery of the message to an addressee), you may not copy or deliver this
> message or its attachments to anyone. Rather, you should permanently delete
> this message and its attachments and kindly notify the sender by reply
> e-mail. Any content of this message and its attachments that does not
> relate to the official business of Fox Corporation, or its subsidiaries
> must be taken not to have been sent or endorsed by any of them. No
> representation is made that this email or its attachments are without
> defect.
> _______________________________________________
> 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:
> https://www.unidata.ucar.edu/mailing_lists/
>
