Recent Posts

Pages: [1] 2 3 ... 10
1
.... Aviation had to get it right. It's used for vertical separation from other aircraft and terrain below 18,000' (FL180).

But QNH and associates are not set and forget, an aircraft requests/sets QNH to take off, then an area QNH, then the local QNH prior to landing.
Please explain to me this relevance to a PWS owner.

Exactly, so why did you actually raise or mention it then? PWS owners are not interested in Aviation matters why did you even mention it?
2
WOW, I can't believe they accepted the UTAH record High from that location. Notice the FARS read about a degree lower, so they thought it was all good. WHAT? That location doesn't meet siting guidelines for temperature or rainfall.
And that's a block fence, they get hotter than hell. And so close to the house.
I don't get it at all.
3
.... Aviation had to get it right. It's used for vertical separation from other aircraft and terrain below 18,000' (FL180).

But QNH and associates are not set and forget, an aircraft requests/sets QNH to take off, then an area QNH, then the local QNH prior to landing.
Please explain to me this relevance to a PWS owner.
4
.... Aviation had to get it right. It's used for vertical separation from other aircraft and terrain below 18,000' (FL180).

But QNH and associates are not set and forget, an aircraft requests/sets QNH to take off, then an area QNH, then the local QNH prior to landing. I just wisthpeople wouldn't keep on confusing people with such stuff that is really not relevant to the normal everyday weather station user. 
5
Even the Kindle version is expensive (but I pre-ordered it).  Got to feed the weather itch :)
6
Good... also change ORZ008 to ORZ118 and KEC42 to ORC039 for the NWS alerts too in Settings.php
Quote
$SITE['NWSalertsCodes'] = array(
    "Southern Willamette Valley|ORZ008|KEC42"
//  "Santa Clara Valley|CAZ513|CAC085",
//  "Santa Cruz Mtns|CAZ512|CAC081|CAC085|CAC087",
//  "Santa Cruz|CAZ529|CAC087",
//  "Monterey|CAZ530|CAC053",
//  "South/East Bay|CAZ508|CAC081",
//  "San Mateo Coast|CAZ509|CAC081",
//  "San Francisco|CAZ006|CAC075"
);
to
Quote
$SITE['NWSalertsCodes'] = array(
    "Southern Willamette Valley|ORZ118|ORC039"
//  "Santa Clara Valley|CAZ513|CAC085",
//  "Santa Cruz Mtns|CAZ512|CAC081|CAC085|CAC087",
//  "Santa Cruz|CAZ529|CAC087",
//  "Monterey|CAZ530|CAC053",
//  "South/East Bay|CAZ508|CAC081",
//  "San Mateo Coast|CAZ509|CAC081",
//  "San Francisco|CAZ006|CAC075"
);
7
Yeah, that's just not right. To be honest, it's not that surprising considering the NWS is using equipment manufactured by a company that went defunct nearly 15 years ago. It comes down to cost I assume. Lots more user friendly technology available now with the ability for better siting. The issues with the current MMTS system have been documented. Although the radiation shield seems to work well. Even Davis published a study in comparison around 2007 and ran into problems https://ams.confex.com/ams/87ANNUAL/techprogram/paper_118190.htm

I was also surprised they accepted this COOP MMTS tying of the Utah state temperature record on siting alone ...
https://www.ncei.noaa.gov/monitoring-content/extremes/scec/reports/20220708-Utah-Maximum-Temperature.pdf

ASOS isn't immune either though as I posted elsewhere a really interesting video from NWS Lexington KY documenting the extremely lax tolerances. At least a fix there is in the works ...
8
I guess the point I was making (or trying to make) is the term “sea level pressure” applies to both Altimeter setting and SLP. SLP is called sea level pressure (Aviation Weather Center) - that's what S-L-P stands for, but Altimeter is also “sea level pressure.” In other words, both are converted down to sea level.

I think the aviation industry got it right; QNH = QNH and QFF = QFF. No confusion there and no head scratching about sea level pressure, barometric pressure, etc, etc.
I get what's trying to be conveyed. Problem is, they're not the same. I think a lack of further explanation here (by whomever) has some people thinking that they actually are. For instance, my altimeter right now 29.82, but my SLP is 29.62. Quite the difference.

Aviation had to get it right. It's used for vertical separation from other aircraft and terrain below 18,000' (FL180).
9
Hey @saratogaWX,

Thank you! I thought I confirmed it was still 008 yesterday, but maybe I looked in wrong place.

Can confirm that fixes the error!

Thank you again!
10
You do have a few updates to do from 30-Jan-2024, but like you say, it doesn't impact advforecast2.php V5.19 which is current.

Your Settings.php has
Quote
$SITE['NWSforecasts']   = array( // for the advforecast2.php V3.xx version script
// use "Zone|Location|Point-printableURL",  as entries .. first one will be the default forecast.
  "ORZ008|Springfield|http://forecast.weather.gov/MapClick.php?CityName=Springfield&state=OR&site=PQR&lat=44.058&lon=-123.006"
);
and the Zone has recently changed for your selected location to be ORZ118 so that should appear as
Quote
$SITE['NWSforecasts']   = array( // for the advforecast2.php V3.xx version script
// use "Zone|Location|Point-printableURL",  as entries .. first one will be the default forecast.
  "ORZ118|Springfield|http://forecast.weather.gov/MapClick.php?CityName=Springfield&state=OR&site=PQR&lat=44.058&lon=-123.006"
);

Also change
Quote
$SITE['noaazone']         = 'ORZ008';
to
Quote
$SITE['noaazone']         = 'ORZ118';

Hopefully, that will fix the issue...
Pages: [1] 2 3 ... 10
anything