Predefined time steps that can be referenced from other config files
Predefined time step that can be referenced from other config files.
Especially useful for verbose time step definitions. E.g. time steps with a time zone.
It is comparable with a global property, it makes no difference to use the global time step or the verbose time step
Since 2014.01. A timeStep that defines a pattern of times in a week. This pattern will be repeated every week
A timeStep that defines a pattern of days in a month. This pattern will be repeated every month. Each day in the month can have a different aggregation period. The start of the aggregation period is exclusive and the end of the aggregation period is inclusive.
A timeStep that defines a pattern of dates in a year. This pattern will be repeated every year. Each date in the year can have a different aggregation period (season). The start of the aggregation period is exclusive and the end of the aggregation period is inclusive. This yearlyTimeStep is meant for seasons, therefore limited to four dates. If more than four dates in a year are required, then either use the monthlyTimeStep or use the monthDays option in the timeStep element instead of this yearlyTimeStep.
Optional time zone for dates and times defined in this timeStep. If no time zone is defined, then dates and times are in GMT.
Identifier of this timeStep.
Short name for the time step which is shown to the user when he can chose one from a list.
Optional time zone for dates and times defined in this timeStep. If no time zone is defined, then dates and times are in GMT.
Define a day for this timestep. For each month this day will be included in the timestep. This monthlyTimeStep is limited to six days. If more than six days in a month are required, then please use the daysOfMonth option in the timeStep element instead of this monthlyTimeStep.
Identifier of this timeStep.
Short name for the time step which is shown to the user when he can chose one from a list.
Optional time zone for dates and times defined in this timeStep. If no time zone is defined, then dates and times are in GMT.
One or more dates in a year for which data values can be stored when this timeStep is used. These dates will be repeated every year. Each date in the year can have a different aggregation period (season). The start of the aggregation period is exclusive and the end of the aggregation period is inclusive. This yearlyTimeStep is meant for seasons, therefore limited to four dates. If more than four dates in a year are required, then either use the monthlyTimeStep or use the monthDays option in the timeStep element instead of this yearlyTimeStep.
Identifier of this timeStep.
Short name for the time step which is shown to the user when he can chose one from a list.
The day for a data value. The time is 00:00:00 hours at the start of the day (in the configured timeZone).
The day of the start of the aggregation period for the data value. The time is 00:00:00 hours at the start of the day (in the configured timeZone). The start of the aggregation period is exclusive.
The day of the end of the aggregation period for the data value. The time is 00:00:00 hours at the start of the day (in the configured timeZone). The end of the aggregation period is inclusive.
The month and day for a data value. The time is 00:00:00 hours at the start of the day (in the configured timeZone).
The month and day of the start of the aggregation period (season) for the data value. The time is 00:00:00 hours at the start of the day (in the configured timeZone). The start of the aggregation period is exclusive.
The month and day of the end of the aggregation period (season) for the data value. The time is 00:00:00 hours at the start of the day (in the configured timeZone). The end of the aggregation period is inclusive.