<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "https://jats.nlm.nih.gov/nlm-dtd/publishing/3.0/journalpublishing3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="3.0" xml:lang="en">
<front>
<journal-meta>
<journal-id journal-id-type="publisher">ISPRS-Annals</journal-id>
<journal-title-group>
<journal-title>ISPRS Annals of Photogrammetry, Remote Sensing and Spatial Information Sciences</journal-title>
<abbrev-journal-title abbrev-type="publisher">ISPRS-Annals</abbrev-journal-title>
<abbrev-journal-title abbrev-type="nlm-ta">ISPRS Ann. Photogramm. Remote Sens. Spatial Inf. Sci.</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">2194-9050</issn>
<publisher><publisher-name>Copernicus Publications</publisher-name>
<publisher-loc>Göttingen, Germany</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.5194/isprs-annals-IV-2-W1-137-2016</article-id>
<title-group>
<article-title>A CITYGML EXTENSION FOR HANDLING VERY LARGE TINS</article-title>
</title-group>
<contrib-group><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Kumar</surname>
<given-names>K.</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
</contrib>
<contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Ledoux</surname>
<given-names>H.</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
</contrib>
<contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Stoter</surname>
<given-names>J.</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
</contrib>
</contrib-group><aff id="aff1">
<label>1</label>
<addr-line>3D Geoinformation, Delft University of Technology, the Netherlands</addr-line>
</aff>
<pub-date pub-type="epub">
<day>05</day>
<month>10</month>
<year>2016</year>
</pub-date>
<volume>IV-2/W1</volume>
<fpage>137</fpage>
<lpage>143</lpage>
<permissions>
<license license-type="open-access">
<license-p/>
</license>
</permissions>
<self-uri xlink:href="https://isprs-annals.copernicus.org/articles/isprs-annals-IV-2-W1-137-2016.html">This article is available from https://isprs-annals.copernicus.org/articles/isprs-annals-IV-2-W1-137-2016.html</self-uri>
<self-uri xlink:href="https://isprs-annals.copernicus.org/articles/isprs-annals-IV-2-W1-137-2016.pdf">The full text article is available as a PDF file from https://isprs-annals.copernicus.org/articles/isprs-annals-IV-2-W1-137-2016.pdf</self-uri>
<abstract>
<p>In addition to buildings, the terrain forms an important part of a 3D city model. Although in GIS terrains are usually represented with
2D grids, TINs are also increasingly being used in practice. One example is 3DTOP10NL, the 3D city model covering the whole of the
Netherlands, which stores the relief with a constrained TIN containing more than 1 billion triangles. Due to the massive size of such
datasets, the main problem that arises is: how to efficiently store and maintain them? While CityGML supports the storage of TINs,
we argue in this paper that the current solution is not adequate. For instance, the 1 billion+ triangles of 3DTOP10NL require 686 GB
of storage space with CityGML. Furthermore, the current solution does not store the topological relationships of the triangles, and also
there are no clear mechanisms to handle several LODs. We propose in this paper a CityGML extension for the &lt;i&gt;compact&lt;/i&gt; representation of
terrains. We describe our abstract and implementation specifications (modelled in UML), and our prototype implementation to convert
TINs to our CityGML structure. It increases the topological relationships that are explicitly represented, and allows us to compress up
to a factor of &amp;sim;&amp;thinsp;25 in our experiments with massive real-world terrains (more than 1 billion triangles).</p>
</abstract>
<counts><page-count count="7"/></counts>
</article-meta>
</front>
<body/>
<back>
</back>
</article>
