Well, I took forecast-table.inc for my Weewx site now. There is no dew
point column, although it is set to #set $forecast_source = 'WU', and the
inc file includes #set $show_dewpoint =
int($local_settings.get('show_dewpoint', $show_dewpoint))
The dew point column shows only in the multiple-tables.inc in the WU
section. I have not activated any other forecaster. So, should I delete the
global setting for dew point in multiple-tables.html.tmpl, rather than
removing it in forecast_table.inc?
Same with windGust, which also does not exist in the WU json file. In
contrast, multible tables contains a column for moon phase, but it does not
show anything. The two columns to the right are therefore shifted next to
moonrise. The header columns are not adjusted correctly, so that the sun
icon is slightly left to the sunrise/set column, the moon icon merely above
these data, the moon phase icon slightly left from the moonrise/set data
and the moon phase icon POP icon on the right border of these data. So, it
is somewhat confusing to coordinate the table.
The URL returns a 5day.json file, which does not show an entry for dewpoint
nor windGust, as far as I can configure. Indeed, there are plenty of
entries. I could detect 11 entries each in the section daypart:0:
temperature:, temperatureHeatIndex: , and temperatureWindChill. There are
two sections for moon phase: moonPhase and moonPhaseCode, which contain 5
entries each.
Today forecast-table shows at two places the B1.png icon, depicted as
"Mostly cloudy". The entries are for today and next thursday. I can not
find the corresponding data in the json file. The most promising entry
would be in
*narrative:*
0 : "Showers possible early. Lows overnight in the mid 50s."
1 : "Cloudy with showers and thunderstorms. Highs in the upper 60s and lows
in the mid 50s."
2 : "Showers possible. Highs in the mid 60s and lows in the low 50s."
3 : "Showers possible in the afternoon. Highs in the low 70s and lows in
the upper 50s."
4 : "Light rain and windy. Highs in the upper 60s and lows in the mid 50s."
5 : "Partly cloudy. Highs in the upper 60s and lows in the low 50s."
Mostly cloudy, however, does not occure anywhere in the json file.
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
>
> <https://api.weather.com/v3/wx/forecast/daily/5day?geocode=37.431495,-122.110937&format=json&units=e&language=en-US&apiKey=d8e258b8a134405ba258b8a134805b1e>
>
> 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.
>
>
>
--
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/31491044-d207-4219-9018-4c92f0d40795o%40googlegroups.com.
