Source: http://docs.ogc.org/is/16-107r2/16-107r2.html
Timestamp: 2020-07-09 23:19:22
Document Index: 584714549

Matched Legal Cases: ['art 7', 'art7', 'arts\n7', 'art 7', 'art 7', 'art 6', 'art 6', 'art 0', 'art7', 'art7', 'art7', 'art 2', 'art7', 'art7', 'art7', 'art7', 'art7', 'art7', 'art7', 'art7', 'art7']

OGC InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard
Submission Date: 2017-06-14
Approval Date: 2017-08-14
External identifier of this OGC® document: http://www.opengis.net/doc/standard/infragml/part7/1.0
Internal reference number of this OGC® document: 16-107r2
Editor: Paul Scarponcini
4.1. Land Division Terms
4.1.1. cadastral survey
7.1.2. Dependent Requirement Classes Defined in Other Parts
7.1.3. Other Standards upon which the Requirement Classes of this Part Depend
7.2. Requirements Class: LandDivision
7.3. Requirements Class: Condominium
A.1. Conformance class: LandDivision
A.2. Conformance class: Condominium
B.1. Complete land division and condominium example
B.2. Bounding Elements example
B.3. Condominium example
InfraGML is published as a multi-part standard. This Part 7 addresses the LandDivision and Condominium Requirements Classes from LandInfra.
ogcdoc, OGC document, LandInfra, InfraGML, infrastructure, land parcel, real estate, immovable property, condominium, strata title
In order to achieve consensus on the concepts supporting land and civil engineering infrastructure facilities, a UML Conceptual Model, LandInfra, was approved as an OGC standard 2nd August, 2016. This model provides a unifying basis for encodings including but not limited to InfraGML, including similar work in buildingSMART International. It can also provide a framework for discussing how other software standards relate to LandInfra.
Aalborg University, Dept. of Development & Planning
The overall scope of this InfraGML Encoding Standard is infrastructure facilities and the land on which they are constructed. Also included is the surveying necessary for the setting out and as-built recording of these facilities and interests in land. Primarily having a civil engineering point of view, InfraGML is relevant across all life cycle phases of a facility. Subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.
The scope of this Part 7 of InfraGML addresses the following subject area(s): land division and condominium. These subject areas are commonly termed ‘cadastral survey’, but this term is avoided here, as it includes surveying, which is addressed by Part 6 of InfraGML. Two InfraGML Requirements Classes are included: LandDivision and Condominium. An application can conform to InfraGML without supporting all other parts of InfraGML, for example the Survey Requirements Classes of Part 6. However, to claim support for LandDivision, an application must also support the InfraGML Core and to claim support for Condominium, an application must in addition support the LandDivision Requirements Class.
software applications which read/write data instances, i.e., XML documents that encode land, infrastructure facility, and survey data for exchange.
OGC 07-036, OpenGIS® Geography Markup Language (GML) Encoding Standard, v3.2.1, August 27, 2007
OGC 10-129r1, OGC® Geography Markup Language (GML) — Extended schemas and encoding rules, v3.3, February 7, 2012
OGC 15-111r1, OGC Land and Infrastructure Conceptual Model Standard (LandInfra), v1.0, August 2nd , 2016.
OGC 16-100, OGC InfraGML 1.0: Part 0 – LandInfra Core – Encoding Standard, v1.0, June, 2017
survey of the boundary of an interest in land
Note 1 to entry: Cadastral survey is performed for the initial formation of property units, as well as for re-establishment of missing boundaries and subsequent changes of the boundaries.
Note 2 to entry: Demarcation of boundary with survey monument and documentation in terms of a statement is covered by this standard, while adjudication (the process leading to determination of rights in land) and registration (the official recording by the pertinent agency) is out of scope.
The LandInfra standard contains UML diagrams for the concepts supported by InfraGML. As these will not be repeated here, the reader is directed to Clause 7 of LandInfra. UML will only appear in InfraGML in the rare cases where LandInfra is extended by InfraGML.
When referred to in a Requirement or Requirements Class, the boxes contained in the LandInfra UML figures may all be called “Classes” even if they are data types, enumerations, code lists, unions etc. In most cases, these will be encoded as XML elements in InfraGML.
When an InfraGML Requirement states that “A conforming application shall support the [Requirements Class] XML elements listed in Table <n> in accordance with the GML XSD in this standard.”, the XSD was developed to support the UML for the corresponding LandInfra Requirements Class as follows:
The URI base for this InfraGML encoding standard is http://www.opengis.net/infragml/part7/1.0. All URIs of Requirements Classes, Requirements, and Conformance Classes contained in this standard are relative to this base.
LandInfra LandDivision
The Requirements Classes for this Part of the InfraGML encoding standard (shown in blue in Figure 3 below) are defined in this Clause 7. Requirements Classes from other Parts upon which this Part’s Requirements Classes are dependent (Core shown in beige in Figure 3 below) are listed here but defined in the documentation of their respective Parts. External OGC and ISO standards on which Requirements Classes in this Standard depend (shown in pink in Figure 3 below) are also listed. Below is a brief summary of the function of each of these Requirements Classes.
LandDivision
Land can be divided up into LandDivisions. These can either be public (political, judicial, or executive) or private in nature. The former are AdministrativeDivisions and the latter are InterestsInLand. Both of these are specified in the LandDivision Requirements Class, though condominium interests in land are specified in a separate, Condominium Requirements Class. The geometrical shape of these spatial units is modelled independently from their administrative or legal status, (see LandInfra UML, 7.10.6 SpatialUnit).
A CondominiumUnit is a concurrent ownership of real property that has been divided into private and common portions [2, 3]. The privately owned part is made up of clearly demarcated, floor related parts of a building (BuildingPart), as specified by a CondominiumScheme. CondominiumUnit owners are members of a mandatory owners’ association. Moreover, each CondominiumUnit has a share in the common parts of the property.
The Condominium Requirements Class includes information about condominium units, buildings and schemes. The Condominium Requirement Class is dependent on the LandDivision Requirement Class.
The Requirements Classes defined in this Part are dependent on the following Requirements Classes from other Parts.
LandInfra is the core Requirements Class and is the only mandatory Requirements Class. This class contains information about the Land and Infrastructure dataset that can contain information about facilities, land features, documents, professional, survey marks, surveys, sets, and feature associations. LandInfra also contains the definition of types common across other Requirements Classes, such as the Status CodeList.
/req/landdivision
/req/landdivision/elements
GML will not allow an element to be associated with another element if it is already on the part side of a composition association. For example, if, as the 15-111r1 Figure 62 UML shows, LandParcel is a compositional part of LandPropertyUnit, then it cannot also be associated with Easement. Therefore the composition association has been replaced by a mandatory, uni-directional (1..*) association from LandPropertyUnit to LandParcel. The LandParcel-Easement association has been simplified to become uni-directional from Easement to LandParcel.
A conforming application shall support the LandDivision XML elements listed in Table 1 below, in accordance with the GML XSD specified in http://schemas.opengis.net/infragml/part7/1.0/landdivision.xsd.
An application conforming to this standard shall support the LandDivision XML elements listed below in Table 1 in accordance with the GML XSD specified in http://schemas.opengis.net/infragml/part7/1.0/landdivision.xsd. LandDivision XML element names are shown with a XML namespace prefix of “lild”. Corresponding LandInfra UML classes are shown with their LandInfra Requirements Class prefix of “LandDivision”.
Table 1. InfraGML LandDivision XML elements with corresponding LandInfra UML classes
lild:AdministrativeDivision
LandDivision::AdministrativeDivision
lild:BEExplicitFace
LandDivision::BEExplicitFace
lild:BEExtrudedFace
LandDivision::BEExtrudedFace
lild:BEFace
LandDivision::BEFace
lild:BEImplicitFace
LandDivision::BEImplicitFace
lild:BEPoint
LandDivision::BEPoint
lild:BESolid
LandDivision::BESolid
lild:BEString
LandDivision::BEString
lild:BEText
LandDivision::BEText
lild:BoundingElement
LandDivision::BoundingElement
lild:Easement
LandDivision::Easement
lild:ExtrusionLimit
LandDivision::ExtrusionLimit
lild:InterestInLand
LandDivision::InterestInLand
lild:LandDivision
LandDivision::LandDivision
lild:LandParcel
LandDivision::LandParcel
lild:LandPropertyUnit
LandDivision::LandPropertyUnit
lild:Ownership
LandDivision::Ownership
lild:PropertyUnit
LandDivision::PropertyUnit
lild:Signatory
LandDivision::Signatory
lild:SpatialUnit
LandDivision::SpatialUnit
lild:Statement
LandDivision::Statement
lild:SuperficieObject
LandDivision::SuperficieObject
lild:SurveyMonument
LandDivision::SurveyMonument
/req/condominium
/req/condominium/elements
The following implementation decisions have been made regarding the OGC 15-111r1 Condominium Requirements Class UML:
LandInfra UML specifies CondominiumBuilding as subtype of Facility::Building, thereby creating a dependency on InfraGML Part 2 Facility. While this modelling is adequate, the benefit does not outweigh the cost of dependency. Waiting for linking with IFCs, CondominiumBuilding is here made subtype of LandInfra::Feature, similar to the modelling chosen for SuperficieObject (LandInfra UML 7.10.2.6)
GML will not allow an element to be associated with another element if it is already on the part side of a composition association. For example, if, as the 15-111r1 Figure 69 UML shows, BuildingPart is a compositional part of CondominiumBuilding, then it cannot also be associated with CondominiumUnit. Therefore the composition association has been replaced by a mandatory, uni-directional association from BuildingPart to CondominiumBuilding. The redundant CondominiumScheme-CondominiumBuilding association can now be dropped, as it is possible to determine the CondominiumBuildings participating in a CondominiumScheme by tracing from CondominiumScheme to CondominiumUnit to BuildingPart to CondominiumBuilding.
A conforming application shall support the Condominium XML elements listed in Table 2 below, in accordance with the GML XSD specified in http://schemas.opengis.net/infragml/part7/1.0/condominium.xsd.
An application conforming to this standard shall support the Condominium XML elements listed below in Table 2 in accordance with the GML XSD specified in http://schemas.opengis.net/infragml/part7/1.0/condominium.xsd. Condominium XML element names are shown with a XML namespace prefix of “lic”. Corresponding LandInfra UML classes are shown with their LandInfra Requirements Class prefix of “Condominium”.
Table 2. InfraGML Condominium XML elements with corresponding LandInfra UML classes
lic:BuildingPart
Condominium::BuildingPart
lic:CondominiumBuilding
Condominium::CondominiumBuilding
lic:CondominiumScheme
Condominium::CondominiumScheme
lic:CondominiumUnit
Condominium::CondominiumUnit
Conformance Class ID: /conf/landdivision
Requirements: /req/landdivision
/conf/landdivision/elements
Verify that the conforming application supports the LandDivision XML elements listed in Table 1 in accordance with the GML XSD specified in http://schemas.opengis.net/infragml/part7/1.0/ landdivision.xsd.
Conformance Class ID: /conf/condominium
Requirements: /req/condominium
Dependency: /conf/landdivision
/conf/condominium/elements
Verify that the conforming application supports the Condominium XML elements listed in Table 2 in accordance with the GML XSD specified in http://schemas.opengis.net/infragml/part7/1.0/condominium.xsd.
The following XML example document demonstrates all attributes and roles from all classes contained in the LandDivision and Condominium RCs, except for bounding elements which are shown in B.2.
<li:LandInfraDataset xmlns:lic="http://www.opengis.net/infragml/condominium/1.0" xmlns:lild="http://www.opengis.net/infragml/landdivision/1.0" xmlns:li="http://www.opengis.net/infragml/core/1.0" xmlns:gml="http://www.opengis.net/gml/3.2" gml:id="c00" xmlns:gmllr="http://www.opengis.net/gml/3.3/lr" xmlns:gmllro="http://www.opengis.net/gml/3.3/lro" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/infragml/condominium/1.0 Part7Condominium0410.xsd">
<li:datasetID>
<li:ID>
<li:identifier>ldco</li:identifier>
<li:scope>OGC LandInfra</li:scope>
</li:ID>
</li:datasetID>
<li:dateTime>2017-05-05T10:00:00</li:dateTime>
<li:datasetVersion>1.0</li:datasetVersion>
<li:application>manual</li:application>
<li:author>Erik Stubkjær, Aalborg University, Denmark</li:author>
<li:infraVersion>1.0</li:infraVersion>
<li:language>English</li:language>
<li:defaultCRS xlink:href="urn:ogc:def:crs:EPSG::4094"/>
<!--   Administrative Division                                      -->
<li:feature>
<lild:AdministrativeDivision gml:id="ad1">
<lild:adID>
<lild:ID>
<li:identifier>851</li:identifier>
</lild:ID>
</lild:adID>
<lild:adType>Municipality</lild:adType>
<lild:shapeAndLocation>
<lild:SpatialUnit gml:id="ad1su">
<lild:spatialUnitID>
<li:identifier>Aalborg</li:identifier>
</lild:spatialUnitID>
<lild:dimension>2D</lild:dimension>
<lild:boundingElement/>
</lild:SpatialUnit>
</lild:shapeAndLocation>
<lild:ownedBy xlink:href="ad2"/>
</lild:AdministrativeDivision>
</li:feature>
<lild:AdministrativeDivision gml:id="ad2">
<li:identifier>DK05</li:identifier>
<lild:adType>Region</lild:adType>
<lild:isoCode>DK-81</lild:isoCode>
<lild:SpatialUnit gml:id="ad2su">
<li:identifier>Nordjylland</li:identifier>
<!-- See file 'complete bounding elements example 20170410 pxs.xml' -->
<lild:part xlink:href="ad1"/>
<!--   Easement with Statement                                       -->
<lild:Easement gml:id="es">
<lild:documentation>
<lild:Statement gml:id="st1">
<li:documentID>
<li:identifier>12</li:identifier>
</li:documentID>
<li:documentType>easementEstablishment</li:documentType>
<li:documentContent>DocumentContent.odt</li:documentContent>
<lild:type xlink:href="http://example.com/StatementType#easementEstablishment"
xlink:title="easementEstablishment"/>
<lild:draftsman>
<li:Professional gml:id="pr1">
<li:fullName>Peter P</li:fullName>
xlink:title="landSurveyor"/>
<li:company>ABC</li:company>
<li:registration>LicenseW1986-23</li:registration>
<li:licensingCountry>DK</li:licensingCountry>
</li:Professional>
</lild:draftsman>
<lild:caseID>
<li:identifier>123</li:identifier>
</lild:caseID>
<lild:landRecordingDocumentId>
<li:identifier>LRident234</li:identifier>
</lild:landRecordingDocumentId>
<lild:signatory>
<lild:Signatory gml:id="sig1">
<lild:signingParty>Sanny Sandy</lild:signingParty>
<lild:role xlink:href="http://example.com/SigningRole#owner" xlink:title="owner"/>
<lild:signingDate>2016-03-03</lild:signingDate>
</lild:Signatory>
</lild:Statement>
</lild:documentation>
<lild:easementID>
<li:identifier>234</li:identifier>
</lild:easementID>
<lild:type xlink:href="http://example.com/EasementType#rightOfWay"
xlink:title="RightOfWay"/>
<lild:beneficiaryParty>Current owner of LandParcel 'lp'</lild:beneficiaryParty>
<lild:permittedUse>Context-specific description of the permitted use</lild:permittedUse>
<lild:across xlink:href="lp"/>
</lild:Easement>
<!--   SurveyMonument                                                -->
<lild:SurveyMonument gml:id="sm">
<lild:type xlink:href="http://example.com/SurveyMonumentType#boundaryMark"
xlink:title="boundaryMark"/>
<lild:documentation xlink:href="st1"/>
</lild:SurveyMonument>
<!--   PropertyUnit                                                  -->
<lild:PropertyUnit gml:id="pu">
<lild:propertyUnitID>
<li:scope>X municipality</li:scope>
</lild:propertyUnitID>
<lild:ownership>
<lild:Ownership gml:id="os">
<lild:name>Sanny Sandy</lild:name>
<lild:relativeShare>100</lild:relativeShare>
<lild:ownerAddress>Next Village Road 5</lild:ownerAddress>
</lild:Ownership>
</lild:PropertyUnit>
<!--    LandPropertyUnit with LandParcel                             -->
<lild:LandPropertyUnit gml:id="lpu">
<lild:documentation/>
<lild:ownership xlink:href="os"/>
<lild:postAddress>Post address of LandPropertyUnit</lild:postAddress>
<lild:landParcel>
<lild:LandParcel gml:id="lp">
<lild:cadastralParcelId>
<li:identifier>13g</li:identifier>
<li:scope>H Township</li:scope>
</lild:cadastralParcelId>
<lild:parcelArea uom="m2">927</lild:parcelArea>
<lild:currentLandUse>Residential</lild:currentLandUse>
<lild:plannedLandUse>Residential, low and detached</lild:plannedLandUse>
<lild:parcelState>current</lild:parcelState>
<lild:SpatialUnit gml:id="su2">
<li:identifier>13/23</li:identifier>
<lild:boundingElement>
<lild:BEString gml:id="e">
<lild:boundingElementID/>
<lild:isComplete>true</lild:isComplete>
<lild:geometry>
<gml:Polygon gml:id="f">
<gml:pos>397291.57 1317064.10</gml:pos>
<gml:pos>397338.29 1317063.42</gml:pos>
<gml:pos>397337.93 1317049.88</gml:pos>
<gml:pos>397336.13 1317043.45</gml:pos>
<gml:pos>397291.50 1317044.11</gml:pos>
</lild:geometry>
<lild:stringType>ring</lild:stringType>
</lild:BEString>
</lild:boundingElement>
<lild:within xlink:href="ad1"/>
</lild:LandParcel>
</lild:LandPropertyUnit>
<!--   SuperficieObject with Statement                               -->
<lild:SuperficieObject gml:id="so1">
<lild:superficieID>
<li:identifier>345</li:identifier>
</lild:superficieID>
<lild:type>Shelter</lild:type>
<lild:Ownership gml:id="os2">
<lild:name>Civil Defence Agency</lild:name>
<lild:ownerAddress>CDA address</lild:ownerAddress>
<lild:encumbranceScheme>
<lild:Statement gml:id="st2">
<li:identifier>456</li:identifier>
<li:documentType/>
<li:documentContent>Details on location, access and relation to surface LandParcels, which may be formally provided through LandParcel, SpatialUnit, and Easement</li:documentContent>
<lild:type/>
<lild:draftsman/>
<li:identifier>567</li:identifier>
<lild:Signatory gml:id="si2">
<lild:signingParty>Expropriation Authority</lild:signingParty>
<lild:signingDate>1964-02-10</lild:signingDate>
</lild:encumbranceScheme>
</lild:SuperficieObject>
<!--   BuildingPart with CondominiumBuilding                            -->
<lic:BuildingPart gml:id="bp1">
<lic:floorNumber>3</lic:floorNumber>
<lic:subSurfaceFloor>false</lic:subSurfaceFloor>
<lic:floorArea uom="m2">87</lic:floorArea>
<lic:buildingPartType>condominiumMainPart</lic:buildingPartType>
<lic:shapeAndLocation/>
<lic:partOf>
<lic:CondominiumBuilding gml:id="cb1">
<lic:buildingNumber>567</lic:buildingNumber>
<lic:parcelLocation xlink:href="lp"/>
</lic:CondominiumBuilding>
</lic:partOf>
</lic:BuildingPart>
<!--  CondominiumScheme with CondominiumUnits                           -->
<lic:CondominiumScheme gml:id="cs1">
<li:identifier>678</li:identifier>
<li:documentType>CondominiumScheme</li:documentType>
<lild:type xlink:href="http://example.com/StatementType#condominiumScheme"
xlink:title="condominiumScheme"/>
<lild:draftsman xlink:href="pr1"/>
<li:identifier>789</li:identifier>
<lild:Signatory gml:id="s3">
<lild:signingParty>sp</lild:signingParty>
<lild:signingDate>2017-03-03</lild:signingDate>
<lic:buildingDescription>Free-text building description</lic:buildingDescription>
<lic:unit>
<lic:CondominiumUnit gml:id="cu1">
<lild:ownership/>
<!-- Unknown at the time of subdivision -->
<lic:shareInJointFacilities>23/108</lic:shareInJointFacilities>
<lic:condominiumUseType
xlink:href="http://example.com/CondominiumUseType#residential"
xlink:title="residential"/>
<lic:designUnitID/>
<!-- Optional id for use during construction -->
<lic:mainPart>
<lic:BuildingPart gml:id="bp2">
<lic:floorNumber>1</lic:floorNumber>
<lic:partOf xlink:href="cb1"/>
</lic:mainPart>
<lic:accessoryPart>
<lic:BuildingPart gml:id="bp3">
<lic:floorNumber>0</lic:floorNumber>
<lic:subSurfaceFloor>true</lic:subSurfaceFloor>
<lic:buildingPartType>condominiumAccessoryPart</lic:buildingPartType>
</lic:accessoryPart>
</lic:CondominiumUnit>
</lic:unit>
<lic:CondominiumUnit gml:id="cu2">
<li:identifier>23</li:identifier>
<lic:shareInJointFacilities>10/108</lic:shareInJointFacilities>
<lic:BuildingPart gml:id="bp4">
<lic:floorNumber>2</lic:floorNumber>
</lic:CondominiumScheme>
</li:LandInfraDataset>
This example demonstrates how Bounding Elements are encoded. Every type is included as if it were valid for Land Parcels, though some may be more appropriate for Condominium Building Parts. Coordinate values are chosen for clarity and may therefore not be realistic for real Land Parcels or Building Parts. See OGC 15-111r1 for a complete definition of the various types of Bounding Elements. The first three Spatial Units demonstrate the difference in dimension only and are not complete in definition, as they lack Bounding Elements.
xmlns:lild="http://www.opengis.net/infragml/landdivision/1.0"
gml:id="BE"
xmlns:gmllr="http://www.opengis.net/gml/3.3/lr"
xmlns:gmllro="http://www.opengis.net/gml/3.3/lro"
xsi:schemaLocation="http://www.opengis.net/infragml/landdivision/1.0 Part7LandDivision0410.xsd">
<identifier>BE</identifier>
<dateTime>2017-03-22T10:00:00</dateTime>
<author>Paul Scarponcini</author>
<defaultCRS/>
<lild:LandPropertyUnit gml:id="lpu1">
<lild:documentation></lild:documentation>
<lild:ownership></lild:ownership>
<!--                                                                                                      -->
<!--     2D Land Parcel                                                                           -->
<lild:LandParcel gml:id="lp2D">
<lild:parcelArea uom="sf">5000</lild:parcelArea>
<lild:SpatialUnit gml:id="su2D">
<lild:boundingElement></lild:boundingElement>
<!--     LIM Land Parcel                                                                           -->
<lild:LandParcel gml:id="lpLIM">
<lild:SpatialUnit gml:id="suLIM">
<lild:dimension>liminal</lild:dimension>
<!--     3D Land Parcel                                                                           -->
<lild:LandParcel gml:id="lp3D">
<lild:parcelArea uom="cf">1000000</lild:parcelArea>
<lild:SpatialUnit gml:id="su3D">
<lild:dimension>3D</lild:dimension>
The 2D-T Spatial Unit demonstrates the use of the BEText Bounding Element in 2D:
<!--     2D-T Land Parcel                                                                          -->
<lild:LandParcel gml:id="lp2D-T">
<lild:SpatialUnit gml:id="su2D-T">
<lild:BEText gml:id="text1">
<lild:boundingElementID></lild:boundingElementID>
"Beginning at Survey Monument SM1, thence North 50 feet, thence East 100 feet,
thence South 50 feet, thence West 100 feet to the point of beginning"
</lild:BEText>
The 2D-P Spatial Unit demonstrates the use of the BEPoint Bounding Element in 2D, where a single representative point within the Land Parcel is used. The 2D-R Spatial Unit demonstrate the use of the BEString ring type of Bounding Element in 2D, where the exterior boundary is specified as a closed linestring geometry. 2D-H extends the ring example to include an interior ring defining a hole boundary.
<!--     2D-P Land Parcel                                                                           -->
<lild:LandParcel gml:id="lp2D-P">
<lild:SpatialUnit gml:id="su2D-P">
<lild:BEPoint gml:id="point1">
<lild:isComplete>false</lild:isComplete>
<gml:pos>50 25</gml:pos>
</lild:BEPoint>
<!--     2D-R Land Parcel                                                                           -->
<lild:LandParcel gml:id="lp2D-R">
<lild:SpatialUnit gml:id="su2D-R">
<lild:BEString gml:id="ring1">
<gml:LineString gml:id="ls1">
<gml:pos>100 0</gml:pos>
<gml:pos>200 0</gml:pos>
<gml:pos>200 50</gml:pos>
<gml:pos>100 50</gml:pos>
<!--     2D-H Land Parcel                                                                           -->
<lild:LandParcel gml:id="lp2D-H">
<lild:parcelArea uom="sf">4800</lild:parcelArea>
<lild:SpatialUnit gml:id="su2D-H">
<lild:BEString gml:id="hole1">
<gml:MultiCurve gml:id="mc1">
<gml:LineString gml:id="ls2">
<gml:pos>300 0</gml:pos>
<gml:pos>300 50</gml:pos>
<gml:LineString gml:id="ls3">
<gml:pos>270 30</gml:pos>
<gml:pos>270 40</gml:pos>
<gml:pos>290 40</gml:pos>
<gml:pos>290 30</gml:pos>
The 2D-CC Spatial Unit demonstrate the use of the other four types of BEString Bounding Elements in 2D: partial, unstructured, structured, and topological. The partial type specifies that only part of the common boundary (linestring ls4) is used by 2D-CC. The 2D-TC Spatial Unit demonstrates how a Bounding Element geometry (linestring ls7) can be shared by two Spatial Units (in opposite directions). Note that 2D-TC uses another part of the common boundary (linestring ls4)
<!--     2D-CC Land Parcel                                                                           -->
<lild:LandParcel gml:id="lp2D-CC">
<lild:SpatialUnit gml:id="su2D-CC">
<lild:BEString gml:id="partial1">
<gml:LineString gml:id="ls4">
<gml:pos>50 0</gml:pos>
<gml:pos>350 0</gml:pos>
<lild:stringType>partial</lild:stringType>
<lild:BEString gml:id="unstructured1">
<gml:LineString gml:id="ls5">
<gml:pos>100 49</gml:pos>
<lild:stringType>unstructured</lild:stringType>
<lild:BEString gml:id="structured1">
<gml:LineString gml:id="ls6">
<lild:stringType>structured</lild:stringType>
<lild:direction>reverse</lild:direction>
<lild:BEString gml:id="topo1">
<gml:LineString gml:id="ls7">
<lild:stringType>topological</lild:stringType>
<!--     2D-TC Land Parcel                                                                           -->
<lild:LandParcel gml:id="lp2D-TC">
<lild:SpatialUnit gml:id="su2D-TC">
<lild:boundingElement xlink:href="partial1">
<lild:BEString gml:id="topo2">
<lild:geometry xlink:href="ls7"></lild:geometry>
<lild:direction>forward</lild:direction>
The last two Spatial Units are 3D. The first, 3D-FC has a combination of the three BEFace types of Bounding Elements: extruded, explicit, and implicit. Only three sides of the Spatial Unit have been specified. The 3D-S provides a complete geometry definition, using a solid geometry type.
<!--     3D-FC Land Parcel                                                                 -->
<lild:LandParcel gml:id="lp3D-FC">
<lild:SpatialUnit gml:id="su3D-FC">
<lild:BEExtrudedFace gml:id="extruded1">
<gml:LineString gml:id="ls8">
<gml:pos>0 0 0</gml:pos>
<lild:lowerLimit>
<lild:Limit>
<lild:distance>0</lild:distance>
</lild:Limit>
</lild:lowerLimit>
<lild:upperLimit>
<lild:distance>20</lild:distance>
</lild:upperLimit>
</lild:BEExtrudedFace>
<lild:BEExplicitFace gml:id="explicit1">
<gml:PolyhedralSurface gml:id="surf1">
<gml:LineString gml:id="ls9">
<gml:pos>100 0 0</gml:pos>
<gml:pos>100 50 0</gml:pos>
<gml:pos>100 50 20</gml:pos>
<gml:pos>100 0 20</gml:pos>
</lild:BEExplicitFace>
<lild:BEImplicitFace gml:id="implicit1">
<lild:geometry>top</lild:geometry>
</lild:BEImplicitFace>
<!--     3D-S Land Parcel                                                                 -->
<lild:LandParcel gml:id="lp3D-S">
<lild:SpatialUnit gml:id="su3D-S">
<lild:BESolid gml:id="solid1">
<gml:Solid gml:id="s1">
<gml:Shell>
<gml:Polygon gml:id="west">
<gml:LineString gml:id="ls10">
<gml:Polygon gml:id="north">
<gml:LineString gml:id="ls11">
<gml:pos>200 50 0</gml:pos>
<gml:pos>200 50 20</gml:pos>
<gml:Polygon gml:id="east">
<gml:LineString gml:id="ls12">
<gml:pos>200 0 0</gml:pos>
<gml:pos>200 0 20</gml:pos>
<gml:Polygon gml:id="south">
<gml:LineString gml:id="ls13">
<gml:Polygon gml:id="top">
<gml:LineString gml:id="ls14">
<gml:Polygon gml:id="bottom">
<gml:LineString gml:id="ls15">
</gml:Shell>
</gml:Solid>
</lild:BESolid>
A PropertyUnit consist of the LandParcel 17b with a building of two stairwells and three floors. The owner wants to subdivide the PropertyUnit into CondominiumUnits. In the example, the CondominiumUnits generally consist of an apartment and a storeroom, as specified in the CondominiumScheme below, here showing only two CondominiumUnits.
<?xml-stylesheet type="text/xsl" href="CondominiumExample0518.xsl"?>
<li:LandInfraDataset xmlns="http://www.opengis.net/infragml/condominium/1.0" xmlns:lild="http://www.opengis.net/infragml/landdivision/1.0" xmlns:li="http://www.opengis.net/infragml/core/1.0" xmlns:gml="http://www.opengis.net/gml/3.2" gml:id="c00" xmlns:gmllr="http://www.opengis.net/gml/3.3/lr" xmlns:gmllro="http://www.opengis.net/gml/3.3/lro" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/infragml/condominium/1.0 Part7Condominium0410.xsd">
<li:identifier>c0</li:identifier>
<li:scope>OGC LandInfraSWG</li:scope>
<li:name>Part7 Condominium Dataset</li:name>
<li:description>LandInfra dataset to test content for Part7 Condominium</li:description>
<li:dateTime>2017-03-10T21:00:00</li:dateTime>
<li:defaultCRS/>
The present dataset is needed for establishment of CondominiumUnits. They consist of one or more parts of CondominiumBuilding(s). Future CondominiumUnits owners get exclusive rights to their CondominiumUnit as well as a mandatory share in the joint elements of the PropertyUnit: Roof, outer walls, technical installations, the LandParcel(s), etc. The sale and future owners are out of scope relative to the present condominiumSchemeEstablishment.
The LandSurveyor documents the requested through the present CondominiumScheme, which provides the data for the above tabular and graphical parts.
<!-- The LandPropertyUnit to be subdivided into CondominiumUnits             -->
<li:scope>Recording District</li:scope>
<lild:Ownership gml:id="o1">
<lild:name>Peter</lild:name>
<lild:ownerAddress>Some other place</lild:ownerAddress>
<lild:LandParcel gml:id="lp1">
<li:identifier>17b</li:identifier>
<li:scope>Cadastral Township x of City y</li:scope>
<lild:parcelArea uom="m2">1200</lild:parcelArea>
<lild:SpatialUnit gml:id="su1">
<li:identifier/>
<lild:BEString gml:id="sub1">
<gml:LineString gml:id="sub11">
<gml:posList srsDimension="2">830 910 830 1290 930 1390 1620 1390 1620 1060
1230 990 830 910</gml:posList>
<!-- The building to be subdivided and its location on the LandParcel        -->
<CondominiumBuilding gml:id="cb1">
<gml:description>Location of CondominiumBuilding on LandParcel</gml:description>
<li:spatialRepresentation>
<li:geometry>
<gml:LineString gml:id="fp1">
<gml:posList srsDimension="2">980 1150 1530 1150 1530 1290 980 1290 980
1150</gml:posList>
</li:geometry>
</li:SpatialRepresentation>
<buildingNumber>1234</buildingNumber>
<parcelLocation xlink:href="lp1"/>
</CondominiumBuilding>
<!-- The CondominiumScheme with CondominiumUnits and their BuildingParts. Of a total of 10 units, only two are shown   -->
<CondominiumScheme gml:id="cs1">
<li:identifier>001</li:identifier>
<li:documentType>condominiumSchemeEstablishment</li:documentType>
<lild:type
xlink:href="http://example.com/StatementType#condominiumSchemeEstablishment"
xlink:title="condominiumSchemeEstablishment"/>
<li:Professional gml:id="prof1">
<li:fullName>Hans Pedometer</li:fullName>
<li:company>Measurewell</li:company>
<li:registration>LicenseX_1968-43</li:registration>
<li:identifier>Case2017-C23</li:identifier>
<li:scope>Aalborg branch</li:scope>
<lild:Signatory gml:id="ld3">
<lild:signingParty>Hans Pedometer</lild:signingParty>
<lild:signingDate>2017-03-04</lild:signingDate>
<buildingDescription>Optional description of building</buildingDescription>
<CondominiumUnit gml:id="cu2">
<lild:documentation xlink:href="c61"/>
<li:identifier>2</li:identifier>
<li:scope/>
<lild:postAddress>Autumn Road 1, ground floor left</lild:postAddress>
<shareInJointFacilities>10/120</shareInJointFacilities>
<condominiumUseType/>
<designUnitID/>
<BuildingPart gml:id="bp2m">
<floorNumber>Ground floor</floorNumber>
<subSurfaceFloor>false</subSurfaceFloor>
<buildingPartType>condominiumMainPart</buildingPartType>
<shapeAndLocation>
<li:identifier>2m</li:identifier>
<lild:area uom="m2">78</lild:area>
<lild:BEString gml:id="w7">
<gml:LineString gml:id="w8">
<gml:posList srsDimension="2">450 1510 100 1510 100 1060 570 1060 570
1260 450 1260 450 1510</gml:posList>
</shapeAndLocation>
<partOf xlink:href="cb1"/>
</BuildingPart>
<accessoryPart>
<BuildingPart gml:id="bp2a">
<floorNumber>Basement</floorNumber>
<subSurfaceFloor>true</subSurfaceFloor>
<buildingPartType>condominiumAccessoryPart</buildingPartType>
<lild:SpatialUnit gml:id="su3">
<li:identifier>2a</li:identifier>
<lild:area uom="m2">6</lild:area>
<lild:BEString gml:id="w10">
<gml:LineString gml:id="w9">
<gml:posList srsDimension="2">560 2160 560 1960 630 1960 630 2160 560
2160</gml:posList>
</accessoryPart>
</CondominiumUnit>
<CondominiumUnit gml:id="cu9">
<lild:documentation xlink:href="c61">
<li:identifier>9</li:identifier>
<lild:postAddress>Autumn Road 3, 1st floor left</lild:postAddress>
<shareInJointFacilities>11/120</shareInJointFacilities>
<BuildingPart gml:id="bp9m">
<floorNumber>1st floor</floorNumber>
<lild:SpatialUnit gml:id="su4">
<li:identifier>9m</li:identifier>
<lild:area uom="m2">77</lild:area>
<lild:BEString gml:id="w1">
<gml:LineString gml:id="w2">
<gml:posList srsDimension="2">790 410 1250 410 1250 610 1130 610 1130 860
790 860 790 410</gml:posList>
<BuildingPart gml:id="bp9a">
<lild:SpatialUnit gml:id="su5">
<li:identifier>9a</li:identifier>
<lild:area uom="m2">5</lild:area>
<lild:BEString gml:id="w3">
<gml:LineString gml:id="w4">
<gml:posList srsDimension="2">980 2160 980 1960 1050 1960 1050 2160 980
<BuildingPart gml:id="bp9b">
<lild:SpatialUnit gml:id="su6">
<li:identifier>9b</li:identifier>
<lild:BEString gml:id="w5">
<gml:LineString gml:id="w6">
<gml:posList srsDimension="2">910 2160 910 1960 980 1960 980 2160 910
</CondominiumScheme>
Fixed GML striping; added complete example; removed Cadastre example
107r2
[1] OGC 08-131r3 The Specification Model — A Standard for Modular specifications, Open Geospatial Consortium, (2009) [2] Des Ormeaux, Anne and Jean-Marie Lessard. Legal Dictionary of Property in Canada - Dictionnaire juridique de la propriété au Canada, [online], 2009. [dualjuridik.org], 6. November 2015 [3] UN/ECE. Guidelines on Condominium Ownership of Housing for Countries in Transition. Geneva, June 2003
Last updated 2018-08-22 15:43:48 EDT