***closed*** weather34 for WeatherDisplay (clientraw and WDapi)

I think you misunderstood the definition of “beta” test or, English is not my native language, it was me who misunderstood it.

I can only assume that your current weather-website has all these errors already solved?
But when I checked, the same remarks are there also. It would be more polite to post “wishes” in the wish-list topic.

This WD34 April version includes 3 weather-alarms, WXSIM is back, Canadian text forecast are included and about 40% of the html errors are removed. And one former WD, now WC user, wanted to continue to use so the Cumulus/WC/Weewx users can now choose between 2 versions.

For every new release of this “WD” version, all user remarks will get sorted and according to my available time, they will be implemented.

Therefor, please try to help this programmer find the errors and omissions, do not waste my time with large lists of discussion points.

Wim

P.S. :oops: #-o :oops:
Sometimes my words sound to harsh. Sorry, So as an example, it took 4 hours to modify the contact-popup (bio-popup) .
It now hides twitter if there is no twitter-account (took approx. 5 minutes).

But it also has no html errors anymore, that took 80% of the time and as I hate unnecessary info, you can remove the links also from the pop-up and that plus testing took the remaining time.

https://validator.w3.org/nu/?doc=http://weather.skybase.net/pwsTEST/bio_popup.php => checking ends with fatal after 8 errors

https://validator.w3.org/nu/?doc=http://wd34.weather-template.com/pwsTEST/bio_popup.php no html errors

There are still numerous CSS errors but they will be removed in the June release.
Demo: the pwsTEST/ version has the links visible. The pwsWD/ version shows no links, still the areas are clickable.

Shouldn’t there be a facebook account added also?


bio_popup.php.zip (5.63 KB)

My appologies, I didn’t know about the “wishes” list - I will post future RFE’s there. :slight_smile:

Thats Ok, we all appreciate the effort you are doing to create this template and understand that it can be frustrating at times.

regards

Tim

Just a little off-topic :wink:

@TSL and all users of abbreviations in their posts

The WW forum caters for an international public with a lot of Dutch, Spanish, Italian, Korean a.s.o visitors.
Maybe English is “spoken” all over the world when one is on vacation, but please refrain from using abbreviations such as RFE as for over ?50%? of the forum visitors English is NOT their native language.

All those non-native speakers often use translate.google.com But that tool only knows that “RFE” is not English but it uses" Translate from: Haitian Creole" So when I read your post, I assumed it was a typo and ignored it, because my brain knows what it stands for. But my brain got it wrong, it was essential information and it seemed to mean for @TSL and maybe other native english speaking software professionals: “Request for Enhancements”

For me, as an older European person, it definitely stands for RadioFreeEurope, for immigrants to the US => Request For Evidence (RFE)
The other meanings for RFE => RFE - Wikipedia

A search for RFE on this forum yield 33 results of the rfe letters as (part of) a word in posts. Only the last one, the only one with the rfe as a separate word is this topic.

IMHO IWBW NTU abbreviations when we want to make our point.
Wim

keep up the good work Wim
we all appreciate your dedication :smiley:

My apologies again ! #-o

As for myself, I work for one of the top computer companies in the world with 135,000+ employees in over 300 countries and the term RFE ( Request for Enhancement ) has always been understood in any conversation I’ve had with anyone anywhere and is considered universal.

That being said … I shall refrain from using any abbreviations in future outside of the work environment in this forum :smiley:

regards

Tim

Something funny in the Nearby metar pop-up this morning. . . Is this a CheckWX problem?


Metar.PNG

Suddenly all metar pop-ups, old or new, show a date of 1-1-1970 UTC and an error message when error reporting is on.
And you are the first to notice it? Thanks :smiley:
First make a copy of the current script and please test this version,
Wim

P.S. “Is this a CheckWX problem” => yes
The date field in the json file now contains something more then the expected string:

"observed":"17-02-2019 <span class=\"tx-light tx-12\">@<\/span> 11:00Z",

metar_popup.php.zip (7.11 KB)

New version shows the wrong time: 00:20 am instead of 1120Z (UTC).

. . . and later 00:50 am instead of 1150Z.


Metar2.PNG

Yes the invalid data is still there, so the time fields are more or less valid.
The “garbage in” results in “garbage out” for the time field, but without large error messages.
The unexpected values are still there, but shorter

"observed":"17-02-2019 @<\/span> 12:00Z"

Second beta version April release ready for download.
Read more at and download from http://wd34.weather-template.com/beta.php

Comments welcome at HWS-template (WD34) beta test topic

Do not update the beta releases, just remove old folder and test the new one from scratch, thanks
Wim

So there is nothing I can do about it?

i assume it will go away, but I modified the script a bit and see if this removes the extra unneeded characters.

Wim


metar_popup.php.zip (7.1 KB)

That’s looking good. Thanks, Wim.

Thought I’d contact CheckWX anyway, here’s their reply:

“Thanks for bringing this issue to our attention. It has been corrected.
I apologize for the inconvenience and thank you for using CheckWX”

Thanks :smiley:

It may be that Dutch is the only language file with that phrase, it doesn’t appear, e.g., in the current French or German language files. . . I haven’t checked them all. In French and German the entries are just |language|choisir… or |language|sprache

Looks like the metar34.txt has changed again the popup gives error 500 in IE11 and edge says something about humidity and line 103 in the metar_load_funct.php it was ok early this morning
http://www.hc-iom.co.uk/pwsWD/index.php

{“results”:1,“data”:[{“icao”:“EGNS”,“name”:“Isle of Man”,“observed”:“21-02-2019 @ 16:50Z”,“raw_text”:“EGNS 211650Z 15009KT 9000 FEW006 10/08 Q1023 NOSIG”,“barometer”:{“mb”:1022.92,“hg”:30.21,“kpa”:102.29},“clouds”:[{“code”:“FEW”,“base_feet_agl”:600,“base_meters_agl”:600,“text”:“Few”}],“dewpoint”:{“celsius”:8,“fahrenheit”:46},“elevation”:{“feet”:55.77,“meters”:17},“flight_category”:“VFR”,“humidity”:{“percent”:88},“temperature”:{“celsius”:10,“fahrenheit”:50},“visibility”:{“miles”:“559”,“miles_float”:5.59,“meters”:“8,996”,“meters_float”:8996.23},“wind”:{“degrees”:150,“speed_kts”:9,“speed_mph”:10,“speed_mps”:5}}]}

Yes they changed the API and the humidity was a string “humidity”: 88, is now an array: “humidity”:{“percent”:88}

Attached new version of script for the normal release pwsWD! Do not for beta test pwsTEST.

Wim


metar_load_funct.php.zip (3.66 KB)

Metar pop-up working OK here in Chrome, Edge and IE11.

No, it’s not! Pop-up is working, humidity isn’t. . . Sorry #-o

Not anymore at 21:25 CET,
Wim


metar.jpg