Bad news: CSV TAF (what AvareX was using) no longer supported from NOAA/NWS as reported on
https://aviationweather.gov/data/api/#changes (/api/data/dataserver) and confirmed below:
From: Jason Rush - NOAA Affiliate
Date: Fri, Sep 19, 2025 at 9:37 AM
Subject: Re: AviationWeather.gov - Bug [B73Dcu]
Unfortunately, the CSV format for TAF data could not be carried over to the new DataServer API endpoint and that was the same code used to generate the cache files. As best as I can recall, part of the problem with attempting to encode TAFs to CSV was the variable number of forecasts that could be included per TAF. That issue does not apply to METARs. We are sorry for the inconvenience this has caused but have had to streamline parts of the service provided in order to keep a maintainable system available.
Name: Bradley
Category: Bug
Subject: TAF CSV cache missing?
/data/cache/tafs.cache.csv.gz is missing?
METARs have both XML and CSV. Thanks!
One of the trade-offs of AvareX pushing Internet-data fetching to client is that FAA/provider changes require code changes and updates to every client install. The legacy Avare used a server-based approach where any FAA/provider changes could be made there and the client interface remains stable. Of course that means more server activity and storage, etc. Trade-offs.
Let me know if I can help further.