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

GIS Analysis of NEXRAD coverage

Joined
Apr 7, 2005
Messages
347
Location
Ames / ISU
Been doing some GIS analysis the last few days on NEXRAD beam height. Put together some graphics that I thought might be worthwhile to share.

Minimum beam height for 0.5 degree scan (ft above radar level) - National Map

http://www.meteor.iastate.edu/~slincoln/GRS/images/0.5deg_min_beam_height_ftarl.png

Minimum beam height for 0.5 degree scan (ft above ground level)* - National Map
http://www.meteor.iastate.edu/~slincoln/GRS/images/0.5deg_min_beam_height_ftagl.png

Minimum beam height for 0.5 degree scan (ft above ground level)* - Central US Map

http://www.meteor.iastate.edu/~slincoln/GRS/images/0.5deg_min_beam_height_ftagl_central.png

NEXRAD coverage deficiences and affected cities*
http://www.meteor.iastate.edu/~slincoln/GRS/images/0.5deg_min_beam_height_ftagl_cities.png


*Note about AGL maps: Uses a fairly simple method for estimating terrain effects to the beam height. Is not a true 3D analysis that would be required for research quality maps and is meant more to be used as a visual aid to show where the ARL maps (and GR status bar info) will be least accurate.
 
I really like this as I have recently been thinking more about how radar tilt effects what I see. The bummer is that the two places I live (between school and home) are two of the cities you listed on your coverage deficiencies map. Oh well haha, I guess I at least have TDWR radar at home thats close by.
 
Very Nice. Very Impressive. Looks like Missouri could use two more radars one in the Northern part of the state and one in the Columbia area. I would go with northern first because of the TV radars in Central Missouri. But kirksville could use one really bad. Too bad there is no funding.
 
Wow. I really like these graphics. As someone who is learning more and more about radar, I find these to be incredibly helpful. I remember trying to pick an appropriate storm for some of the storms near on April 26th. Thanks much for this!
 
Very nice graphics. I always noticed how certain areas of the country do not have a radar site close enough to scan low levels.
 
Back
Top