Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
C
citygml-energy
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • energyade
  • citygml-energy
  • Issues
  • #95

Closed
Open
Opened 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
v0.7.0
Milestone
v0.7.0
Assign milestone
Time tracking
None
Due date
None
Reference: energyade/citygml-energy#95