• 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.

eSpotter Phased Out?

Snowfall and rainfall are already covered through CoCoRAHS already though, so why would eSpotter's removal change that?

eSpotter is only for general public reports really, given the tools available for trained spotters.
 
Snowfall and rainfall are already covered through CoCoRAHS already though, so why would eSpotter's removal change that?

I can't be the only one making such reports through the eSpotter interface?

Why will it change anything? Because I'm not setting up a CoCoRAHS station; http://www.cocorahs.org/Application.aspx

As I said, I'll just stop making reports.
 
I can't be the only one making such reports through the eSpotter interface?

I don't know a number, it just seems strange that spotters would use that method with all the others out there.

Because I'm not setting up a CoCoRAHS station

Gotcha, I thought you were using an official rain gauge. I find that the automated weather stations are not very accurate at rain counts, which is why CoCoRAHS doesn't allow you to use those.

http://www.cocorahs.org/Content.aspx?page=faqgeneral#autogauges
 
I don't know a number, it just seems strange that spotters would use that method with all the others out there.

What other online methods?

Gotcha, I thought you were using an official rain gauge.

You are right, I do not have an official CoCoRAHS rain gauge. Also, I don't take daily measurements as required... If something is noteworthy, I'll punch it into eSpotter and be done with it.

Again, not that big of a deal. If there are many CoCoRAHS stations out there, then one missing report isn't going to hurt anything ;)
 
I was always under the impression that SN was for severe weather reports (wind > 58mph, hail > 1 inch, etc), but I do see other types of reports accepted... and generally what I report anyway (flooding rains, snow >4 inches, winds > 50mph, etc). I have also tried registering for NWSChat and was declined.

Maybe I'm misunderstanding, but this is what's on the CoCoRAHS site:

It is important to the CoCoRaHS that your rain gauge is read and emptied at the same time each day.

I guess SN is a good option.
 
Right - they are saying that don't report 5am today and then 10am tomorrow and then 1pm the next. Keep it at 24 hours if possible, but no requirement to be online 365/year.
 
I think the real issue here is that SN isn't NWS endorsed - which leaves the official lines of communication somewhat unclear for low end events (including p-type changes, which while not emergency events, are time sensitive). As mentioned, CoCoRaHS isn't practical for all of us - I don't even have a place I could set up a station if I wanted to. NWSChat has always given me the impression that it was meant for some of the rather "elite" users - TV meteorologists, EMAs, and some of the most well known chasers.

This is a bit off-topic, but is there any way to know whether a SN report has actually been sent and accepted by the NWS office? From what I know, not all of them even use it.
 
NWSChat has always given me the impression that it was meant for some of the rather "elite" users - TV meteorologists, EMAs, and some of the most well known chasers.

This is a bit off-topic, but is there any way to know whether a SN report has actually been sent and accepted by the NWS office? From what I know, not all of them even use it.

It is my understanding that NWSChat is for NWS offices to communicate. It is up to the office to decide which non-NWS personnel can access it, and that is because, like many chat facilities, the more concurrent users there are, the more out of control things can get. So, the offices determine who their most trusted sources are and allow access to them. However, as I said earlier, if I make a report on SpotterNetwork, it will show up on NWSChat ... specifically, it appears in the ongoing chat room for the office for the CWA of the report. So, assuming the office is using NWSChat and are watching it during an event, they will get your report.

As far as ANY report being "accepted" by the office, that is really sort of nebulous. I believe they log all reports (at least, the local office around here does), but, typically, not all reports are included in a LSR or PNS especially if there are many reports for the same event. If they decide a report is bogus, it also will not make it to a product, but, absence from a product does not mean they discounted the report.
 
It is my understanding that NWSChat is for NWS offices to communicate. It is up to the office to decide which non-NWS personnel can access it, and that is because, like many chat facilities, the more concurrent users there are, the more out of control things can get. So, the offices determine who their most trusted sources are and allow access to them. However, as I said earlier, if I make a report on SpotterNetwork, it will show up on NWSChat ... specifically, it appears in the ongoing chat room for the office for the CWA of the report. So, assuming the office is using NWSChat and are watching it during an event, they will get your report.

As far as ANY report being "accepted" by the office, that is really sort of nebulous. I believe they log all reports (at least, the local office around here does), but, typically, not all reports are included in a LSR or PNS especially if there are many reports for the same event. If they decide a report is bogus, it also will not make it to a product, but, absence from a product does not mean they discounted the report.

That's what I was hoping to hear - if there were still a thanks feature I'd provide one. :D
 
It is my understanding that NWSChat is for NWS offices to communicate. It is up to the office to decide which non-NWS personnel can access it, and that is because, like many chat facilities, the more concurrent users there are, the more out of control things can get.

Actually no... NWS offices don't use it as their primary means of communications at all. They CAN, but that's not what it is for. It is to communicate to and from EM, media mets, spotter networks (NCS) and Federal entities (DNR, Coast Guard, etc.) http://nwschat.weather.gov

If you fit those criteria, you get in the system.
 
I have made several inquiries on rdale's supposed "inside knowledge" and so far, none of this seems to have one iota of truth to it. There doesn't seem to be any plan in place to eliminate eSpotter, and I'm not sure why there would. eSpotter is just one of several ways we receive reports of all kinds during inclement weather (internal NWSChat, SpotterNetwork, telephone, amateur radio, facebook, twitter, etc...).

Evan
 
At the moment...I will only add that I have inquired at NWS HQ right here in Silver Spring....and the basic thing I get in all this is that there is absolutely no one working, knowledgeable, concerned with or working/interested in doing anything regarding eSpotter (phase out or in) or any other national standard. What I always understood was the eSpotter was once implemented but now essentially abandoned "in-place". Kinda like various other commercial software (ie. netscape). This extend to such things as any sort of national effort to standardize Skywarn materials and/or education, policies, protocals, etc. Essentially with budget cuts and other priorities there is just little focus on any of this. Each NWS itself is basically has near free reign to do as it pleases according to the MIC. Whenever someone talks about national coordination, I ask about a name or division to contact to get more information to confirm the information and I never-ever get a response....just a "I was told....." or "Discussed at the _______________ conference".
 
Here is a list of WFO's that the NWS says utilize eSpotter.

Aberdeen, SD (ABR) Albuquerque, NM (ABQ) Amarillo, TX (AMA)
Atlanta, GA (FFC) Austin/San Antonio, TX (EWX) Billings, MT (BYZ)
Binghamton, NY (BGM) Birmingham, AL (BMX) Bismarck, ND (BIS)
Blacksburg, VA (RNK) Boise, ID (BOI) Brownsville, TX (BRO)
Buffalo, NY (BUF) Charleston, WV (RLX) Cheyenne, WY (CYS)
Chicago, IL (LOT) Cleveland, OH (CLE) Corpus Christi, TX (CRP)
CRH HELPDESK, MO (CRH) Dallas/Fort Worth, TX (FWD) Denver/Boulder, CO (BOU)
Des Moines, IA (DMX) Detroit, MI (DTX) Dodge City, KS (DDC)
Duluth, MN (DLH) Elko, NV (LKN) Eureka, CA (EKA)
Flagstaff, AZ (FGZ) Gaylord, MI (APX) Glasgow, MT (GGW)
Goodland, KS (GLD) Grand Forks, ND (FGF) Grand Junction, CO (GJT)
Grand Rapids, MI (GRR) Green Bay, WI (GRB) Hanford, CA (HNX)
Hastings, NE (GID) Houston, TX (HGX) Indianapolis, IN (IND)
Jackson, MS (JAN) Jackson, KY (JKL) Kansas City, MO (EAX)
Key West, FL (EYW) La Crosse, WI (ARX) Lake Charles, LA (LCH)
Las Vegas, NV (VEF) Lincoln, IL (ILX) Los Angeles, CA (LOX)
Louisville, KY (LMK) Lubbock, TX (LUB) Marquette, MI (MQT)
Medford, OR (MFR) Melbourne, FL (MLB) Memphis, TN (MEG)
Miami, FL (MFL) Midland/Odessa, TX (MAF) Milwaukee, WI (MKX)
Minneapolis, MN (MPX) Missoula, MT (MSO) Mobile, AL (MOB)
Morristown, TN (MRX) Nashville, TN (OHX) New Orleans, LA (LIX)
New York City, NY (OKX) Norman, OK (OUN) North Platte, NE (LBF)
Nrn. Indiana, IN (IWX) Omaha, NE (OAX) Paducah, KY (PAH)
Pendleton, OR (PDT) Phoenix, AZ (PSR) Pittsburgh, PA (PBZ)
Pocatello, ID (PIH) Portland, OR (PQR) Pueblo, CO (PUB)
Quad Cities, IA (DVN) Raleigh, NC (RAH) Rapid City, SD (UNR)
Reno, NV (REV) Riverton, WY (RIW) Sacramento, CA (STO)
Salt Lake City, UT (SLC) San Angelo, TX (SJT) San Diego, CA (SGX)
San Francisco, CA (MTR) San Juan, PR (SJU) Seattle, WA (SEW)
Shreveport, LA (SHV) Sioux Falls, SD (FSD) Spokane, WA (OTX)
Springfield, MO (SGF) St. Louis, MO (LSX) State College, PA (CTP)
Tallahassee, FL (TAE) Tampa Bay Area, FL (TBW) Topeka, KS (TOP)
Tucson, AZ (TWC) Tulsa, OK (TSA) Wakefield, VA (AKQ)
Western Region Hqtrs, UT (VHW) Wichita, KS (ICT) Wilmington, OH (ILN)
 
Back
Top