![caa vfr charts caa vfr charts](https://nats-uk.ead-it.com/cms-nats/export/sites/default/en/Charts/vfr-charts/Helicopter-Twilight-Blue_RGB-1.png)
The QCT format is proprietory to Memory Map and whilst some apps (such as GPS Utility) will open these files, none will allow any form of modification and subsequent export. The first, and most obvious hurdle is the format of the maps. In order to pursue either option, a jailbroken iPhone is required.
#Caa vfr charts Offline
It is highly configurable and also supports offline maps. This is a GPS nav application which is freely available from Cydia. This allows the use of the app when you have no GSM signal, without a SIM inserted, when abroad without getting stung for data roaming, etc. The Google Maps application has some little-known functionality which allows the provision of offline maps, meaning that instead of downloading a new map tile as you move into that area you can actually download a huge area from Google Maps and store it on your iPhone. There are a couple of possibilities here. Second on the possibilities list was to use the QCT maps on an existing iPhone GPS nav product.
#Caa vfr charts code
Additionally I had to sign an NDA for the AMD code and was told there were no plans to contribute it to the WINE project at the current time which would have obliged them to GPL it. However, this was far from friendly (ok, it was downright butchery) and not something the vast majority of people would ever want to attempt.
#Caa vfr charts serial
The serial device mapping for the GPS was fairly easy. The former were the worst in terms of performance due to the emulation overhead, but work they did in a limited capacity. However the mouse worked ok and I was able to run both x86 Win32 and ARM WinCE apps with some degree of usability. The performance was less than impressive, and the issue of the on-screen keyboard not working is obviously a problem. Messing around with products such as Qemu and WINE, some ARM instruction set porting work (c/o a good friend AMD, thanks!) and the addition of some butchered WinCE DLL source from the ReactOS project eventually bore fruit. Obviously this presents a whole wealth of problems, but for a seasoned Unix geek these were not insurmountable. The initial line of experimentation was to run Memory Map and/or Pocket Navigator on the iPhone. It should be noted that geeky terms maybe used from here on in. Personally, I did not do this because I wanted to use CAA charts on my iPhone in the air, I did it to prove it could be done. If however you still want to persist in using a phone for your navigation in the cockpit, and your phone happens to be the splendid iPhone 3G or 3GS, there are ways and means to get around the fact that the CAA charts are produced in the proprietory Memory Map QCT format and thus constrained to being run on the world's worst operating system Windows Mobile. It also contains all the airway waypoints which is rather handy when flying abroad in Class D/E airways, a world away from the Class A fetish of the UK. A SkyMap 3 (I got mine on eBay for under £500) packs much more punch and makes minced-meat out of the cheaper Garmin VFR units. So you want to be able to use CAA VFR charts on your iPhone, huh? My first response would be, "don't bother". stack tracing, debugging & reverse engineering) require in-depth understanding of how computers work and hence are not discussed in any detail. I recommend you do the same as they're all excellent.
#Caa vfr charts software
Note that I in no way advocate software piracy, have earnt a good living writing assembler in the distant past, and have happily paid for all the commercial products referenced in this article. Instead of replying to everyone individually I decided I'd do a little write up on the subject. Apologies for what is quite a long post, but having casually mentioned the use of CAA maps on the iPhone I got rather a lot of emails.