AI/ML-Based Integrated heavy rainfall Early Warning and Inundation Prediction System using Satellite, Radar, observational Weather and numerical weather prediction model data.

The receipts 🧾

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

1. Exhibit A

   Urban inundation depends on terrain at metre resolution plus the storm drain network, and neither is publicly available for Indian cities — the freely available elevation data is far too coarse to say which road floods, which is the entire question

2. It gets worse

   Two distinct disciplines are joined in one sentence, and a team that splits its time between rainfall forecasting and hydraulic modelling will produce a weak version of each

3. Still reading?

   Errors compound through the chain: a modest rainfall forecast error becomes a large inundation error, so propagating uncertainty rather than presenting a single crisp flood map is both more honest and more defensible

4. And the finisher

   A confident flood extent map is exactly the kind of output that gets used for decisions, so overstating the resolution of your terrain model is a real hazard rather than a presentational flaw

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.

  The rainfall half is well supported with free satellite precipitation products and gridded gauge data, but the inundation half needs terrain at metre-scale resolution together with drainage and storm-sewer network data, and neither exists publicly for Indian cities — the coarse elevation models that are free cannot resolve which street floods.

• Innovation scope

  4/5

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

  The description repeats the title, so no method, region, lead time, resolution or model type is prescribed anywhere and the entire approach is yours to define.

• Clarity

  1/5

  Nobody is sure what is being asked, quite possibly including the people who asked it.

  The description is the title reproduced verbatim, giving no background, no requirement, no lead time, no spatial scale and no definition of what a correct inundation prediction would be.

• Acceptance potential

  2/5

  The numbers do not like you. Bring something the numbers cannot see.

  The inundation half is the differentiator and it rests on high-resolution terrain and drainage data that is not publicly available in India, so most submissions will run a flood model over coarse elevation data and produce maps that look authoritative while being unable to resolve the street-level question the system exists to answer.

• Effort

  Massive

  A semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.

  Multi-source rainfall blending and calibration is a full project, hydrological and hydraulic inundation modelling is another entirely different discipline, and chaining them with honest uncertainty propagation is a third — this is two research problems joined by a sentence.

• Demo-ability

  Medium

  Demoable, if you rehearse it. Nobody rehearses it.

  A flood extent map over a city is compelling and hindcasting against a documented event gives you real evidence, but the result is only as credible as the terrain model beneath it and a judge who knows flood modelling will ask about resolution first.

• 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 140–330 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.

• Satellite radar imagery of past floods gives you genuinely observed inundation extent for validation, which is a rare opportunity to check a flood model against reality rather than against another model
• Free global satellite precipitation products and gridded gauge data make the rainfall half entirely tractable and calibratable
• Because the description is only the title, you can scope to a single well-documented catchment and a single past event and be fully responsive while remaining achievable