Some thought about the case of more than one data source

87 views
Skip to first unread message

Karen K

unread,
Feb 21, 2024, 1:26:39 PM2/21/24
to weewx-development
I read the roadmap.md file and I saw the item about supporting more than one driver at the same time.

So there are some thoughts.

Some people not only have one single weather station but different sources of data to process. That could be:
  • additional hardware (measurement devices)
  • measurements from other locations in the neighborhood
  • data received from governmental services to use for comparison purposes like this.
Some of those data sources deliver their readings with some delay but include a timestamp. Or they provide an update to a previously sent reading after performing quality checks. In all those cases data do not arrive within the archive interval they belong to. This involves updating database records and summaries. 

I have got that case about governmental data and I actually work around the limitations by
  • not using addRecord() for writing into the database
  • using the binding for reading the database only
  • writing to the database like this.
The disadvantage of that solution is, that the DaySummaryManager cannot be used.

Updating a database record is not only a question of importing. It is also required if you want to use data that arrive with some delay and include a timestamp of their own.

Tom Keffer

unread,
Feb 21, 2024, 7:42:43 PM2/21/24
to Karen K, weewx-development
The method addRecord() now has an "update" parameter, making it possible to update old records. To appear in V5.1.


--
You received this message because you are subscribed to the Google Groups "weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/12bc601f-220d-4cfd-87c5-e4e956882a1bn%40googlegroups.com.

Karen K

unread,
Feb 22, 2024, 1:22:43 AM2/22/24
to weewx-development
What I understood about the "update" parameter is, that it is intended to fill in observation types that are None before. 

What about updating a reading that - for example - set the maximum value in the daily summary, and the updated value is lower than before?

Tom Keffer

unread,
Feb 22, 2024, 6:09:53 PM2/22/24
to Karen K, weewx-development
This is a good point. Gary is going to give it a rethink.

Thanks for pointing this out, Karen.

On Wed, Feb 21, 2024 at 10:22 PM Karen K <kk44...@gmail.com> wrote:
What I understood about the "update" parameter is, that it is intended to fill in observation types that are None before. 

What about updating a reading that - for example - set the maximum value in the daily summary, and the updated value is lower than before?

--
You received this message because you are subscribed to the Google Groups "weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-developm...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages