...
| no data stored in database (also when looking outside of the view period) |
| only missing values available in view period |
| only missing values available in view period for some time series (configurable since 2011_02; see someSeriesCompletelyMissingIconVisible in Explorer.xml) |
| some missing values available in view period |
| soft validation limit exceeded |
| hard validation limit exceeded |
| data edited or interpolated |
| Info |
|---|
Although the icon descriptions are always true, there are some common assumptions that are not always correct. Following are some examples and an elaboration with details why it's not true. -"If a timeSeries contains only missing values (also when looking outside of the view period), it will have a purple cross". In most cases this is true because missing values are not This often results from the missing values not being stored in the database but deduced (but are deduced (i.e, for an equidistant time steps). However, missing values that are the result of a manual adjustment are stored int in the database. -"If a timeSeries has a red cross, there are some values available, just not in this view period". The only reason a red cross is not a purple cross is because there is data stored in the database (for the timeSeries). But besides values there is also other data stored for a timeSeries like expired forecasts or the example shown above. These two "data" examples are not an exhaustive list and is not meant to be, just to show that this assumption is not correct. -"A red cross means I will see no data in the timeSeries display (or the other way around)". The selected filter determines the view period that is used to determine which data availability icon should be shown. This view period configured for a filter does not have to be the same as the view period for the timeSeries displayed in the timeSeries Dialog. If the relative view periods are the same, then the assumption can be used. |
...