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
  • #143

Closed
Open
Opened Aug 07, 2017 by Moritz Robert Lauster@mlausterMaintainer

Stereotype of OfficialAreaReferenceValue and VolumeTypeValue

Created by: JoachimBenner

From my point of view, there is an inconsistancy in the modelling of OfficialAreaReferenceValue (Entries: NetFloorArea, GrossFloorArea, EnergyReferenceArea, Stereotype CodeList) and VolumeTypeValue (Entries NetVolume, GrossVolume, EnergyReferenceVolume, Stereotype Enumeration). I see no reason to use different modelling concepts and therefore propose to define Enumerations in both cases.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: energyade/citygml-energy#143