Re: [Flightgear-devel] --metar and --enable-real-weather-fetch

2009-12-20 Thread Stuart Buchanan
John Denker wrote: On 05/24/2009 02:58 AM, Torsten Dreyer wrote in part: Step #2 Add an option --metar= - this implies --disable-real-weather-fetch and set scenario to METAR - make the metar string editable in the weather_scenario dialog This option needs some changes in the logic of

Re: [Flightgear-devel] --metar and --enable-real-weather-fetch

2009-12-20 Thread John Denker
On 12/20/2009 12:54 PM, Stuart Buchanan wrote: I believe --metar= 012345Z 0KT 99SM CLR 59/M01 A2992 is a correct and useful example ... but somebody should double check. Thanks for the example - I'll include it in the docs. My only comment is that I thought the temperature was

Re: [Flightgear-devel] --metar and --enable-real-weather-fetch

2009-12-20 Thread Peter Brown
As a separate issue: With rare exceptions, the largest visibility you will see reported in a metar is 10SM (in the US) or (meters, elsewhere). This is a problem for real-weather fetch, because the _reported_ visibility can be significantly less than the _real_ visibility. I have tried to

Re: [Flightgear-devel] --metar and --enable-real-weather-fetch

2009-12-20 Thread Melchior FRANZ
* Peter Brown -- Sunday 20 December 2009: IMHO there is no choice other than the bold solution- anything reported as 10SM = unlimited, and 9.99 and less is actual. And so guaranteeing the lowest possible frame rate? Sounds like a truly bad idea. The whole thing has been discussed before.

Re: [Flightgear-devel] --metar and --enable-real-weather-fetch

2009-12-20 Thread Peter Brown
its a way to weed out the gamer... Just thoughts I'm sure were considered before. Peter Brown --Original Message-- From: Melchior FRANZ To: flightgear-devel@lists.sourceforge.net ReplyTo: FlightGear developers discussions Subject: Re: [Flightgear-devel] --metar and --enable-real-weather

Re: [Flightgear-devel] --metar and --enable-real-weather-fetch

2009-12-20 Thread Melchior FRANZ
I had looked at some research papers at that time, which were about estimating visibility from other, measurable factors. I stopped when Thomas announced his solution. My original idea was a simple formula, based on the idea that: - visibility is derived from humidity (high humidity - low

Re: [Flightgear-devel] --metar and --enable-real-weather-fetch

2009-12-20 Thread Peter Brown
: Melchior FRANZ To: flightgear-devel@lists.sourceforge.net ReplyTo: FlightGear developers discussions Subject: Re: [Flightgear-devel] --metar and --enable-real-weather-fetch Sent: Dec 20, 2009 5:18 PM I had looked at some research papers at that time, which were about estimating visibility from

Re: [Flightgear-devel] --metar and --enable-real-weather-fetch

2009-12-19 Thread John Denker
On 05/24/2009 02:58 AM, Torsten Dreyer wrote in part: Step #2 Add an option --metar=arbitrary handcoded METAR - this implies --disable-real-weather-fetch and set scenario to METAR - make the metar string editable in the weather_scenario dialog This option needs some changes in the logic of