-
After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.
I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.
For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.
From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.
Sincerely, Jeff D.
Dispatcher Fired Over Tornado Siren Delay
- Thread starter Adam Reagan
- Start date
Rob H
EF5
You have to dig into the previous story that this was a follow up from before you find out the reason:
The SPC reports for 7/26 don't list anyone as being injured, but reports had 2x4s as missiles - so it must have been a decently powerful tornado. Glad to hear this error didn't result in anyone's harm.
The SPC reports for 7/26 don't list anyone as being injured, but reports had 2x4s as missiles - so it must have been a decently powerful tornado. Glad to hear this error didn't result in anyone's harm.
Mike Smith
They need WeatherData's SelectWarn® system. It prompts the dispatcher so he/she only needs to respond with one click of the mouse. For siren systems that allow individual sirens to be triggered, it sounds them only in the polygon and a locally selectable buffer around the polygon.
www.weatherdata.com/products/selectwarn.pdf
www.weatherdata.com/products/selectwarn.pdf
Think Sedgwick Co could use this system. One of these days a large tornado is going to come barreling through some part of town there and kill a bunch of people b/c people are so used to the damn sirens going off for a warning in any part of the county. And quite frankly I cant say I blame them for half ignoring the sirens with them being a countywide system and not broken off into sections.
*shakes head*
Adam Reagan
EF2
It was an EF1 tornado that touched down between North Nashville and Goodlettsville in the Belshire community from a renegade cell that quickly got it's act together.
You're right it is very fortunate no one got hurt I was watching live coverage of the storm on local TV and nothing was mentioned about sirens till after the second tornado warning was issued for Downtown Nashville.
Similar threads
