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

US Chase Map Project

Jeremy Perez

Supporter
Joined
Aug 31, 2008
Messages
342
Location
Flagstaff, Arizona, USA
I’ve had a goal of creating a detailed US Chaseability map for a couple years now. I wanted to factor in road grid, tree density and terrain. I’ve made progress on the first two items, and it’s at a point now where it should help inform my chase planning this year. I wanted to share in case anyone else finds it helpful. (For chasers that dwell and chase frequently in the central US, this might be superfluous :) )

My intention for it is to frame what I might expect and be ready for during a chase, or possibly inform my targeting decisions (all other thing being equal).

The two images below are 1920 pixels wide. The original is 13,500 pixels wide, so I can export larger if ST is able to host images larger than 2MB.
Please also note that I have not completed road network analysis on Wisconsin, Indiana, Michigan, Ohio, Florida, and Mississippi River Valley (see future plans at bottom of this post).

US Storm Chase Map - with forested areas
US_ChaseMap_20150505A.jpg
US Storm Chase Map - without forested areas
US_ChaseMap_20150505B.jpg

For any who are interested, I’d like to make this available as a community resource. If you’d like to edit, proof, or add content to the layered PSD file, please let me know and I can provide a download link. It is too big—150MB—to provide an ongoing public link (my web host would probably threaten to terminate my account if I did that). If anyone wants to do their own work on it, I’d just ask that any copies or derivatives of this content be re-distributed non-commercially.

Details

Road grid quality
  • Green = Typically 1 mile grid with some 2-3 mile gaps
  • Yellow = Typically 2-4 mile network with some 8 mile gaps / 1-2 mile network with discontinuous junctions
  • Orange = Typically 5-10 mile network/uncertain network with gaps up to 16 miles
  • Empty = Questionable or non-existant. Mainly highway chasing.

Tree Density
Contour of areas with highest tree density.

Urban Areas
Highlighted in dark red.​

Caveats
  • This is not intended as a tactical navigation resource. It is meant to provide a strategic overview of chase navigability/storm visibility.
  • Road grid quality does not speak to actual road conditions—mud bogs, sand traps, plowed-over roads, and map mirages.

Map choice
To avoid copyright issues, I took my first dip into working with shapefiles from the US Census Bureau using QGIS on the Mac to convert to DXF and then import into Illustrator. This provided vector data I could use to add county and state boundaries, interstate paths, and urban areas.

I chose a map projection for the data that was compatible with Google Maps mercator projection (EPSG:900913). This aligned with the road network resource I used and the default projection at Data Basin.

Road Network Method
The US Census Bureau provide shapefiles for all roads in the US, but the number of shapefiles is enormous (3200+) and without scripting would be an extremely tedious process. However, reddit user, WestCoastBestCoast94, did go through this process and used the data to generate a high-res PNG image of all roads in the US. I referenced this image to make estimates of road networks and to draw in boundaries. I gave preference to networks with primarily straight roads and perpendicular intersections. There may be decent networks with lots of diagonal roads and angled intersections (I’m looking at you, Texas), but without a more detailed & lengthy examination, I can’t tell which of these are halfway-decent and which are terrible, so I tended to leave them in the lower quality buckets.

I did not have an eternity to do this, so there is going to be some slop in places—taken as a whole, it should provide a reasonable estimate of road network. However, DeLorme, Garmin, Google, Yahoo, Microsoft, whatever map software of your choice, would still need to be the prime resource for current/reasonably-accurate info.

I am not including the actual road-network map in the image above or in the layered PSD file, because I don’t know if ‘WestCoastBestCoast94’ wanted it to be re-distributed in a Creative Commons non-commercial sense. However, you can find his US map and more detailed individual state maps in the directory he created here: http://foid.me/roads/. It is scaled such that you could paste it into the layered PSD document to compare to contours I’ve drawn.

Tree Density Method
I used the ‘Mask Of Forested Lands Contiguous US’ data from Data Basin to draw contour lines around the areas of highest tree density. There are less dense tree signals that I did not include in the boundaries. I am also not sure how well the data correlates to the real world and whether it includes other annoying, visibility-killing plant life.

Future Plans & Possibilities
  • Road Network: Add contours for California, Wisconsin, Indiana, Michigan, Ohio, Florida and Mississippi River Valley.
  • Evaluate color choices for accessibility and easy evaluation of features (it's probably pretty bad for deuteranopes at this point).
  • Terrain: flat / hilly (maybe 2 or 3 degrees of this?) / rugged / mountainous — with obstructions (rivers/escarpments)
  • River crossings
  • Hostile counties: I’m collecting a list (e.g., Barber Cty, KS)
  • Rest Stop/Boondocking locations
 
I'm wondering if the Indiana whiteout is due to lack of knowledge of the state? I know that for the most part central, northern and western Indiana, at least in the northern 1/2 or so, has paved road grids for the most part.

Sorry, I see now that you have plans to update Indiana in the future
 
Yeah, all those unforested areas from Wisconsin/Michigan down to the lower Mississippi flood plain seem to have some really great road options from my initial browsing. Hoping to fill those in pretty soon—plus that California central valley area!
 
i spot and chase in central kentucky and here you only hill top. trees, unpaved roads and if it is raining a lot of back roads flood. best advice have a local guide or dont.
 
Hey now... that's neat! I wanted to do something very similar to this nearly 10 years ago, but never found the time to put it together. Most of that looks quite good....... I can attest that it looks very accurate for my home state (Missouri) and my current state (Alabama).
 
Thanks for the feedback, Matthew! So far I've only marked up Alabama for tree cover. A quick peek, at that little whisper of lightly-treed terrain on the north edge of the state looks like it has about 3-4 counties' worth of gridded roads, but interspersed between Huntsville and surrounding urban centers.

After a bit more searching, I came across some interesting content from the USGS with better resolution/detail for tree canopy/coverage, and another pretty nice one for landforms that would help with the terrain aspect. Now it's down to seeing if I can get their data to cooperate without an epic technical battle.
 
This is something I have wanted to do since I took a GIS class back in 2010. This looks really good. I'm glad someone finally got around to doing it.

I had started an ST thread in 2010 about an idea I had, but I never got around to doing it (lack of ability + other stuff getting in the way). It looks like the threaddidn't survive the failures over the years. I have a picture of it, though.

just_in_case.png

Anyway, I figured you could take some elements from my proposed methodology to incorporate terrain, land use, and perhaps improve the roads method. Great job!
 
@Marc R. O'Leary — thanks for the input—I hope it turns out to be of some use.

@Jeff Duda — thanks for sharing the reminder about that post! I think I remember reading that. (Although ST search function didn’t locate it, it is still here —> https://stormtrack.org/threads/chase-terrain-suitability-study-map.22994/ )

I think your proposed strategy for evaluating chase suitability is the ideal way to go—a lot more objective. I especially like the possibility it would bring out those ‘sleeper areas’. I wonder if any of the road shapefile resources contain data on paved vs unpaved? That would go a long way toward refining the road network—even if it was 10% out of date, it would still be very telling. I’d probably have to quit my day job to figure out how to make all of this work though…same problem most everyone has, I guess. The tactics I’m using on this one are pretty subjective, but maybe it can serve as a stop-gap or inspiration for a future version with much more precise evaluations.

For the better USGS canopy and landform maps I thought I found earlier this week, I’m now having trouble locating shapefile data for those that QGIS doesn’t get stumped on. I may have to use image warping in Photoshop to morph the high-res map images to the right projection and process from there.

Thanks @Brandon Centeno . Yeah that one probably works best on an ATV. A lot of the reservation areas do seem to confirm as slim pickings for decent road networks.
 
Jeremy, thanks for doing this and making it available to us. Obviously a lot of work went into this. I look forward to adding it to my toolkit during my upcoming chase trip!


Sent from my iPad using Tapatalk HD
 
This is marvelous! Now a statistics freak can easily see why Nebraska has always had a pronounced "tornado drought" in the Sandhills portion of the state.....there are few trustworthy chasing roads there. This is in spite of radar verifications showing tornadoes frequenting this area year after year. It's not uncommon for these to occasionally be large, long-track tornadoes, as well. I don't know how many times I've personally had to terminate my chases of tornadic storms and sometimes actual tornadoes on the ground due to the propensity of poor roads in there. To be fair, there are remote ranch-access roads usually miles apart from each other in the Sandhills, but experience has repeatedly proven her point to me to stay off those no-maintenance/sand+clay roads, especially during wet episodes. Knowing Nebraska as well as I do as a native who LOVES chasing the entire state, I do see some areas on this map that I believe I could update. I'll be in Nebr. the last week of May to begin my month-long chase vacation, and will seek to verify this as I chase here and throughout the remainder of the alley as well.
 
Back
Top