05 / Persistent terrain scene
Contour, light, altitude.
Scroll through a generated landscape while one renderer changes its camera, contour interval and snow threshold. The terrain belongs to this study, not a geographic survey.
Read the land.
Elevation becomes contour bands. This terrain is generated from a local mathematical surface, not a real route.
Follow the light.
A single renderer stays alive while camera angle, hillshade and chapter text change with scroll progress.
Meet the snow line.
Altitude selects the snow treatment. Change the threshold and compare the same terrain under a new reading.
NO GEOGRAPHIC CLAIM
Read the land.
Elevation becomes contour bands. This terrain is generated from a local mathematical surface, not a real route.
Follow the light.
A single renderer stays alive while camera angle, hillshade and chapter text change with scroll progress.
Meet the snow line.
Altitude selects the snow treatment. Change the threshold and compare the same terrain under a new reading.
What this study teaches
One persistent Canvas 2D surface projects an independently generated elevation grid. Elevation bands, approximate surface hillshade and a snow threshold are derived during drawing. Document progress selects camera and chapter state; the renderer is never remounted. This isolates terrain presentation and lifecycle principles without an actual DEM, glTF or Webflow integration.
Independent implementation informed by “Building Ridgeline: Engineering a Real-Time 3D Experience in Webflow”, Filip Zrnzevic, Codrops. This is newly authored code and artwork, not a recovered original project. Original generated terrain replaces the hiking route and DEM. The study uses a software-projected surface, not the publisher’s shader assets or Webflow/React project.