NOAA NCEI is migrating away from the remote WAF harvesting workflow in FY2027. This means that, once finished, they will no longer harvest metadata from the centralized WAF we maintain at https://data.ioos.us/waf/.
To publish our metadata to NOAA OneStop and Data.gov, will will need to migrate to the CoMET API instead.
Info, timeline, and links below on the CoMET API from NCEI:
Our timeline as of now is Q4 of FY27 to be fully operational in NCCF with CoMET and stand down RWAF.
Which would mean having the publish workflow setup by Q3 FY27 would be ideal.
You can start using CoMET APIs anytime, we are currently migrating NCEI operational CoMET to the cloud as well but we have a DEV and TEST tier if you wanted to start working on the publish workflow.
We have lots of examples of Python scripts that use the CoMET APIs.
Some of them are in the documentation and we have another Git repo which has more.
NOAA NCEI is migrating away from the remote WAF harvesting workflow in FY2027. This means that, once finished, they will no longer harvest metadata from the centralized WAF we maintain at https://data.ioos.us/waf/.
To publish our metadata to NOAA OneStop and Data.gov, will will need to migrate to the CoMET API instead.
Info, timeline, and links below on the CoMET API from NCEI: