Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • CityDoctor2 CityDoctor2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CityDoctor
  • CityDoctor2CityDoctor2
  • Issues
  • #115
Closed
Open
Issue created Jun 27, 2025 by Riegel@alexander.riegelContributor

Relative Geometries are not correctly parsed

Summary

Implicit Geometries which reference a Relative Geometry are currently not being correctly parsed, leading to them missing their geometry.

Steps to reproduce

Open CityDoctor
Load a CityGML file or ZIP-Archive with an Implicit Geometry which references a Relative Geometry as prototype geometry

What is the current bug behavior?

For Files:
The file is loaded, however, the affected Implicit Geometries have no geometry.

For ZIP-Archives: CityDoctor gets stuck during the loading and throws a StackOverflowError

What is the expected correct behavior?

The file(s) are correctly loaded and the Relative Geometries referencing a Relative Geometry have their respectively transformed geometry.

Relevant logs and/or screenshots

Possible cause

Relative geometries get resolved via referencing the gmlid of the prototype geometry, however, the current parser implementation uses their geometry and respective top level feature for resolving.

Assignee
Assign to
Time tracking

Dies ist die Gitlab-Instanz des Transferportals der Hochschule für Technik Stuttgart. Hier geht es zurück zum Portal