<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal>Folks,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Just looking at the changes recently made by BOM to their VK1/VK2/VK3
forecast and warning regions, there will be several significant changes
required on WXSVR-AU to support the changes.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The good (great) news is that BOM have finally provided a
public set of shapefiles for their forecast areas, AND are in the process of providing
XML based products, which makes it REALLY easy to generate the warnings (And we
no longer need to maintain our own ‘custom’ shapefiles)<o:p></o:p></p>
<p class=MsoNormal>However, since the BOM filename and zone formatting does not
align with the NWS formatting used in the U.S, it may finally be time to create
our own local UI-View client (rather than use UI-NWS), and investigate changes
required in Xastir to support the new data stream.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>For now, the existing warning data stream will continue,
although there may be some introduced errors given the changes to some forecast
region boundaries. We will be working in the background to convert the
VK1/2/3 warnings to use the new XML feeds (The framework for this already
exists for the VK2 RFS Fire warnings – Changing WXSVR itself will also
allow the remaining Fire warnings for other states to be completed). <o:p></o:p></p>
<p class=MsoNormal>Initially we’ll aim to allow the backwards compatibility
to the existing NWS clients, but no guarantee that it will happen – it may
just be easier to go forward rather than write protocol converters to take the
new BOM standards back to what we are working with now…..<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>These changes also won’t happen overnight, so please
be patient.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Stay tuned <span style='font-family:Wingdings'>J</span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Regards,<o:p></o:p></p>
<p class=MsoNormal>Geoff VK2XJG<o:p></o:p></p>
</div>
</body>
</html>