Develop a web-based interactive 3D visualization platform that integrates numerical ocean model outputs and in-situ observations.
Ministry of Earth Sciences (MoES) · Smart Automation · Software
Open data, a complete specification and one of the most visually striking demos available — but browser volumetric rendering is the whole technical risk, so prove you can render a real field at interactive frame rates before you build anything else.
What it actually is
Ocean forecasters have huge three-dimensional model outputs on one side and readings from drifting floats and gliders on the other, and no single tool that shows both together. So they flip between desktop programs and flat 2D maps and cannot quickly check whether the model matches what the instruments actually saw. The ask is one browser-based 3D environment showing both at once.
What to build
A browser-native 3D ocean viewer with volumetric rendering of model fields — temperature, salinity and current vectors through the full water column — supporting the interactions the statement enumerates including depth-slice navigation, isosurface extraction and time-step animation; an instrument overlay placing float, glider, CTD and biogeochemical observations as geospatially accurate markers that open a depth-versus-variable profile chart on click so a forecaster can compare the model to the observation at the same point; a NetCDF and delimited-text ingestion layer built modularly so a new variable or sensor type needs configuration rather than code; interactive colorbar, variable, opacity and vertical exaggeration controls; and a lightweight backend serving the data over open standards.
Smallest thing that wins the room
Rotate a volumetric temperature field, drag the depth slice down through the thermocline, then click a float marker and show its measured profile beside the model's values at that exact position and time.
How crowded this one gets
A guess, projected from the 2025 statements — the last year where both the submission counts and the winners were published.
Quieter than 56% of the 226 · #100 of 226 by expected field
A normal-sized field. Your idea has to be good, not miraculous.
Why: central ministry statements sat below the average.
This is a guess, not a fact
Nobody has published 2026’s numbers yet. This is an analysed estimate from last year’s pattern, so please do not take it as the truth — check the live counter on the SIH portal before you decide anything. The range covers the middle half of likely outcomes, so one statement in two lands outside it. Entry closes at 500 ideas per statement, so no range goes past that — a statement that reaches the cap fills and shuts rather than drawing an unlimited crowd. The model reads only three things a team can see before choosing — software or hardware, the theme, and what kind of body posted it — and those explain about a quarter of the variation in last year’s field sizes (R² 0.25 on held-out statements). Trust the band more than the number, and the ordering more than either. It cannot see how good your idea is, which is the part that actually decides it.
The scores
The number is the shorthand. The line under it is the reason.
Acceptance potential
4/5Fully open data, an unambiguous specification, a visually outstanding demo and a scientific visualisation field that very few teams enter all count strongly — the drag is that this is a viewer with no analysis in it, so a panel looking for intelligence will find excellent engineering and no model.
Feasibility
4/5The data situation is excellent — global float profiles are fully open, ocean model reanalysis and forecast fields are freely distributed in NetCDF, and the parsing and web rendering libraries the statement names are all mature — so the only real difficulty is performance rather than access.
Innovation scope
2/5The functional requirements are enumerated exhaustively down to the rendering library options, the control set, the ingestion approach, the architecture and the standards to follow, so this is an implementation brief rather than a design problem.
Clarity
5/5Comprehensively specified — it identifies the exact gaps to close, lists the core functional requirements individually, names the rendering and parsing technologies, specifies the open standards to conform to and even describes the outreach use case, though it closes with an unfilled placeholder where two tables were meant to go.
Effort
HeavyBrowser volumetric rendering of a large gridded field is genuinely hard — the naive approach stalls the tab — and on top of it sit NetCDF ingestion, instrument overlay with profile charts, a full control surface and a backend, so five components with one of them technically deep.
Demo-ability
EasyA rotating three-dimensional ocean with a depth slice moving through it is genuinely arresting, and clicking a float to see its real profile against the model closes the loop in a way any judge follows immediately.
In its favour
- Green flag: Global float profile data and ocean model fields are both fully open, so you can build against real operational data from the first day rather than mocking anything
- Green flag: The model-versus-observation comparison at a clicked float is the feature that actually solves the stated problem, and it is also the most compelling five seconds of your demo — build it early
- Green flag: Scientific 3D visualisation is a thin field and the result is visually far more striking than the dashboards that dominate this event
- Green flag: The statement names the standards to conform to, so interoperability claims can be demonstrated against a real specification rather than asserted
Against it
- Red flag: Volumetric rendering of a full ocean model field in a browser will freeze the tab if approached naively — chunking, decimation and level-of-detail are prerequisites, not optimisations, and this is where the project succeeds or fails
- Red flag: There is no analysis anywhere in this statement, only display, so a panel expecting intelligence will need to be told explicitly why a viewer is the right answer here
- Red flag: Vertical exaggeration and depth perception are genuinely tricky in ocean data where the domain is thousands of kilometres wide and one kilometre deep, and getting this wrong makes the rendering unreadable
- Red flag: The description ends with a placeholder where the acronym and dataset tables were meant to be, so the specific data sources the sponsor intended to point you at are missing
What you will be writing
- Three.js or Cesium WebGL volumetric rendering
- xarray and NetCDF CF-convention parsing
- OPeNDAP / OGC WMS backend services
- Argo GDAC float profile ingestion
- marching cubes isosurface extraction
- chunked tile streaming for large gridded fields
- Scientific visualisation
- Operational oceanography
- Geospatial web platforms
Prior art to read before you start
web-based 3D volumetric data rendering · model and in-situ observation co-visualisation · NetCDF ingestion and depth-resolved display
Analysed by Claude Opus. Every score above is a judgment call with its reasoning attached — kindly cross-check this against the official statement on the SIH portal before your team commits to it.