Re: [Xastir] NWS Info

2018-02-19 Thread Gerry Creager - NOAA Affiliate
Kevin

Hopefully we won't send too many your way this year, or if we do, they
won't affect you and your folks!

gerry n5jxs

On Sun, Feb 18, 2018 at 9:41 AM, Kj5fa  wrote:

> Hello Tom. The latest script worked great. Got the shapefile loade and
> changed settings Now waiting for some warnings to come into my area.
>
> 73s,
> Kevin KJ5FA
>
>
> ⁣Sent from Blue ​
>
> On Feb 16, 2018, 12:45 PM, at 12:45 PM, Tom Russo 
> wrote:
> >On Fri, Feb 16, 2018 at 08:53:24AM -0700, we recorded a bogon-computron
> >collision of the  flavor, containing:
> >> I did take a quick look at the new NWS site, and it looks like they
> >only
> >> rearranged things and moved the URL, and not like they actually broke
> >all the
> >> shapefiles.
> >>
> >> I think it may be an easy matter to update get-NWSdata again, because
> >it'll
> >> just be a matter of changing the fetch urls we use.
> >>
> >> Won't be able to do that until tonight.
> >
> >Make me a liar.  It was fairly straightforward, but there were some
> >newly
> >updated files, and surprisingly, a couple of files whose revision dates
> >had
> >not changed but whose DBF signatures *HAD* changed since Curt last
> >updated
> >this stuff.
> >
> >That complicated matters slightly, because it meant creating more
> >"backward
> >compatibility" dbfawks.  That is necessary so that folks are not
> >*forced* to
> >update NWS shapefiles by this commit if they already have a set that
> >works for
> >them.  If you like your NWS shapefiles, you can keep your NWS
> >shapefiles.
> >
> >Fix is in, tested, and pushed to git master. This won't help you much
> >if
> >you're working out of 2.1.0 tarballs (dang it), but if you're running
> >off of
> >master, a git pull and reinstall will do the trick.
> >
> >The fix is git commit  1f40ff1.  One could conceivably use a diff
> >created
> >from this commit to patch 2.1.0 if one wanted (package maintainers
> >might want
> >to do that).  I don't think I want to do a patch release just for this,
> >but
> >I supposed that would be possible.
> >
> >We apologize for the inconvenience.
> >
> >> While most of the files haven't changed since get-NWSdata was last
> >updated,
> >> a couple have, so I'll also have to check that the dbfawk files still
> >work
> >> with the new ones.
> >>
> >> That is, unless Curt is just dying to jump in and take this over, in
> >which
> >> case he should reassign the bug to himself:
> >>
> >> https://github.com/Xastir/Xastir/issues/26
> >>
> >> On Fri, Feb 16, 2018 at 08:34:11AM -0700, we recorded a
> >bogon-computron collision of the  flavor,
> >containing:
> >> > On Fri, Feb 16, 2018 at 06:22:59AM -0600, we recorded a
> >bogon-computron collision of the  flavor,
> >containing:
> >> > > Thanks Tom.
> >> > >
> >> > > This looks promising. I have ran the get-NWSdata script, but it
> >looked
> >> > > like it errored out not being able to find the files. I went to
> >the
> >> > > webpage where the permanent location was supposed to
> >> > > be(www.weather.gov/gis if my memory is good from last night) and
> >could
> >> > > not find a way to download a file?
> >> > >
> >> > > With these new instructions I will try again this evening.
> >> >
> >> > GROAN.  Yes, get-NWSdata is broken again.
> >> >
> >> > It looks like NWS has *completely* revamped their entire GIS
> >download site,
> >> > and the get-NWSdata script no longer works.  The links we used in
> >> > that script now return HTTP error pages instead of zip files.  This
> >has
> >> > happened sometime since Curt last updated the script, in September.
> >> >
> >> > I do not have time to look into this until at least tonight or
> >tomorrow.
> >> > Odds are good that even if I can hack the script up to obtain the
> >newest
> >> > files from NWS's reorganized site, they'll have changed the format
> >again
> >> > and Xastir will need additional adjustments.  This will take some
> >time.
> >> > Yay.
> >> >
> >> > I just happen to have run get-NWSdata between the time that Curt
> >updated it
> >> > last and the time NWS invalidated it, so I have all those
> >shapefiles on my
> >> > system.  I will try to zip them up and put them somewhere where
> >they can be
> >> > downloaded as a temporary workaround.  That way you can bypass
> >get-NWSdata
> >> > and use a set of (possibly slightly outdate) zip files that worked
> >at least
> >> > as recently as September.  I might not get to that until tonight.
> >When I do,
> >> > I'll post updated instructions for the temporary workaround.
> >> >
> >> > Thanks for calling this to my attention.  I very rarely update  my
> >own
> >> > NWS weather alert shapefiles, because the actual shapes in them for
> >my area
> >> > of the country pretty much never change --- I can usually get away
> >without
> >> > updating them for a few years at a stretch.  Luckily I had just
> >done it before
> >> > get-NWSdata became borken.
> >> >
> >> > > On 2/15/2018 11:34 PM, Tom Russo wrote:
> >> > > > On Thu, Feb 15, 2018 at 09:55:51PM -0700, we recorded a
> >bogon-c

Re: [Xastir] NWS Info

2018-02-18 Thread Kj5fa
Hello Tom. The latest script worked great. Got the shapefile loade and changed 
settings Now waiting for some warnings to come into my area.

73s,
Kevin KJ5FA


⁣Sent from Blue ​

On Feb 16, 2018, 12:45 PM, at 12:45 PM, Tom Russo  wrote:
>On Fri, Feb 16, 2018 at 08:53:24AM -0700, we recorded a bogon-computron
>collision of the  flavor, containing:
>> I did take a quick look at the new NWS site, and it looks like they
>only
>> rearranged things and moved the URL, and not like they actually broke
>all the
>> shapefiles.
>> 
>> I think it may be an easy matter to update get-NWSdata again, because
>it'll 
>> just be a matter of changing the fetch urls we use.
>> 
>> Won't be able to do that until tonight.
>
>Make me a liar.  It was fairly straightforward, but there were some
>newly
>updated files, and surprisingly, a couple of files whose revision dates
>had
>not changed but whose DBF signatures *HAD* changed since Curt last
>updated
>this stuff.  
>
>That complicated matters slightly, because it meant creating more
>"backward
>compatibility" dbfawks.  That is necessary so that folks are not
>*forced* to 
>update NWS shapefiles by this commit if they already have a set that
>works for 
>them.  If you like your NWS shapefiles, you can keep your NWS
>shapefiles.
>
>Fix is in, tested, and pushed to git master. This won't help you much
>if 
>you're working out of 2.1.0 tarballs (dang it), but if you're running
>off of 
>master, a git pull and reinstall will do the trick.
>
>The fix is git commit  1f40ff1.  One could conceivably use a diff
>created 
>from this commit to patch 2.1.0 if one wanted (package maintainers
>might want 
>to do that).  I don't think I want to do a patch release just for this,
>but
>I supposed that would be possible.
>
>We apologize for the inconvenience.
>
>> While most of the files haven't changed since get-NWSdata was last
>updated,
>> a couple have, so I'll also have to check that the dbfawk files still
>work
>> with the new ones.
>> 
>> That is, unless Curt is just dying to jump in and take this over, in
>which
>> case he should reassign the bug to himself:
>> 
>> https://github.com/Xastir/Xastir/issues/26
>> 
>> On Fri, Feb 16, 2018 at 08:34:11AM -0700, we recorded a
>bogon-computron collision of the  flavor,
>containing:
>> > On Fri, Feb 16, 2018 at 06:22:59AM -0600, we recorded a
>bogon-computron collision of the  flavor,
>containing:
>> > > Thanks Tom.
>> > > 
>> > > This looks promising. I have ran the get-NWSdata script, but it
>looked 
>> > > like it errored out not being able to find the files. I went to
>the 
>> > > webpage where the permanent location was supposed to 
>> > > be(www.weather.gov/gis if my memory is good from last night) and
>could 
>> > > not find a way to download a file?
>> > > 
>> > > With these new instructions I will try again this evening.
>> > 
>> > GROAN.  Yes, get-NWSdata is broken again.
>> > 
>> > It looks like NWS has *completely* revamped their entire GIS
>download site,
>> > and the get-NWSdata script no longer works.  The links we used in
>> > that script now return HTTP error pages instead of zip files.  This
>has 
>> > happened sometime since Curt last updated the script, in September.
>> > 
>> > I do not have time to look into this until at least tonight or
>tomorrow.
>> > Odds are good that even if I can hack the script up to obtain the
>newest 
>> > files from NWS's reorganized site, they'll have changed the format
>again 
>> > and Xastir will need additional adjustments.  This will take some
>time.
>> > Yay.  
>> > 
>> > I just happen to have run get-NWSdata between the time that Curt
>updated it
>> > last and the time NWS invalidated it, so I have all those
>shapefiles on my 
>> > system.  I will try to zip them up and put them somewhere where
>they can be
>> > downloaded as a temporary workaround.  That way you can bypass
>get-NWSdata 
>> > and use a set of (possibly slightly outdate) zip files that worked
>at least 
>> > as recently as September.  I might not get to that until tonight. 
>When I do,
>> > I'll post updated instructions for the temporary workaround.
>> > 
>> > Thanks for calling this to my attention.  I very rarely update  my
>own 
>> > NWS weather alert shapefiles, because the actual shapes in them for
>my area
>> > of the country pretty much never change --- I can usually get away
>without
>> > updating them for a few years at a stretch.  Luckily I had just
>done it before
>> > get-NWSdata became borken.
>> > 
>> > > On 2/15/2018 11:34 PM, Tom Russo wrote:
>> > > > On Thu, Feb 15, 2018 at 09:55:51PM -0700, we recorded a
>bogon-computron collision of the  flavor,
>containing:
>> > > >> On Thu, Feb 15, 2018 at 09:31:22PM -0600, we recorded a
>bogon-computron collision of the  flavor,
>containing:
>> > > >>> Can someone point me to the instructions of how to get NWS
>warnings to
>> > > >>> show up on my map in Xastir?
>> > > >> Looks like there is no one spot where all the instructions are
>clearly laid
>> > > >> out.  Rather

Re: [Xastir] NWS Info

2018-02-16 Thread Tom Russo
On Fri, Feb 16, 2018 at 08:53:24AM -0700, we recorded a bogon-computron 
collision of the  flavor, containing:
> I did take a quick look at the new NWS site, and it looks like they only
> rearranged things and moved the URL, and not like they actually broke all the
> shapefiles.
> 
> I think it may be an easy matter to update get-NWSdata again, because it'll 
> just be a matter of changing the fetch urls we use.
> 
> Won't be able to do that until tonight.

Make me a liar.  It was fairly straightforward, but there were some newly
updated files, and surprisingly, a couple of files whose revision dates had
not changed but whose DBF signatures *HAD* changed since Curt last updated
this stuff.  

That complicated matters slightly, because it meant creating more "backward
compatibility" dbfawks.  That is necessary so that folks are not *forced* to 
update NWS shapefiles by this commit if they already have a set that works for 
them.  If you like your NWS shapefiles, you can keep your NWS shapefiles.

Fix is in, tested, and pushed to git master. This won't help you much if 
you're working out of 2.1.0 tarballs (dang it), but if you're running off of 
master, a git pull and reinstall will do the trick.

The fix is git commit  1f40ff1.  One could conceivably use a diff created 
from this commit to patch 2.1.0 if one wanted (package maintainers might want 
to do that).  I don't think I want to do a patch release just for this, but
I supposed that would be possible.

We apologize for the inconvenience.

> While most of the files haven't changed since get-NWSdata was last updated,
> a couple have, so I'll also have to check that the dbfawk files still work
> with the new ones.
> 
> That is, unless Curt is just dying to jump in and take this over, in which
> case he should reassign the bug to himself:
> 
> https://github.com/Xastir/Xastir/issues/26
> 
> On Fri, Feb 16, 2018 at 08:34:11AM -0700, we recorded a bogon-computron 
> collision of the  flavor, containing:
> > On Fri, Feb 16, 2018 at 06:22:59AM -0600, we recorded a bogon-computron 
> > collision of the  flavor, containing:
> > > Thanks Tom.
> > > 
> > > This looks promising. I have ran the get-NWSdata script, but it looked 
> > > like it errored out not being able to find the files. I went to the 
> > > webpage where the permanent location was supposed to 
> > > be(www.weather.gov/gis if my memory is good from last night) and could 
> > > not find a way to download a file?
> > > 
> > > With these new instructions I will try again this evening.
> > 
> > GROAN.  Yes, get-NWSdata is broken again.
> > 
> > It looks like NWS has *completely* revamped their entire GIS download site,
> > and the get-NWSdata script no longer works.  The links we used in
> > that script now return HTTP error pages instead of zip files.  This has 
> > happened sometime since Curt last updated the script, in September.
> > 
> > I do not have time to look into this until at least tonight or tomorrow.
> > Odds are good that even if I can hack the script up to obtain the newest 
> > files from NWS's reorganized site, they'll have changed the format again 
> > and Xastir will need additional adjustments.  This will take some time.
> > Yay.  
> > 
> > I just happen to have run get-NWSdata between the time that Curt updated it
> > last and the time NWS invalidated it, so I have all those shapefiles on my 
> > system.  I will try to zip them up and put them somewhere where they can be
> > downloaded as a temporary workaround.  That way you can bypass get-NWSdata 
> > and use a set of (possibly slightly outdate) zip files that worked at least 
> > as recently as September.  I might not get to that until tonight.  When I 
> > do,
> > I'll post updated instructions for the temporary workaround.
> > 
> > Thanks for calling this to my attention.  I very rarely update  my own 
> > NWS weather alert shapefiles, because the actual shapes in them for my area
> > of the country pretty much never change --- I can usually get away without
> > updating them for a few years at a stretch.  Luckily I had just done it 
> > before
> > get-NWSdata became borken.
> > 
> > > On 2/15/2018 11:34 PM, Tom Russo wrote:
> > > > On Thu, Feb 15, 2018 at 09:55:51PM -0700, we recorded a bogon-computron 
> > > > collision of the  flavor, containing:
> > > >> On Thu, Feb 15, 2018 at 09:31:22PM -0600, we recorded a 
> > > >> bogon-computron collision of the  flavor, 
> > > >> containing:
> > > >>> Can someone point me to the instructions of how to get NWS warnings to
> > > >>> show up on my map in Xastir?
> > > >> Looks like there is no one spot where all the instructions are clearly 
> > > >> laid
> > > >> out.  Rather, it is scattered about in README.Getting-Started and other
> > > >> places.  Even the Wiki doesn't have it clearly stated in a single 
> > > >> spot.  This
> > > >> is unfortunate and should be fixed.
> > > > I have tried.  There is a new "HowTo:Weather Alerts" page on the wiki, 
> > > > linked
> > > > to from t

Re: [Xastir] NWS Info

2018-02-16 Thread Gerry Creager - NOAA Affiliate
So, for NWS warnings, there are a couple of ways to get them. Tom's
identified th most "normal" web-scraping method.

Another method is to use a system from UCAR/Unidata, called LDM, to receive
the weather warnings and parsethe header for the VTEC info, which
identifies the type of warning, and the polygon vertices. Building a
shapefile from that is pretty straightforward, especially if you store the
polygon info in a PostGIS database then drag it out with a shapefile
query...

Let me see if I can approximate some of the LDM functionality in Python (or
find someone who's done that legwork already!) over the next 2 weeks. It
should be do-able. I'll also have to identify a source who'll work with us
to provide the LDM data, as my old haunt, Texas A&M, and all the
infrastructure I set up to support this stuff, is getting out of that line
of work. Seems the current management, now that I've left, could see no
benefit to generating good will  for TAMU, among all the users who received
LDM data from them.

gerry

On Fri, Feb 16, 2018 at 10:37 AM, Tom Russo  wrote:

> On Fri, Feb 16, 2018 at 08:25:55AM -0800, we recorded a bogon-computron
> collision of the  flavor, containing:
> > On Fri, 16 Feb 2018, Tom Russo wrote:
> >
> > > That is, unless Curt is just dying to jump in and take this over, in
> which
> > > case he should reassign the bug to himself:
> >
> > You're funny.
>
> A regular riot.
>
> > I'm in final preparations for a multi-hour in-the-field test of my H/W
> units tomorrow. No time!
>
> GL with that trial run.  Lemme know how it pans out.
>
> In the meantime, I'll try to attack this NWS issue tonight.  I don't think
> it's as big a deal as it appeared at first, just some changed URLs.  At
> worst maybe a new dbfawk file to go with it.
>
> --
> Tom RussoKM5VY
> Tijeras, NM
>
>  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> [n-z][a-m]
>
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
>



-- 
Gerry Creager
NSSL/CIMMS
405.325.6371
++
“Big whorls have little whorls,
That feed on their velocity;
And little whorls have lesser whorls,
And so on to viscosity.”
Lewis Fry Richardson (1881-1953)
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir


Re: [Xastir] NWS Info

2018-02-16 Thread Tom Russo
On Fri, Feb 16, 2018 at 08:25:55AM -0800, we recorded a bogon-computron 
collision of the  flavor, containing:
> On Fri, 16 Feb 2018, Tom Russo wrote:
> 
> > That is, unless Curt is just dying to jump in and take this over, in which
> > case he should reassign the bug to himself:
> 
> You're funny. 

A regular riot.

> I'm in final preparations for a multi-hour in-the-field test of my H/W units 
> tomorrow. No time!

GL with that trial run.  Lemme know how it pans out.

In the meantime, I'll try to attack this NWS issue tonight.  I don't think
it's as big a deal as it appeared at first, just some changed URLs.  At
worst maybe a new dbfawk file to go with it.

-- 
Tom RussoKM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir


Re: [Xastir] NWS Info

2018-02-16 Thread Curt, WE7U

On Fri, 16 Feb 2018, Tom Russo wrote:


That is, unless Curt is just dying to jump in and take this over, in which
case he should reassign the bug to himself:


You're funny. I'm in final preparations for a multi-hour in-the-field test of 
my H/W units tomorrow. No time!

--
Curt, WE7U.http://we7u.wetnet.net
U.S. Weather Alerts:  Firenet.aprs2.net, port 14580, filter "t/n e/WE7U-WX"
Coordinate Converter (Android): http://www.sarguydigital.com
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir


Re: [Xastir] NWS Info

2018-02-16 Thread Tom Russo
I did take a quick look at the new NWS site, and it looks like they only
rearranged things and moved the URL, and not like they actually broke all the
shapefiles.

I think it may be an easy matter to update get-NWSdata again, because it'll 
just be a matter of changing the fetch urls we use.

Won't be able to do that until tonight.

While most of the files haven't changed since get-NWSdata was last updated,
a couple have, so I'll also have to check that the dbfawk files still work
with the new ones.

That is, unless Curt is just dying to jump in and take this over, in which
case he should reassign the bug to himself:

https://github.com/Xastir/Xastir/issues/26

On Fri, Feb 16, 2018 at 08:34:11AM -0700, we recorded a bogon-computron 
collision of the  flavor, containing:
> On Fri, Feb 16, 2018 at 06:22:59AM -0600, we recorded a bogon-computron 
> collision of the  flavor, containing:
> > Thanks Tom.
> > 
> > This looks promising. I have ran the get-NWSdata script, but it looked 
> > like it errored out not being able to find the files. I went to the 
> > webpage where the permanent location was supposed to 
> > be(www.weather.gov/gis if my memory is good from last night) and could 
> > not find a way to download a file?
> > 
> > With these new instructions I will try again this evening.
> 
> GROAN.  Yes, get-NWSdata is broken again.
> 
> It looks like NWS has *completely* revamped their entire GIS download site,
> and the get-NWSdata script no longer works.  The links we used in
> that script now return HTTP error pages instead of zip files.  This has 
> happened sometime since Curt last updated the script, in September.
> 
> I do not have time to look into this until at least tonight or tomorrow.
> Odds are good that even if I can hack the script up to obtain the newest 
> files from NWS's reorganized site, they'll have changed the format again 
> and Xastir will need additional adjustments.  This will take some time.
> Yay.  
> 
> I just happen to have run get-NWSdata between the time that Curt updated it
> last and the time NWS invalidated it, so I have all those shapefiles on my 
> system.  I will try to zip them up and put them somewhere where they can be
> downloaded as a temporary workaround.  That way you can bypass get-NWSdata 
> and use a set of (possibly slightly outdate) zip files that worked at least 
> as recently as September.  I might not get to that until tonight.  When I do,
> I'll post updated instructions for the temporary workaround.
> 
> Thanks for calling this to my attention.  I very rarely update  my own 
> NWS weather alert shapefiles, because the actual shapes in them for my area
> of the country pretty much never change --- I can usually get away without
> updating them for a few years at a stretch.  Luckily I had just done it before
> get-NWSdata became borken.
> 
> > On 2/15/2018 11:34 PM, Tom Russo wrote:
> > > On Thu, Feb 15, 2018 at 09:55:51PM -0700, we recorded a bogon-computron 
> > > collision of the  flavor, containing:
> > >> On Thu, Feb 15, 2018 at 09:31:22PM -0600, we recorded a bogon-computron 
> > >> collision of the  flavor, containing:
> > >>> Can someone point me to the instructions of how to get NWS warnings to
> > >>> show up on my map in Xastir?
> > >> Looks like there is no one spot where all the instructions are clearly 
> > >> laid
> > >> out.  Rather, it is scattered about in README.Getting-Started and other
> > >> places.  Even the Wiki doesn't have it clearly stated in a single spot.  
> > >> This
> > >> is unfortunate and should be fixed.
> > > I have tried.  There is a new "HowTo:Weather Alerts" page on the wiki, 
> > > linked
> > > to from the main HowTo page.
> > >
> > > Please let me know if this is not enough to get you going.
> > >
> > >> So here goes:
> > >>
> > >>- You must have NWS shapefiles downloaded and installed in your
> > >>  maps directory.  Get them using the script "get-NWSdata" included 
> > >> in the
> > >>  Xastir scripts directory.  That's /usr/local/share/xastir/scripts 
> > >> if you
> > >>  installed from source.  Leave out the "local" if you've gotten via a
> > >>  binary package.
> > >>
> > >>  This script must be run as root (or better yet, with sudo).
> > >>
> > >>  NWS changes the format of their shapefiles often, and this requires 
> > >> us to
> > >>  chase their file format a lot.  If you're not running a recent 
> > >> version of
> > >>  Xastir, you might have trouble getting suitable shapefiles from 
> > >> NWS.  This
> > >>  one script is the single most frequently updated file in Xastir.
> > >>
> > >>  The script in Xastir 2.1.0 or git master was updated recently 
> > >> enough that
> > >>  it should work and get you the right files.
> > >>
> > >>- Then, after you've downloaded the NWS shapefiles, you must get them 
> > >> indexed.
> > >>  A restart of Xastir will do it, but you could also use the menu 
> > >> entry
> > >>  "Map->Configure->Index: Add new m

Re: [Xastir] NWS Info

2018-02-16 Thread Tom Russo
On Fri, Feb 16, 2018 at 06:22:59AM -0600, we recorded a bogon-computron 
collision of the  flavor, containing:
> Thanks Tom.
> 
> This looks promising. I have ran the get-NWSdata script, but it looked 
> like it errored out not being able to find the files. I went to the 
> webpage where the permanent location was supposed to 
> be(www.weather.gov/gis if my memory is good from last night) and could 
> not find a way to download a file?
> 
> With these new instructions I will try again this evening.

GROAN.  Yes, get-NWSdata is broken again.

It looks like NWS has *completely* revamped their entire GIS download site,
and the get-NWSdata script no longer works.  The links we used in
that script now return HTTP error pages instead of zip files.  This has 
happened sometime since Curt last updated the script, in September.

I do not have time to look into this until at least tonight or tomorrow.
Odds are good that even if I can hack the script up to obtain the newest 
files from NWS's reorganized site, they'll have changed the format again 
and Xastir will need additional adjustments.  This will take some time.
Yay.  

I just happen to have run get-NWSdata between the time that Curt updated it
last and the time NWS invalidated it, so I have all those shapefiles on my 
system.  I will try to zip them up and put them somewhere where they can be
downloaded as a temporary workaround.  That way you can bypass get-NWSdata 
and use a set of (possibly slightly outdate) zip files that worked at least 
as recently as September.  I might not get to that until tonight.  When I do,
I'll post updated instructions for the temporary workaround.

Thanks for calling this to my attention.  I very rarely update  my own 
NWS weather alert shapefiles, because the actual shapes in them for my area
of the country pretty much never change --- I can usually get away without
updating them for a few years at a stretch.  Luckily I had just done it before
get-NWSdata became borken.

> On 2/15/2018 11:34 PM, Tom Russo wrote:
> > On Thu, Feb 15, 2018 at 09:55:51PM -0700, we recorded a bogon-computron 
> > collision of the  flavor, containing:
> >> On Thu, Feb 15, 2018 at 09:31:22PM -0600, we recorded a bogon-computron 
> >> collision of the  flavor, containing:
> >>> Can someone point me to the instructions of how to get NWS warnings to
> >>> show up on my map in Xastir?
> >> Looks like there is no one spot where all the instructions are clearly laid
> >> out.  Rather, it is scattered about in README.Getting-Started and other
> >> places.  Even the Wiki doesn't have it clearly stated in a single spot.  
> >> This
> >> is unfortunate and should be fixed.
> > I have tried.  There is a new "HowTo:Weather Alerts" page on the wiki, 
> > linked
> > to from the main HowTo page.
> >
> > Please let me know if this is not enough to get you going.
> >
> >> So here goes:
> >>
> >>- You must have NWS shapefiles downloaded and installed in your
> >>  maps directory.  Get them using the script "get-NWSdata" included in 
> >> the
> >>  Xastir scripts directory.  That's /usr/local/share/xastir/scripts if 
> >> you
> >>  installed from source.  Leave out the "local" if you've gotten via a
> >>  binary package.
> >>
> >>  This script must be run as root (or better yet, with sudo).
> >>
> >>  NWS changes the format of their shapefiles often, and this requires 
> >> us to
> >>  chase their file format a lot.  If you're not running a recent 
> >> version of
> >>  Xastir, you might have trouble getting suitable shapefiles from NWS.  
> >> This
> >>  one script is the single most frequently updated file in Xastir.
> >>
> >>  The script in Xastir 2.1.0 or git master was updated recently enough 
> >> that
> >>  it should work and get you the right files.
> >>
> >>- Then, after you've downloaded the NWS shapefiles, you must get them 
> >> indexed.
> >>  A restart of Xastir will do it, but you could also use the menu entry
> >>  "Map->Configure->Index: Add new maps"
> >>  
> >>- You must be connected to an on-line APRS-IS source that sends weather
> >>  alerts.  Only those of a particularly high level of urgency are sent
> >>  on the normal rotate.aprs.net or rotate.aprs2.net servers.
> >>  Firenet.aprs2.net will have the lower level alerts (advisories and
> >>  watches, not just warnings).
> >>
> >>- You must enable display of weather alerts in the map menu and NOT 
> >> select
> >>  "Disable all maps"!
> >>
> >> That should be it.
> >>
> >> -- 
> >> Tom RussoKM5VY
> >> Tijeras, NM
> >>
> >>   echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] 
> >> [n-z][a-m]
> >>
> >> ___
> >> Xastir mailing list
> >> Xastir@lists.xastir.org
> >> http://xastir.org/mailman/listinfo/xastir
> 
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] NWS Info

2018-02-16 Thread KJ5FA

Thanks Tom.

This looks promising. I have ran the get-NWSdata script, but it looked 
like it errored out not being able to find the files. I went to the 
webpage where the permanent location was supposed to 
be(www.weather.gov/gis if my memory is good from last night) and could 
not find a way to download a file?


With these new instructions I will try again this evening.

73s,

Kevin KJ5FA


On 2/15/2018 11:34 PM, Tom Russo wrote:

On Thu, Feb 15, 2018 at 09:55:51PM -0700, we recorded a bogon-computron collision of 
the  flavor, containing:

On Thu, Feb 15, 2018 at 09:31:22PM -0600, we recorded a bogon-computron collision of 
the  flavor, containing:

Can someone point me to the instructions of how to get NWS warnings to
show up on my map in Xastir?

Looks like there is no one spot where all the instructions are clearly laid
out.  Rather, it is scattered about in README.Getting-Started and other
places.  Even the Wiki doesn't have it clearly stated in a single spot.  This
is unfortunate and should be fixed.

I have tried.  There is a new "HowTo:Weather Alerts" page on the wiki, linked
to from the main HowTo page.

Please let me know if this is not enough to get you going.


So here goes:

   - You must have NWS shapefiles downloaded and installed in your
 maps directory.  Get them using the script "get-NWSdata" included in the
 Xastir scripts directory.  That's /usr/local/share/xastir/scripts if you
 installed from source.  Leave out the "local" if you've gotten via a
 binary package.

 This script must be run as root (or better yet, with sudo).

 NWS changes the format of their shapefiles often, and this requires us to
 chase their file format a lot.  If you're not running a recent version of
 Xastir, you might have trouble getting suitable shapefiles from NWS.  This
 one script is the single most frequently updated file in Xastir.

 The script in Xastir 2.1.0 or git master was updated recently enough that
 it should work and get you the right files.

   - Then, after you've downloaded the NWS shapefiles, you must get them 
indexed.
 A restart of Xastir will do it, but you could also use the menu entry
 "Map->Configure->Index: Add new maps"
 
   - You must be connected to an on-line APRS-IS source that sends weather

 alerts.  Only those of a particularly high level of urgency are sent
 on the normal rotate.aprs.net or rotate.aprs2.net servers.
 Firenet.aprs2.net will have the lower level alerts (advisories and
 watches, not just warnings).

   - You must enable display of weather alerts in the map menu and NOT select
 "Disable all maps"!

That should be it.

--
Tom RussoKM5VY
Tijeras, NM

  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir


___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir


Re: [Xastir] NWS Info

2018-02-15 Thread Tom Russo
On Thu, Feb 15, 2018 at 09:55:51PM -0700, we recorded a bogon-computron 
collision of the  flavor, containing:
> On Thu, Feb 15, 2018 at 09:31:22PM -0600, we recorded a bogon-computron 
> collision of the  flavor, containing:
> > Can someone point me to the instructions of how to get NWS warnings to 
> > show up on my map in Xastir?
> 
> Looks like there is no one spot where all the instructions are clearly laid
> out.  Rather, it is scattered about in README.Getting-Started and other 
> places.  Even the Wiki doesn't have it clearly stated in a single spot.  This
> is unfortunate and should be fixed.

I have tried.  There is a new "HowTo:Weather Alerts" page on the wiki, linked
to from the main HowTo page.

Please let me know if this is not enough to get you going.

> So here goes:
> 
>   - You must have NWS shapefiles downloaded and installed in your 
> maps directory.  Get them using the script "get-NWSdata" included in the 
> Xastir scripts directory.  That's /usr/local/share/xastir/scripts if you 
> installed from source.  Leave out the "local" if you've gotten via a 
> binary package.  
> 
> This script must be run as root (or better yet, with sudo).  
> 
> NWS changes the format of their shapefiles often, and this requires us to 
> chase their file format a lot.  If you're not running a recent version of 
> Xastir, you might have trouble getting suitable shapefiles from NWS.  
> This 
> one script is the single most frequently updated file in Xastir.
> 
> The script in Xastir 2.1.0 or git master was updated recently enough that 
> it should work and get you the right files.  
> 
>   - Then, after you've downloaded the NWS shapefiles, you must get them 
> indexed.
> A restart of Xastir will do it, but you could also use the menu entry
> "Map->Configure->Index: Add new maps"
> 
>   - You must be connected to an on-line APRS-IS source that sends weather
> alerts.  Only those of a particularly high level of urgency are sent
> on the normal rotate.aprs.net or rotate.aprs2.net servers.  
> Firenet.aprs2.net will have the lower level alerts (advisories and
> watches, not just warnings).
> 
>   - You must enable display of weather alerts in the map menu and NOT select
> "Disable all maps"!
> 
> That should be it.
> 
> -- 
> Tom RussoKM5VY
> Tijeras, NM  
> 
>  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]
> 
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir

-- 
Tom RussoKM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir


Re: [Xastir] NWS Info

2018-02-15 Thread Tom Russo
On Thu, Feb 15, 2018 at 09:31:22PM -0600, we recorded a bogon-computron 
collision of the  flavor, containing:
> Can someone point me to the instructions of how to get NWS warnings to 
> show up on my map in Xastir?

Looks like there is no one spot where all the instructions are clearly laid
out.  Rather, it is scattered about in README.Getting-Started and other 
places.  Even the Wiki doesn't have it clearly stated in a single spot.  This
is unfortunate and should be fixed.

So here goes:

  - You must have NWS shapefiles downloaded and installed in your 
maps directory.  Get them using the script "get-NWSdata" included in the 
Xastir scripts directory.  That's /usr/local/share/xastir/scripts if you 
installed from source.  Leave out the "local" if you've gotten via a 
binary package.  

This script must be run as root (or better yet, with sudo).  

NWS changes the format of their shapefiles often, and this requires us to 
chase their file format a lot.  If you're not running a recent version of 
Xastir, you might have trouble getting suitable shapefiles from NWS.  This 
one script is the single most frequently updated file in Xastir.

The script in Xastir 2.1.0 or git master was updated recently enough that 
it should work and get you the right files.  

  - Then, after you've downloaded the NWS shapefiles, you must get them indexed.
A restart of Xastir will do it, but you could also use the menu entry
"Map->Configure->Index: Add new maps"

  - You must be connected to an on-line APRS-IS source that sends weather
alerts.  Only those of a particularly high level of urgency are sent
on the normal rotate.aprs.net or rotate.aprs2.net servers.  
Firenet.aprs2.net will have the lower level alerts (advisories and
watches, not just warnings).

  - You must enable display of weather alerts in the map menu and NOT select
"Disable all maps"!

That should be it.

-- 
Tom RussoKM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir