SN Spotter Network: APRS—>SN Unstable Again

7/4 12:00 PM - and I see no (not just those from APRS - all) spotter network tags anywhere. Even in Radar Scope the list is not populated.
 
AllisonHouse has a place file for APRS tracking. Why not look at that and incorporate that into the SN place file?

Oh by the way, it’s 7/8/2016 8:38am and APRS locations are still not showing up.
 
With cellular networks working as well as they do nowadays, is there really a reason to use APRS to update your SN icon anymore? I'm just curious what the reasoning is behind it in 2019. The only thing you can do with it is update a position, with multiple hops that hopefully get to the internet.
 
With cellular networks working as well as they do nowadays, is there really a reason to use APRS to update your SN icon anymore? I'm just curious what the reasoning is behind it in 2019. The only thing you can do with it is update a position, with multiple hops that hopefully get to the internet.

A lot of us HAMs still use APRS when out in the field because

a) not everyone has the ability to bring a laptop in the vehicle.
b) not everyone has RadarScope on their mobile device, or the ability to have it open the entire time to plot location.
c) it is still a viable means of communication when cellular networks get overloaded (which they do) during times of severe weather and communication is critical.
 
That goes back to my point, though. How is updating a position on SN a worthy cause when you are unable to report by those means to the SN? They have other apps than radarscope to update position with SN as well, and they allow reporting. Just curious as to what benefit it is besides the 'look at me im on a map'?
 
Ben, I don't know you and you don't know me, so it is easy for us to misunderstand what each is saying.
I think many people would agree with me that your reply appears to be "chaser" concentric. I understand why that might be. I agree that most "chasers" have other methods of reporting their position and using Spotter Network to make reports. I am not sure the same can be said for those "spotters" that are staying in their home area and making reports to their local net via amateur radio.

I know several of our counties where the net control is using an APRS Client to keep track of their spotters. At the NWS where I volunteer at the amateur radio desk, we do not normally look at an APRS Client. There are just too many other windows we are concentrating on. Also, we may be working with spotter groups in many counties at the same time. It is not uncommon to have multiple instances of GR running looking at different parts of the CWA and using different radar sites. For us, that is why we like the Spotter Network interface to the GR radar display. There is a amateur radio operator in one of our counties that has written his own interface to the APRS-IS and builds a dynamic GR placefile for the APRS locations of their spotters. You know, kind of like what was developed for the Spotter Network/APRS interface. It is still working, by the way.

We rarely receive amateur radio reports from the Chaser community and I have ideas why that might be - not all of them are flattering so I won't go into my perceptions.

One has to wonder, with all the bad reports in Spotter Network, how much the trust in the SN community has been eroded? It seems daily there are multiple bad reports on SN - 1/4 inch hail, minor flooding, heavy rain, bad drivers, "high wind", etc. Sadly, the same is true in NWSCHAT and over amateur radio networks. Just now, I saw a report in NWSCHAT of "heavy rain and cloud to ground lightning".

I think your Look at Me reference is more for the "wanna be chasers" They are some that would probably never make a report to a local NWS anyway.

It was not my intention to belittle anyone or make anyone mad, just to present another point of view.
 
So I still don't understand what the problem is. If you've got the APRS placefile, then use that. There's obviously a problem with the interface of APRS to SN, whether it be a feed or whatever. You're still not using your APRS function on the radios to place a report, you're using voice (VHF or UHF) or other means to do so. It's just showing up on a map on spotternetwork.org too.

And why would you want to receive reports from the chaser community? Why have to manually voice out a report to someone who doesn't know you from adam that may or may not pass it along to perhaps another liaison net or over nwschat when we can just send a lat/long through SN on our smartphones or computers? I still listen here in Oklahoma. I'd report via radio if my other means were restricted.

The bad reports are a problem, but every method of taking data from the general public is prone to the same problems. The difference with SN is that people QC the reports (like me - I've reviewed 100s of reports this year) and the bad ones are followed up upon. We're also working on better training. I believe there will be more about that in the coming future. Must be the heavy rain and cloud to ground lightning report was taken care of, because I don't even see it in our reports at this point.

But trust me, I am not ignorant of the duties and mission of running a local net. I've been in all positions from spotting to chasing to running net control to doing radar updates to running a large training session of 150-200+ spotters. I still fail to see how it's critical to have that link to SN from aprs at this point. Seems like there are bigger fish to fry, judging by your gripes with SN just in your post.
 
As someone who is both a spotter in the FWD CWA and an active chaser who goes all over the place, I will share my thought's on this. First, I wiil note that you would be hard pressed to find a WFO that has ham radio as integrated into operations as FWD. The WX5FWD team volunteers hundreds of hours each year at the office, are well trained, and they sit across a short cubicle wall from the forecasters. There also is very good APRS coverage in the FWD area, especially in the northern 2/3rd's and center of the southern CWA. Putting on my chaser hat, I will note that outside of the FWD CWA and major cities, APRS digi access is lacking. I can chase in NW TX or large parts of OK for hours and not get any APRS packets digipeared or igated. It can also be very hard to find a frequency with an active Skywarn net (even after @ScottCurry and I created hamchaser.org to help with that). Having said that, it would be nice if the aprs -> sn interface worked again, because it is clearly used by at least FWD. I have been called out by net controllers in 2 counties in the FWD CWA because they saw my APRS becon and they wanted reports from the area I was in. I also understand that SN is ran by volunteers, and user support and other issues keep the team busy.
 
So I still don't understand what the problem is. If you've got the APRS placefile, then use that. There's obviously a problem with the interface of APRS to SN, whether it be a feed or whatever.

We'd love to use the spotternetwork.org APRS placefile... if it worked as it was intended, which included capturing those APRS positions that have !SN! located within the comment section of their APRS beacon.
 
Back
Top