Meshes are needed for geospatial work
summary
Argues that geospatial work needs explicit meshes and shows working code that separates topology and geometry as distinct indexed datasets, uses a Delaunay triangulation library for clean triangles, and detects degeneracies by vertex-count changes (13→15→14→15). Treats rasters as meshes so a DEM becomes a quad mesh, renders interactive views with an OpenGL widget, projects meshes to XYZ for a textured globe, handles reprojection while preserving quantities, and reports the approach works in practice.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:05What are meshes in topology
- 4:42Problems with spatial data handling
- 8:56Topology fixes and triangulation
- 12:12Mesh applications in geospatial work
- 15:163D visualization with meshes
- 16:47Future of mesh usage in GIS
- 19:49Q&A and closing remarks
related talks
05mMVT Tiles and Autonomous Driving, and other non-UI usage
37m3DGraphics with Threejs by Ruben Meschian (Eng) | JSConfAM19
02h 02mInteractive 3D Web Mapping
37mVisualizing Large Datasets with JavaScript Using deck.gl
41mBuilding Enterprise 3D Web Applications
05mCloud Optimised Geotiffs in TerriaJS
45mOptimizing Data Visualization Performance in Web Maps
40mStronger App Architecture Using Maps