Request to add ATZ to OpenAir format

[René]

In the Netherlands we have special areas around aerodromes called ATZ
Aerodrome Traffic Zone. 5 civil one's and 9 military ATZ's.
These areas have special shapes ( military ones are 1500 ft AAL and
are circles of 2 NM around the aerodrome) The civil ATZ have different
shapes and heights.
Since these areas are most of the time prohibited for vfr flights it
is imported to "see" them. They are all on the official ICAO map and
are published in the Dutch AIP as well.
I know they have ATZ's and MATZ's in the UK as well. For other
countries I don't know.
I will suggest to ad ATZ as airspace type to the OpenAir definition
like CTR is too.
ATZ should get a separate "color type" in shape files too.

Regards
René

[Bart Vandewoestyne]

On 05/07/2012 09:45 PM, Ren� wrote:
> In the Netherlands we have special areas around aerodromes called ATZ
> Aerodrome Traffic Zone. 5 civil one's and 9 military ATZ's.
> These areas have special shapes ( military ones are 1500 ft AAL and
> are circles of 2 NM around the aerodrome) The civil ATZ have different
> shapes and heights.
> Since these areas are most of the time prohibited for vfr flights it
> is imported to "see" them. They are all on the official ICAO map and
> are published in the Dutch AIP as well.

Hello Ren�,

Can you give an example of such an Aerodrome Traffic Zone? Can you
point me to a specific section in the Dutch AIP
(http://www.ais-netherlands.nl) where such a zone is mentioned so that I
can take a look at it?

Regards,
Bart

[René]

See Dutch AIP section "-ENR 5 NAVIGATION WARNINGS" at the end.
Examples are:

Military ATZ
Volkel Circle, radius 2 NM, centre 51°39'25.95"N 005°42'28.17"E. 1500
ft AAL Outside AD OPR HR (see ENR 2.1).

Civil ATZ
Schinveld 50°58'33.93"N 005°58'18.01"E;
50°58'48.48"N 005°58'18.84"E;
along Dutch-German border to
50°58'59.57"N 006°01'35.71"E;
along Dutch-German border to
50°58'54.15"N 006°01'36.92"E;
50°58'55.93"N 006°01'17.09"E;
50°58'49.93"N 006°00'58.09"E;
50°58'32.94"N 006°00'20.10"E;
to point of origin. up to 3000 ft AMSL OPR HR EHBK during UDP (see
EHBK AD 2.3) ATZ Schinveld is situated within Maastricht CTR. All
aircraft not participating in the glider activities at or near
Schinveld glider site shall avoid the ATZ, unless an ATC clearance to
cross has been obtained from Beek Tower. This clearance will only be
issued when there are no glider activities at Schinveld glider
site.ATZ Schinveld is during set time periods subject to local
agreement for use by local participants only.

Best regards
René


On May 7, 11:02 pm, Bart Vandewoestyne <Bart.Vandewoest...@telenet.be>
wrote:

[Bart Vandewoestyne]

> Ren�

OK. So it seems like for the Civil ATZ's the recommendation is to
'avoid' them. For the Military ATZ's, it seems like they are all
situated 'inside a CTR'...

Since, however, according to http://en.wikipedia.org/wiki/Airspace_class
these ATZ's and MATZ's do not fall within the ICAO classes, adding them
as an allowed airspace class to our OpenAir files might make our files
non-compatible with certain devices that don't support ATZ and MATZ classes.

My suggestion would therefore be to add the string 'ATZ' to the *name*
of the class (AN-record). The oaconvert software can then check if the
AN record in the OpenAir file contains the substring 'ATZ' and if this
is the case, select the appropriate type for visualization.

The airspace class to assign to the AC record, can be found in the
Remarks collumn in the AIP. For example for a Civil one:

AC G
AN Budel ATZ

and for a military one:

AC CTR
AN Deelen ATZ

What do you think? Does this make sense to you? If yes, feel free to
start coding these OpenAir files and send me a git pull request! :-)

Regards,
Bart

[Arien Hoiting]

I think this could work but.....:
The software should assign a different type for visualization to the
combinations
AC G + AN ...ATZ type x
AC CTR + AN .... ATZ type y
On my Gramin type x will pop up as a forbidden area and type y as a
danger or restricted area.

Best regards,
René








On May 7, 11:56 pm, Bart Vandewoestyne <Bart.Vandewoest...@telenet.be>
wrote:

> Since, however, according tohttp://en.wikipedia.org/wiki/Airspace_class

[René]

He that was suppose to be me instead of my wyfe with a response
René

[Bart Vandewoestyne]

This was indeed exactly as I had it in mind.  I will put this on the Issues list and get to it when I have some time.

Regards,
Bart