Closed bsttsai closed 2 months ago
The TUM dataset violates the CityGML conceptual model. That's why it's not fully imported by citydb-tool.
The issue is not the geometry. gml:Surface
, gml:patches
, and gml:PolygonPatch
are all supported by citydb-tool.
The problem is caused by the core:boundary
elements which link tran:TrafficArea
and tran:AuxiliaryTrafficArea
boundaries to tran:Section
spaces. According to the CityGML 3.0 conceptual model standard, both boundary types are not allowed for sections (see here).
You can manually fix the dataset by replacing
<tran:Section>
<core:boundary>
<tran:TrafficArea>
...
</tran:TrafficArea>
</core:boundary>
</tran:Section>
with
<tran:Section>
<tran:trafficSpace>
<tran:TrafficSpace>
<core:boundary>
<tran:TrafficArea>
...
</tran:TrafficArea>
</core:boundary>
</tran:TrafficSpace>
</tran:trafficSpace>
</tran:Section>
Be careful to use tran:auxiliaryTrafficSpace
and tran:AuxiliaryTrafficSpace
instead to enclose the tran:AuxiliaryTrafficArea
boundaries in the dataset.
Thanks for pointing this out. We fixed the issue and updated the dataset.
Nice, thanks @ChBeil
@clausnagel Thanks for the explanations and solutions.
@ChBeil Thanks for updating the TUM dataset! now it works normally with the citydb-tool. Could you please also update the "CityGML3_Transportation_NYC" dataset in the same repository? as it has the same missing (auxiliary) traffic space issue to link with tran:Section
spaces.
Closing this isssue. Disucssion about fixing other datasets should take place in the TUM repository.
Hi, I'd like to inquire about an issue encountered when importing CityGML 3.0 test datasets into PostgreSQL.
I imported the TUM_citygml_V3.gml file using citydb-tool v. 0.7.1-beta, and no errors were seen in the log file. However, upon checking the feature and geometry_data tables, I found that the features' envelopes and geometries were missing—they were both empty.
To troubleshoot, I also tried importing the FZK Haus CityGML 3.0 test dataset from this link. In this case, the feature envelopes and geometries were imported correctly.
excerpt of FZK gml file:![image](https://github.com/3dcitydb/citydb-tool/assets/42941872/14e93f66-fb3e-41e8-b17d-9fc00a185095)
Steps to Reproduce
Environment
Citydb-tool version: 0.7.1-beta
Database: PostgreSQL
Operating System: MacOS Ventura 13.6.7
I appreciate any insights or suggestions on resolving this issue in advance. Thank you.