The way it currently works is NOTAMs first, then Airspace. If several NOTAMs are superimposed they are ordered smallest to largest. If no NOTAMs, then Airspace is displayed. Airspace is prioritised in order of importance. I agree that the popup logic could be improved.

While you are looking at the popup code, there is something else I have just noticed.
If I am looking at a point outside of any NOTAM coverage, and hover over a CTA I get the CTA displayed in a popup. Within NOTAM cover I only get the NOTAM.
If I uncheck 'View NOTAM' I get the popup for CTAs inside the notam coverage.
It looks like there is a hierarchy of over-rides in what gets displayed in popups. NOTAMS splat everything else, Danger areas override CTAs, glider areas, etc.
Maybe this is how it should be, but I would have expected lower level popup info to be displayed as well, perhaps as an extra box after all of the higher priority data.
John T.

Curiously, the information popups are sometimes displayed within overlapping MATZs, but only If you remove CTA/CTR from display and position the crosshair precisely on the dot at the airfield centre.
Take Dishforth/Topcliffe/Leeming for example. Spot on EGXZ you get the popup. Elsewhere within the combined boundary you don't, not even on the other airfield centres.
Similar for Cranwell/Barkston heath, you get the popup at EGYE, but nowhere else in the MATZ.
However, I cannot find any point within any other overlapping MATZ (I have not tried all of them!) where you display the popup.
If you enable CTA/CTR you only get that info, not the MATZ.
John T.

Yes, it appears that where two MATZ circles overlap, the "is visible" algorithm breaks down, so the boundaries are not displayed near the edge, even though they are partially still on the screen.

You may also notice that the information popups do not occur in these areas, or else they display the info for another underlying area.

I'll take a look into this - thanks for pointing it out.

Welcome to the forum!

OK, this might be me, or my PC, but...

If I have on display a non-circular MATZ region where two or more MATZs overlap, for example  Boscombe Down/Middle Wallop, or Dishforth/Topcliffe/Leeming, then slowly move the display centre away from the MATZ until the centre of the combined MATZ boundary is just off screen, the boundary vanishes.
MATZ stubs still on screen remain.
It does not matter which screen edge the MATZ is moved off, it happens on all four.

This problem does not happen on circular objects such as the Benson or Odiham MATZs, and I have not observed it with objects other than MATZs.

Could I have discovered a bug on the very first day I try using this application ?
John T.

Goodness, names I recognize ! I too am an ex deccie, though in VAX (and Alpha) hardware support.
Now effectively retired from commercial computing and back into gliding after 43 years since my Air Cadet solo's in what we now know as a T31.
Better late than never...

Added *@gmx.com to the email ban list.

Thanks for spotting this and reporting it.

Yes, the dates are given in different formats for the two methods (wish they would standardise!), and Spine processes accordingly. I can't believe they have changed the format yet again! (Meaning: it wouldn't surprise me in the least.)

I will check this out. If the format has indeed changed, I'll try to make the parsing a bit more robust, in case they feel like changing it back again.

PS: My internet connection was down this morning, otherwise I'd probably have picked this up earlier.

I have Spine 5.5 and Spine 5.4 on different pooters (both WinXP) and neither plot NOTAMs any more. It could be because they're misinterpreting dates - I notice that all today's batch via the AIS website are listed by Spine as being valid from and to Sat 30-Dec-1899 00:00 UTC

Just checked, the 'download' option does plot.
Date representation in Download, thus:

<span class="endgap">
<b>
FROM:
</b>
24 SEP 2009 00:01
</span>
<span>
<b>
TO:
</b>
08 APR 2010 23:59
</span>

and same date representation from AIS website, thus:

<span style="padding: 0 20px 0 0">
B) FROM: 09/09/24 00:01
</span>
C) TO: 10/04/08 23:59


maybe that's something to do with it.