Originally Posted by
BackPacker
Furthermore, it's very easy for the writer of the NOTAM to get the coordinates/radius wrong, since there's not a lot of checking done on this sort of thing. NOTAMs have been known to have a wrongly encoded bounding circle, so that parts, or even all of the NOTAM lies outside the bounding box. And sometimes the radius is set ridiculously large.
The Google App Engine backend to the maps scans the E-Line for co-ordinates and compares it the the formal extent in the Q-Line, and if there is a disparity emails various relevant folk reporting the issue. Invariably they are fixed before most people see them. The report generates a Google Map showing the mismatch -
for example