If supporting TNP airspace format is more likely than adding a Radio field to OpenAir version of the airspace file then this is what I found. # 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 # BASE=SFC
Hi! Since 6.0 is now out there we officially support the TNP airspace file format. I haven't yet heard of that radio frequency field though. Could you provide us with some more information about that?! I guess it would be best to open a ticket on trac if anyone would want us to implement it, so that we don't forget ;) Adding a frequency field to the open air format isn't as easy as it sounds. The problem is that the people providing the open air file need to be aware of such a feature and use it. Also the addition of stuff to that file format standard is not within our hands... The only thing we could do is support a non-standard, but I don't really like that idea. Turbo -- View this message in context: http://old.nabble.com/Data-files-used-in-XCSoar%3A-airfield-data-tp30492353p30507771.html Sent from the xcsoar-user mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Forrester recently released a report on the Return on Investment (ROI) of Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even within 7 months. Over 3 million businesses have gone Google with Google Apps: an online email calendar, and document program that's accessible from your browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
