release: bump version to 0.58.0
Release 0.58.0 includes the Earth high-precision boundary PMTiles/MVT pipeline, standardized Earth boundary source collectors, China POV boundary configuration templates, and removal of the legacy low-precision GeoJSON fallback. It also adds Earth news target-location queueing/archive support, fixes datasource task status visibility, documents the Earth surface depth-spacing rules that prevent far-zoom z-fighting snow/black blocks, and updates bilingual operations/developer docs.
This commit is contained in:
3
rules.md
3
rules.md
@@ -379,6 +379,9 @@ Editing `frontend/public/earth`, 3D Earth, canvas/Three.js rendering, BGP/vessel
|
||||
- Avoid one-off visual patches before checking render order, coordinate ownership, and data lifecycle.
|
||||
- Use Three.js for 3D elements.
|
||||
- Verify 3D/canvas work with real rendering, not only TypeScript build.
|
||||
- For concentric or near-concentric Earth surface shells, do not place overlay radii too close to `CONFIG.earthRadius`.
|
||||
Maintain explicit altitude offsets with enough separation for far-zoom depth-buffer precision, document them in `earth-render-layer-order.md`, and verify at zoomed-out views such as 50%.
|
||||
If snow, black blocks, or flicker appears on the globe, check for z-fighting between the base sphere, land/ocean fill, HD texture, terrain, clouds, and occluder before hiding layers or adding LOD workarounds.
|
||||
- Do not let loading messages, phase labels, or optimistic UI override real backend task state.
|
||||
- WebSocket data frames should include timestamps, type, and payload when streaming Earth state.
|
||||
- Default heartbeat for real-time streams is 30 seconds unless a protocol states otherwise.
|
||||
|
||||
Reference in New Issue
Block a user