FlightHistorian can now generate GPX and KML map data files for every map it shows.
Flight Historian has been updated to version 2.3.
Flight Historian has been updated to Version 2.2.
I used to manually keep track of which airports were within the contiguous United States in Flight Historian’s airport data, but I realized that I could determine airports’ regions by looking at their ICAO codes instead.
I’ve added to Flight Historian the ability to create flights by importing digital boarding passes from the Apple Wallet app.
On my Flight Historian application, a number of my pages make use of the flash and flash.now session messages capability for errors, warnings, successes, and informational messages. However, some of those pages needed to have multiple messages of the same type (e.g., multiple warnings), which flash didn’t allow me to do. To fix this, I wrote my own messages structure.
Boarding pass barcodes contain data that’s useful for automatically filling in flight data, but their dates are particularly difficult to parse.
Why did I build my own flight log instead of using an existing one? One big contributor was that existing flight logs all seemed to double-count layovers.
I’ve relaunched my flight log as its own separate site, and it’s now known as Flight Historian.
Each country has its own assigned format for tail numbers, so it's possible to look at each tail number and determine what country it’s from. I wanted to create a regular expression to recognize US tail numbers.