For WU, the cloud icon is now calculated from cloud cover percentage.

You’ll need to pull head.

> On Aug 23, 2020, at 3:48 PM, John Kline <[email protected]> wrote:
> 
> 
> WU does have a cloud cover percentage, so this will work.  Thanks.
> 
>>> On Aug 23, 2020, at 3:44 PM, steeple ian <[email protected]> wrote:
>>> 
>> 
>> <Untitled.png>
>> 
>> 
>> 
>>> On Sun, 23 Aug 2020 at 22:45, John Kline <[email protected]> wrote:
>>> What do you propose I put in for clouds in the cases you mention?
>>> 
>>> The choices are:
>>> 'CL': 'Clear',
>>> 'FW': 'Few Clouds',
>>> 'SC': 'Scattered Clouds',
>>> 'BK': 'Broken Clouds',
>>> 'B1': 'Mostly Cloudy',
>>> 'B2': 'Considerable Cloudiness',
>>> 'OV': 'Overcast',
>>> 
>>>>> On Aug 23, 2020, at 12:45 PM, Vetti52 <[email protected]> wrote:
>>>>> 
>>>> 
>>>> 
>>>> wxPhraseShort      
>>>> 0  null
>>>> 1  "Showers"
>>>> 2  "Rain"
>>>> 3  "P Cloudy"
>>>> 4  "PM Lgt Rain"
>>>> 5  "Light Rain"
>>>> 6  "Rain/Wind"
>>>> 7  "Shwrs Early"
>>>> 8  "M Cloudy"
>>>> 9  "M Cloudy"
>>>> 10 "Showers"
>>>> 11 "Showers"
>>>> 
>>>> That is, what the API returns right now.
>>>> the forecast shows (just look at the icons)
>>>> Mo
>>>> 24 Aug             19
>>>> 10 13-14   06:12:54
>>>> 20:28:16   13:16:00
>>>> 22:53:04   33%     90% 
>>>> 8,89  
>>>> 
>>>> 
>>>> 07:00
>>>> 
>>>> 19 14 
>>>> 
>>>> 13:16:00   
>>>> 90% 
>>>> 8,89  
>>>> 
>>>> 19:00
>>>>    10      13 
>>>> 20:28:16   22:53:04        
>>>> 20% 
>>>> 
>>>> 
>>>> Di
>>>> 25 Aug     
>>>> 21
>>>> 10 14-21   06:14:42
>>>> 20:25:55   14:41:38
>>>> 23:17:51   44%     70% 
>>>> 4,06  
>>>> 
>>>> 
>>>> Mi
>>>> 26 Aug     
>>>> 18
>>>> 10 27-32   06:16:30
>>>> 20:23:34   16:03:24
>>>> 23:50:02   55%     90% 
>>>> 9,65  
>>>> 
>>>> 
>>>> Do
>>>> 27 Aug             19
>>>> 10 13-21   06:18:17
>>>> 20:21:12   17:17:11
>>>> 00:32:33   66%     20% 
>>>> 
>>>> 
>>>> 
>>>> 07:00
>>>>    19      21 
>>>> 
>>>> 17:17:11   
>>>> 10% 
>>>> 
>>>> 
>>>> 19:00
>>>>    10      13 
>>>> 20:21:12   
>>>> 
>>>> 20% 
>>>> 
>>>> 
>>>> Fr
>>>> 28 Aug     
>>>> 19
>>>> 10 13-16   06:20:05
>>>> 20:18:49   18:18:50
>>>> 00:32:33   76%     60% 
>>>> 6,10  
>>>> 
>>>> 
>>>> WU forecast for geocode=54.09,10.26 issued on 23-Aug-2020 21:10 
>>>> report generated in 0.175 s
>>>> 
>>>> 
>>>> You can see two entries, first for today at 19:00 "mostly cloudy", and the 
>>>> second one on Thursday "considerable cloudiness" all day. What about 
>>>> showers and rain/wind and all the others? Rain without clouds? I am 
>>>> confused.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>  Hope, I could demonstrate it.
>>>> 
>>>> 
>>>> Am Freitag, 21. August 2020 16:45:38 UTC+2 schrieb John Kline:
>>>>> 
>>>>> As your incorporating this into your Seasons skin, it makes sense to 
>>>>> remove (from the .inc files) the data that is not provided by WU (e.g., 
>>>>> dew point).
>>>>> 
>>>>> You should have a look at what’s coming back from WU by using the 
>>>>> following URL (assuming you are using the default–station’s lat/long–for 
>>>>> the forecast).  Do substitute your api key for the XXX.
>>>>> 
>>>>> https://api.weather.com/v3/wx/forecast/daily/5day?geocode=37.431495,-122.110937&format=json&units=e&language=en-US&apiKey=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>>>> 
>>>>> Let me know if you think something in the WU forecast returned from the 
>>>>> above URL is amiss in the forecast extension.  Note: there is plenty in 
>>>>> what WU sends that has no place in the forecast extension schema.
>>>>> 
>>>>> 
>>>>>>> On Aug 21, 2020, at 7:32 AM, Vetti52 <[email protected]> wrote:
>>>>>>> 
>>>>>> 
>>>>>> Finally, I managed to install the latest release also. I used WU Api key 
>>>>>> and it works nicely. I find it much easier to integrate it into the 
>>>>>> season skin as a wiget than as iframe. I do not get iframes sized 
>>>>>> correctly for tablet or smartphone displays. The wigeds look much 
>>>>>> better. And, as the forecasts are produced just like a separate web 
>>>>>> site, it would be easier to integrate one of the html files into the 
>>>>>> season skin than to take it from the WU web site. Moreover, as there are 
>>>>>> ready to use *.inc files, it is pretty easy to introduce these as 
>>>>>> widgets. I followed the forecasting wiki  forecast data in the Season 
>>>>>> skin. I am considering to add more than one *.inc file, as soon as I am 
>>>>>> satisfied with the results. This is only described for the Standard 
>>>>>> skin, but I hope, it will work in the Season skin as well. 
>>>>>> Meanwhile, there are some things I don't understand:
>>>>>> single table has a toggle on the the date column (onclick toggle_hours), 
>>>>>> but without any action.
>>>>>> multiple tables toggles hours as expected, but has an extra column for 
>>>>>> dewpoint, which has no values (N/A)
>>>>>> single strip horizontal has not date line, only hours, and three 
>>>>>> temperature lines, one of them may be dew point? There is an empty 
>>>>>> windspeed line, maybe for gust data?
>>>>>> single strip vertical is exactly the same, except that the icons for 
>>>>>> clouds are double sized and blow up the matrix. 
>>>>>> And why isn't there a cloud prediction for all days? In my case, it only 
>>>>>> occures once, but this may be WU specific.
>>>>>> The rest of the examples look fine to me, besides that there are no 
>>>>>> tides available for the North Sea. Looking at 
>>>>>> https://flaterco.com/xtide/faq.html#60 I have learned, that tides are no 
>>>>>> longer maintained outside of US, since early 2012. Maybe the forecast 
>>>>>> documentation could need an update, meanwhile...
>>>>>> 
>>>>>> 
>>>>>> Am Dienstag, 18. August 2020 14:39:09 UTC+2 schrieb [email protected]:
>>>>>>> 
>>>>>>> The latest release, v3.4.0b6 has resolved my issue above. Forecasts are 
>>>>>>> now being generated along with tides. Thank you for updating!
>>>>>>> 
>>>>>>> -Troy
>>>>>> 
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>> an email to [email protected].
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/ffa219fd-0a10-4283-8605-032932e27503o%40googlegroups.com.
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/01173606-c326-4707-ae56-d8d11b3fcdd8o%40googlegroups.com.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/B902B523-1F3D-43BF-8DD0-A2EEE4D2B7EB%40johnkline.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CADASSaScMJUyVsTX0eCtb4YB1bQ5m8qLzKFKtVmESaVOnB3Czg%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6A1A11CA-AC93-471A-B5A9-37C36ADA447C%40johnkline.com.

Reply via email to