jason (@WxArizona) header
jason (@WxArizona) profile picture

i have pride despite my dismal circumstances

SE AZ, USA
Joined May 2019
Photo by jason (@WxArizona)Photo by jason (@WxArizona)Photo by jason (@WxArizona)Photo by jason (@WxArizona)Photo by jason (@WxArizona)Photo by jason (@WxArizona)Photo by jason (@WxArizona)Photo by jason (@WxArizona)Photo by jason (@WxArizona)Photo by jason (@WxArizona)
All 3 videos with movement of actual vortex, the tornado was overcondensed (thanks to high relative humidity), with the small vortex sitting on the backside of the tor. The video ends right as winds accelerate to ~110-125 MPH, with passage of 150-160 MPH winds just moments after.
3
50
1
368
10,760
Personal damage contours.
1
19
469
Synced footage of Union City direct hit and distant view, genuinely forgot who filmed either of these but just wanted to post NOTE: discovery 100% added some sort of sound effect when the roof got ripped off
13
119
10
860
50,919
vid with synced 3rd perspective from north of the tornado
2
33
1,697
Aftermath of recorder's home, he suffered a broken neck. (to my knowledge)
2
1
60
2,350
As a very avid DAT user, I’ve been using the updated Damage Assessment Toolkit for about a day now, and I wanted to share my thoughts so far. Pros: • Damage photos load significantly faster. • The filtering feature is much better. • The bookmark feature is pretty neat and useful for immediately being directed to specific cases or outbreaks. Cons: • Loading data feels more cumbersome and slower. • The quality of paths and points on the map appears worse than before. I’m noticing significantly more pixelation. • Basemap quality also seems to have decreased. • The updated DAT relies more heavily on newer ArcGIS features, particularly the pop-ups, which I personally don’t care for. • Zooming in and out feels overly sensitive, and it seems to take longer for data to load afterward. • The measurement tool currently does not work. • Tornado paths are too thin and, in my opinion, should be a bit thicker. • The date box is weirdly cut off in the top-right corner. • Damage Indicators (DIs) appear as smaller now, and the EF0 DI color was changed for no apparent reason. • When overlaying data from the "Add Data" feature, it covers tornado paths, points, and polygons. • You can't manually type in a date range anymore. Overall, I’m not particularly impressed with the UI changes or the update as a whole. It honestly feels a bit like a case of fixing something that wasn’t broken, it seems like a step back to the DAT from the 2019-2020 era. That said, I’m not sure who is currently responsible for these changes, or whether they’re actively looking for feedback from frequent DAT users. Also, I’m pretty sure this update had to be done because ESRI’s Web AppBuilder was deprecated. I’d also be interested to hear from NWS meteorologists who utilize the DAT regularly: What are your thoughts on the update? And just to clarify, I’m not trying to come across as rude or overly negative with these criticisms. I’m simply sharing my honest thoughts from the perspective of someone who uses the DAT very frequently, as well as someone looking at the changes from a human-factors perspective. There are some improvements here, but I think there are also several areas that should be reconsidered if possible.
3
18
1
71
5,270
almost absolutely obliterated by this singular negative CG from the tiniest electric field ever and camera wasn't even in focus #Fairs
2
184
Replying to @NWSTucson
@NWSTucson Powerflashes going on looks like on Hwy 92, at least 5 flashes.
1
229
Absolutely gorgeous thunderstorm getting ready to hit Sierra Vista
6
279
Was it something I said? 😢
3
222
Genuinely what are you even saying anymore? Cycloidals are perfectly calculable but not at all in whatever sense you are trying to apply here. There is no "recipe for EF5 intensities" in cycloidals. It is simply the rotational velocity and forward speed that determines them.
unavailable
4
45
3,545
And let's not forget when this guy was horrendously wrong about the cycloidals from the Kouts IN tornado, where he assumed 180 MPH... and then they ended up being calculated at about 60 MPH below that. So so aggravating people can be so confidently wrong.
10
308
Ran out of words: Theres more to it than rotational velocity and fwd speed, swirl ratio is also an important factor. The cycloidals here aren't even calculable at that low of a resolution.
8
310
Feel this would be a lot cooler of a finding if photogrammetry was on a 3-second basis (which is what the EF scale uses) rather than instantaneous. A lot of tornadoes including weak ones likely exceed 200 MPH regularly on that sort of scale, but it doesn't reflect on true speeds.
Photogrammetic analysis by Anton Seimon suggests that the Floyd, NM, tornado of May 25, 2025, may have been of EF-4/5 intensity. The tornado didn't hit much and is officially rated EF-1.
2
1
16
1,255
Definitely no disappointments earlier
8
284
Tornado warned supercell east of Sierra Vista, AZ
16
531
Some decent bolts earlier tonight from a storm north of Bisbee. Storm tapered off as it moved into the lower elevations east of Sierra Vista. #azwx
9
481
yes guys i know its a chart error now
something tells me the new rating/reanalysis from the pre-1900s tors on tornadoarchive aren't very reliable... but i cannot put my finger on the reason why!
5
564
something tells me the new rating/reanalysis from the pre-1900s tors on tornadoarchive aren't very reliable... but i cannot put my finger on the reason why!
5
2
22
3,098
youtube.com/watch?v=LxJZgkJL… Insane video of the 2013 Moore EF5 as it intensified before inflicting its first EF4 indicators.
7
11
1
117
70,608