In aggregate operations, does eagle consider 00:00:00 data to be part of the previous day or the subsequent day? The Campbell Scientific standard is that a 00:00:00 timestamp represents data that ends at midnight. For example, with hourly aggregates, the 00:00:00 timestamp represents the aggregation of all data between 23:00:00 to 00:00:00.. Therefore, the data actually belongs to the previous day, even though the timestamp (midnight) belongs to the subsequent day. If eagle treats 00:00:00 data as part of the subsequent day, the results are incorrect because they are offset by one hour. Please clarify.
Treatment of 00:00:00 data in aggregates
Posts 2 | Views 6 | browsing
The OPC specification for historic data access (which is used by eagle.io) regards a timestamp of 00:00 as the beginning of the current day. However, date ranges are always end-exclusive, so if you were to specify a range of 23:00 to 00:00, that signifies a request for all data up to, but not including, the 00:00 timestamp. In this case, the data specified by that range would indeed all belong to the previous day when compared to the 00:00 timestamp which belongs to the next day.