PPRuNe Forums - View Single Post - European AIS Database
View Single Post
Old 23rd July 2003 | 00:31
  #48 (permalink)  
Andrew Sinclair
 
Joined: Jul 2002
Posts: 94
Likes: 0
From: UK
It took me a while to get it sorted out so I sympathize with you there Aerobatic Flyer.

There is one point that is worth bringing up at this time and again it is the issue of this Q Line, sorry to bang on about it!

In the particular example I posted, this part
<QLine>
<FIR>EGTT</FIR>
<Code23>RO</Code23>
<Code45>LP</Code45>
<Traffic>IV</Traffic>
<Purpose>NBO</Purpose>
<Scope>E</Scope>
<Lower>000</Lower>
<Upper>040</Upper>
</QLine>
<Coordinates>4932N00153W</Coordinates>
<Radius>50</Radius>
contains all the information that is required by a s/w developer in order to present the information graphically on a map. This is the part that is currently removed from the NOTAM prior to them being placed on the UK AIS AES tool as PIB. This is the difference between a NOTAM and a PIB. At the moment NATS/AIS and the CAA are considering whether they should release the Q Line. As both organisations are necessarily very structured in their working practices it takes time to discuss the ramifications of releasing the Q Line before they make a decision.

The interesting point is that the Q Line information above came direct from AED to me, the Public User, via the internet and AED is owned and controlled by Eurocontrol, so they have decided it is ok to release the Q Line. It is hoped that the CAA are able to come to the same conclusion as Eurocontrol and release the Q Line. The CAA may not agree for a variety of reasons unilaterally specific to the UK and are of course entitled to make an their own autonomous decision on this issue. The release of the Q Line coupled with direct data from the ADIMS database (via whatever firewall protection is deemed necessary) gives the GA world huge possibilities for accurate data manipulation without the need to parse a text file (i.e. recover date from a presentation primarily intended for visual/human use). In essence What we are after is data in a defined database-type format, rather than an unstructured and undefined text file which is what we are presently getting. With the raw data we know exactly what data appears where.

This is an ideal state and is possible from a technical point of view. There are, however, other surrounding issues that need more debate, negotiation and agreement by interested stakeholders including us the GA community. These issues are being actively pursued by a number of private flyers and representative organisations, but it is good that we all have an understanding of the issues.

Last edited by Andrew Sinclair; 23rd July 2003 at 15:49.
Andrew Sinclair is offline