Return to the Worldwide Soaring Turnpoint Exchange
Table of Contents?
Please contact John Leibacher with any suggestions concerning this material.
############################################################# ##################### USER DEFINED FILE ################## ##################### UPDATED JANUARY 2006 ################## ############################################################# # # This is an (almost) empty file in which you can define your own Display Data. # # The standard extension for these files is AIR # # All lines beginning # are considered comments and will be ignored. # # INCLUDE= skip all text when a line beginning INCLUDE=NO is encountered # until a line beginning INCLUDE=YES is encountered. # This will normally be on the line BEFORE a TITLE= line. # YES and NO are the only permitted Values. # # The file provides descriptions of blocks of airspace. # These blocks of airspace may consist of more than one sub-block. # Blocks of airspace have the following attributes: # # Each block of airspace must have a TITLE. # The TITLE determines the start of a new block of airspace. # # Blocks of Airspace # ----------------------------- # Each block of airspace will consist of one or more sub-blocks # Each block of airspace should have one or more BASE and one or more TOPS. # The BASE and TOPS do not persist between blocks. # Each block of airspace should have a TYPE which may persist between blocks. # Each block of airspace may have a CLASS which may persist between blocks. # Each block of airspace may have a ACTIVE which may persist between blocks. # Each block of airspace may have a RADIO which may persist between blocks. # # Sub-blocks of airspace # --------------------------- # The sub-blocks describe the shape of the airspace. # Each sub-block will have a shape statement. eg POINT, CLOCKWISE, CIRCLE, AWY. # Each sub-block may have further attributes describing the shape eg RADIUS,WIDTH # Each sub-block may have a BASE or TOPS or RADIO attribute. # The BASE and TOPS and RADIO attributes may persist between sub-blocks. # # Each line consists of a Keyword and a value. # These Keywords are defined as follows: # # TITLE= Blocks always commence with a line beginning TITLE=. # Most programs should display up to 12 characters of a title. # Programs should not change the type of airspace based on the title. # # TYPE= values are:This defines the Type of Airspace. The permitted values are: # Definition Abbreviation # CTA/CTR C # AIRWAYS A # RESTRICTED R # PROHIBITED P # DANGER D # OTHER O # TRAINING ZONE Z # TRAFFIC INFO I # GSEC G Glider Sector # MATZ M Military Zone # TMZ T Transponder mandatory zone # BOUNDARY B Boundary FIS or country # A blank line, or X eg TYPE= should set the value to blank / unknown # # # CLASS= This defines the Classification of Airspace. # The permitted values are: A,B,C,D,E,F,G # A blank line, or X eg CLASS= should set the value to blank / unknown. # # ACTIVE= airspace. This defines the normal hours of operation of the airspace. # The permitted values are: # WEEKDAY normally only operational during the week and inactive at weekends # EVERYDAY normally operational everyday including weekends # NOTAM normally only operational by NOTAM # WEEKEND normally only operational at weekends and public holidays # A blank line, or X eg ACTIVE= should set the value to blank / unknown. # # RADIO= in MHz. If used, this describes a control radio frequency in MHz # Values are a text field. For example: # 127.75 # APP 127.75 # 130.23 / 126.56 # A blank line RADIO= should set the value to blank / unknown. # Abbreviations: APP Approach, TWR Tower, RAD Radar, INF Information # # TOPS= # BASE= Each block of airspace requires a BASE= and TOPS= statement # in order that Air_Check can detect infringements. The BASE can be # defined as a Flight Level or ALT. TOPS will normally be a Flight # Level. For example: # WIDTH=10 # BASE=2500ALT # TOPS=FL245 # or # WIDTH=10 # BASE=FL55 # TOPS=FL245 # Also acceptable SFC surface eg BASE=SFC # # The following extension to the specification may be used, but is not recognised # by all software as it require topographic data in addition. # # AGL above ground level eg TOPS=800AGL # AAL above aerodrome level eg TOPS=2000AAL # # Note: Not handled, variable height airspace. # # POINT= This is always followed by a Lat/Long position, for example # POINT=N524033 W0014350. It is important that the construction # is followed exactly. If this is the first POINT= line AFTER a # TITLE=, drawing will commence from this point, otherwise a line # will be drawn from the previous point to this new point. The last # POINT will normally be the same as the first POINT. # # CLOCKWISE or ANTI-CLOCKWISE # This is always followed by a RADIUS keyword, a CENTRE Keyword and # a TO Keyword (The only valid place for RADIUS, CENTRE and TO # keywords is when describing an Arc or Circle.), and describes # an arc to be drawn Clockwise or Anti-Clockwise from the current # position, and should be constructed as follows: # ANTI-CLOCKWISE RADIUS=8 CENTRE=N522734 W0014404 TO=N521948 W0014754 # or CLOCKWISE RADIUS=8 CENTRE=N522734 W0014404 TO=N521948 W0014754 # The units of Radius are Nautical Miles. # # CIRCLE= Secondary keywords.Similar to Arc but with only RADIUS and CENTRE Secondary keywords. # e.g. CIRCLE RADIUS=10 CENTRE=N555700 W0032227 # WIDTH= Nautical Miles and This Keyword describes the width of an Airway in Nautical Miles and # is only used in conjunction with an AWY keyword. If no WIDTH= # statement is given then 10NM will be assumed. # AWY= This is like the POINT= keyword and describes a point on the # centre-line of an Airway whose width has been previously given in # a WIDTH= statement # e.g. WIDTH=10 # AWY=N555223 W0042607 # # Note: no need to handle airways with offset centre lines,although they exist. # # The file must finish with the word END # # You can use this file to draw any shape you wish, for instance you could # draw your Base Airfield's ATZ or Runway. The following sample data draws the # Main Runway at Lasham, and by request, the 'Compton Box' which may be made # available on some days at Lasham Competitions. # # minutes, seconds NOTE: POINTs etc. are in the format (d)ddmmss [degrees, minutes, seconds] # INCLUDE=YES TYPE=TRAINING ZONE # TITLE=Lasham Runway 09/27 # POINT=N511112 W0010238 POINT=N511114 W0010238 POINT=N511119 W0010109 POINT=N511117 W0010109 POINT=N511112 W0010238 # # # COMPTON BOX # INCLUDE=NO TITLE=COMPTON BOX (Below 5500ALT) BASE=4500ALT TOPS=5500ALT # POINT=N512435 W0011444 POINT=N513423 W0011138 POINT=N513348 W0010654 POINT=N512400 W0011001 POINT=N512435 W0011444 # # # End of File. Have Fun! # END
Return to the Worldwide Soaring Turnpoint Exchange
Table of Contents?
Please contact John Leibacher with any suggestions concerning this material.