> 2010/11/12 16:00 LFST 121600Z 19009KT 170V230 9999 BKN030 13/09 Q1004 > NOSIG > > So I ran the metar command from the CLI to see what it told. That gives > the same result for this particular airport. I was using git revision > 0917a5e0. Upgrading to the current git revision 5bb247d4 also shows the > same result. I haven't found another airport for which the METAR > information is wrong/outdated (LFPO, KSFO, KJFK, EHAM showed correct > METAR and date). This METAR is to old to be used as a weather source. Some airfield don't update their METAR regularly and some abandoned airfields don't update their METAR at all any more, but the last issued report persists in NOAA's database.
To avoid rapid weather changes when hitting these airports enroute, theses reports are discarded. So, this is a feature - not a bug. Torsten BTW: you can set the maximum allowed age of METAR reports by setting /environment/params/metar-max-age-min to you prefered maximum age in minutes. ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
