Maybe I am looking at the wrong place? But I dot not see the same information you mention.
January version and beta are the same for today = March 2 rise 04:44 moonset 13:56
January version has no data for March 3
The main page of the beta version displays “upcoming data” so it says “MoonRise 05:25 tomorrow”
The January version displays “Moon rise 04:44” which could be considered incorrect as it should have been worded “Moon rose 04:44” bacause the displayed time is in the past. Strange thing is that for sun-rise/set we are accustomed to a sunrise in the past when it is daylight.
But not for the moon, there the times should be about future rise/set, because we can not see were the moon is during daytime.
At least that was how it was explained to me. All times for sun/moon - rise/set are future times and have the word “tomorrow” added or the exact date.
I really like your template. Now that you have the new wunderground forecasting working it is perfect.
I am having one problem with the wunderground forecast. I like 4 days forecast but I am getting no precipitation chance percentage. When I run w34_module_test.php and run forecastWUblock.php the %'s are there but not on the main page.
Edit: I went to wunderground and got a new api key right after I setup this beta. I’ve now figured out that the forecast is Dark Sky not WU. I don’t know why I’m not getting WU.
I was looking at the production version of w34_livedata.php and noticed that average and max wind speed are both defined using clientraw #158, which is “10-minute average wind speed (kts)”
$weather[“wind_speed_avg”] = convert_speed ($wd[158],$from,$to); and
$weather[“wind_speed_max”] = convert_speed ($wd[158],$from,$to);
I checked and it is still the same in beta. Maybe it doesn’t matter because we don’t show max wind speed anywhere, do we? Max gust shown uses CR#71.
But I would prefer the beta to make it clearer that the small “Average” value shown at top left of the Wind|Gust block is the 10-minute average, as is done in production.
Hi
beta version 1-3-19 gives error in MS edge as
Notice: Undefined offset: 1 in /pwsWDTEST/metar_popup.php on line 203
Notice: Undefined offset: 1 in /pwsWDTest/metar_popup.php on line 205
CheckWX appear to be moving the goal post again re there data output file changing
@ALL
The format of the JSON file from the METAR provider has changed again.
Sorry, this should not have been visible for the production version. Still it is.
For the beta version all errors are displayed by default.
As I am “off the grid” for at least 3 weeks after tomorrow I have very little time left to find a solution.
FOR NOW: Start easyweather and select nearly at the bottom at the question “Where do we get our current conditions from?” => “Use Darksky for current conditions (needs API key).”
That way your main window will not load the METAR scripts.
And do not use the “nearby” pop-up for now until i have had a chance to find out why they removed the airport name and others from the .JSON
As other users already discovered, the layout changed again.
[ol]
[li]The airport-name is not available anymore / for now??.[/li]
[li]The date/time field layout changed from:
old: 01-03-2019 @ 07:20Z"
new: 2019-03-05T05:55:00.000Z[/li][/ol]
I attach a zip with the two changed scripts for the pwsTEST users.
First make a copy of the two scripts you are going to replace.
These two scripts are only tested with the latest (a few day old) beta release.
The updates for the pwsWD version is posted in the other topic.
Probably not quite exactly 24 hrs; but I do notice that the “total darkness” figures in the main Sun block are very different to those in the “Moon info” popup? (At the beta test sites and in production version here.)
Only approximately unless, as Wim says, you have 24 hours’ day or night.
Are we confusing sunrise/sunset with civil, nautical or astronomical dawn/dusk somewhere? Original Sun block or pop-up showed times of civil dawn/dusk (elevation -6