Note: This page describes publicly shareable technical approaches and engineering ideas. It does not include internal data or unpublished metrics.
Context
This is a WebGL engine for digital earth and digital twin scenarios. In the browser it needs to handle city-scale terrain, imagery, vector data, photogrammetry, BIM/glTF models, spatial analysis, underground pipelines and urban flood simulation.
The hard part is not simply drawing models. It is:
- integrating heterogeneous data sources under a unified coordinate system;
- keeping large scenes responsive through loading, scheduling and frame-rate stability;
- giving business teams reusable rendering capabilities rather than one-off effects;
- bringing analysis results back into the 3D scene.
Technical work
The work falls into four areas:
- Rendering: materials, lighting, post-processing, particles, dynamic line/area effects and business-specific render pipelines.
- Data integration: extending 3D formats and sources, handling coordinate systems, hierarchy, transforms and style mapping.
- Performance and stability: reducing unnecessary draw calls and state changes, improving loading and interaction for large datasets.
- Business support: turning requirements from urban flood simulation, underground pipelines and digital twins into reusable engine capabilities.
Key directions
Specialized render pipelines
Business scenarios often need effects that the engine does not provide out of the box, such as:
- water surfaces, heatmaps and rainfall/river coupling for urban flood simulation;
- clipping, transparency, occlusion and flow animation for underground pipelines;
- analytical representations for building blocks, administrative areas and skylines.
The approach is to split each effect into three layers — data preparation, render pipeline, interaction/analysis — and reuse the existing render flow instead of writing a separate system for every project.
Geometry and spatial analysis
GIS analysis is more than visualization. Geometry editing, boolean operations, rectangle picking, skyline analysis and cross-sections require geometric correctness, screen interaction and rendering performance at the same time.
This is where geometry algorithms and 3D rendering meet in practice.
Outcomes
- Built a reusable set of 3D rendering and spatial analysis capabilities for multiple scenarios.
- Turned several project-specific effects into engine capabilities, reducing duplicate development.
- Validated loading, rendering and interaction stability with real city-scale datasets.
Reflection
Engine work can easily become feature accumulation. The difficult part is drawing boundaries: what goes into the engine, what stays in the business layer, what should be a generic pipeline and what must be customized. That judgment is more valuable than any single flashy effect.