Go to town, take what you need, copy wholesale, whatever, as long as there's a nice set of working measures people can use (like you've done already). I just provided mine as a shiv for people stuck without working measures (like I was). Better there be a single file everyone can download and work with, so once yours are up I'll make sure to delete mine.jsmorley wrote: ↑June 5th, 2020, 12:25 pm The more the merrier really. I see that you have done some good work already on parsing the new V3 version of the JSON. I haven't looked at the new stuff really carefully yet, but it looks to me like there might be some new information that wasn't part of the old method. I want to be sure that as much as possible, we get everything that is available into a measure, so what is used and not used is up to the skin author.
I may well steal some of your RegExp as I work on this, I'll be sure to credit you when I do.
Maybe take the opportunity to make everythig slightly more consistent (like I suggested on page 23), for example in the forecast you call them "today", "day2", "day3", whereas with your moon measures you call it "day1", "day2" etc., which makes more sense.
I only utilized "getSunV3LocationPointUrlConfig", "getSunV3CurrentObservationsUrlConfig" and "getSunV3DailyForecastUrlConfig". Personally, I think air quality and pollen are overkill and hardly worth the effort. If you're striving for coverage, I'd prioritise hourly forecasts, those seem more useful.jsmorley wrote:This is the starting point for what I am looking at. These seem to be the relevant sections of the JSON.
As for Moon data, I included an updated V3 moon file in the zip on page 23, so maybe you can use that as a starting point (in fact its complete compared to your original moon measures).