CityGML: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:


CityJSON is a different exchange format which uses the same underlying data model as CityGML. Both formats can be imported into the {{software}}.
CityJSON is a different exchange format which uses the same underlying data model as CityGML. Both formats can be imported into the {{software}}.
==Supported Types==
Currently the {{software}} supports the import of the following modules of the CityGML standard:
* Building (and class BuildingPart)
* Bridge ( and class BridgePart )
* CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)


{{article end
{{article end
|notes=
|notes=
*Currently the {{software}} supports the import of the following modules of the CityGML standard:
** Building (and class BuildingPart)
** Bridge ( and class BridgePart )
** CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)
:Other modules are not read when importing with the [[Geo Data Wizard]].
:Other modules are not read when importing with the [[Geo Data Wizard]].



Revision as of 10:49, 7 February 2024

CityGML is an open standardised data model and exchange format to store digital 3D models of cities and landscapes. It defines ways to describe most of the common 3D features and objects found in cities (such as buildings, roads, rivers, bridges, vegetation and city furniture). It supports several levels of details and supports materials and textures. 3D features have standardized attributes based on their type (building, road, bridge) and support additional user attributes.

CityJSON is a different exchange format which uses the same underlying data model as CityGML. Both formats can be imported into the Tygron Platform.

Supported Types

Currently the Tygron Platform supports the import of the following modules of the CityGML standard:

  • Building (and class BuildingPart)
  • Bridge ( and class BridgePart )
  • CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)


Notes

Other modules are not read when importing with the Geo Data Wizard.
These 3D Models will be stored in the project as Custom Geometries. These Custom Geometries can be automatically assigned to buildings present in the project based on their location.

How-to's

See also