House Calls

Now Offering SSL / HTTPS

We are proud to announce the availability of SSL/HTTPS for all AllisonHouse web properties beginning today, October 6th, 2015. This includes Level 2 and Level 3 Radar, Data Overlays (Feeds & Placefiles), GRearth and even Warnings. While nearly all of the data supplied by these addresses is in binary format and of no value to hackers because it doesn’t contain any personal information, we believe this is a necessary step to keep customer information safe for many years to come.

Customers may begin using this feature immediately. Simply change “http://” to “https://” in any of your links before integrating them into your software. This will ensure that all of the information exchanged between your software and our servers is encrypted and kept away from prying eyes. We will reach out to our development partners regarding the availability of this new security feature so that it may be built into future versions of their applications. Apple’s newer versions of iOS may even begin to prevent applications from reaching insecure (HTTP) web addresses due to the risks it poses.

Security has always been a top priority at AllisonHouse. After all, our Founder and President has worked in Information Security for over 20 years. So it’s no surprise that has always had the strictest encryption policy, forcing all customers to use SSL/HTTPS, even when just visiting our homepage. This ensures that absolutely none of your personal information is ever exchanged over the unencrypted (insecure) HTTP used by most websites. We have always sacrificed faster website loads for improved security because we value your privacy.

As the web has evolved, so have hackers’ methods of attack. There will always be malicious parties who wish to obtain your personal information for their own personal gains. This is evidenced through the numerous security breaches over recent years, including Home Depot, Target, and even more recently, Experian, Scottrade and even Trump Hotels. The sophistication of these attacks varies greatly and no two are exactly alike. All companies which conduct business on the internet should take the necessary steps to protect their customers’ information, regardless of the difficulty or associated costs.

We will continue to monitor industry trends and adapt in order to protect the personal information of the people we value most, our customers. As always, please feel free to email us at support[AT]allisonhouse[.]com with any questions you might have regarding these changes. You’re also free to email me, Ryan Hickman (CTO), directly at ryan[AT]allisonhouse[.]com.

Risk perception and the normalcy bias: What, me worry?

Over the past few weeks, 19 people have died from flash flooding in just one incident. Heavy rainfall fell and flooded canyons in Zion National Park, killing 7 people…and in another incident from the same storm, another 12 died…most women and children.

For this post, I want to concentrate on the 7 who perished in Zion National Park, because we know what happened. Seven men and women, all in their 50s, went on a hike on a beginner’s trail that would require them to go to caves, hike, and swim across streams in canyons. When they do the latter, you are helpless if flash flooding occurs. These 7 hikers ignored repeated warnings, according to news reports, that flash flooding was a major possibility. In fact, soon after they departed, the Park Service closed the trail they were on because of the flash flood warning the National Weather Service had issued for that area, including those canyons. According to reports, after 2″-4″ of rain fell north of the canyons, a wall of water raged through them, sweeping the 7 almost instantly to their deaths as they were caught by the water. They couldn’t swim or run away in time.

Now, some callously might call them stupid for ignoring the warnings. But these people were anything but stupid: one was a police officer for 20 years, one who—beyond all the others—knows about dangers in various situations, such as robberies. A digital camera found on one of the deceased showed a photo of them happily standing together, posing with all smiles—likely a very short time before they all perished.

So what happened? It was certainly a failure of risk perception, and normalcy bias. What are those? To put it simply: your risk perception, when done right, warns you that we just picked up 3″ of rain in over an hour, and there could be flooding. Or, a tornado is coming, and I’d better take shelter (or for you storm chasers, grab your camera and head out…I know you!). In other words: risk perception critically analyzes a situation and determine what risk(s) are associated with an incident, or activity. If you play football, correct risk perception indicates players can hurt you as you are being tackled, and you need to wear proper protective gear. Or that if you climb a ladder to paint, you had better not climb on that rung that says “don’t climb up here or go above this rung, you may lose your balance and hurt yourself” (I’ve always laughed at that one…why have that rung there if you don’t want people on it?).

Normalcy bias says: well, yes, we have had a tornado in our county two years ago, but THAT will never happen again. Or: I suppose there is a risk of a flood, living close to a stream, but we’ve never seen the water levels rise up to where we are before, so therefore, it can’t happen here! But the truth is…it most certainly can happen! But what about those deceased hikers at Zion National Park? If you think I’m going to call them stupid or foolish: I cannot claim that I can perfectly assess risk nor have a normalcy bias. So what went wrong?

First, they did get the warnings about the heavy rain and potential severe flooding that could occur; the canyon they were swept away in was under a flash flood warning. Risk analysis says that hey, canyons are where water is channeled, the park rangers say it could flood instantly, and a flash flood warning is in effect. So, by the account of the park rangers, the risk analysis on their end was correct. They had the information that led them to believe a serious danger was unfolding. For whatever reason, they didn’t close the canyon at that point. They must have believed that the risk was still not high enough yet to make that call. Either way, everyone knew that there was a risk of the canyons flooding in an almost instantaneous timeframe.

Risk analysis would then say: “that’s too dangerous; let’s do something else, even though we spent money on this.” Or: “there is no danger to us.”, Or: “we can get out of there, if we need to; it doesn’t seem too high of a risk to me, let’s go and have fun!”. God only knows what they thought, but it was ultimately one of those three. While I can speculate on which one it is, it won’t matter, as it won’t bring them back, and I’d just be guessing, even though I have a pretty good idea which one it was.

So what about you? If you live in the Midwest and say “A tornado cannot happen here”, I am going to argue that your risk perception is incorrect. Yes, there is a lot of junk on the Internet, but there is also many sites online that are vetted and will correctly tell you of the risks of lightning, floods, tornadoes, earthquakes and more. And when you come to that point…where you realize you have family, friends and loved ones to protect, talk to us as to how we can serve you in that way. Please drop us an email or support ticket! Displaying pretty pictures of precipitation is not what we do; it is one of many tools we offer to minimize your exposure to atmospheric dangers, and thus minimize or even eliminating your risk of experiencing loss. By understanding and minimizing your risk to weather hazards, your correct risk perception and destroying your normalcy biases will help keep you safe in weather and non weather-related hazards, when others cry out, “how could this happen to me?” and “it came without warning!”.

Keep your software updated! (Or, you aren’t getting what you’re paying for)

In this insightful blog post from Mike Gibson (account on required to view):

He notes a lot of people are running old versions of his software:

GRLevel3 versions:
2.17 : 57.1%
2.18 : 1.5%
2.20 : 6.1%
2.21 : 35.2% (current 8/15/2015))

GR2Analyst versions:
2.13 : 22.1%
2.20 : 11.0%
2.21 : 52.6%
2.22 : 14.3% (current 8/15/2015)

GREarth versions:
2.12 : 0.5%
2.13 : 2.9%
2.14 : 1.8%
2.15 : 0.3%
2.16 : 17.4%
2.17 : 0.3%
2.20 : 5.0%
2.30 : 9.5%
2.31 : 62.4% (current 8/15/2015)

As you can see, some of these users, who are AllisonHouse customers, are using old versions of the software. This is a problem, because, as an AllisonHouse customer, you aren’t getting all the features and data you paid for, on both our end, and on the software end of things as well. For instance, as of this writing, GR2Analyst is now at version 2.22, which fixes an issue with
forecast model sounding data not being ingested into the program, which helps dealias velocity data. In GRLevel3, you aren’t getting 1 minute to 90 second updates from NWS/FAA radars which have upgraded to the latest operations software, which will soon be all of them!

If you have PYKL3, RadarScope, or other phone apps, updates are usually pushed out automatically. Currently, however, Gibson Ridge software requires you to go to the website, log in and grab the updates. To all our GR users, we encourage you to check at least once every 3 months, before a major event, and if things stop working properly, whichever comes first. So, after you get the chores done this weekend, hit the website, and download the latest updates. This helps reduce frustration on your end, trouble tickets on our end, and makes both of us happy campers. So, If you aren’t (as of 8/15/2015) running GREarth 2.31, GRLevel3 2.21, and GR2Analyst 2.22, head to, and sit back, and watch the weather roll in!

As an aside, I have made a request to Mike Gibson to have future versions check for software updates. If you think that this is a good idea, the thread I linked to near the top of my post is where you should post that request.