Thanks for the feedback chaps.
I'm planning a few enhancements, but I'd be interested in hearing what you think might be of immediate benefit.
1) Geolocation - the extension uses a reverse geocoding web-service to annotate the tree view with an approximate location name for the NOTAM centre co-ordinate. The web-service has a request-rate quota which means it takes a while to populate the tree view fully, particularly if you run a multi-FIR area brief. I'm planning on using the client-side SQL database in Chrome to cache these results so that a NOTAM which has previously been reverse geocoded has the location immediately available.
2) Using the same data storage, add a set of user preferences - fill/edge colors, transparency factors, radius thresholds at which only the outline of the NOTAM is shown.
3) Display filters, adding fine-tuning to the query parameters used to generate the AIS brief in the first place. Upper/Lower limits, start/end times. Filter out trigger NOTAMs. Also, a persistent kill-list of NOTAMs you don't wish to see again.
4) Quality check - highlight NOTAMs which appear to have been miscoded - by identifying cases where the text of the NOTAM included references to co-ordinates outside of the circular extent (for example B1724/10 this morning - temporary Class A from the Highlands to Stornaway, NOTAM had a 12nm circle over Anglesey)
5) Reverse navigation by NOTAM id from the map to the text of the AIS brief.
6) Narrow Route Brief preview. Currently if a Narrow Route Brief is run, the route is projected onto the map - including intermediate points identified by navaid ID, navaid plus offset, raw lat/lng and by airway/UAR segment traversal. It wouldn't be difficult to add a small preview map to the NRB query page showing the proposed route in the same way, before the NRB
is generated.
7) Optionally prune the text of the report for printing, either by a small
show/hide checkbox in the text report itself, or by linking visibility of
NOTAMs in the map to visibility in a printed report.
8) Obviously, extending support to Safari and Firefox - but ahead of the enhancements above?
Any other ideas, I'm all ears.