Skip to content
Documentation

Quotations

Time series quotations allow users to relate data points to a specific quotation timestamp of their choice. Time series data can be stored independently for each quotation timestamp.

Essentially, a single time series is divided into several sub time series, with the quotation timestamp acting as the unique key for the sub time series.

flask Weather forecast quotations

Section titled “ Weather forecast quotations”

A real world example for quotations is weather forecast data. Consider hourly temperature predictions for a specific day. The quotation timestamp represents when the forecast was issued. Each time a new forecast is issued (e.g., Monday morning, Monday afternoon, Tuesday morning), it predicts the same hours but often with different values. For the same timestamp (e.g., 14:00 on the predicted day), different quotations (forecasts) may have different temperature values. Using exact retrieval would return only the specific forecast, while not-exact retrieval would fill missing hours from the most recent available forecast.

Three hourly temperature forecasts issued Monday 08, Monday 14 and Tuesday 08 predict different values for the same timestamp, for example 18 °C, 20 °C and 19 °C at 14

For quotation time series it is also possible to select whether audit logs and historical records should be stored or not by setting the properties PreserveAuditLog and PreserveHistoricData on the time series.

As mentioned above, each quotation date can be interpreted as a sub time series and therefore has its own independent historization. For more information on this topic, see Audit and Historization.

When reading quotation data, a quotation date can optionally be given and it can also be specified, if the returned time series consists only of the given quotation date or if it is a combination of multiple quotations (exact/not-exact). If no quotation date is given, the quotation default behavior of time series comes into play, which is used to determine which quotation data is fetched. This property can be changed at any time on the time series.

In order to retrieve only values for a specific quotation date, time series data can be requested with the option “exact”. In case data points are missing within the given time range, the value 0 with flag “Missing” will be returned.

When reading data by a not-exact quotation date, the returned time series is combined by possible multiple quotations in case of missing data. So if a data point is missing within the given time range, the data point from the nearest quotation from the past will be taken.

The quotation default behavior can be set on the time series and in the HAKOM.xml configuration file and can have the following possible values:

Value Description
MaxExact The latest quotation date for which data is available in the readout time range is determined. Only the data of this quotation are read out.
MaxNotExact The data with the latest quotation time is read out. Different quotations can be loaded in individual time ranges.
NowNotExact Like MaxNotExact, but no quotations from the future are loaded.

If no quotation default behavior is set on the time series, the behavior is as defined in the HAKOM.xml by the administrator.

© 2026 Volue.Version v0.6.38017 November 2026