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
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • energyade
  • citygml-energy
  • Issues
  • #130

Closed
Open
Created Dec 07, 2016 by Moritz Robert Lauster@mlausterMaintainer

Simulation results

Created by: JoachimBenner

I think the EnergyADE should be able to represent also the output data of simulation systems. At the moment, it is possible to include simulated energy demands into an EnergyADE file, but not, e.g., the simulated actual temperature of a Thermal Zone.

Because the ADE supports different types of simulations and mutiple simulation systems, it is quite difficult to model arbitrary simulation results. Therefore, I propose to start with a very simple and generic data type SimulationData: A text attribute describing the simulated quantity (e.g. actual temperature) and a Time Series with time dependent, scalar data. This data structure can be referenced by every city object (ADE attribute of _CityObject). In future versions of the standard, it might be extended for other types of simulation data, or for supporting references to data bases.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None