Volumetric clouds up close, seeded from the cloud map
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, three.js
- Domain
- computer-graphics
Research direction
The issue names no files, tests, or entry points. Start by reading the parent issues #111, #88, and #41 to understand the cloud-map and renderer plans, then locate the existing Cesium swap and cloud rendering paths. Done means a smooth orbit-to-low-altitude blend to volumetric clouds matching the map in coverage, with parity on both sides of the swap.
Written by the indexing model from the issue text.
Description
Under #111. Split from #88 (2026-10-06 planning).
What
From far away clouds are a texture (#88: daily from NASA GIBS where data exists). Zooming in, cross-fade to generated volumetric clouds: raymarched or impostor cloud volumes whose coverage, type and height are seeded by the cloud map at that location (so the volumetric clouds are where the satellite saw clouds), lit by the Sun and the atmosphere pass in exposure units, casting shadows on the ground where affordable.
Generalization
The same renderer, with per-body parameters, for Venus's deck, Titan's haze and gas-giant cloud tops (#41).
Done when
Descending from orbit to a few km over a cloudy region of a given date blends smoothly from the GIBS texture to volumetric clouds that match it in coverage, on both sides of the Cesium swap (parity check).
Generated by Claude Code
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 4
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 134
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from celestiary/web
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
celestiary/web#345 ·
Maintainers usually reply within 1 day
-
Cesium guest (?cesium=iframe): white flicker near Mars's and Earth's surface remains after #335Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
celestiary/web#344 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
celestiary/web#340 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 48/100
celestiary/web#336 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
celestiary/web#334 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
danilogiles/enki-browser#113 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
evcc-io/evcc#35605 · 1 comment ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
weavefox/awesome-opc#29 ·
Maintainers usually reply within 1 day