Yes I am testing a new sun-block.php, it should always display the correct sun-position ,also when someone from another time-zone visits your site. That “Estimated” is only displayed in the “dark theme”. I removed it in the script as all text should be translated to the default language.
2. I think the webcam fits better at $webcam_height of 155px (webcam2) rather than 160px (webcam1, where it hangs over the bottom of the frame)? (I changed mine to show width 70%, too, to reproduce the 4:3 aspect ratio without stretching.)
The problem is not with the height the webcam image. The problem is a difference in the CSS between light and dark. All block-headers are displayed lower in the dark theme, just outside the band. In the light theme they are correctly place inside the grey band.
Have to find where it is specified.
Wim FOUNDIT: weatheritem has 6px padding in dark 0px in light theme
There are more differences this pushes all content lower in the box.
You are using clientraw.txt for your “livedata”.
The http://swanston.maui.co.uk/clientraw.txt has 10 fields for rain-hour, they all contain 0.3 mm
The clientrawextra.txt has 24 fields for rain-hour, the first 9 contain zero , other 15 contain0.3 mm
Seems Brian, as the programmer of WD, has to tell me how I should calculate rain-last hour.
Probably I have to subtract the tenth = last hour value from the ninth one to get the last hour rain.
Wim
That would explain it! I did check that WD was showing “rain last hour” correctly, and SSGauges is showing “time of last rain” correctly, before I posted. . . but didn’t think to check the values in clientraw.txt.
http://swanston.maui.co.uk/clientrawhour.txt Those 60 fields also contain 0.3 mm
361 rain total last 60 min for min 01 M 0.3 mm ( = 0.012 in )
362 rain total last 60 min for min 02 M 0.3 mm ( = 0.012 in )
363 rain total last 60 min for min 03 M 0.3 mm ( = 0.012 in )
It seems that all those “rain-minute” “rain-hour” fields all contain cumulative values, but Brian has to confirm that.
Wim
To get the graphs to work using WU where do I set the API key, Do I place it in the dark weather section?
I see the station name for WU not a spot to add my API key.
Also moon rise moon set does not match WD using same lat/long
You do not need an WU API-key. Your own data was always available without any key, your station ID is the only id needed.
The current WU-API-key was/is used to load the WU forecast for your area. That is now the DarkSky forecast with the DarkSky API-key.
[li]On February 15th
all “rules of the game” will change[/li][li]WU will switch to new API-keys for all access including our own station data.[/li][li] But at this moment there is no documentation or description how we can load our stations data over a longer period then 7 days.
[/li]
[/ol]
So for now and at least until Feb 15, all graphs should work with your WU-station data. Just set the correct station-key usinge easyweather.
Wim
To check this out, I need the URL of your pwsWD/ folder.
And can you please post your latitude / longitude as you set in WD and in Easyweather? I con not check these myself as settings are protected from spying eyes.
Be aware that WeatherDisplay uses a minus for latitude east of Greenwich (f.i. Europe).
Other programs use the standard minus for west of Greenwich (f.i. the USA).
Also be aware that moon data can be confusing since the rise and set seen on one calendar day may be from two different moon cycles, see this recent thread.
The date-time seemed to be in “UTC” for other test-sites. Now it is in local as far as i can see.
Try this script for a few days, I changed only line 93 from gmdate() to date()
As the time difference here in wester Europe between UTC and local is small, this error was not found when testing.