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
  • #96
Closed
Open
Issue created Mar 29, 2016 by Moritz Robert Lauster@mlausterMaintainer

Additional attribute status in EnergyDemand

Created by: JoachimBenner

The featureType EnergyDemand can be used either to provide input data for energy demand simulations or to represent the output data of these simulations. At the moment, EnergyDemand has no property to indicate whether the property energyAmount carries input data or simulation results.

Proposal

  1. Introduce a new (mandatory?) property status of EnergyDemand with property values defined by an enumeration
  2. Introduce a new enumeration EnergyDamandStatusValue with items: Simulated, Measured, Estimated, Unknown (must be discussed)
Assignee
Assign to
Time tracking