DepthWizard - Single-View Height Estimation and 3D Flythrough

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   Monocular depth models are trained on egocentric photos, so the domain gap to overhead imagery is real and building heights will be the weak point

2. It gets worse

   Converting relative depth to accurate absolute metric height from a single view is genuinely hard, and an ISRO judge will check the metres against known structures

3. Still reading?

   SRTM is coarse at 30 metres, so anchoring fine structure to it leaves per-building height uncertain

4. And the finisher

   A visually impressive flythrough can mask metrically inaccurate heights, and the description explicitly asks for metric accuracy on the georeferenced path

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  3/5

  Buildable. Not comfortably. There is a week in here you have not planned for yet.

  Strong pre-trained monocular depth backbones exist and SRTM is freely available for the metric anchoring, but monocular depth on overhead imagery faces a real domain gap from models trained on egocentric photos, and converting relative depth to accurate absolute building heights from a single view is genuinely hard, so metric accuracy on structures will be the weak point.

• Innovation scope

  4/5

  There is something genuinely new here. Do not bury it under another dashboard.

  Bridging the domain gap from egocentric monocular depth to overhead remote sensing, and anchoring relative depth to absolute metric elevation with a coarse DEM, are both genuinely open, and how you fuse the fine relative structure with the coarse absolute scale is the real contribution.

• Clarity

  5/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  The description specifies both input paths precisely, names the backbone approach, the SRTM and ground-control anchoring, the relative-versus-absolute outputs and the 3D flythrough, making the deliverable exceptionally well defined.

• Acceptance potential

  4/5

  Strong footing before you have written a line. Try not to waste it.

  A strong pick — the data is free, the pipeline is well-scoped with SRTM handed to you for anchoring, and the flythrough is a memorable demo, though the honest weak point is metric accuracy of single-view building heights, which an ISRO judge will test against known references.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  Adapting the depth backbone, the metric-anchoring pipeline, the georeferencing handling and the interactive 3D flythrough are focused, well-bounded pieces on available data.

• Demo-ability

  Easy

  Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

  A 3D flythrough over terrain and buildings reconstructed from a single flat image is a genuinely striking, self-explanatory visual, and building heights in metres give it quantitative substance.

The demo they will have already seen 🪞

Somewhere around 150–340 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• Strong pre-trained monocular depth backbones like Depth Anything give you a powerful starting point rather than training from scratch
• SRTM is freely available, so the metric-anchoring reference for georeferenced imagery costs nothing
• The 3D flythrough over a surface reconstructed from a single flat image is a genuinely striking, memorable demo