# River flood levels on 3D terrain

> An aerial-textured river model pairs blue water surfaces with cross-section diagrams and flow-dependent measurements, then presents a green-yellow-red overview of remaining clearance along the river.

- Kind: Video
- Page: https://meetreference.com/v/video-river-flood-levels-on-3d-terrain-05a5e0/
- Ready-to-use agent handoff: https://meetreference.com/v/video-river-flood-levels-on-3d-terrain-05a5e0/agent.txt
- Authorship: AI-made, per the source
- Made with: Not stated
- Model: Claude Opus 5.5
- Built with: not stated
- Skills or plugins: Python
- Style: Data stories; geospatial, scientific, 3d terrain, aerial imagery, heatmap, dashboard
- Length and format: 46 sec, 16:9 (1280x720 source)
- Playback: a muted visual reference. The original soundtrack is available only at the source.
- Shared by @dobokuya77 in X, Oct 4, 2026: https://x.com/dobokuya77/status/2106604492728967620
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

Requirements reported by the source: Install the creator-stated skill or plugin: Python..

## Recreating this video

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Use aerial-textured terrain to place an engineering quantity in recognizable geographic context. Pair a selected location with a cross-section inset and a few large measurements, then show the full corridor with a simple categorical risk palette. Keep annotation panels dark and compact so they remain readable against detailed imagery.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the video frames, not by the creator.

Stylized river-flow dashboard featuring winding blue waterways across 3D terrain, with flow-condition overlays and measurement panels.

- Color: Bright blue water, muted greens and olive terrain, pale tan and green fields, and dark navy interface panels with white text.
- Type: Small, clean sans-serif interface text; Japanese headings and labels, KP markers, numeric measurements, and compact chart legends.
- Framing: Oblique terrain maps center on the river and surrounding fields. Dark callout boxes, map markers, and, in some views, a data panel with a river profile chart and numeric readings sit over the maps.
- Structure: The interface presents river maps at different locations and scales, alongside labeled monitoring points, flow-status colors, brief explanatory captions, and detailed calculation readouts.

Storyboard, nine frames spread across the video: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/storyboard.webp

- Frame 1 at 2.6s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f1.webp
- Frame 2 at 7.7s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f2.webp
- Frame 3 at 12.9s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f3.webp
- Frame 4 at 18.0s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f4.webp
- Frame 5 at 23.2s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f5.webp
- Frame 6 at 28.3s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f6.webp
- Frame 7 at 33.5s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f7.webp
- Frame 8 at 38.6s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f8.webp
- Frame 9 at 43.8s: https://meetreference.com/media/video-river-flood-levels-on-3d-terrain-05a5e0/f9.webp

## Links

- Watch: https://x.com/dobokuya77/status/2106604492728967620
- Original post: https://x.com/dobokuya77/status/2106604492728967620
- Discovery collection: https://data.openchamber.dev/opus-5-5-videos/v/dobokuya77-2106604492728967620