Skip to content
GitLab
Commit 3c8fe882 authored by Claus Nagel's avatar Claus Nagel
Browse files

prepare release of 2.0ea

parent 69272f9d
Expand all Show whitespace changes
Inline Side-by-side
.classpath
View file @ 3c8fe882
......@@ -7,6 +7,8 @@
<classpathentry kind="lib" path="lib/jaxb-xjc.jar"/>
<classpathentry kind="lib" path="lib/jsr173_1.0_api.jar"/>
<classpathentry kind="lib" path="lib/args4j-2.0.9.jar"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk1.5.0_22"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="lib" path="lib/xercesImpl.jar"/>
<classpathentry kind="lib" path="lib/xml-apis.jar"/>
<classpathentry kind="output" path="bin"/>
</classpath>
build.xml
View file @ 3c8fe882
......@@ -3,7 +3,7 @@
<!-- application specific variables -->
<property name="app.name" value="ade-xjc" />
<property name="app.version" value="1.0" />
<property name="app.version" value="2.0ea" />
<property name="app.jar" value="${app.name}.jar" />
<property name="app.title" value="JAXB xjc wrapper for citygml4j version ${app.version}" />
<property name="app.vendor" value="IGG, Technical University Berlin, Germany, http://www.igg.tu-berlin.de" />
......
lib/activation.jar
View file @ 3c8fe882
No preview for this file type
lib/jaxb-api.jar
View file @ 3c8fe882
No preview for this file type
lib/jaxb-impl.jar
View file @ 3c8fe882
No preview for this file type
lib/jaxb-xjc.jar
View file @ 3c8fe882
No preview for this file type
lib/jsr173_1.0_api.jar
View file @ 3c8fe882
No preview for this file type
schemas/CityGML/0.4.0/CityGML.xsd deleted 100644 → 0
View file @ 69272f9d
This diff is collapsed.
schemas/CityGML/1.0.0/appearance.xsd
View file @ 3c8fe882
......@@ -5,8 +5,9 @@
<!-- Prof. Dr. Thomas H. Kolbe, Institute for Geodesy and Geoinformation Science, Technical University of Berlin -->
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/appearance/1.0" xmlns:core="http://www.opengis.net/citygml/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml" targetNamespace="http://www.opengis.net/citygml/appearance/1.0" elementFormDefault="qualified"
<xs:schema xmlns="http://www.opengis.net/citygml/appearance/1.0" xmlns:core="http://www.opengis.net/citygml/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="http://www.opengis.net/citygml/appearance/1.0" elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/citygml/1.0" schemaLocation="cityGMLBase.xsd"/>
......@@ -15,8 +16,8 @@
<!-- ========================================================================================= -->
<xs:complexType name="AppearanceType">
<xs:annotation>
<xs:documentation> Named container for all surface data (texture/material). All appearances of the same name ("theme") within a CityGML file are
considered a group. </xs:documentation>
<xs:documentation> Named container for all surface data (texture/material). All appearances of the same name ("theme")
within a CityGML file are considered a group. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
......@@ -33,8 +34,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="AppearancePropertyType">
<xs:annotation>
<xs:documentation>Denotes the relation of a _CityObject resp. CityModel to its appearances. The AppearancePropertyType element must either carry a
reference to a Appearance object or contain a Appearance object inline, but neither both nor none.</xs:documentation>
<xs:documentation>Denotes the relation of a _CityObject resp. CityModel to its appearances. The AppearancePropertyType
element must either carry a reference to a Appearance object or contain a Appearance object inline, but neither both nor
none.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:FeaturePropertyType">
......@@ -69,11 +71,12 @@
<!-- ========================================================================================= -->
<xs:complexType name="SurfaceDataPropertyType">
<xs:annotation>
<xs:documentation>Denotes the relation of an Appearance to its surface data. The SurfaceDataPropertyType element must either carry a reference to a
_SurfaceData object or contain a _SurfaceData object inline, but neither both nor none.</xs:documentation>
<xs:documentation>Denotes the relation of an Appearance to its surface data. The SurfaceDataPropertyType element must either
carry a reference to a _SurfaceData object or contain a _SurfaceData object inline, but neither both nor
none.</xs:documentation>
</xs:annotation>
<xs:sequence minOccurs="0">
<xs:element ref="_SurfaceData" minOccurs="0"/>
<xs:element ref="_SurfaceData"/>
<xs:element ref="gml:_ADEComponent" minOccurs="0"/>
</xs:sequence>
<xs:attributeGroup ref="gml:AssociationAttributeGroup"/>
......@@ -81,8 +84,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="AbstractTextureType">
<xs:annotation>
<xs:documentation>Base class for textures. "imageURI" can contain any valid URI from references to a local file to preformatted web service
requests. The linking to geometry and texture parameterization is provided by derived classes.</xs:documentation>
<xs:documentation>Base class for textures. "imageURI" can contain any valid URI from references to a local file to
preformatted web service requests. The linking to geometry and texture parameterization is provided by derived
classes.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractSurfaceDataType">
......@@ -104,8 +108,8 @@
<!-- ========================================================================================= -->
<xs:simpleType name="WrapModeType">
<xs:annotation>
<xs:documentation>Fill mode for a texture. "wrap" repeats the texture, "clamp" extends the edges of the texture, and "border" fills all undefined
areas with "borderColor"</xs:documentation>
<xs:documentation>Fill mode for a texture. "wrap" repeats the texture, "clamp" extends the edges of the texture, and
"border" fills all undefined areas with "borderColor"</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="none"/>
......@@ -118,9 +122,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="ParameterizedTextureType">
<xs:annotation>
<xs:documentation>Specialization for standard 2D textures. "target" provides the linking to surface geometry. Only gml:MultiSurface and decendants
of gml:AbstractSurfaceType are valid targets. As property of the link, a texture parameterization either as set of texture coordinates or
transformation matrix is given. </xs:documentation>
<xs:documentation>Specialization for standard 2D textures. "target" provides the linking to surface geometry. Only
gml:MultiSurface and decendants of gml:AbstractSurfaceType are valid targets. As property of the link, a texture
parameterization either as set of texture coordinates or transformation matrix is given. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractTextureType">
......@@ -138,14 +142,15 @@
<!-- ========================================================================================= -->
<xs:complexType name="GeoreferencedTextureType">
<xs:annotation>
<xs:documentation>Specialization for georeferenced textures, i.e. textures using a planimetric projection. Such textures contain an implicit
parameterization (either stored within the image file, in an acompanying world file, or using the "referencePoint" and "orientation"-elements).
A georeference provided by "referencePoint" and "orientation" always takes precedence. The search order for an external georeference is
determined by the boolean flag preferWorldFile. If this flag is set to true (its default value), a world file is looked for first and only if it
is not found the georeference from the image data is used. If preferWorldFile is false, the world file is used only if no georeference from the
image data is available. The "boundedBy"-property should contain the bounding box of the projected image data. Since a georeferenced texture has
a unique parameterization, "target" only provides links to surface geometry without any additional texture parameterization. Only
gml:MultiSurface or decendants of gml:AbstractSurfaceType are valid targets.</xs:documentation>
<xs:documentation>Specialization for georeferenced textures, i.e. textures using a planimetric projection. Such textures
contain an implicit parameterization (either stored within the image file, in an acompanying world file, or using the
"referencePoint" and "orientation"-elements). A georeference provided by "referencePoint" and "orientation" always takes
precedence. The search order for an external georeference is determined by the boolean flag preferWorldFile. If this flag
is set to true (its default value), a world file is looked for first and only if it is not found the georeference from the
image data is used. If preferWorldFile is false, the world file is used only if no georeference from the image data is
available. The "boundedBy"-property should contain the bounding box of the projected image data. Since a georeferenced
texture has a unique parameterization, "target" only provides links to surface geometry without any additional texture
parameterization. Only gml:MultiSurface or decendants of gml:AbstractSurfaceType are valid targets.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractTextureType">
......@@ -166,9 +171,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="TextureAssociationType">
<xs:annotation>
<xs:documentation>Denotes the relation of a texture to a surface, that is augmented by a TextureParameterization object. The TextureAssociationType
element must either carry a reference to a _TextureParameterization object or contain a _TextureParameterization object inline, but neither both
nor none.</xs:documentation>
<xs:documentation>Denotes the relation of a texture to a surface, that is augmented by a TextureParameterization object. The
TextureAssociationType element must either carry a reference to a _TextureParameterization object or contain a
_TextureParameterization object inline, but neither both nor none.</xs:documentation>
</xs:annotation>
<xs:sequence minOccurs="0">
<xs:element ref="_TextureParameterization"/>
......@@ -179,9 +184,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="AbstractTextureParameterizationType" abstract="true">
<xs:annotation>
<xs:documentation>Base class for augmenting a link "texture->surface" with texture parameterization. Subclasses of this class define concrete
parameterizations. Currently, texture coordinates and texture coordinate generation using a transformation matrix are available.
</xs:documentation>
<xs:documentation>Base class for augmenting a link "texture->surface" with texture parameterization. Subclasses of this
class define concrete parameterizations. Currently, texture coordinates and texture coordinate generation using a
transformation matrix are available. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:AbstractGMLType">
......@@ -193,16 +198,18 @@
</xs:complexContent>
</xs:complexType>
<!-- ========================================================================================= -->
<xs:element name="_TextureParameterization" type="AbstractTextureParameterizationType" abstract="true" substitutionGroup="gml:_GML"/>
<xs:element name="_TextureParameterization" type="AbstractTextureParameterizationType" abstract="true"
substitutionGroup="gml:_GML"/>
<!-- ========================================================================================= -->
<xs:element name="_GenericApplicationPropertyOfTextureParameterization" type="xs:anyType" abstract="true"/>
<!-- ========================================================================================= -->
<xs:complexType name="TexCoordListType">
<xs:annotation>
<xs:documentation>Texture parameterization using texture coordinates: Each gml:LinearRing that is part of the surface requires a separate
"textureCoordinates"-entry with 2 doubles per ring vertex. The "ring"- attribute provides the gml:id of the target LinearRing. It is prohibited
to link texture coordinates to any other object type than LinearRing. Thus, surfaces not consisting of LinearRings cannot be textured this way.
Use transformation matrices (see below) or georeferenced textures instead. </xs:documentation>
<xs:documentation>Texture parameterization using texture coordinates: Each gml:LinearRing that is part of the surface
requires a separate "textureCoordinates"-entry with 2 doubles per ring vertex. The "ring"- attribute provides the gml:id
of the target LinearRing. It is prohibited to link texture coordinates to any other object type than LinearRing. Thus,
surfaces not consisting of LinearRings cannot be textured this way. Use transformation matrices (see below) or
georeferenced textures instead. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractTextureParameterizationType">
......@@ -228,11 +235,12 @@
<!-- ========================================================================================= -->
<xs:complexType name="TexCoordGenType">
<xs:annotation>
<xs:documentation>Texture parameterization using a transformation matrix. The transformation matrix "worldToTexture" can be used to derive texture
coordinates from an object's location. This 3x4 matrix T computes the coordinates (s,t) from a homogeneous world position p as (s,t) = (s'/q',
t'/q') with (s', t', q') = T*p. Thus, perspective projections can be specified. The SRS can be specified using standard attributes. If an object
is given in a different reference system, it is transformed to the SRS before applying the transformation. A transformation matrix can be used
for whole surfaces. It is not required to specify it per LinearRing. </xs:documentation>
<xs:documentation>Texture parameterization using a transformation matrix. The transformation matrix "worldToTexture" can be
used to derive texture coordinates from an object's location. This 3x4 matrix T computes the coordinates (s,t) from a
homogeneous world position p as (s,t) = (s'/q', t'/q') with (s', t', q') = T*p. Thus, perspective projections can be
specified. The SRS can be specified using standard attributes. If an object is given in a different reference system, it
is transformed to the SRS before applying the transformation. A transformation matrix can be used for whole surfaces. It
is not required to specify it per LinearRing. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractTextureParameterizationType">
......@@ -258,9 +266,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="X3DMaterialType">
<xs:annotation>
<xs:documentation>Class for defining constant surface properties. It is based on X3D's material definition. In addition, "isSmooth" provides a hint
for value interpolation. The link to surface geometry is established via the "target"-property. Only gml:MultiSurface or decendants of
gml:AbstractSurfaceType are valid targets. </xs:documentation>
<xs:documentation>Class for defining constant surface properties. It is based on X3D's material definition. In addition,
"isSmooth" provides a hint for value interpolation. The link to surface geometry is established via the "target"-property.
Only gml:MultiSurface or decendants of gml:AbstractSurfaceType are valid targets. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractSurfaceDataType">
......@@ -285,10 +293,10 @@
<!-- ========================================================================================= -->
<xs:simpleType name="TextureTypeType">
<xs:annotation>
<xs:documentation>Textures can be qualified by the attribute textureType. The textureType differentiates between textures, which are specific for a
certain object and are only used for that object (specific), and prototypic textures being typical for that kind of object and are used many
times for all objects of that kind (typical). A typical texture may be replaced by a specific, if available. Textures may also be classified as
unknown. </xs:documentation>
<xs:documentation>Textures can be qualified by the attribute textureType. The textureType differentiates between textures,
which are specific for a certain object and are only used for that object (specific), and prototypic textures being
typical for that kind of object and are used many times for all objects of that kind (typical). A typical texture may be
replaced by a specific, if available. Textures may also be classified as unknown. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="specific"/>
......@@ -299,8 +307,8 @@
<!-- ========================================================================================= -->
<xs:simpleType name="Color">
<xs:annotation>
<xs:documentation>List of three values (red, green, blue), separated by spaces. The values must be in the range between zero and one.
</xs:documentation>
<xs:documentation>List of three values (red, green, blue), separated by spaces. The values must be in the range between zero
and one. </xs:documentation>
</xs:annotation>
<xs:restriction base="core:doubleBetween0and1List">
<xs:length value="3"/>
......@@ -309,8 +317,8 @@
<!-- ========================================================================================= -->
<xs:simpleType name="ColorPlusOpacity">
<xs:annotation>
<xs:documentation>List of three or four values (red, green, blue, opacity), separated by spaces. The values must be in the range between zero and
one. If no opacity is given, it is assumed as 1.0.</xs:documentation>
<xs:documentation>List of three or four values (red, green, blue, opacity), separated by spaces. The values must be in the
range between zero and one. If no opacity is given, it is assumed as 1.0.</xs:documentation>
</xs:annotation>
<xs:restriction base="core:doubleBetween0and1List">
<xs:minLength value="3"/>
......
schemas/CityGML/1.0.0/building.xsd
View file @ 3c8fe882
This diff is collapsed.
schemas/CityGML/1.0.0/cityFurniture.xsd
View file @ 3c8fe882
......@@ -5,8 +5,9 @@
<!-- Prof. Dr. Thomas H. Kolbe, Institute for Geodesy and Geoinformation Science, Technical University of Berlin -->
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/cityfurniture/1.0" xmlns:core="http://www.opengis.net/citygml/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml" targetNamespace="http://www.opengis.net/citygml/cityfurniture/1.0" elementFormDefault="qualified"
<xs:schema xmlns="http://www.opengis.net/citygml/cityfurniture/1.0" xmlns:core="http://www.opengis.net/citygml/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="http://www.opengis.net/citygml/cityfurniture/1.0" elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/citygml/1.0" schemaLocation="cityGMLBase.xsd"/>
......@@ -15,8 +16,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="CityFurnitureType">
<xs:annotation>
<xs:documentation>Type describing city furnitures, like traffic lights, benches, ... As subclass of _CityObject, a CityFurniture inherits all
attributes and relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing city furnitures, like traffic lights, benches, ... As subclass of _CityObject, a
CityFurniture inherits all attributes and relations, in particular an id, names, external references, and generalization
relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="core:AbstractCityObjectType">
......@@ -47,16 +49,16 @@
<!-- ========================================================================================= -->
<xs:simpleType name="CityFurnitureFunctionType">
<xs:annotation>
<xs:documentation>Function of a Furniture. The values of this type are defined in the XML file CityFurnitureFunctionType.xml, according to the
dictionary concept of GML3. </xs:documentation>
<xs:documentation>Function of a Furniture. The values of this type are defined in the XML file
CityFurnitureFunctionType.xml, according to the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- ========================================================================================= -->
<xs:simpleType name="CityFurnitureClassType">
<xs:annotation>
<xs:documentation>Class of a Furniture. The values of this type are defined in the XML file CityFurnitureClassType.xml, according to the dictionary
concept of GML3. </xs:documentation>
<xs:documentation>Class of a Furniture. The values of this type are defined in the XML file CityFurnitureClassType.xml,
according to the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
......
schemas/CityGML/1.0.0/cityGMLBase.xsd
View file @ 3c8fe882
......@@ -5,8 +5,9 @@
<!-- Prof. Dr. Thomas H. Kolbe, Institute for Geodesy and Geoinformation Science, Technical University of Berlin -->
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/1.0" xmlns:xAL="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml" xmlns:app="http://www.opengis.net/citygml/appearance/1.0" xmlns:gen="http://www.opengis.net/citygml/generics/1.0"
<xs:schema xmlns="http://www.opengis.net/citygml/1.0" xmlns:xAL="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
xmlns:app="http://www.opengis.net/citygml/appearance/1.0" xmlns:gen="http://www.opengis.net/citygml/generics/1.0"
targetNamespace="http://www.opengis.net/citygml/1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0" schemaLocation="../../xAL/2.0/xAL.xsd"/>
......@@ -19,8 +20,8 @@
<!-- ========================================================================================= -->
<xs:complexType name="CityModelType">
<xs:annotation>
<xs:documentation>Type describing the "root" element of any city model file. It is a collection whose members are restricted to be features of a
city model. All features are included as cityObjectMember. </xs:documentation>
<xs:documentation>Type describing the "root" element of any city model file. It is a collection whose members are restricted
to be features of a city model. All features are included as cityObjectMember. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureCollectionType">
......@@ -43,10 +44,11 @@
<!-- ========================================================================================= -->
<xs:complexType name="AbstractCityObjectType" abstract="true">
<xs:annotation>
<xs:documentation>Type describing the abstract superclass of most CityGML features. Its purpose is to provide a creation and a termination date as
well as a reference to corresponding objects in other information systems. A generalization relation may be used to relate features, which
represent the same real-world object in different Levels-of-Detail, i.e. a feature and its generalized counterpart(s). The direction of this
relation is from the feature to the corresponding generalized feature.</xs:documentation>
<xs:documentation>Type describing the abstract superclass of most CityGML features. Its purpose is to provide a creation and
a termination date as well as a reference to corresponding objects in other information systems. A generalization relation
may be used to relate features, which represent the same real-world object in different Levels-of-Detail, i.e. a feature
and its generalized counterpart(s). The direction of this relation is from the feature to the corresponding generalized
feature.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
......@@ -87,9 +89,9 @@
<!-- ========================================================================================== -->
<xs:complexType name="AbstractSiteType" abstract="true">
<xs:annotation>
<xs:documentation>Type describing the abstract superclass for buildings, facilities, etc. Future extensions of CityGML like bridges and tunnels
would be modelled as subclasses of _Site. As subclass of _CityObject, a _Site inherits all attributes and relations, in particular an id, names,
external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the abstract superclass for buildings, facilities, etc. Future extensions of CityGML like
bridges and tunnels would be modelled as subclasses of _Site. As subclass of _CityObject, a _Site inherits all attributes
and relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractCityObjectType">
......@@ -108,9 +110,10 @@
<!-- ========================================================================================= -->
<xs:complexType name="GeneralizationRelationType">
<xs:annotation>
<xs:documentation>Denotes the relation of a _CityObject to its corresponding _CityObject in higher LOD, i.e. to the _CityObjects representing the
same real world object in higher LOD. The GeneralizationRelationType element must either carry a reference to a _CityObject object or contain a
_CityObject object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of a _CityObject to its corresponding _CityObject in higher LOD, i.e. to the
_CityObjects representing the same real world object in higher LOD. The GeneralizationRelationType element must either
carry a reference to a _CityObject object or contain a _CityObject object inline, but neither both nor none.
</xs:documentation>
</xs:annotation>
<xs:sequence minOccurs="0">
<xs:element ref="_CityObject"/>
......@@ -123,11 +126,11 @@
<!-- ========================================================================================== -->
<xs:complexType name="ExternalReferenceType">
<xs:annotation>
<xs:documentation>Type describing the reference to an corresponding object in an other information system, for example in the german cadastre ALKIS,
the german topographic information system or ATKIS, or the OS MasterMap. The reference consists of the name of the external information system,
represented by an URI, and the reference of the external object, given either by a string or by an URI. If the informationSystem element is
missing in the ExternalReference, the ExternalObjectReference must be an URI, which contains an indication of the
informationSystem.</xs:documentation>
<xs:documentation>Type describing the reference to an corresponding object in an other information system, for example in
the german cadastre ALKIS, the german topographic information system or ATKIS, or the OS MasterMap. The reference consists
of the name of the external information system, represented by an URI, and the reference of the external object, given
either by a string or by an URI. If the informationSystem element is missing in the ExternalReference, the
ExternalObjectReference must be an URI, which contains an indication of the informationSystem.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="informationSystem" type="xs:anyURI" minOccurs="0"/>
......@@ -147,8 +150,8 @@
<!-- ========================================================================================== -->
<xs:complexType name="AddressPropertyType">
<xs:annotation>
<xs:documentation>Denotes the relation of an _CityObject to its addresses. The AddressPropertyType element must either carry a reference to an
Address object or contain an Address object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of an _CityObject to its addresses. The AddressPropertyType element must either carry
a reference to an Address object or contain an Address object inline, but neither both nor none. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="gml:AssociationType">
......@@ -161,9 +164,9 @@
<!-- ========================================================================================== -->
<xs:complexType name="AddressType">
<xs:annotation>
<xs:documentation>Type for addresses. It references the xAL address standard issued by the OASIS consortium. Please note, that addresses are
modelled as GML features. Every address can be assigned zero or more 2D or 3D point geometries (one gml:MultiPoint geometry) locating the
entrance(s). </xs:documentation>
<xs:documentation>Type for addresses. It references the xAL address standard issued by the OASIS consortium. Please note,
that addresses are modelled as GML features. Every address can be assigned zero or more 2D or 3D point geometries (one
gml:MultiPoint geometry) locating the entrance(s). </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
......@@ -193,15 +196,17 @@
<!-- ========================================================================================== -->
<xs:complexType name="ImplicitGeometryType">
<xs:annotation>
<xs:documentation> Type for the implicit representation of a geometry. An implicit geometry is a geometric object, where the shape is stored only
once as a prototypical geometry, e.g. a tree or other vegetation object, a traffic light or a traffic sign. This prototypic geometry object is
re-used or referenced many times, wherever the corresponding feature occurs in the 3D city model. Each occurrence is represented by a link to
the prototypic shape geometry (in a local cartesian coordinate system), by a transforma-tion matrix that is multiplied with each 3D coordinate
tuple of the prototype, and by an anchor point denoting the base point of the object in the world coordinate reference system. In order to
determine the absolute coordinates of an implicit geometry, the anchor point coordinates have to be added to the matrix multiplication results.
The transformation matrix accounts for the intended rotation, scaling, and local translation of the prototype. It is a 4x4 matrix that is
multiplied with the prototype coordinates using homogeneous coordinates, i.e. (x,y,z,1). This way even a projection might be modelled by the
transformation matrix. The concept of implicit geometries is an enhancement of the geometry model of GML3. </xs:documentation>
<xs:documentation> Type for the implicit representation of a geometry. An implicit geometry is a geometric object, where the
shape is stored only once as a prototypical geometry, e.g. a tree or other vegetation object, a traffic light or a traffic
sign. This prototypic geometry object is re-used or referenced many times, wherever the corresponding feature occurs in
the 3D city model. Each occurrence is represented by a link to the prototypic shape geometry (in a local cartesian
coordinate system), by a transforma-tion matrix that is multiplied with each 3D coordinate tuple of the prototype, and by
an anchor point denoting the base point of the object in the world coordinate reference system. In order to determine the
absolute coordinates of an implicit geometry, the anchor point coordinates have to be added to the matrix multiplication
results. The transformation matrix accounts for the intended rotation, scaling, and local translation of the prototype. It
is a 4x4 matrix that is multiplied with the prototype coordinates using homogeneous coordinates, i.e. (x,y,z,1). This way
even a projection might be modelled by the transformation matrix. The concept of implicit geometries is an enhancement of
the geometry model of GML3. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:AbstractGMLType">
......@@ -220,9 +225,10 @@
<!-- ========================================================================================== -->
<xs:complexType name="ImplicitRepresentationPropertyType">
<xs:annotation>
<xs:documentation>Denotes the relation of a _CityObject to its implicit geometry representation, which is a representation of a geometry by
referencing a prototype and transforming it to its real position in space. The ImplicitRepresentationPropertyType element must either carry a
reference to a ImplicitGeometry object or contain a ImplicitGeometry object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of a _CityObject to its implicit geometry representation, which is a representation
of a geometry by referencing a prototype and transforming it to its real position in space. The
ImplicitRepresentationPropertyType element must either carry a reference to a ImplicitGeometry object or contain a
ImplicitGeometry object inline, but neither both nor none. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="gml:AssociationType">
......@@ -237,8 +243,8 @@
<!-- ========================================================================================= -->
<xs:simpleType name="doubleBetween0and1">
<xs:annotation>
<xs:documentation>Type for values, which are greater or equal than 0 and less or equal than 1. Used for color encoding, for example.
</xs:documentation>
<xs:documentation>Type for values, which are greater or equal than 0 and less or equal than 1. Used for color encoding, for
example. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:double">
<xs:minInclusive value="0"/>
......@@ -248,17 +254,17 @@
<!-- ========================================================================================= -->
<xs:simpleType name="doubleBetween0and1List">
<xs:annotation>
<xs:documentation>List for double values, which are greater or equal than 0 and less or equal than 1. Used for color encoding, for example.
</xs:documentation>
<xs:documentation>List for double values, which are greater or equal than 0 and less or equal than 1. Used for color
encoding, for example. </xs:documentation>
</xs:annotation>
<xs:list itemType="doubleBetween0and1"/>
</xs:simpleType>
<!-- ========================================================================================= -->
<xs:simpleType name="TransformationMatrix4x4Type">
<xs:annotation>
<xs:documentation>Used for implicit geometries. The Transformation matrix is a 4 by 4 matrix, thus it must be a list with 16 items. The order the
matrix element are represented is row-major, i. e. the first 4 elements represent the first row, the fifth to the eight element the second
row,... </xs:documentation>
<xs:documentation>Used for implicit geometries. The Transformation matrix is a 4 by 4 matrix, thus it must be a list with 16
items. The order the matrix element are represented is row-major, i. e. the first 4 elements represent the first row, the
fifth to the eight element the second row,... </xs:documentation>
</xs:annotation>
<xs:restriction base="gml:doubleList">
<xs:length value="16"/>
......@@ -267,9 +273,9 @@
<!-- ========================================================================================= -->
<xs:simpleType name="TransformationMatrix2x2Type">
<xs:annotation>
<xs:documentation>Used for georeferencing. The Transformation matrix is a 2 by 2 matrix, thus it must be a list with 4 items. The order the matrix
element are represented is row-major, i. e. the first 2 elements represent the first row, the fifth to the eight element the second row,...
</xs:documentation>
<xs:documentation>Used for georeferencing. The Transformation matrix is a 2 by 2 matrix, thus it must be a list with 4
items. The order the matrix element are represented is row-major, i. e. the first 2 elements represent the first row, the
fifth to the eight element the second row,... </xs:documentation>
</xs:annotation>
<xs:restriction base="gml:doubleList">
<xs:length value="4"/>
......@@ -278,9 +284,9 @@
<!-- ========================================================================================= -->
<xs:simpleType name="TransformationMatrix3x4Type">
<xs:annotation>
<xs:documentation>Used for texture parameterization. The Transformation matrix is a 3 by 4 matrix, thus it must be a list with 12 items. The order
the matrix element are represented is row-major, i. e. the first 4 elements represent the first row, the fifth to the eight element the second
row,... </xs:documentation>
<xs:documentation>Used for texture parameterization. The Transformation matrix is a 3 by 4 matrix, thus it must be a list
with 12 items. The order the matrix element are represented is row-major, i. e. the first 4 elements represent the first
row, the fifth to the eight element the second row,... </xs:documentation>
</xs:annotation>
<xs:restriction base="gml:doubleList">
<xs:length value="12"/>
......@@ -289,8 +295,8 @@
<!-- ========================================================================================= -->
<xs:simpleType name="integerBetween0and4">
<xs:annotation>
<xs:documentation>Type for integer values, which are greater or equal than 0 and less or equal than 4. Used for encoding of the LOD number.
</xs:documentation>
<xs:documentation>Type for integer values, which are greater or equal than 0 and less or equal than 4. Used for encoding of
the LOD number. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:integer">
<xs:minInclusive value="0"/>
......@@ -300,8 +306,9 @@
<!-- ========================================================================================= -->
<xs:simpleType name="MimeTypeType">
<xs:annotation>
<xs:documentation>MIME type of a geometry in an external library file. MIME types are defined by the IETF (Internet Engineering Task Force). The
values of this type are defined in the XML file MimeTypeType.xml, according to the dictionary concept of GML3. </xs:documentation>
<xs:documentation>MIME type of a geometry in an external library file. MIME types are defined by the IETF (Internet
Engineering Task Force). The values of this type are defined in the XML file MimeTypeType.xml, according to the dictionary
concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
......
schemas/CityGML/1.0.0/cityObjectGroup.xsd
View file @ 3c8fe882
......@@ -6,8 +6,9 @@
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/cityobjectgroup/1.0" xmlns:core="http://www.opengis.net/citygml/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml" targetNamespace="http://www.opengis.net/citygml/cityobjectgroup/1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="http://www.opengis.net/citygml/cityobjectgroup/1.0" elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/citygml/1.0" schemaLocation="cityGMLBase.xsd"/>
<!-- ========================================================================================= -->
......@@ -15,13 +16,14 @@
<!-- ========================================================================================= -->
<xs:complexType name="CityObjectGroupType">
<xs:annotation>
<xs:documentation> A group may be used to aggregate arbitrary CityObjects according to some user-defined criteria. Examples for groups are the
buildings in a specific region, the result of a query, or objects put together for visualization purposes. Each group has a name (inherited from
AbstractGMLType), functions (e.g., building group), a class and zero or more usages. A geometry may optionally be attached to a group, if the
geometry of the whole group differs from the geometry of the parts. Each member of a group may be qualified by a role name, reflecting the role
each CityObject plays in the context of the group. As subclass of _CityObject, a CityObjectGroup inherits all attributes and relations, in
particular an id, names, external references, and generalization relations. As CityObjectGroup itself is a CityObject, it may also be contained
by another group. </xs:documentation>
<xs:documentation> A group may be used to aggregate arbitrary CityObjects according to some user-defined criteria. Examples
for groups are the buildings in a specific region, the result of a query, or objects put together for visualization
purposes. Each group has a name (inherited from AbstractGMLType), functions (e.g., building group), a class and zero or
more usages. A geometry may optionally be attached to a group, if the geometry of the whole group differs from the
geometry of the parts. Each member of a group may be qualified by a role name, reflecting the role each CityObject plays
in the context of the group. As subclass of _CityObject, a CityObjectGroup inherits all attributes and relations, in
particular an id, names, external references, and generalization relations. As CityObjectGroup itself is a CityObject, it
may also be contained by another group. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="core:AbstractCityObjectType">
......@@ -46,8 +48,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="CityObjectGroupMemberType">
<xs:annotation>
<xs:documentation>Denotes the relation of a CityObjectGroup to its members, which are _CityObjects. The CityObjectGroupMemberType element must
either carry a reference to a _CityObject object or contain a _CityObject object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of a CityObjectGroup to its members, which are _CityObjects. The
CityObjectGroupMemberType element must either carry a reference to a _CityObject object or contain a _CityObject object
inline, but neither both nor none. </xs:documentation>
</xs:annotation>
<xs:sequence minOccurs="0">
<xs:element ref="core:_CityObject"/>
......@@ -61,11 +64,11 @@
<!-- ========================================================================================= -->
<xs:complexType name="CityObjectGroupParentType">
<xs:annotation>
<xs:documentation>Denotes the relation of a CityObjectGroup to its parent, which is a CityObject. The CityObjectGroupParentType element must either
carry a reference to a _CityObject object or contain a _CityObject object inline, but neither both nor none. The parent association allows for
modelling of a generic hierarchical grouping concept. Named aggregations of components (CityObjects) can be added to specific CityObjects
considered as the parent object. The parent association links to the aggregate, while the parts are given by the group members.
</xs:documentation>
<xs:documentation>Denotes the relation of a CityObjectGroup to its parent, which is a CityObject. The
CityObjectGroupParentType element must either carry a reference to a _CityObject object or contain a _CityObject object
inline, but neither both nor none. The parent association allows for modelling of a generic hierarchical grouping concept.
Named aggregations of components (CityObjects) can be added to specific CityObjects considered as the parent object. The
parent association links to the aggregate, while the parts are given by the group members. </xs:documentation>
</xs:annotation>
<xs:sequence minOccurs="0">
<xs:element ref="core:_CityObject"/>
......
schemas/CityGML/1.0.0/generics.xsd
View file @ 3c8fe882
......@@ -5,9 +5,9 @@
<!-- Prof. Dr. Thomas H. Kolbe, Institute for Geodesy and Geoinformation Science, Technical University of Berlin -->
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/generics/1.0" xmlns:core="http://www.opengis.net/citygml/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml" targetNamespace="http://www.opengis.net/citygml/generics/1.0" elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:schema xmlns="http://www.opengis.net/citygml/generics/1.0" xmlns:core="http://www.opengis.net/citygml/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="http://www.opengis.net/citygml/generics/1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/citygml/1.0" schemaLocation="cityGMLBase.xsd"/>
<!-- ========================================================================================= -->
......@@ -17,10 +17,11 @@
<!-- ========================================================================================= -->
<xs:complexType name="GenericCityObjectType">
<xs:annotation>
<xs:documentation>Generic (user defined) city objects may be used to model features which are not covered explicitly by the CityGML schema. Generic
objects must be used with care; they shall only be used if there is no appropiate thematic class available in the overall CityGML schema.
Oherwise, problems concerning semantic interoperability may arise. As subclass of _CityObject, a generic city object inherits all attributes and
relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Generic (user defined) city objects may be used to model features which are not covered explicitly by the
CityGML schema. Generic objects must be used with care; they shall only be used if there is no appropiate thematic class
available in the overall CityGML schema. Oherwise, problems concerning semantic interoperability may arise. As subclass of
_CityObject, a generic city object inherits all attributes and relations, in particular an id, names, external references,
and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="core:AbstractCityObjectType">
......@@ -54,10 +55,10 @@
<!-- ========================================================================================= -->
<xs:complexType name="AbstractGenericAttributeType" abstract="true">
<xs:annotation>
<xs:documentation> Generic (user defined) attributes may be used to represent attributes which are not covered explicitly by the CityGML schema.
Generic attributes must be used with care; they shall only be used if there is no appropiate attribute available in the overall CityGML schema.
Oherwise, problems concerning semantic interoperability may arise. A generic attribute has a name and a value, which has further subclasses
(IntAttrribute, StringAttribute, ...). </xs:documentation>
<xs:documentation> Generic (user defined) attributes may be used to represent attributes which are not covered explicitly by
the CityGML schema. Generic attributes must be used with care; they shall only be used if there is no appropiate attribute
available in the overall CityGML schema. Oherwise, problems concerning semantic interoperability may arise. A generic
attribute has a name and a value, which has further subclasses (IntAttrribute, StringAttribute, ...). </xs:documentation>
</xs:annotation>
<xs:sequence/>
<xs:attribute name="name" type="xs:string" use="required"/>
......
schemas/CityGML/1.0.0/landUse.xsd
View file @ 3c8fe882
......@@ -5,9 +5,9 @@
<!-- Prof. Dr. Thomas H. Kolbe, Institute for Geodesy and Geoinformation Science, Technical University of Berlin -->
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/landuse/1.0" xmlns:core="http://www.opengis.net/citygml/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml" targetNamespace="http://www.opengis.net/citygml/landuse/1.0" elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:schema xmlns="http://www.opengis.net/citygml/landuse/1.0" xmlns:core="http://www.opengis.net/citygml/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="http://www.opengis.net/citygml/landuse/1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/citygml/1.0" schemaLocation="cityGMLBase.xsd"/>
<!-- ========================================================================================= -->
......@@ -15,9 +15,10 @@
<!-- ========================================================================================= -->
<xs:complexType name="LandUseType">
<xs:annotation>
<xs:documentation>Type describing the class for Land Use in all LOD. LandUse objects describe areas of the earth’s surface dedicated to a specific
land use. The geometry must consist of 3-D surfaces. As subclass of _CityObject, a LandUse inherits all attributes and relations, in particular
an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the class for Land Use in all LOD. LandUse objects describe areas of the earth’s surface
dedicated to a specific land use. The geometry must consist of 3-D surfaces. As subclass of _CityObject, a LandUse
inherits all attributes and relations, in particular an id, names, external references, and generalization relations.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="core:AbstractCityObjectType">
......@@ -42,24 +43,24 @@
<!-- ========================================================================================= -->
<xs:simpleType name="LandUseClassType">
<xs:annotation>
<xs:documentation>Class of a Landuse. The values of this type are defined in the XML file LandUseClassType.xml, according to the dictionary concept
of GML3. </xs:documentation>
<xs:documentation>Class of a Landuse. The values of this type are defined in the XML file LandUseClassType.xml, according to
the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- ========================================================================================= -->
<xs:simpleType name="LandUseFunctionType">
<xs:annotation>
<xs:documentation>Function of a Landuse. The values of this type are defined in the XML file LandUseFunctionType.xml, according to the dictionary
concept of GML3. </xs:documentation>
<xs:documentation>Function of a Landuse. The values of this type are defined in the XML file LandUseFunctionType.xml,
according to the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- ========================================================================================= -->
<xs:simpleType name="LandUseUsageType">
<xs:annotation>
<xs:documentation>Usage of a Landuse. The values of this type are defined in the XML file LandUseUsageType.xml, according to the dictionary concept
of GML3. </xs:documentation>
<xs:documentation>Usage of a Landuse. The values of this type are defined in the XML file LandUseUsageType.xml, according to
the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
......
schemas/CityGML/1.0.0/relief.xsd
View file @ 3c8fe882
......@@ -5,9 +5,9 @@
<!-- Prof. Dr. Thomas H. Kolbe, Institute for Geodesy and Geoinformation Science, Technical University of Berlin -->
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/relief/1.0" xmlns:core="http://www.opengis.net/citygml/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml" targetNamespace="http://www.opengis.net/citygml/relief/1.0" elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:schema xmlns="http://www.opengis.net/citygml/relief/1.0" xmlns:core="http://www.opengis.net/citygml/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="http://www.opengis.net/citygml/relief/1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/citygml/1.0" schemaLocation="cityGMLBase.xsd"/>
<!-- ========================================================================================= -->
......@@ -15,8 +15,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="ReliefFeatureType">
<xs:annotation>
<xs:documentation>Type describing the features of the Digital Terrain Model. As subclass of _CityObject, a ReliefFeature inherits all attributes and
relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the features of the Digital Terrain Model. As subclass of _CityObject, a ReliefFeature
inherits all attributes and relations, in particular an id, names, external references, and generalization relations.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="core:AbstractCityObjectType">
......@@ -35,9 +36,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="AbstractReliefComponentType" abstract="true">
<xs:annotation>
<xs:documentation>Type describing the components of a relief feature - either a TIN, a Grid, mass points or break lines. As subclass of _CityObject,
a ReliefComponent inherits all attributes and relations, in particular an id, names, external references, and generalization relations.
</xs:documentation>
<xs:documentation>Type describing the components of a relief feature - either a TIN, a Grid, mass points or break lines. As
subclass of _CityObject, a ReliefComponent inherits all attributes and relations, in particular an id, names, external
references, and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="core:AbstractCityObjectType">
......@@ -56,8 +57,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="ReliefComponentPropertyType">
<xs:annotation>
<xs:documentation>Denotes the relation of a ReliefFeature to its components. The ReliefComponentPropertyType element must either carry a reference
to a _ReliefComponent object or contain a _ReliefComponent object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of a ReliefFeature to its components. The ReliefComponentPropertyType element must
either carry a reference to a _ReliefComponent object or contain a _ReliefComponent object inline, but neither both nor
none. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="gml:AssociationType">
......@@ -70,8 +72,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="TINReliefType">
<xs:annotation>
<xs:documentation>Type describing the TIN component of a relief feature. As subclass of _CityObject, a TINRelief inherits all attributes and
relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the TIN component of a relief feature. As subclass of _CityObject, a TINRelief inherits
all attributes and relations, in particular an id, names, external references, and generalization relations.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractReliefComponentType">
......@@ -89,8 +92,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="RasterReliefType">
<xs:annotation>
<xs:documentation>Type describing the raster component of a relief feature. As subclass of _CityObject, a RasterRelief inherits all attributes and
relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the raster component of a relief feature. As subclass of _CityObject, a RasterRelief
inherits all attributes and relations, in particular an id, names, external references, and generalization relations.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractReliefComponentType">
......@@ -108,8 +112,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="MassPointReliefType">
<xs:annotation>
<xs:documentation>Type describing the mass point component of a relief feature. As subclass of _CityObject, a MassPoint Relief inherits all
attributes and relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the mass point component of a relief feature. As subclass of _CityObject, a MassPoint
Relief inherits all attributes and relations, in particular an id, names, external references, and generalization
relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractReliefComponentType">
......@@ -127,9 +132,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="BreaklineReliefType">
<xs:annotation>
<xs:documentation>Type describing the break line Component of a relief feature. A break line relief consists of break lines or ridgeOrValleyLines.
As subclass of _CityObject, a BreaklineRelief inherits all attributes and relations, in particular an id, names, external references, and
generalization relations. </xs:documentation>
<xs:documentation>Type describing the break line Component of a relief feature. A break line relief consists of break lines
or ridgeOrValleyLines. As subclass of _CityObject, a BreaklineRelief inherits all attributes and relations, in particular
an id, names, external references, and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractReliefComponentType">
......@@ -148,8 +153,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="tinPropertyType">
<xs:annotation>
<xs:documentation>Denotes the relation of a TINRelief to its components. The tinPropertyType element must either carry a reference to a
gml:TriangulatedSurface object or contain a gml:TriangulatedSurface object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of a TINRelief to its components. The tinPropertyType element must either carry a
reference to a gml:TriangulatedSurface object or contain a gml:TriangulatedSurface object inline, but neither both nor
none. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="gml:AssociationType">
......@@ -163,8 +169,9 @@
<xs:complexType name="gridPropertyType">
<xs:complexContent>
<xs:annotation>
<xs:documentation>Denotes the relation of a RasterReliefType to its components. The gridPropertyType element must either carry a reference to a
gml:RectifiedGridCoverage object or contain a gml:RectifiedGridCoverage object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of a RasterReliefType to its components. The gridPropertyType element must either
carry a reference to a gml:RectifiedGridCoverage object or contain a gml:RectifiedGridCoverage object inline, but
neither both nor none. </xs:documentation>
</xs:annotation>
<xs:restriction base="gml:AssociationType">
<xs:sequence minOccurs="0">
......
schemas/CityGML/1.0.0/texturedSurface.xsd
View file @ 3c8fe882
......@@ -6,8 +6,9 @@
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/texturedsurface/1.0" xmlns:core="http://www.opengis.net/citygml/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml" targetNamespace="http://www.opengis.net/citygml/texturedsurface/1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="http://www.opengis.net/citygml/texturedsurface/1.0" elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/citygml/1.0" schemaLocation="cityGMLBase.xsd"/>
<!-- ========================================================================================= -->
......@@ -22,12 +23,14 @@
<xs:complexType name="TexturedSurfaceType">
<xs:annotation>
<xs:appinfo>deprecated</xs:appinfo>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. The concept of positioning
textures on surfaces complies with the standard X3D. Because there has been no appropriate texturing concept in GML3, CityGML adds the class
TexturedSurface to the geometry model of GML 3. A texture is specified as a raster image referenced by an URI, and can be an arbitrary resource,
even in the internet. Textures are positioned by employing the concept of texture coordinates, i.e. each texture coordinate matches with exactly
one 3D coordinate of the TexturedSurface. The use of texture coordinates allows an exact positioning and trimming of the texture on the surface
geometry. Each surface may be assigned one or more appearances, each refering to one side of the surface. </xs:documentation>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. The
concept of positioning textures on surfaces complies with the standard X3D. Because there has been no appropriate
texturing concept in GML3, CityGML adds the class TexturedSurface to the geometry model of GML 3. A texture is specified
as a raster image referenced by an URI, and can be an arbitrary resource, even in the internet. Textures are positioned by
employing the concept of texture coordinates, i.e. each texture coordinate matches with exactly one 3D coordinate of the
TexturedSurface. The use of texture coordinates allows an exact positioning and trimming of the texture on the surface
geometry. Each surface may be assigned one or more appearances, each refering to one side of the surface.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:OrientableSurfaceType">
......@@ -45,12 +48,13 @@
<xs:complexType name="AppearancePropertyType">
<xs:annotation>
<xs:appinfo>deprecated</xs:appinfo>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. A property that has an
_Appearance as its value domain, which can either be a Material (Color,...) or a Texture. The _Appearance Element can either be encapsulated in
an element of this type or an XLink reference to a remote _Appearance element (where remote geometry elements are located in another document or
elsewhere in the same document). Either the reference or the contained element must be given, but neither both nor none. The side of the surface
the _Appearance refers to is given by the orientation attribute, which refers to the corresponding sign attribute of the orientable surface: +
means the side with positive orientation, and - the side with negative orientation. </xs:documentation>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. A
property that has an _Appearance as its value domain, which can either be a Material (Color,...) or a Texture. The
_Appearance Element can either be encapsulated in an element of this type or an XLink reference to a remote _Appearance
element (where remote geometry elements are located in another document or elsewhere in the same document). Either the
reference or the contained element must be given, but neither both nor none. The side of the surface the _Appearance
refers to is given by the orientation attribute, which refers to the corresponding sign attribute of the orientable
surface: + means the side with positive orientation, and - the side with negative orientation. </xs:documentation>
</xs:annotation>
<xs:sequence minOccurs="0">
<xs:element ref="_Appearance"/>
......@@ -62,9 +66,10 @@
<xs:complexType name="AbstractAppearanceType" abstract="true">
<xs:annotation>
<xs:appinfo>deprecated</xs:appinfo>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. This abstract type is the
parent type of MaterialType and SimpleTextureType. It is derived from gml:AbstractGMLType, thus it inherits the attribute gml:id and may be
referenced by an appearanceProperty, although it is defined elsewhere in another appearanceProperty. </xs:documentation>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. This
abstract type is the parent type of MaterialType and SimpleTextureType. It is derived from gml:AbstractGMLType, thus it
inherits the attribute gml:id and may be referenced by an appearanceProperty, although it is defined elsewhere in another
appearanceProperty. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gml:AbstractGMLType"/>
......@@ -76,8 +81,8 @@
<xs:complexType name="MaterialType">
<xs:annotation>
<xs:appinfo>deprecated</xs:appinfo>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. Adopted from X3D standard
(http://www.web3d.org/x3d/) </xs:documentation>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. Adopted
from X3D standard (http://www.web3d.org/x3d/) </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractAppearanceType">
......@@ -98,8 +103,8 @@
<xs:complexType name="SimpleTextureType">
<xs:annotation>
<xs:appinfo>deprecated</xs:appinfo>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. Adopted from X3D standard
(http://www.web3d.org/x3d/). ToDo: repeat </xs:documentation>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. Adopted
from X3D standard (http://www.web3d.org/x3d/). ToDo: repeat </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractAppearanceType">
......@@ -118,10 +123,11 @@
<xs:simpleType name="TextureTypeType">
<xs:annotation>
<xs:appinfo>deprecated</xs:appinfo>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. Textures can be qualified by
the attribute textureType. The textureType differentiates between textures, which are specific for a certain object and are only used for that
object (specific), and prototypic textures being typical for that kind of object and are used many times for all objects of that kind (typical).
A typical texture may be replaced by a specific, if available. Textures may also be classified as unknown. </xs:documentation>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead.
Textures can be qualified by the attribute textureType. The textureType differentiates between textures, which are
specific for a certain object and are only used for that object (specific), and prototypic textures being typical for that
kind of object and are used many times for all objects of that kind (typical). A typical texture may be replaced by a
specific, if available. Textures may also be classified as unknown. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="specific"/>
......@@ -133,8 +139,9 @@
<xs:simpleType name="Color">
<xs:annotation>
<xs:appinfo>deprecated</xs:appinfo>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. List of three values (red,
green, blue), separated by spaces. The values must be in the range between zero and one. </xs:documentation>
<xs:documentation>Deprecated since CityGML version 0.4.0. Use the concepts of the CityGML Appearance module instead. List of
three values (red, green, blue), separated by spaces. The values must be in the range between zero and one.
</xs:documentation>
</xs:annotation>
<xs:restriction base="core:doubleBetween0and1List">
<xs:length value="3"/>
......
schemas/CityGML/1.0.0/transportation.xsd
View file @ 3c8fe882
......@@ -5,8 +5,9 @@
<!-- Prof. Dr. Thomas H. Kolbe, Institute for Geodesy and Geoinformation Science, Technical University of Berlin -->
<!-- For further information see: www.citygml.org -->
<!-- For the history of changes and additions to this CityGML schema see file history.txt -->
<xs:schema xmlns="http://www.opengis.net/citygml/transportation/1.0" xmlns:core="http://www.opengis.net/citygml/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml" targetNamespace="http://www.opengis.net/citygml/transportation/1.0" elementFormDefault="qualified"
<xs:schema xmlns="http://www.opengis.net/citygml/transportation/1.0" xmlns:core="http://www.opengis.net/citygml/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"
targetNamespace="http://www.opengis.net/citygml/transportation/1.0" elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../GML/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/citygml/1.0" schemaLocation="cityGMLBase.xsd"/>
......@@ -32,9 +33,10 @@
<!-- ========================================================================================= -->
<xs:complexType name="TransportationComplexType">
<xs:annotation>
<xs:documentation>Type describing transportation complexes, which are aggregated features, e.g. roads, which consist of parts (traffic areas, e.g.
pedestrian path, and auxiliary traffic areas). As subclass of _CityObject, a TransportationComplex inherits all attributes and relations, in
particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing transportation complexes, which are aggregated features, e.g. roads, which consist of
parts (traffic areas, e.g. pedestrian path, and auxiliary traffic areas). As subclass of _CityObject, a
TransportationComplex inherits all attributes and relations, in particular an id, names, external references, and
generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractTransportationObjectType">
......@@ -60,9 +62,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="TrafficAreaType">
<xs:annotation>
<xs:documentation>Type describing the class for traffic Areas. Traffic areas are the surfaces where traffic actually takes place. As subclass of
_CityObject, a TrafficArea inherits all attributes and relations, in particular an id, names, external references, and generalization relations.
</xs:documentation>
<xs:documentation>Type describing the class for traffic Areas. Traffic areas are the surfaces where traffic actually takes
place. As subclass of _CityObject, a TrafficArea inherits all attributes and relations, in particular an id, names,
external references, and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractTransportationObjectType">
......@@ -85,9 +87,10 @@
<!-- ========================================================================================= -->
<xs:complexType name="AuxiliaryTrafficAreaType">
<xs:annotation>
<xs:documentation>Type describing the class for auxiliary traffic Areas. These are the surfaces where no traffic actually takes place, but which
belong to a transportation object. Examples are kerbstones, road markings and grass stripes. As subclass of _CityObject, an AuxiliaryTrafficArea
inherits all attributes and relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the class for auxiliary traffic Areas. These are the surfaces where no traffic actually
takes place, but which belong to a transportation object. Examples are kerbstones, road markings and grass stripes. As
subclass of _CityObject, an AuxiliaryTrafficArea inherits all attributes and relations, in particular an id, names,
external references, and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="AbstractTransportationObjectType">
......@@ -109,8 +112,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="TrafficAreaPropertyType">
<xs:annotation>
<xs:documentation>Denotes the relation of TransportationComplex to its parts, which are traffic areas. The TrafficAreaPropertyType element must
either carry a reference to a TrafficArea object or contain a TrafficArea object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of TransportationComplex to its parts, which are traffic areas. The
TrafficAreaPropertyType element must either carry a reference to a TrafficArea object or contain a TrafficArea object
inline, but neither both nor none. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="gml:AssociationType">
......@@ -123,8 +127,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="AuxiliaryTrafficAreaPropertyType">
<xs:annotation>
<xs:documentation>Denotes the relation of TransportationComplex to its parts, which are auxiliary traffic areas. The TrafficAreaPropertyType element
must either carry a reference to a TrafficArea object or contain a TrafficArea object inline, but neither both nor none. </xs:documentation>
<xs:documentation>Denotes the relation of TransportationComplex to its parts, which are auxiliary traffic areas. The
TrafficAreaPropertyType element must either carry a reference to a TrafficArea object or contain a TrafficArea object
inline, but neither both nor none. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="gml:AssociationType">
......@@ -139,8 +144,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="TrackType">
<xs:annotation>
<xs:documentation>Type describing the class for tracks. A track is a small path mainly used by pedestrians. As subclass of _CityObject, a Track
inherits all attributes and relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the class for tracks. A track is a small path mainly used by pedestrians. As subclass of
_CityObject, a Track inherits all attributes and relations, in particular an id, names, external references, and
generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="TransportationComplexType">
......@@ -157,8 +163,8 @@
<!-- ========================================================================================= -->
<xs:complexType name="RoadType">
<xs:annotation>
<xs:documentation>Type describing the class for roads. As subclass of _CityObject, a Road inherits all attributes and relations, in particular an
id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the class for roads. As subclass of _CityObject, a Road inherits all attributes and
relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="TransportationComplexType">
......@@ -175,8 +181,8 @@
<!-- ========================================================================================= -->
<xs:complexType name="RailwayType">
<xs:annotation>
<xs:documentation>Type describing the class for railways. As subclass of _CityObject, a Railway inherits all attributes and relations, in particular
an id, names, external references, and generalization relations. </xs:documentation>
<xs:documentation>Type describing the class for railways. As subclass of _CityObject, a Railway inherits all attributes and
relations, in particular an id, names, external references, and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="TransportationComplexType">
......@@ -193,9 +199,9 @@
<!-- ========================================================================================= -->
<xs:complexType name="SquareType">
<xs:annotation>
<xs:documentation>Type describing the class for squares. A square is an open area commonly found in cities (like a plaza). As subclass of
_CityObject, a Square inherits all attributes and relations, in particular an id, names, external references, and generalization relations.
</xs:documentation>
<xs:documentation>Type describing the class for squares. A square is an open area commonly found in cities (like a plaza).
As subclass of _CityObject, a Square inherits all attributes and relations, in particular an id, names, external
references, and generalization relations. </xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="TransportationComplexType">
......@@ -212,40 +218,40 @@
<!-- ========================================================================================= -->
<xs:simpleType name="TransportationComplexFunctionType">
<xs:annotation>
<xs:documentation>Function of a transportation complex. The values of this type are defined in the XML file TransportationComplexFunctionType.xml,
according to the dictionary concept of GML3. </xs:documentation>
<xs:documentation>Function of a transportation complex. The values of this type are defined in the XML file
TransportationComplexFunctionType.xml, according to the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- ========================================================================================= -->
<xs:simpleType name="TransportationComplexUsageType">
<xs:annotation>
<xs:documentation>Actual Usage of a transportation complex. The values of this type are defined in the XML file TransportationComplexUsageType.xml,
according to the dictionary concept of GML3. </xs:documentation>
<xs:documentation>Actual Usage of a transportation complex. The values of this type are defined in the XML file
TransportationComplexUsageType.xml, according to the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- ========================================================================================= -->
<xs:simpleType name="TrafficAreaFunctionType">
<xs:annotation>
<xs:documentation>Function of a traffic area. The values of this type are defined in the XML file TrafficAreaFunctionType.xml, according to the
dictionary concept of GML3. </xs:documentation>
<xs:documentation>Function of a traffic area. The values of this type are defined in the XML file
TrafficAreaFunctionType.xml, according to the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- ========================================================================================= -->
<xs:simpleType name="AuxiliaryTrafficAreaFunctionType">
<xs:annotation>
<xs:documentation>Function of an auxiliary traffic area. The values of this type are defined in the XML file AuxiliaryTrafficAreaFunctionType.xml,
according to the dictionary concept of GML3. </xs:documentation>
<xs:documentation>Function of an auxiliary traffic area. The values of this type are defined in the XML file
AuxiliaryTrafficAreaFunctionType.xml, according to the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- ========================================================================================= -->
<xs:simpleType name="TrafficAreaUsageType">
<xs:annotation>
<xs:documentation>Usage of a traffic area. The values of this type are defined in the XML file TrafficAreaUsageType.xml, according to the dictionary
concept of GML3. </xs:documentation>
<xs:documentation>Usage of a traffic area. The values of this type are defined in the XML file TrafficAreaUsageType.xml,
according to the dictionary concept of GML3. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

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