On Mon, 2011-12-12 at 00:35 +0100, HB-GRAL wrote:
I guess we will run into some problems finally with keeping closed
airports for historical reason, i.e. when codes move to another
facility. And maybe also some frequencies can change to another facility
in range to the closed one ? Maybe
Hi Gene,
Gene Buckle wrote:
One thing you guys are forgetting is that both apt.dat and nav.dat are
updated regularly by Robin Peel, the keeper of those two files. I think
changing them would probably bite you after a while.
Robin's v8.10 files are unmaintained since August 2008, v8.50
Am 11.12.11 23:13, schrieb HB-GRAL:
Am 11.12.11 13:31, schrieb HB-GRAL:
Ok, its me again with this apt.dat changes. Now it is more cleaned at
all and instead of the script log you can see the diff here:
http://download.fgx.ch/data-update/diff-20111212.txt
Thanks for checking ;-)
Yves
The
Am 08.12.11 13:36, schrieb HB-GRAL:
Hi all
I am recently trying to update apt.dat airport names (in all flightgear
relevant data versions, means original xplane 8.10/8.50 and flightgear
apt.dat). I noticed caps in names, i.e. I am changing this names to
It is not in specs of xplane 8.50
Sure, but it was his former homebase which he remembered by heart. I am not
saying they are not useful in an emergency, but as they are not official
airports, there is no guarantee the runway is even suitable for landing or
takeoff. Hence the question whether they should be part of the airport
On Sun, 11 Dec 2011 16:38:26 +0200, Tuomas wrote in message
-1192042695539871148@unknownmsgid:
Sure, but it was his former homebase which he remembered by heart. I
am not saying they are not useful in an emergency, but as they are
not official airports, there is no guarantee the runway is
Since FG is a simulator, some folks like to go back in time and use
closed airports as if they are open. So don't always assume time can
only go forward in a simulator.
Therefore it is important that well known closed airports are still in
the apt.dat file.
S.
On Sun, 2011-12-11 at
One thing you guys are forgetting is that both apt.dat and nav.dat are
updated regularly by Robin Peel, the keeper of those two files. I think
changing them would probably bite you after a while.
g.
--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
Am 11.12.11 13:31, schrieb HB-GRAL:
The result of current processed apt.dat is:
- Cleaned 62 airport lines with wrong count of chars in elevation row
(minor cleaning)
- marked ~100 airports as closed with [X] at beginning of airport name,
changed name to upper/lower when needed, state based
Am 11.12.11 22:43, schrieb Scott:
Since FG is a simulator, some folks like to go back in time and use
closed airports as if they are open. So don't always assume time can
only go forward in a simulator.
Therefore it is important that well known closed airports are still in
the apt.dat
On Sat, 2011-12-10 at 00:49 +0100, HB-GRAL wrote:
Am 08.12.11 13:36, schrieb HB-GRAL:
Hi all
Hi again
About marking closed airports in apt.dat:
- marking the name with [X] might be closer to charts I guess and
most airports marked as closed in apt.dat comes with the x
- removing x
Am 10.12.11 10:29, schrieb Erik Hofman:
On Sat, 2011-12-10 at 00:49 +0100, HB-GRAL wrote:
Am 08.12.11 13:36, schrieb HB-GRAL:
Hi all
Hi again
About marking closed airports in apt.dat:
- marking the name with [X] might be closer to charts I guess and
most airports marked as closed in
On Sat, 2011-12-10 at 11:14 +0100, HB-GRAL wrote:
The airports marked as closed are closed at all, no service. And for
temporary closed runways you will need NOTAM I think, or not?
I don't think NOTAMS are good enough for permanently closed runways.
Erik
Am 10.12.11 07:52, schrieb Tuomas Kuosmanen:
Wouldn't it be useful to somehow flag the airport as
closed/restricted/whatever in the data, so that nav displays and gps/fms
units could show a different airfield symbol if desired for closed
airports? Does the data format support this?
There is
NOTAM has usually a time of validity, so permanent/long term changes
usually end up as an AIP supplement which have a longer lifespan.
Closed runways have a big white X on both ends of the runway (I guess if it
is closed both ways? ;))
One more thought: Should completely closed airports be
Yves
-Original Message-
From: HB-GRAL [mailto:flightg...@sablonier.ch]
Sent: 10 December 2011 10:25
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] apt.dat update (lowercase names etc.)
Am 10.12.11 07:52, schrieb Tuomas Kuosmanen:
Wouldn't it be useful
Sure they are marked in some charts as they might be useful in an
emergency, but essentially they are not much different from a large
parking lot or a wide road.
One came in pretty handy a few years ago when a guy ran out of gas.
Something about the glimly glider (sp?)
jj
Am 11.12.11 01:10, schrieb James J. Brennan:
Sure they are marked in some charts as they might be useful in an
emergency, but essentially they are not much different from a large
parking lot or a wide road.
One came in pretty handy a few years ago when a guy ran out of gas.
Something
Am 08.12.11 13:36, schrieb HB-GRAL:
Hi all
Hi again
About marking closed airports in apt.dat:
- marking the name with [X] might be closer to charts I guess and
most airports marked as closed in apt.dat comes with the x
- removing x and marking with (closed) at end of name is possible in
On Friday 09 December 2011 16:49:14 HB-GRAL wrote:
Am 08.12.11 13:36, schrieb HB-GRAL:
Hi all
Hi again
About marking closed airports in apt.dat:
- marking the name with [X] might be closer to charts I guess and
most airports marked as closed in apt.dat comes with the x
- removing x and
Wouldn't it be useful to somehow flag the airport as
closed/restricted/whatever in the data, so that nav displays and gps/fms
units could show a different airfield symbol if desired for closed
airports? Does the data format support this?
FG could say (closed) in the end also based on the flag,
On Thu, 2011-12-08 at 13:36 +0100, HB-GRAL wrote:
I wish to submit this changes and updates. But I am asking you to review
the different changes/possibilities of the script in a code 1 line of
apt.dat :
a) Same name, but to lower:
Old line: '13141 0 1 01MT CRYSTAL LAKES RESORT'
New
On Thu, 2011-12-08 at 14:02 +0100, Roland Häder wrote:
On Thu, 2011-12-08 at 13:36 +0100, HB-GRAL wrote:
I wish to submit this changes and updates. But I am asking you to review
the different changes/possibilities of the script in a code 1 line of
apt.dat :
a) Same name, but to
Another small question might be for ourairports names like this one:
Mario's Flying Pizza Airport (sic!)
should this become ...
a) Marios Flying Pizza Airport
b) Mario s Flying Pizza Airport
c) Mario Flying Pizza Airport
(This is serious, this is 2TA4 and it is in FlightGears apt.dat.)
HB-GRAL wrote
-Original Message-
From: HB-GRAL [mailto:flightg...@sablonier.ch]
Sent: 08 December 2011 17:44
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] apt.dat update (lowercase names etc.)
Another small question might be for ourairports names like
On Thursday 08 December 2011 07:07:58 Geoff McLane wrote:
I guess the only thing is concerning 'closed'
airports. Should they be in apt.dat at all?
But if they are retained for 'historic', or
other purposes, it would be good if they were
all consistent...
Just because an airport is 'closed'
Subject: Re: [Flightgear-devel] apt.dat update (lowercase names etc.)
On Thursday 08 December 2011 07:07:58 Geoff McLane wrote:
I guess the only thing is concerning 'closed'
airports. Should they be in apt.dat at all?
But if they are retained for 'historic', or
other purposes, it would
27 matches
Mail list logo
