Re: Weather Architecture

Don't we want to keep some version of METAR report if for no other 
reason but because pilots are used to looking at METAR reports for 
configuring flights in general? Not necessarily tied to weather 
simulating, but to pilot data and expectations at the destination and track.

Wayne

On 4/14/2026 4:15 PM, Israel Emmanuel wrote:
> Well, hopefully it will be better than the old one. My idea was to 
> have METAR and OpenMeteo do separate things, more or less, but still 
> tie into the same endpoints, with more endpoints being created for 
> OpenMeteo to tie into in all its glory. Eventually, if it becomes 
> evident that OpenMeteo is consistent and reliable, we can cut out the 
> METAR altogether. Or, perhaps, we could keep it for those who prefer 
> that information to OpenMeteo. Either way, my plan was not to replace 
> METAR straight out of the gate.
> ------------------------------------------------------------------------
> *From:* [email protected] <[email protected]>
> *Sent:* Tuesday, April 14, 2026 2:10 PM
> *To:* [email protected] 
> <[email protected]>
> *Subject:* Re: [Flightgear-devel] Weather Architecture
> On 4/14/26 4:55 PM, Israel Emmanuel wrote:
> > Are you saying I should combine sources from both METAR and 
> OpenMeteo? I forsee
> > that getting a bit hairy, and we can get all METAR info from 
> OpenMeteo, but I
> > can try that out if it's a better idea overall.
>
> i would expect the new stuff to reside in its own source file that 
> would be
> included... then the code would, when it runs its loops, pull data 
> from the
> existing METAR, pull data from the newly included OpenMeteo you are 
> working on,
> and whatever else it does in the loop...
>
> both weather fetchers would/should be feeding their data into some 
> central
> weather cache that all other weather-needing code would query... then 
> when we're
> (TINW) satisfied the old code can be cut loose, then it can be 
> un-included and
> the call removed from the loop...
>
> others may have different ideas... i kind of see it like switching 
> accounting
> packages... use both, old and new, in parallel for several months to 
> make sure
> everything is running as desired and the final results are the same or 
> better...
> then cut the old stuff loose from live use but keep it around for 
> possible
> fallback... it can be fully removed later during maintenance...
>
>
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel