On Sunday, April 14, 2019 at 9:27:40 AM UTC-4, vigilancewx wrote: > > Multiple bindings > >> i'm afraid that multiple bindings will not help you in this case. as gary pointed out, the forecasting schema is not at all like the typical weewx observation schema. the typical weewx observation schema has columns like this:
dateTime, usUnits, interval, barometer, pressure, altimeter, ... the forecast schema has a record for each forecast period, like this: method, usUnits, dateTime, issued_ts, event_ts, duration, location, ... complete details about the design are in the 'Database Schema' section of the forecast.py source code. that shows how the data from each forecast service (WU, USNWS, UKMET, darksky, etc) map onto the forecast schema. the schema is designed to be generic so that it can handle *any* forecast source - that makes it possible to compare forecasts, or change to a new one when the one you used to use goes away. when you need to display the data in your weewx reports, there is a search list extension called ForecastVariables that provides access to the forecast data. there is a short example of how to do this in the wiki page that gary referred to. there is a detailed enumeration of variables in the comments in the forecast.py source code. and there are many, many examples of how to use the variables in the .tmpl files that come with the forecast extension. m -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
