CityGML - Revision history

Maxim@tygron.com at 15:10, 4 March 2026

2026-03-04T15:10:41Z

← Older revision		Revision as of 15:10, 4 March 2026
Line 43:		Line 43:
	\|seealso=		\|seealso=
	* [[Custom Geometries]]		* [[Custom Geometries]]
			* [[IFC]]
			* [[SLPK]]
	\|references=		\|references=
	<references>		<references>

Maxim@tygron.com at 13:36, 4 March 2026

2026-03-04T13:36:22Z

← Older revision		Revision as of 13:36, 4 March 2026
Line 39:		Line 39:
	\|howtos=		\|howtos=
	* [[How to import 3D BAG data]]		* [[How to import 3D BAG data]]
	* [[How to import a CityGML/CityJSON file]]		* [[How to import a CityGML or CityJSON file]]
	* [[How to import a CityGML/CityJSON file for 2D Spatial data]]		* [[How to import a CityGML/CityJSON file for 2D Spatial data]]
	\|seealso=		\|seealso=

Rudolf@tygron.nl at 14:05, 17 October 2025

2025-10-17T14:05:50Z

← Older revision		Revision as of 14:05, 17 October 2025
Line 1:		Line 1:
	CityGML<ref>T. H. Kolbe, T. Kutzner, C. S. Smyth, C. Nagel, C. Roensdorf, C. Heazel ∙ OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard ∙ found at: [https://docs.ogc.org/is/20-010/20-010.html https://docs.ogc.org/is/20-010/20-010.html] (last visited 2024-02-07)</ref> is an open standardized 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.		CityGML{{ref\|citygml}} is an open standardized 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 {{software}}.		CityJSON is a different exchange format which uses the same underlying data model as CityGML. Both formats can be imported into the {{software}}.
Line 44:		Line 44:
	* [[Custom Geometries]]		* [[Custom Geometries]]
	\|references=		\|references=
	<references/>		<references>
			{{ref\|citygml
			\|name=OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard
			\|author=T. H. Kolbe, T. Kutzner, C. S. Smyth, C. Nagel, C. Roensdorf, C. Heazel
			\|page=
			\|source=
			\|link=https://docs.ogc.org/is/20-010/20-010.html
			\|lastvisit=2024-02-07
			}}
			</references>
	}}		}}


	{{GeoDataOverview}}		{{GeoDataOverview}}
	[[Category:CityGML]]		[[Category:CityGML]]

Maxim@tygron.com at 10:10, 8 October 2025

2025-10-08T10:10:09Z

← Older revision		Revision as of 10:10, 8 October 2025
Line 41:		Line 41:
	* [[How to import a CityGML/CityJSON file]]		* [[How to import a CityGML/CityJSON file]]
	* [[How to import a CityGML/CityJSON file for 2D Spatial data]]		* [[How to import a CityGML/CityJSON file for 2D Spatial data]]
	* [[Converting a Sketchup model to CityGML format‎‎]]
	\|seealso=		\|seealso=
	* [[Custom Geometries]]		* [[Custom Geometries]]

Maxim@tygron.com at 09:59, 8 October 2025

2025-10-08T09:59:40Z

← Older revision		Revision as of 09:59, 8 October 2025
Line 42:		Line 42:
	* [[How to import a CityGML/CityJSON file for 2D Spatial data]]		* [[How to import a CityGML/CityJSON file for 2D Spatial data]]
	* [[Converting a Sketchup model to CityGML format‎‎]]		* [[Converting a Sketchup model to CityGML format‎‎]]
	* [[Exporting Blender models to CityJSON]]
	\|seealso=		\|seealso=
	* [[Custom Geometries]]		* [[Custom Geometries]]

Frank@tygron.nl: /* Supported Types */

2024-02-07T12:12:36Z

Supported Types

← Older revision		Revision as of 12:12, 7 February 2024
Line 9:		Line 9:
	* CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)		* CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)

			===Parts===
	Each Building, BuildingPart, Bridge and BridgePart can contain one or more surfaces. These surfaces are used to create a 2-dimensional polygon for a feature ([[Building]] in the {{software}}) and 3-dimension [[Custom Geometries]] for visualization. Unsupported surfaces are not processed. The surface types that are currently supported by the {{software}} are:		Each Building, BuildingPart, Bridge and BridgePart can contain one or more surfaces. These surfaces are used to create a 2-dimensional polygon for a feature ([[Building]] in the {{software}}) and 3-dimension [[Custom Geometries]] for visualization. Unsupported surfaces are not processed. The surface types that are currently supported by the {{software}} are:
	*Polygon (gml geometry types such as LineStrings and Polygons)		*Polygon (gml geometry types such as LineStrings and Polygons)
	*CompositeSurface (that contains Polygons and other CompositeSurfaces)		*CompositeSurface (that contains Polygons and other CompositeSurfaces)

	Each building part can contain multiple LODs (Level of ~~Details~~). Currently only one is selected for each surface, based on the following preference:		===Level of Detail===
			Each building part can contain multiple LODs (Level of Detail). Currently only one is selected for each surface, based on the following preference:
	# LoD 2		# LoD 2
	# LoD 3		# LoD 3
Line 20:		Line 22:
	# LoD 0		# LoD 0

			===Texture and Color===
	Each surface can be textured with 1 image. If the surface is not textured, a color is obtained for the surface when the surface has X3DMaterial surface data.		Each surface can be textured with 1 image. If the surface is not textured, a color is obtained for the surface when the surface has X3DMaterial surface data.
	Of a X3DMaterial, the color (including transparency) is picked based on the first occurrence of:		Of a X3DMaterial, the color (including transparency) is picked based on the first occurrence of:

Frank@tygron.nl at 12:11, 7 February 2024

2024-02-07T12:11:59Z

← Older revision		Revision as of 12:11, 7 February 2024
Line 14:		Line 14:

	Each building part can contain multiple LODs (Level of Details). Currently only one is selected for each surface, based on the following preference:		Each building part can contain multiple LODs (Level of Details). Currently only one is selected for each surface, based on the following preference:
	* LoD 2		# LoD 2
	* LoD 3		# LoD 3
	* LoD 1		# LoD 1
	* LoD 4		# LoD 4
			# LoD 0

	Each surface can be textured with 1 image. If the surface is not textured, a color is obtained for the surface when the surface has X3DMaterial surface data.		Each surface can be textured with 1 image. If the surface is not textured, a color is obtained for the surface when the surface has X3DMaterial surface data.

Frank@tygron.nl at 12:10, 7 February 2024

2024-02-07T12:10:46Z

← Older revision		Revision as of 12:10, 7 February 2024
Line 1:		Line 1:
	CityGML<ref></ref> is an open standardized 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.		CityGML<ref>T. H. Kolbe, T. Kutzner, C. S. Smyth, C. Nagel, C. Roensdorf, C. Heazel ∙ OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard ∙ found at: [https://docs.ogc.org/is/20-010/20-010.html https://docs.ogc.org/is/20-010/20-010.html] (last visited 2024-02-07)</ref> is an open standardized 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 {{software}}.		CityJSON is a different exchange format which uses the same underlying data model as CityGML. Both formats can be imported into the {{software}}.

Frank@tygron.nl at 11:56, 7 February 2024

2024-02-07T11:56:57Z

← Older revision		Revision as of 11:56, 7 February 2024
Line 1:		Line 1:
	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.		CityGML<ref></ref> is an open standardized 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 {{software}}.		CityJSON is a different exchange format which uses the same underlying data model as CityGML. Both formats can be imported into the {{software}}.
Line 9:		Line 9:
	* CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)		* CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)

	Each Building, BuildingPart, Bridge and BridgePart can contain one or more surfaces. These surfaces are used to create a 2-dimensional polygon for a feature ([[Building]] in the {{software}}) and 3-dimension [[~~custom geometries~~]]. Unsupported surfaces are not processed. The surface types that are currently supported by the {{software}} are:		Each Building, BuildingPart, Bridge and BridgePart can contain one or more surfaces. These surfaces are used to create a 2-dimensional polygon for a feature ([[Building]] in the {{software}}) and 3-dimension [[Custom Geometries]] for visualization. Unsupported surfaces are not processed. The surface types that are currently supported by the {{software}} are:
	*Polygon (gml geometry types such as LineStrings and Polygons)		*Polygon (gml geometry types such as LineStrings and Polygons)
	*CompositeSurface (that contains Polygons and other CompositeSurfaces)		*CompositeSurface (that contains Polygons and other CompositeSurfaces)
Line 41:		Line 41:
	\|seealso=		\|seealso=
	* [[Custom Geometries]]		* [[Custom Geometries]]
			\|references=
			<references/>
	}}		}}




	{{GeoDataOverview}}		{{GeoDataOverview}}
	[[Category:CityGML]]		[[Category:CityGML]]

Frank@tygron.nl: /* Supported Types */

2024-02-07T11:07:37Z

Supported Types

← Older revision		Revision as of 11:07, 7 February 2024
Line 9:		Line 9:
	* CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)		* CityObjectGroup (containing other Buildings, BuildingParts, Bridges, BridgeParts and CityObjectGroups)

	~~For each~~ Building, BuildingPart, Bridge and BridgePart surfaces are processed. The surface types that are currently supported by the {{software}} are:		Each Building, BuildingPart, Bridge and BridgePart can contain one or more surfaces. These surfaces are used to create a 2-dimensional polygon for a feature ([[Building]] in the {{software}}) and 3-dimension [[custom geometries]]. Unsupported surfaces are not processed. The surface types that are currently supported by the {{software}} are:
	*Polygon		*Polygon (gml geometry types such as LineStrings and Polygons)
	*CompositeSurface (that contains Polygons and other CompositeSurfaces)		*CompositeSurface (that contains Polygons and other CompositeSurfaces)

	Each surface can be textured with 1 image. If it is not ~~textures~~, a color is obtained for the surface when the surface has X3DMaterial surface data.		Each building part can contain multiple LODs (Level of Details). Currently only one is selected for each surface, based on the following preference:
	Of ~~this~~ X3DMaterial, the color (including transparency) is picked based on the first occurrence of:		* LoD 2
			* LoD 3
			* LoD 1
			* LoD 4

			Each surface can be textured with 1 image. If the surface is not textured, a color is obtained for the surface when the surface has X3DMaterial surface data.
			Of a X3DMaterial, the color (including transparency) is picked based on the first occurrence of:
	* Diffuse color		* Diffuse color
	* Specular color		* Specular color
	* Emissive color		* Emissive color
			A white color is the fallback color when none of the colors are specified in any X3DMaterials associated with the surface.