Thank you Amar, for this and your whole website. On my blackberry the official NWAC telemetry sites are long and large to load.
On yours the font size is still fixed, it seems, and the tab offsets make the page too wide and the columns get messed up. But you have given me hope, and an excuse to figure out PHP.
The font size is not fixed or set anywhere in my script, you can reduce it in a web browser (not sure about Blackberry, I've never used one). My script does keep the <pre></pre> tags from the NWAC source, which forces a fixed-width font to make sure the columns stay aligned.
About half of the NWAC data sites have a left margin of whitespace, which is either 4 spaces or 10 spaces wide (I'm not sure why they can't all just be left-justified with no left margin, that would be nicer). I figured that it would be easy to narrow those NWAC files, since stripping leading whitespace is very simple in PHP using ltrim, so it should only take a couple minutes to add that to the code. WRONG! Unfortunately ltrim strips ALL the leading whitespace and mangles the column alignment. It took an hour to figure things out and write reliable code to strip only the left margin from data sites which have it, while leaving those leading spaces which are necessary. It appears to be working now, and as a bonus the "concatenate ALL" display looks much nicer now with all the left margins stripped off and date/time columns aligned for all sites.
Making the data for widest NWAC sites (e.g. Snoqualmie is 98 chars wide, several others are 84) any narrower might be possible, by carefully stripping certain characters without ruining the column alignment. I'll try this afternoon . . .
Edited to add: Well, it was pretty easy to shrink the Snoqualmie data from 98 to 82 chars wide. Does anyone really want an even narrower version of that, or narrow versions of other wide sites? The narrow version has to be manually figured out and coded for each individual site, since they all have different columns and widths.
TAY weather links section also now has the 10 day text-only telemetry data available. There doesn't seem to be any need for the individual 24 hour pages any more.
The "now" data is often needed, because the 10-day files are not always generated correctly. The code which generates the 10-day files has a few bugs. For example: as of this morning, the "mtsthelens" 10-day file does not exist, even though there is several hours of data in the "now" file. And the "campmuir" 10-day file is always missing 4am every day.
And on some days, the underlying NWAC archive files (e.g OSOMTB.1, OSOMTB.2, ..., OSOMTB.10) from which the 10-day files are generated are not properly updated, so that the OSOMTB.1 actually has 2 day old data, OSOMTB.2 has 3 day old, etc., and yesterday is completely missing. In this case, the "now" is the only place to find the last 24 hours of data, since the 10-day file will have a gap from 4am this morning to 4am yesterday when such problems occur.
