BIM roadmap

[pjcozzi]

Priority 1 - Optimizations / BIM Requirements

Optimizations for large 3D Tiles tilesets

• [ ] Viewlets - 2D schematics in separate window. Click in a schematic to highlight/zoom in BIM view. Also text list-view of objects, click to highlight/zoom in BIM view. 2D schematic vs. water pipes on a neighborhood, e.g., drape line under street. #5214
  • Rasterize on server with pick IDs or send vector data to client (requires custom fonts). @pjcozzi suggests the former
  • [x] Analyze latest reality model (RM) and design model (DM) tilesets
  • Do RMs have too many levels? Looking into coarser levels for DM tilesets
  • [x] Long list of optimizations in #3241 until things are smooth enough (on iPad in particular)
  • [ ] Better memory management on mobile in general
  • [ ] Try adding a request volume to a BIM model so it is not loaded until the viewer enters the volume

Priority 2 - BIM Requirements

• [x] Navigation
  • [x] Indoor mode - adjust far/near to avoid z-fighting, render environment to texture given know area of interest

Priority 3 - Classification of mesh + GIS data

• [x] Polygon-on-terrain approach or texture generation at runtime, both from declarative style. Also want to do pick and know classification
  • Branches: 3d-tiles-classification, 3d-tiles-classification-height
• https://github.com/AnalyticalGraphicsInc/cesium/compare/vector-tiles...vector-tiles-buildings

Priority 4 - BIM Requirements

• [x] Object selection: Post-processed animated silhouettes for objects of interest
• [ ] Polyline shader (if support is needed)

Priority TBA

• [ ] Separate into multiple modules, #2524
• [ ] Type script definitions? #4434
• [ ] Per-tileset AA for tilesets with thin lines?
• [ ] Do not request terrain tiles under tileset (or maybe tileset tiles under tilesets)
  • Blend terrain with tileset for sparse areas of a tileset
• [ ] Diffing/blending BIM vs. Reality Model. Focus on one or the other. Review http://pellacini.di.uniroma1.it/
• Possibility once performance optimizations reach a reasonable point
  • [x] Draco compression https://github.com/AnalyticalGraphicsInc/cesium/issues/5120
  • [ ] Underground - railways with signals along track, subway tunnels (pick on assets underground), utilities (pipes, service tunnels), geotechnics: (e.g., 3-4 floors of basement for 40-50 story building)
• [ ] Integrate with other WebGL engines, also useful for 2D, #648
• [ ] Runtime batching, perhaps scoped just for point clouds
• [x] Polygon clamping in ortho (for classification)? #5110
• [ ] Full lighting system when appropriate. IBL/PBR from glTF
• [ ] Time-dynamic: 4 or 5 reality models each with a time stamp. Blending
• [ ] Site planning - viewsheds. When foggy, what is the visibility in a corridor? Smoke sim, what is the path to replace a pump?
• [ ] Fix for camera workaround for to looking directly toward / away from the globe:

  
  Cartesian3.clone(modelDest, camera.position);
  Cartesian3.clone(view.dir, camera.direction);
  Cartesian3.clone(view.up, camera.up);

// orthogonalization Cartesian3.cross(camera.direction, camera.up, camera.right); Cartesian3.cross(camera.right, camera.direction, camera.up);

// ensure normalized, cross can give non-unit vectors because of floating-point numbers Cartesian3.normalize(camera.up, camera.up); Cartesian3.normalize(camera.right, camera.right); // normalize camera.direction if view.dir is not a unit vector

- [ ] Merge walk tool into core Cesium
- [ ] High-res printing (multiview port).  Perhaps also save as pdf.
- [ ] **Measurements**
   * Take measurements by, for example, manually selecting points on the roof to define polygons that cover entire roof, show polygons overlaid/intersecting with 3D model
      * Approximation with local plane is OK.
   * Allow multiple polygons to be defined and displayed on the model at the same time
   * Needed measurements include area, pitch, lengths (valley, ridges, hips, eaves, rakes, parapets, etc.)
   * Ability to classify, apply tags, or otherwise group the different measurements to allow total calculations for the roof
   * Given a polygon in a plane, extrude it, and compute the volume.
- [ ] **Collision detection** with avatar, e.g., person going into the sewer.
- [ ] @pjcozzi's suggestions
   - [ ] WebGL 2
   - [x] CPU usage, #1865 

# Done

- [x] Classification WIP, #5234
- [x] Not require file extensions for tiles since they are created on the fly.  #5206
- [x] Viewlet research, #5225
- [x] Update FXAA, #5200
- [x] Investigate issue with breath-first loading, #5128
- [x] Terrain clamping: turn off depth test per entity for labels, billboards, polylines, and polygons, #5160, #5168, (#5159)
- [x] Orthographic frustum in 3D, #5021, #5108, #5107, #5132, #5143
- [x] **Object selection**: Pick translucent objects, #4511, #4979
- [x] Performance improvements and tools: #4872, http://cesiumjs.org/2017/02/02/Tighter-Frustum-Culling-and-Why-You-May-Want-to-Disregard-It/, http://cesiumjs.org/2017/02/17/Hierarchical-Culling-With-Children-Bounding-Volumes/
- [x] Texture compression, #4679, #4758, https://github.com/AnalyticalGraphicsInc/gltf-pipeline/pull/204
- [x] Enable 3D Tiles in Columbus View
- [x] 3D Tiles in 2D, #4884
   - [x] i3dm in 2D, #4996
- [x] 3D Tiles declarative styling: replacement or highlight color (can we do this without using a lot of memory?)
- [x] New Batch Table design and/or Cesium tile load events so that the Batch Table can store more complex data structures with less redundancy, e.g., duplicate model IDs.  Related: https://github.com/AnalyticalGraphicsInc/3d-tiles/issues/66
- [x] **Inside lighting**: default rig with two lights to start
- [x] **Navigation** - @pmconne willing to contribute
  - [x] Option to keep camera "up"
  - [x] Walk tool, including walk through walls/floors, walk at constant rate.  Constrain motion so user doesn't get lost/confused
  - [x] "Turn off camera" - change from perspective to orthographic projection
- [x] **Object selection**
  - [x] Opaque objects of interest.  Make everything else translucent

[pmconne]

Regarding Navigation section: I've ported our view navigation tools to javascript so the first 3 items in that section can probably be considered complete. The code is rather specific to our tool/view framework but if you feel some of it could be usefully integrated into Cesium please let us know.

Regarding 'Object selection > Opaque objects of interest': I reworked the way I manipulate the tileset style and can no longer observe significant performance degradation with transparency applied.

[pjcozzi]

I've ported our view navigation tools to javascript so the first 3 items in that section can probably be considered complete. I reworked the way I manipulate the tileset style and can no longer observe significant performance degradation with transparency applied.

Very nice, updated the above roadmap.

if you feel some of it could be usefully integrated into Cesium please let us know

Thanks for the offer. When you have time, can you send me a demo of the walk mode? It could be generally useful to Cesium.