Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Storage, Maintenance and Dissemination of Massive 3D City Objects

3D4EM
May 31, 2016
490

Storage, Maintenance and Dissemination of Massive 3D City Objects

3D4EM

May 31, 2016
Tweet

Transcript

  1. Voluminous data • CityGML 3DTOPNL Terrains : TIN : ~700

    GB (1 billion triangles) ( x 1 , y 1 , z 1) ( x 2 , y 2 , z 2) ( x 3 , y 3 , z 3) < gml : triangle > < gml : exterior > < gml : LinearRing > < gml : posList > x 1 y 1 z 1 x 2 y 2 z 2 x 3 y 3 z 3 x 1 y 1 z 1 < /gml : posList > < gml : LinearRing > < gml : exterior > < gml : triangle > OGC Simple Feature No referencing No TIN topology
  2. Problems • No support for terrain topology in: • CityGML

    TINRelief and • CityGML MassPointRelief
  3. Nothing for Tiling Unsafe Triangles Tile 1 Tile 2 Tile

    3 Tile 4 Tile Boundary Triangles spanning multiple tiles
  4. Terrain as TIN + Grid TIN Relief Grid Coverage validity

    polygon Not at the centre of grid cell
  5. What needs to be done? • Redefinition of conceptual model

    of geometry in the CityGML schema for terrains.
  6. Terrain@CityGML • CityGML 3DTOPNL Terrains : ~700 GB (1 billion

    triangles) • For 1 tile: • CityGML: ~ 740 MB • Terrains@CityGML: ~ 30 MB ~25x less storage space Compressed workable file (~5 to 7 MBs for 1 tile)
  7. 3D over Cesium • A s g e o m

    e t r y ( P o l y g o n / B o x / C y l i n d e r / Rectangle,..etc.)
  8. 3D over Cesium • A s g e o m

    e t r y ( P o l y g o n / B o x / C y l i n d e r / Rectangle,..etc.) Coordinates
  9. 3D over Cesium • A s g l T F

    ( G L Tr a n s m i s s i o n F o r m a t ) : Interoperability??
  10. A way around glTF Terrains@CityGML Parser JSON Description file Binary

    data file Textures Cesium API 30 MB 8 KB 24 MB
  11. As Quantized Mesh • At present: • only height maps

    for Rasters • No TIN implementation Terrains@CityGML Generate Quadtree Cesium API Generate header .terrain tiles Cesium Terrain Server