Monday, October 13, 2008

Profiler status updated

I mentioned last Tuesday that I would be updating and streamlining the Profiler scripts once the data was back up on UCAR's site. I noticed the return this morning at work, so this afternoon we got down to business.

The scripts are nearly identical to the upper air scripts but instead they'll display 8 profiler sites in/around Kansas. Please refer to the "profiler.txt" placefile and the "profilerUCARbat.txt" batch file in the "Profiler/Upper Air Project" section on the right hand side of the page.

As always, there's incredible flexibility built in with this application. You can easily take out a site that doesn't apply to your needs and plug in the appropriate one. Just be sure to change the URL and file names in the batch file, get the correct lat/lon for it and you'll be good to go.

At this time, I'm not going to write a script that puts all 30+ sites that UCAR has into one placefile. It can be done...just not today!

Thursday, October 9, 2008

Update from KDOT

I want to thank Barb from KDOT for the nice email reply I received yesterday. She stated that the camera views from Garden City and Wichita are down because of firewall issues. It is unknown when they will be back online.

She also said that the new cameras (slated for along I-70) should be up in mid-November.

I say that's not a minute too soon! I know at least a couple of times last year when KDOT shut down parts of I-70 because of snow and blizzard conditions. I'm looking forward to the views they will provide for all users and for my camera scripts on GR3.

** UPDATE: SUNDAY 10/12 **

One back...one to go. Wichita returned Friday and has been steady ever since. C'mon GCK!

Tuesday, October 7, 2008

Update on Upper Air

I did a little house cleaning this morning with the Upper air data for GR3 (see my earlier post on this). I consolidated the individual raob placefiles into one, thus freeing up a few extra places in the placefile manager. I also added more raob sites. I'm now at 8 raob sites around my area, which just happens to be the limit (you can have up to 8 "Iconfiles" statements).

When I first put this together, I put each raob site into it's own placefile because of overlapping issues when displaying multiple sites. This time around, I simply changed the threshold statement from 250 to 100. As a result, you have to zoom in a ways to get the sites to pop up, far enough so that it ensures that they won't overlap one another.

I'll do the same to the profiler data once it is available again.

Monday, October 6, 2008

I missed the memo!

I was wondering this past weekend why I couldn't get my profiler scripts to work for GR3. I just figured there was a problem at NCAR/UCAR:

EFFECTIVE OCTOBER 1 2008 ALL NWS WIND PROFILER PRODUCTS WILL BE UNAVAILABLE FOR APPROXIMATELY 3 TO 5 WEEKS.

THE SUSPENSION IN AVAILABILITY OF WIND PROFILER DATA IS
NECESSARY BECAUSE OF RECENTLY INDENTIFIED IT SECURITY
THREATS. THE WIND PROFILER NETWORK CURRENTLY OPERATES ON OBSOLETE EQUIPMENT THAT CAN NOT SUPPORT NECESSARY IT SECURITY METHODS. INTERCONNECTION TO MAJOR NWS SYSTEMS EXTENDS THE VULNERABILITY TO OTHER NWS IT SYSTEMS.

There's no good time for this kind of data loss but I guess better now than the middle of April or May!!

Monday morning updates

I spent an hour this morning going through the Kansas camera scripts again. I found a couple of errors I overlooked from the previous update (my bad!). I also took out some other cameras that were down and replaced them with cameras that have returned to the fray.

I sent an email to the Kansas Department of Transportation this morning too. They still have 2 cameras down, one in Garden City and in Wichita, with the former down since 9/16. I don't have a timetable for return yet.

Friday, October 3, 2008

A few tweaks

I spent a few minutes today updating the Kansas camera batch script. The issue was a URL change by KDOT which affected all 8 of their cameras (2 of them remain down though, even after the change). I'll continue to monitor things and won't make changes to any down camera(s) unless it's clear there's a persistent problem. Otherwise, I'll spend too much time switching/editing scripts.