<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Mathew....i been searching for the new website but cant find
it....what is the URL for the site <br>
</p>
<p><br>
</p>
<p>73 David VK4BDJ<br>
</p>
<br>
<div class="moz-cite-prefix">On 24/11/17 17:18, Mathew McKernan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SYXPR01MB2093EB2F9D6B6C2BD535F7359F260@SYXPR01MB2093.ausprd01.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"
dir="ltr">
<div id="divtagdefaultwrapper" style="font-size: 12pt; color:
rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif,
"EmojiFont", "Apple Color Emoji",
"Segoe UI Emoji", NotoColorEmoji, "Segoe UI
Symbol", "Android Emoji", EmojiSymbols;"
dir="ltr">
<p style="margin-top:0;margin-bottom:0">Hi all,</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Thanks to everyone who
has helped at every turn with this project resurrection,
including Geoff for the original code, plus everyone who has
helped with old shape files, content, the former WXSVR-AU
website and the like. It is very much appreciated.<br>
</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">An update for everyone
as to the current status. </p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<ul style="margin-bottom: 0px; margin-top: 0px;">
<li>I've activated WXSVR-AU and it is working <span>😊</span>
with some fixes due to changes in BOM, NSW RFS,
VicEmergency etc. Biggest challenge was the massive
learning curve and mixture of "what was previously done"
and now.</li>
<li>Key items for awareness:
<ul>
<li>UIView32 is dead with shapes for BOM areas. Geoff
made a change some time ago to stop using the NWS
Format for events, so we don't cause confusion on the
network. I don't plan on hacking WXSVR-AU to make it
work with older clients that only do NWS weather
bulletins. Seemed to be a lot of debate on this in the
US APRS mailing lists years ago around this.</li>
<li>Xastir has implemented functionality in line with
this change. I am planning on reaching out to APRSISCE
for Windows Users.</li>
<li>Shape files have <b>changed</b>, the BOM changed
these some time ago and have moved away from the
method and format they previously used.</li>
<li>This means new dbfawk files are needed for Xastir.</li>
<li>It also means get-BOMdata no longer works as well.
The shapes are available, but filenames have changed
and content has changed as well, hence why we need
different dbfawk files.</li>
<li>The good news is that Xastir doesn't necessarily
need development changes. Just that certain files need
to be renamed - e.g. IDM00001.shp becomes
<span>gfe_public_weather</span>.shp etc.
gfe_metro_areas.shp is retired.</li>
</ul>
</li>
<li>The old WXSVR-AU was very reliant on using LGA's (Local
Government Areas) in NSW for Fire Incidents.
<ul>
<li>I've changed this and have coded in functionality to
take the Latitude/Longitude from the fire incidents,
tie it to a forecast area and send it out that way.
This is done by finding the forecast shape that the
fire incident is within.</li>
<li>The end goal is to include incidents from all Fire
Agencies Australia wide, all publish the
Latitude/Longitude, but not the LGA - hence the need
to make this change to map it back to forecast area.</li>
<li>NSW Fire Incidents will trigger a Weather Bulletin
for incidents that have community warnings associated
to them for Advice, Watch and Act, Emergency Warning.
Victorian fires do not have this functionality, yet.</li>
<li>This also makes setting up iGates much, much easier.<br>
</li>
</ul>
</li>
<li>Weather Warnings
<ul>
<li>Available Australia wide as a Weather Bulletin
Message and a Area specific shape.</li>
<li>Each event includes a object in the centreoid of the
weather zone.</li>
<li>The idea of the object is so you can know what the
alert is all about with some useful text.<br>
</li>
<li>The warnings available are:
<ul>
<li>Severe Thunderstorm Warning<br>
</li>
<li>
<div>Flood Watch or Warning</div>
</li>
<li>
<div>Severe Weather Warning</div>
</li>
<li>
<div>Fire Weather Warning</div>
</li>
<li>
<div>Sheep Weather / Graziers</div>
</li>
<li>
<div>Bushwalker Weather Alert</div>
</li>
<li>
<div>Frost Warning</div>
</li>
<li>
<div>Cyclone Watch or Warning</div>
</li>
<li>
<div>Fire Ban Advice</div>
</li>
<li>
<div>Marine Wind Warning</div>
</li>
<li>
<div>Brown Rot Advice<br>
</div>
</li>
<li>
<div>Downy Mildew Advice<br>
</div>
</li>
<li>
<div>Tsunami Threat Watch or Warning<br>
</div>
</li>
<li>
<div>Aviation Lightning Warning<br>
</div>
</li>
</ul>
</li>
</ul>
</li>
<li>Fire Danger Ratings:
<ul>
<li>Only available for all of Victoria at this stage.</li>
<li>Objects created for all rating levels from
Low-Moderate through to Code Red (or Catastrophic,
depending on your state). These are positioned in the
centre of the zone based on the "centreoid" of the
zone - essentially the middle position taking into
consideration that our zones are not circles and
follow natural land edges. </li>
<li>Low-Moderate & High will not result in an output
for a weather warning but will output an object giving
the FDR.</li>
<li>Very High, Severe will result in a Weather Watch
with object<span> giving the FDR</span></li>
<li>Extreme and Catastrophic (or Code Red) will result
in a weather warning with object
<span>giving the FDR</span>.<br>
</li>
</ul>
</li>
<li>New Implementation Detail:<br>
<ul>
<li>Source callsigns have the format of ZZZxxx, ZZZ is a
3 letter code assigned for the forecast zone, xxx is
the product type - this is assigned by the WXSVR and
doesn't match any BOM names unfortunately.
<br>
</li>
<li>BOM use 8 digit values (e.g. NSW_PW001 is a zone),
meaning we then lose the ability to include the
product type (meaning people can't filter particular
products). Not to mention it is too long I believe for
AX25 packets and breaks the format.</li>
<li>If people want to gate the data onto RF, they would
allow anything with the callsign starting with their
respective forecast area. This will then gate weather
warnings, fire danger ratings and fire incidents onto
the air.</li>
<li>I will publish the zone codes next week sometime
when I replicate the data a bit more.</li>
</ul>
</li>
<li>WXBot like functionality:
<ul>
<li>Not available as yet, I am working on this. <br>
</li>
<li>I found the source for the US Version of WXBot and
plan to use this as a basis and enhance it for
Australia.
<br>
</li>
<li>I am thinking it will have the same callsign as
WXSVR-AU, meaning we can eventually provide "finger"
functionality to obtain more information from the
original bulletin.</li>
</ul>
</li>
</ul>
</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
If you'd like to see this data in your respective client, add
"e/WXSVR-AU" to your filter on APRS-IS.</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
Feedback is very much welcome, including being told to turn it
off because it is too noisy!<br>
</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
Cheers and 73s!</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
<br>
</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
Matty</div>
<div style="font-size: 12pt; color: rgb(0, 0, 0); font-family:
Calibri, Helvetica, sans-serif, "EmojiFont",
"Apple Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol", "Android
Emoji", EmojiSymbols;" dir="ltr">
VK3MJM<br>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" face="Calibri, sans-serif"
color="#000000"><b>From:</b> OZAPRS
<a class="moz-txt-link-rfc2396E" href="mailto:ozaprs-bounces@aprs.net.au"><ozaprs-bounces@aprs.net.au></a> on behalf of Mathew
McKernan <a class="moz-txt-link-rfc2396E" href="mailto:mathew@mmckernan.id.au"><mathew@mmckernan.id.au></a><br>
<b>Sent:</b> Thursday, 23 November 2017 3:11 PM<br>
<b>To:</b> Australian APRS Users<br>
<b>Subject:</b> Re: [OZAPRS] WXSVR</font>
<div> </div>
</div>
<div dir="ltr">
<table
id="msexchangesafetytips;b025c973-97f1-4303-0323-08d5322846bb;R:en-AU"
style="border:0; display:table; width:100%;
table-layout:fixed; border-collapse:seperate;
float:none" cellspacing="0" cellpadding="0" align="left"
width="100%" border="0">
<tbody>
<tr>
<td cellpadding="7px 2px 7px 2px" style="padding:7px
2px 7px 2px; background-color:#910A19"
valign="middle" bgcolor="#910A19" width="1px">
<br>
</td>
<td cellpadding="7px 5px 7px 15px" color="#212121"
style="width:100%; background-color:#FDF2F4;
padding:7px 5px 7px 15px;
font-family:wf_segoe-ui_normal,Segoe UI,Segoe
WP,Tahoma,Arial,sans-serif; font-size:12px;
font-weight:normal; color:#212121;
text-align:left; word-wrap:break-word"
valign="middle" bgcolor="#FDF2F4" width="100%">
<div>This sender failed our fraud detection checks and may not be who they appear to be. Learn about <a
href="http://aka.ms/LearnAboutSpoofing"
moz-do-not-send="true">spoofing</a></div>
</td>
<td cellpadding="7px 5px 7px 5px" color="#212121"
style="width:75px; background-color:#FDF2F4;
padding:7px 5px 7px 5px;
font-family:wf_segoe-ui_normal,Segoe UI,Segoe
WP,Tahoma,Arial,sans-serif; font-size:12px;
font-weight:normal; color:#212121;
text-align:left; word-wrap:break-word"
valign="middle" bgcolor="#FDF2F4" align="left"
width="75px">
<a href="http://aka.ms/SafetyTipsFeedback"
moz-do-not-send="true">Feedback</a></td>
</tr>
</tbody>
</table>
<div>
<div id="x_divtagdefaultwrapper" dir="ltr"
style="font-size: 12pt; color: rgb(0, 0, 0);
font-family: Calibri, Helvetica, sans-serif,
"EmojiFont", "Apple Color Emoji",
"Segoe UI Emoji", NotoColorEmoji,
"Segoe UI Symbol", "Android
Emoji", EmojiSymbols;">
<p>Hi Peter,</p>
<p><br>
</p>
<p>No problem!</p>
<p><br>
</p>
<p>Just wondering, how did you handle those FDR
objects? Did you do them as polygons or as points?</p>
<p><br>
</p>
<p>I've noticed there is very limited support nowdays
around NWS/BOM alerts in ARPS products. The original
version of the weather alerts in WXSVR-AU used NWS
objects and we'd upset our friends in the united
states. It also meant we had to hack around with
modified shape files to make it all work.</p>
<p><br>
</p>
<p>Xastir seems to work with the BOM shape files with
the BOM based notifications, which means we have a
more uniformed setup and we don't need to handcraft
shape files.</p>
<p><br>
</p>
<p>Another option I am thinking of for some situations
are publishing polygon objects instead.</p>
<p><br>
</p>
<p>Thanks,</p>
<p><br>
</p>
<p>Matty<br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block;
width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" face="Calibri, sans-serif"
color="#000000"><b>From:</b> OZAPRS
<a class="moz-txt-link-rfc2396E" href="mailto:ozaprs-bounces@aprs.net.au"><ozaprs-bounces@aprs.net.au></a> on behalf of
Peter Wicklein <a class="moz-txt-link-rfc2396E" href="mailto:vk3tbn@hotmail.com"><vk3tbn@hotmail.com></a><br>
<b>Sent:</b> Wednesday, 22 November 2017 6:45:02 PM<br>
<b>To:</b> Australian APRS Users<br>
<b>Subject:</b> Re: [OZAPRS] WXSVR</font>
<div> </div>
</div>
<div dir="ltr">
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_x_MsoNormal, li.x_x_MsoNormal, div.x_x_MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:x_x_link, span.x_x_MsoHyperlink
{color:blue;
text-decoration:underline}
a:x_x_visited, span.x_x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
ol
{margin-bottom:0cm}
ul
{margin-bottom:0cm}
-->
</style>
<div class="x_x_WordSection1">
<p class="x_x_MsoNormal"><span lang="EN-GB">Matty</span></p>
<p class="x_x_MsoNormal"><span lang="EN-GB"> </span></p>
<p class="x_x_MsoNormal"><span lang="EN-GB">Great,
more particularly the Fire items, years ago i
used to add them as objects via ui view, bit
hard to keep updated if you go on holidays..</span></p>
<p class="x_x_MsoNormal"><span lang="EN-GB"> </span></p>
<p class="x_x_MsoNormal"><span lang="EN-GB">Regards</span></p>
<p class="x_x_MsoNormal"><span lang="EN-GB">Pete</span></p>
<p class="x_x_MsoNormal"> </p>
<p class="x_x_MsoNormal">Sent from my Windows 10
phone</p>
<p class="x_x_MsoNormal"> </p>
</div>
<hr tabindex="-1" style="display:inline-block;
width:98%">
<div id="x_x_divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" face="Calibri, sans-serif"
color="#000000"><b>From:</b> OZAPRS
<a class="moz-txt-link-rfc2396E" href="mailto:ozaprs-bounces@aprs.net.au"><ozaprs-bounces@aprs.net.au></a> on behalf of
Mathew McKernan <a class="moz-txt-link-rfc2396E" href="mailto:mathew@mmckernan.id.au"><mathew@mmckernan.id.au></a><br>
<b>Sent:</b> Wednesday, November 22, 2017 12:49:07
PM<br>
<b>To:</b> Australian APRS Users<br>
<b>Subject:</b> [OZAPRS] WXSVR</font>
<div> </div>
</div>
<div>
<div id="x_x_divtagdefaultwrapper" dir="ltr"
style="font-size: 12pt; color: rgb(0, 0, 0);
font-family: Calibri, Helvetica, sans-serif,
"EmojiFont", "Apple Color
Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol",
"Android Emoji", EmojiSymbols;">
<p>Hi all,</p>
<p><br>
</p>
<p>I reached out to Geoff Gatward who was the
creator/original maintainer (to my knowledge) of
the old WXSVR-AU service.</p>
<p><br>
</p>
<p>I've been doing some work on this over the past
few days and seem to have it operating again.</p>
<p><br>
</p>
<p>Is this a service everyone would be interested
in returning to service?</p>
<p><br>
</p>
<p>In terms of functionality for those who can't
remember:</p>
<ul style="margin-bottom:0px; margin-top:0px">
<li>Weather warnings from the BOM for
<ul>
<li>Severe Thunderstorm Warning<br>
</li>
<li>
<div>Road Weather Alert</div>
</li>
<li>
<div>Flood Watch or Warning</div>
</li>
<li>
<div>Severe Weather Warning</div>
</li>
<li>
<div>Fire Weather Warning</div>
</li>
<li>
<div>Sheep Weather Alert</div>
</li>
<li>
<div>Bushwalker Weather Alert</div>
</li>
<li>
<div>Frost Warning</div>
</li>
<li>
<div>Cyclone Watch or Warning</div>
</li>
<li>
<div>Fire Ban Advice</div>
</li>
<li>
<div>Marine Wind Warning</div>
</li>
<li>
<div>Brown Rot Advice</div>
</li>
<li>
<div>Downy Mildew Advice</div>
</li>
<li>
<div>Tsunami Threat Watch or Warnin</div>
</li>
<li>
<div>Aviation Lightning Warning</div>
</li>
</ul>
</li>
<li>Fire Incidents for VIC and NSW</li>
<li>Fire Danger Ratings for VIC<br>
</li>
<li>Fire Alerts & Community Warnings for NSW
(VIC to come)</li>
<li>Marine warnings above only work for NSW,
VIC, TAS and WA. Nothing for QLD or NT as yet</li>
</ul>
<p><br>
</p>
<p>In terms of enhancements, I think we can
improve with:</p>
<ul style="margin-bottom:0px; margin-top:0px">
<li>Marine warnings for all states/territories</li>
<li>Fire incidents for all states/territories <span>(where
we can, agencies seem to have a mixture of
quality data...)</span></li>
<li>Fire Alerts & Community Warnings for all
states/territories (where we can, agencies
seem to have a mixture of quality data...)<br>
</li>
<li>Fire Danger Ratings for all
states/territories (as above with fire alerts
etc)</li>
<li>Ability to have WXBOT style functionality
for Australia (this would be cool for those on
the road, especially on HF APRS to get their
local weather observations & forecasts)</li>
<li>Once we have a working platform again, work
with our iGate operators to gate bulletins
& alerts onto the network where
appropriate. This would involve configuring
appropriate filters to pass through (is this
permitted however?)<br>
</li>
</ul>
<p><br>
</p>
<p>There are some challenges at the moment, the
website for WXSVR-AU is gone and Geoff is
tracking down what he can. One limit we have at
the moment is a copy of the shapefiles. If
anyone has these on record somewhere, please let
me know. I'd very much appreciate a starting
point to work with.</p>
<p><br>
</p>
<p>Cheers & 73s,</p>
<p><br>
</p>
<p>Matty</p>
<p>VK3MJM<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OZAPRS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>
<a class="moz-txt-link-freetext" href="http://lists.aprs.net.au/mailman/listinfo/ozaprs">http://lists.aprs.net.au/mailman/listinfo/ozaprs</a>
</pre>
</blockquote>
<br>
</body>
</html>