<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 8, 2018, at 6:27 AM, Warin <<a href="mailto:61sundowner@gmail.com" class="">61sundowner@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;" class="">airmark:light I think is better.<span class="Apple-converted-space"> </span></span></div></blockquote></div><br class=""><div class="">there are already approach lights, PAPI lights, etc. I think saying that these are obstacle / hazard warning lights is appropriate. </div><div class=""><br class=""></div><div class="">Beyond mapping runways and terminal buildings, The airmark stuff is very specific because people flying planes all use extremely specific language for things to avoid confusion. </div><div class=""><br class=""></div><div class="">Javbw. </div></body></html>