It's hard to explain this but I'll try. Objects on the display can be divided into two groups - waypoints and outlines. Waypoints are point source objects like fixes, navaids, VRP's etc and outlines are line drawings to delineate controlled airspace or danger areas or whatever. The trouble is that the SCT file format has not taken the above into account and so we don't have a lot of options for creating outlines. The only choice is to place these in the few categories that do exist and so LOW AIRWAY or HIGH AIRWAY get hijacked for other purposes. This is why, in my own SCT file, I have moved holding points to Low Airway and VRP's to High Airway so at least I get the chance to turn them off. In the SBS software there are no less than 30 individual sections for waypoints and the same for outlines. I can therefore have coastlines, TMA, CTA, CTR, ATZ, MATZ, Upper airways, lower airways, Danger areas, FIR, AIAA, ARA, ATA, Airports and so on as separate items to turn on or off as I wish. The same goes for waypoints and I have these separated into Major Airfields, VOR's, NDB's, Fixes, TACAN, Minor Airfields, Masts, Disused airfields, Heliports, VRP's - and even Hang Gliding, Microlight and Parachute sites. The SCT file format needs urgent revision to allow similar flexibility. Until then each designer does what he thinks best for his own airspace and this may not be ideal for other sectors. bones -----Original Message----- From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On Behalf Of 175@xxxxxxxxxxxx Sent: 03 February 2008 03:52 To: jhb@xxxxxxxxxxxxx Subject: [jhb] Re: dvd Many thanks bones Reading through the IVAO Forum, I discover that many sector files for Ground and Approach are written with overlays in the Airways pages, as these are generally not utilised for these positions. Having read further "wishlist" posts, extra pages for overlays are high on the agenda for v2. I say this as I have a lot of stand, taxiway and apron info on the screen for use when giving taxi and parking instructions, however when zoomed out this becomes a huge blob completely obscuring the airfield plan. Having used the controller software for a while it is growing on me, but it can get very lonely, especially due to having only the one comms channel, and being a smidgen over 200 miles from EGNS I cant see how the experts do it! Muchas Gracias Kev T "bones" <bones@xxxxxxx> wrote: > I don't add LARS to my airspace files normally as it isn't controlled > airspace - just a boundary for providing a service. All other > airfields have a LARS boundary of 30nm or 40nm radius so it's not > exactly difficult for the controller to work out his area of > operation. > > The Farnborough LARS is quite unique and you are right that it needs > flagging up on screen. I'll send you the data sometime over the > weekend for the SCT file. > > bones > > -----Original Message----- > From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On > Behalf Of 175@xxxxxxxxxxxx > Sent: 02 February 2008 14:15 > To: jhb@xxxxxxxxxxxxx > Subject: [jhb] Re: dvd > > > All good news bones > > Can you advise how to add this "Farnborough Radar" area to my .sct > info? Might you have it for SBS? > > http://www.ais.org.uk/aes/en/LARS.PDF > > Cheers > > Kev T > > > > "bones" <bones@xxxxxxx> wrote: > > > Now that Farnborough is providing LARS for the east as well as west > > and south sectors I think you will have your hands full... <g> > > > > bones > > > > -----Original Message----- > > > > > > >