Meteobridge 2.8 (Mar 9 2016, build 9499), FW 1.4
Data Export: every full hour
Time Frame: current Day
Resolution: Minutes
Template: standard-iso (does same with standard-imp)
Through the day exports right up to the (every full) hour eg. @ 6am last data record is 06:00, @7am last data record is 07:00
At midnight last data record is 23:00 with this being the final file for Current Day
Probably is a result of what midnight means to current day 24:00 as in current day or 00:00 as in current day being in effect the next day. However the effect is a series of files for each day/date with only 23 hours of data.
Export - Dropping the hour before Midnight **rejected**
Moderator: Mattk
Re: Export - Dropping the hour before Midnight
I noticed a similar thing today, I have a sql insert command which is fired off every 10 mins to save data to a database, this morning I noticed that one of the saved parameters [rain0total.sumday] which I log to plot cumulative rain value resets at 00:00 (obviously) this means the last record of the day for that parameter, from 11:50 to 00:00 is lost. I'll have to think of another approach to save the rain data. I only noticed because we had a tremendous amount of rain over midnight and the values in the database did not tally with the Davis console.
Re: Export - Dropping the hour before Midnight
Sorry guys, this exactly works as designed.
It is not intended use to generate the data for a day every hour.
Wait until day has passed and then get data for "yesterday" which
will be complete 24 data sets. Please rethink your general approach.
when you need hourly updates, generate data for that passed hour on
every new hour. I am really wondering what masses of redundant data
you are going to produce here. Rethink your approach, it looks
seriously broken.
It is not intended use to generate the data for a day every hour.
Wait until day has passed and then get data for "yesterday" which
will be complete 24 data sets. Please rethink your general approach.
when you need hourly updates, generate data for that passed hour on
every new hour. I am really wondering what masses of redundant data
you are going to produce here. Rethink your approach, it looks
seriously broken.
Re: Export - Dropping the hour before Midnight **rejected**
I wouldn't say the approach is seriously broken but one has to keep in mind that MB effectively does not have a "midnight" even though some selections refer to midnight options as 23:59:59 + 1 second becomes 00:00 the next day even though there is a dual time consideration, midnight today or 00:00 tomorrow. Just something one has to keep in mind, been caught a couple of times now working around "midnight", which doesn't really exist with MB