> So the question is: How can I easily calculate the distance and how many > nautical miles are "out of reach" (thinking of e.g. radar systems) ?
It could be that VFR-equipped planes (esp. those w/o radar) only need things within the visibility range. I don't know about airborne radars, never flew with one, either :) http://www.faa.gov/ATpubs/AIM/Chap4/aim0405.html gives a pretty good coverage of the existing ATC radars in the US and their capabilities. The question is whetheer you have the capability to map all the enroute (ARTCC) radar installations and other range-extending radar installations around busier airports, i.e., not on the field itself. Also, you have to take terrain in consideration when talking about the radar reach. > 3) artificial life at airports > The server gives a lot of opportunities. One of the first things which came > to my mind was artificial traffic at airports. It should be fairly easy to > write clients in any (network capable) language which do simulate a client. > This can be simply a helicopter standing near a hangar or even a plane flying > around an airport. This would disburden fgfs itself (since it does not need > to create AI traffic itself) and allow an arbitrary number of artificial > clients, each serving it's "own" airport (or whatever area), bringing life to > many areas of the world without manipulating fgfs itself. Great idea. It's probably a good thing to coordinate this with the server, otherwise there will be a lot of artificial life burdening the server at the fields noone actually is flying at! _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
