Browsing: Uncategorized

2019 Hurricane Season Website preparation

I've started shaking the dust off the chips in my servers. Due to medical issues, I haven't had the strength to do anything for a good while. Months and months. You can read about it in a brief here: "Answers, not good ones, but answers just the same." There are many other articles about it, but the linked one summarizes and tries to draw closure.

On to business. Improvements that I have planned for this season:

  • Graphic representation of weather systems drawing from ground-based sensors.
  • Fully automated storm detection and notification.
  • Beautification of the site (I'm going to draw from my wife for this--I suck at pretty websites)

I'm looking forward to presenting current frontal movements on a near-real-time basis. I was working on the task when my body fired my brain. I've been collecting data-sets from OpenWeather.org for the last year. I've stored away more than 8.5 million lines of data to create these charts.

There are two major reasons for this:

  • Non-critical event
    • Frontal systems, rainfall and other weather elements can be visualized in a method not currently available
    • Simplicity is key. What I find currently available would confuse Einstein. The design goal is for people to be able to see the map and say, "Meh, I'm safe." or, "Damn, time to inflate the rubber raft."
  • Critical Event
    • Watching a satellite image of the storm doesn't really tell the people on the ground where the damage is being done. It is a lovely image of the storm from the sky. Not the ground.
    • The maps will present the viewer with as much data is available during the storms.
      • NOTE: I tested this concept during one of the storms that hit the East Coast. It needed refinement, but most of the ground-based stations kept reporting days into the aftermath.
      • The fact that the stations kept reporting lends to the idea of Critical event mapping an obtainable goal
    • Again, not currently available in a simple form.

Why? I hate commercials and sites that track you. I track storms, and weather data, not people. The funds for this site come out of my own pocket. If you care to support my efforts, you can donate at may PayPal Account

God Bless and I hope we have an uneventful season. I'm perfectly content with tracking fish-storms.

Thanks for reading,

Jay C. "Jazzy_J" Theriot

{ Add a Comment }

Connective Tissue

Here is what Unisys' actions did.

Old code:

wget -N -nd http://weather.unisys.com/hurricane/atlantic/2017/IRMA/track.dat

New Code:

wget -O nhc_basins_current_status.txt https://www.nhc.noaa.gov/?text
grep "Forecast Discussion" nhc_basins_current_status.txt > nhc_Forecast_Discussion_links.txt
awk -F'"' '{print $4}' nhc_Forecast_Discussion_links.txt > nhc_end_links.txt
while read l; do 
	echo "https://www.nhc.noaa.gov$l" > nhc_links_to_get.txt
done < nhc_end_links.txt
while read l; do
	wget -P /home/jay/data/nhc_basins/ $l 
done < nhc_links_to_get.txt
for fname in /home/jay/data/nhc_basins/*; do
	grep "" $fname  | awk '{gsub("<title>", "");print}' | awk '{gsub("", "Forecast Discussion", "");print}' | awk '{gsub("Forecast Discussion", "");print}' | awk -F"(" '{print $1}'
	grep -A 8 "INIT" $fname
done

The two code blocks do the same.

I have things like this scattered through out the data-acquisition side of the programming.  When I redesigned the site this last year,  I made most everything modularized.  That is, you have a bunch of small blocks of code called by a unifying script rather than having one script with all the code in it.  Thus, repairing the site should be a little less than trivial, but doable just the same.

I'm just really exhausted from visiting my mom yesterday.  I should have the code repaired and the site back up and running within a few days if my body doesn't disown me.

Jay C. "Jazzy_J" Theriot

{ Add a Comment }

%d bloggers like this: