Develop a web-based interactive 3D visualization platform that integrates numerical ocean model outputs and in-situ observations.

The receipts 🧾

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

1. Exhibit A

   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

2. It gets worse

   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

3. Still reading?

   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

4. And the finisher

   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

The damage report 📉

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

• Feasibility

  4/5

  Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

  The 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/5

  Nothing here is new. Your only edge is execution — and execution is also everyone else's only edge.

  The 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/5

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

  Comprehensively 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.

• Acceptance potential

  4/5

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

  Fully 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.

• Effort

  Heavy

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

  Browser 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

  Easy

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

  A 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.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 120–270 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.

• 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
• 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
• Scientific 3D visualisation is a thin field and the result is visually far more striking than the dashboards that dominate this event