HWS-template (WD34) July version available

blainec · 17 August 2019 19:00

bitsostring post:248:

It is in my script, but I am not using the latest version. . .

It is line 138 in the latest version, which puts back the UV estimate in front of rain, but correcting it might affect something else further down?
138 $break = '.
';

This is the version date mine has:
$scrpt_vrsn_dt = ‘w34_util_ccn.php|00|2019-04-25|’; #icons w34

bitsostring · 17 August 2019 19:07

And me. . . but latest version is

$scrpt_vrsn_dt = ‘w34_util_ccn.php|00|2019-06-29|’; # added UV | icons w34

See HWS-template (WD34) July version available - #32 by pwsdashboard - PWS Dashboard 2012 - Weather-Watch Forum

blainec · 17 August 2019 19:17

Wow, I missed that one. Thanks

meteolive57 · 18 August 2019 13:13

hello
i uploaded the latest version of the template
http://valdefench57sgz.franceserv.com/pwsWD/index.php
live data running with the WL 2.0 API
for graphs, my setup parameterized with WU
on the other hand the monthly charts are “out” and the annual ones are all stopped at 25; 07.2019 ??
Regards

pwsdashboard · 18 August 2019 14:59

That is a severe problem with WU. They are working on it, maybe they solve it or they kill it altogether.

Most stations have intermittent gaps in the .CSV downloads as they often contain partial data only. Your yearly data is only available until July 25.
https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=ILORRAIN49&graphspan=year&year&format=1
Yout “this month” data is empty file https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=ILORRAIN49&graphspan=month&year&month&format=1

Your other weather-websites are affected also, example => July 25
http://valdefench57sgz.franceserv.com/realtime/weather28/index.php?p=wsReports&lang=en&wp=MB#data-area

There are dozens of discussions about all WU problems at the WX-forum, most important one: Weather Underground Issues and Bug Tracking - Check here before posting

WIM

ms372591 · 18 August 2019 23:46

Have you heard anything from WU? Nothing has changed on my site.

blainec · 19 August 2019 02:39

I had a problem like this about 1 year ago. They never responded to my requests and about 3 months later, it was fixed

meteolive57 · 19 August 2019 13:37

I contacted WU support
the answer :

" [i]The URL you are using has been retired. It will not return reliable data.
If you are uploading data, you have access to the PWS API. You can download data via the API. Go to

bitsostring · 19 August 2019 18:58

Bit late now, but I can’t help wonder why the Dark Sky rain forecasts should be so drastically different between the Jan and July versions.

Same place, same time, same API key.

pwsdashboard · 19 August 2019 19:50

There was (maybe still is) some confusion about what the amount shown in the DarkSky file means.

=> SI units are as follows:
==> precipIntensity: Millimeters per hour. (also for UK2 units rain is in mm)

=> A data point object contains various properties, each representing the average of a particular weather phenomenon occurring during a period of time
==> precipIntensity: The intensity (in inches of liquid water per hour) of precipitation occurring at the given time.
So it is now assumed that for a day forecast the intensity is the average for 24 hours in mm, not in inches.
The scripts display the value from the day-record but multiplied with 24 to get the daily value.

Wim

pwsdashboard · 19 August 2019 19:59

[quote author=meteolive57 link=topic=68132.msg549442#msg549442 date=1566221834]
I contacted WU support
the answer :

" [i]The URL you are using has been retired. It will not return reliable data.
If you are uploading data, you have access to the PWS API. You can download data via the API. Go to

bitsostring · 19 August 2019 21:47

I had a look at the current documentation, and I agree that the data point objects are all defined in Imperial units - the default. However, it seems obvious that, if you request a response in uk2, you should get UK units returned. So there should be no confusion. I presume this is what you are assuming now.

So what was being assumed in January? I can not see any easy conversion factor.

EDIT: It has been pointed out that July rain ~ 6 x January rain :?

meteolive57 · 20 August 2019 06:47

re_thanks for the explanations ok so it is possible to work around the malfunction WU by running cron tasks following the installation instructions of the template? but do you also have to edit the files “34_cron_addtoyear.php” and “w34_cron_stationcron.php”? … for live data I use the WL 2.0 api
thank you in advance
Regards

pwsdashboard · 20 August 2019 06:58

You should run the w34_cron_stationcron.php every 5 minutes and the 34_cron_addtoyear.php at 23:55
The files will be created the first time the crons run.
The data will be loaded into the day file by the station cron.
The addtoyear will add 1 line to the yearly file and 1 line to the month file.

You normally never have to change any scripts.
In this case you should change your easyweather setting as in this screenshot.

Wim

pwsdashboard · 20 August 2019 07:08

bitsostring post:240:

Just noticed a problem in current conditions block: there is a point (full stop) after the windspeed units in “This hour” Wind-Gust forecast. Suggest deleting the point in w34_util_ccn.php - the last line shown here:
echo '</span> '.$windunit.PHP_EOL;
# rain
if (isset ($hourlyPrecipProb) )
     {  echo '.
';
Yes, I think you should do so.
Wim

Apologies: I have modified my original file so I can’t give line numbers, but I think it will be obvious.

meteolive57 · 20 August 2019 07:58

thnx ok i just did cron job scheduling …
I find a file “today.txt” in my folder ./chartsmydata
I’m waiting for the execution of the cron at “23:55” to see
normally it should work
Regards

today.txt (254 Bytes)

bitsostring · 20 August 2019 11:50

A quick look at the scripts showed that the January release was using the single value “precipIntensityMax” instead of the current “24 * precipIntensity”. . . problem solved.

pwsdashboard · 21 August 2019 09:41

For those who already want to switch from WU to your own graphs-data,
I wrote a smal script to convert the WU_CSV file in chartswudata/ to the data as used in chartsmydata/

The script will get your wuID from the easyweather settings, read the chartswudata/wuID.txt
and outputs chartsmydata/2019.txt and 2019_08.txt

I have no access to a WU.CSV file with imperial units, so maybe some USA user would be so kind to test it.

The graphs at https://www.weerstation-herent.be/pws07/ now use the converted wu data.

You have to set the easyweather setting to use your own data
AND run the w34_cron_addtoyear.php at 23:55 every day
AND rund the w34_cron_stationcron.php every 5 → 10 minutes, but most of you already use that cron.

PLEASE remove the script after use from your pwsXX/ folder, it has to run only once.

===

A lot of us are missing one or more groups of multiple days of data in their WU-CSV files.
This weekend I will write a small script to search the WU-api-database for those missing days in the converted file.

Wim

_cvt_wucsv.php.zip (2.71 KB)

meteolive57 · 22 August 2019 06:44

hello
thank you for the script i just did the test actually we found the files txt pr against in my case we return to the starting point … to go back, just delete the files in the folder “chartsmydata /”?
Regards

pwsdashboard · 22 August 2019 07:36

Not all problems are solved at WU, sometimes new problems arise also.
Your “old” WU.CSV contains data until July 25.
Your new WU-dashboard is missing far more days for July https://www.wunderground.com/dashboard/pws/ILORRAIN49/table/2019-07-1/2019-07-1/monthly
Also the August data is incomplete, missing august 12.
https://www.wunderground.com/dashboard/pws/ILORRAIN49/table/2019-08-1/2019-08-1/monthly

thank you for the script i just did the test actually we found the files txt pr against in my case we return to the starting point ... to go back, just delete the files in the folder "chartsmydata /"? Regards

The version of the script I posted yesterday, only converts the WU file without adding missing data. So yes, only the available data until July 25 was generated.

The new version (planned for this weekend) of the script reads the WU-api and tries to add missing days. I was glad to test that new script with your ILORRAIN49 data.
Attached the chartsmydata/ folder with all available from the .CSV and the WU-api history.

The only days missing are 2019-07-27 2019-07-28 and 2019-08-12
Unzip the folder and move only the 2019.txt and 2019_08.txt to your website => chartsmydata/ folder.

@ALL
Very strange, it seems that the new data base has it flaws also. There are more and different days missing in the dashboard as in the .CSV

I do need some other wu_ID’s with missing data to test with.
Post or PM me your wuID if you have missing data in the .CSV which, in your opinion, was uploaded correctly to WU in the past.

Wim

chartsmydata.zip (7.24 KB)

HWS-template (WD34) July version available

You should run the w34_cron_stationcron.php every 5 minutes and the 34_cron_addtoyear.php at 23:55 The files will be created the first time the crons run. The data will be loaded into the day file by the station cron. The addtoyear will add 1 line to the yearly file and 1 line to the month file.

You should run the w34_cron_stationcron.php every 5 minutes and the 34_cron_addtoyear.php at 23:55
The files will be created the first time the crons run.
The data will be loaded into the day file by the station cron.
The addtoyear will add 1 line to the yearly file and 1 line to the month file.