Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C citygml-energy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • energyade
  • citygml-energy
  • Issues
  • #95
Closed
Open
Issue created Mar 29, 2016 by Moritz Robert Lauster@mlausterMaintainer

Mandatory and additional properties for _TimeSeries

Created by: JoachimBenner

For the processing of time series (_TimeSeries), it is essential to know how the different values need to be interpreted, e.g. whether they represent the total amount of a measure value or a single value, whether the measure values are related with the preceeding or the succeding time interval, and whether it is feasible to interpolate between different values. This indispensible information can be stated with the property interpolationType of TimeValuesProperties, with actually is optional but should be mandatory.

In several use cases, the time series will be generated by "meters" (e.g. electricity or gas meters), and the values of the time series represent a "total amount" (InterpolationType InstantaneousTotal, PreceedingTotal or SucceedingTotal). The meters normally have a value different from zero at the starting time of the time series, and this starting value must be known to interpret the time series values.

Proposal

  1. Make property variableProperties of _TimeSeries mandatory
  2. Make property interpolationType" of *TimeValuesProperties mandatory
  3. Add optional property startValue (type Measure) to TimeValuesProperties
Assignee
Assign to
Time tracking