⭐ Weather.com - Parsing the V3 JSON

[jsmorley]

Ha ha, unfortunately the parsing part is out of my league but at least I did manage to point out the problem...

Yes, you certainly did. Check the new .rmskin in the first post.

[Pflosch]

Yeah, the whole en-GB thing throws a new wrinkle into this. Before, it felt safest to use en-GB to get "metric" instead of en-US to get "imperial", as the language-based text should be pretty similar. With the new "hybrid" units of measure they use for en-GB, it might be much safer to use en-CA or en-AU or something, to get pure "metric", while having some hope that the text and phrases used will be familiar to a US English speaker.

Yes, as usual, you nailed it.
If I switch to en-CA, both work correctly, the speeds and the pressure.
Thanks heaps.

[VClouds]

Yes, you certainly did. Check the new .rmskin in the first post.

Great I will check it out, thanks!

[Yincognito]

Ha ha, unfortunately the parsing part is out of my league but at least I did manage to point out the problem...

Yeah, no worries - identifying the problem is no doubt the first step in solving it.
Personally, I admit not checking the regexes in jsmorley's skin, since I don't use them - shame on me.

[xenium]

xxenium is with some of his still parsing the HTML from the site, and I expect there could be some subtle differences between the HTML and the JSON.

My skin uses JSON, it no longer uses HTML.

[jsmorley]

My skin uses JSON, it no longer uses HTML.

I think that particular person might be using one of the older skins you haven't changed yet. Not sure.

Let me know when you get all your excellent skins fully corrected, so I can indicate that on the thread that lists them.

[Yincognito]

By the way, just in case it is needed, a (so far) foolproof way of handling commas in the string values, without affecting other non-string ones:

Code: Select all

(?:[^"]*|(?:(?:\\"|[^"])*"){2}),

You can, of course, replace the comma at the end with a more comprehensive form of the delimiter at the end of the value:

Code: Select all

(?:,|\{|\[|\]|\}|$)

By the way, this handles the escaped quotes (i.e. \") in the string value as well (the job of converting them to literal quotes is another matter, naturally), according to the JSON specification. I'm using these patterns as variables, to simplify the code.

Again, only if you need it.

[jsmorley]

By the way, just in case it is needed, a (so far) foolproof way of handling commas in the string values, without affecting other non-string ones:

Code: Select all

(?:[^"]*|(?:(?:\\"|[^"])*"){2}),

You can, of course, replace the comma at the end with a more comprehensive form of the delimiter at the end of the value:

Code: Select all

(?:,|\{|\[|\]|\}|$)

By the way, this handles the escaped quotes (i.e. \") in the string value as well (the job of converting them to literal quotes is another matter, naturally), according to the JSON specification. I'm using these patterns as variables, to simplify the code.

Again, only if you need it.

We will see if we run into trouble. So far at least, it seems to handle commas in strings just fine.

1.jpg

[VClouds]

Yes, you certainly did. Check the new .rmskin in the first post.

Downloaded and replaced your updated templates and the conditions are fixed.
now Fair is Fair and not Partly Cloudy...
Thanks!

[jsmorley]

Downloaded and replaced your updated templates and the conditions are fixed.
now Fair is Fair and not Partly Cloudy...
Thanks!

Fair enough...