Irrigation Department

Tell us what to change or add.

Your name (optional)Your roleReview date

Continue a saved review

1. Check a decision

Open a decision below. Check the area, period, inputs, result and proposed next step.

2. Try the inputs

Use Change example to try different values. Use Data needed to check the fields and sources. The land-use change decision has its own comparison views.

Record your corrections below, then download your answers or print them.

3. Check each decision

1. Prepare an irrigation allocation proposal 2. Check canal delivery shortfalls 3. Review storage consequences of proposed releases 4. Compare reservoir-capacity survey records 5. Review overdue irrigation repairs 6. Select drainage improvements for persistently waterlogged areas 7. Check conductivity records for saline-intrusion review 8. Schedule approved gate operations without conflicts 9. Target schemes with low crop output per water delivered 10. Check proposed flows against the stated conditions 11. Check whether model calibration can be reproduced 12. Compare pumping electricity per water volume 13. Compare rehabilitation cash-flow scenarios 14. Investigate delayed irrigation construction milestones 15. Prevent shortages of critical irrigation equipment spares 16. Correct missing metadata in published reservoir information 17. Flag a reservoir nearing its agreed storage floor

1. Prepare an irrigation allocation proposalDEC-DP05-001 · Command water demand

Try this decision

Prepare irrigation demand figures for an allocation proposal.

Verified published component · Crop evapotranspiration ETc component

Fictional default example · 2025.

Fictional case / area	Gross daily irrigation requirement [m³/day]	Net field requirement [mm/day]	Next check
Laggala Pallegama — command water demand / 2025	6,687.5	5.35	Review weather, crop, water-availability and operating evidence
Rattota — command water demand / 2025	6,687.5	5.35	Review weather, crop, water-availability and operating evidence
Panvila — command water demand / 2025	6,687.5	5.35	Review weather, crop, water-availability and operating evidence

What the selected record shows. Gross daily irrigation requirement: 6,687.5 m³/day.

Next step. Review weather, crop, water-availability and operating evidence. Prepare water-needs scenario in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Available water, operating constraints and authority are needed before a release decision.

Inputs, method and sources

Supplied input	Value	Unit
Irrigated crop area	85	ha
Reference evapotranspiration	4.5	mm/day
Crop coefficient	1.1	ratio
Rainfall reaching the field after runoff	1.6	mm/day
Deep percolation and paddy allowance	2	mm/day
Capillary contribution	0	mm/day
Desired change in stored soil water	0	mm/day
Field application efficiency	0.68	fraction

ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency.

The full local balance, rooting depth, stress, crop stage and operating constraints still matter. The paddy allowance is explicit and must be zero where inapplicable. This is not an authorized reservoir release.

Other required records: Command hectares; crop stage; evapotranspiration; rainfall; percolation; efficiency.

Food and Agriculture Organization of the United Nations · FAO Irrigation and Drainage Paper 56 Crop Evapotranspiration
Institution publication · Chapter 5, Crop coefficient approach, equation 56

This verifies the ETc component only. Local water-balance allowances, coefficients and operating decisions still need confirmation.

Calculation appendix

FAO 56: crop evapotranspiration — Institution publication. FAO 56 Chapter 5 equation 56; ETc = Kc × ETo. Institutional context; does not establish the calculation or local approval.
FAO56 root-zone water balance — Institution publication. Chapter8 equation85 and ETc = Kc ETo. Daily water balance components; local coefficients and operating assumptions still need review.
FAO Irrigation Water Management Training Manual 3 — Institution publication. Chapter 4.4 Irrigation water need of rice; steps 1 to 8. Institutional context; does not establish the calculation or local approval.
SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Your checks for this decisionDoes this decision belong to your institution?Is the required data list complete?Are the sources, places and time periods suitable?Can staff use the proposed entry or upload steps?Are the calculation, units and limits correct?Do the chart and result help you decide?Are the checking officer and decision authority correct?Are the access and sharing limits suitable?

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

2. Find stale or missing water observationsDEC-DP05-002 · Gauge operations

Try this decision

Identify river or reservoir observations needing restoration or source checks.

Validation required

Fictional default example · 2025.

Fictional case / area	Completeness [%]	Age of latest observation [days]	Missing observations [observations]	Next check
Laggala Pallegama — gauge operations / 2025	80	2	6	Check overdue observation
Rattota — gauge operations / 2025	80	2	6	Check overdue observation
Panvila — gauge operations / 2025	80	2	6	Check overdue observation

What the selected record shows. Completeness: 80 %. Check overdue observation.

Next step. Check overdue observation. Prepare observation request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Stale information must not be presented as a current reading.

Inputs, method and sources

Supplied input	Value	Unit
Expected observations in the window	30	observations
Distinct valid observations	24	observations
Latest valid observation	2025-06-28
Assessment date	2025-06-30
Required observation interval	1	days

Completeness = 100 × valid / expected. Age = assessment date − latest valid observation; compare with the explicitly supplied interval.

A recent observation does not fill earlier gaps. Unknown schedule or observation time cannot establish freshness.

Other required records: Gauge ID; observation schedule; last valid reading; outage duration; calibration.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

2. Check canal delivery shortfallsDEC-DP05-003 · Canal performance

Try this decision

Compare planned and measured canal deliveries to identify shortfalls for review.

Validation required

Fictional default example · 2025.

Fictional case / area	Difference [m³]	Relative change [%]	Next check
Laggala Pallegama — canal performance / 2025	-17,000	-20	Review the delivery gap with the scheme operator
Rattota — canal performance / 2025	-4,000	-4.706	Review the delivery gap with the scheme operator
Panvila — canal performance / 2025	-9,000	-10.588	Review the delivery gap with the scheme operator

What the selected record shows. Difference: -17,000 m³. Review the delivery gap with the scheme operator.

Next step. Review the delivery gap with the scheme operator. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Delivery volume alone does not establish urgency or the cause of a shortfall.

Example chart

Inputs, method and sources

Supplied input	Value	Unit
Planned canal delivery for the period	85,000	m³
Measured canal delivery for the same period	68,000	m³

Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive.

Other required records: Canal outlet; planned cubic metres; delivered cubic metres; period; command area.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

3. Review storage consequences of proposed releasesDEC-DP05-004 · Reservoir operation

Try this decision

Reconcile opening storage, flows and closing observations for a release scenario.

Validation required

Fictional default example · 2025.

Fictional case / area	Calculated closing storage [m³]	Observed minus calculated closing [m³]	Next check
Laggala Pallegama — reservoir operation / 2025	164,000	-500	Reconcile closing balance
Rattota — reservoir operation / 2025	164,000	-500	Reconcile closing balance
Panvila — reservoir operation / 2025	164,000	-500	Reconcile closing balance

What the selected record shows. Calculated closing storage are 164,000 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -500 m³. Check the component records before explaining that difference.

Next step. Reconcile closing balance. Prepare balance review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

The balance does not authorise a release or certify storage measurements.

Inputs, method and sources

Supplied input	Value	Unit
Opening storage	160,000	m³
All measured inflows and transfers in	48,000	m³
Releases and transfers out	35,000	m³
Evaporation and other outflows	9,000	m³
Independently observed closing storage	163,500	m³

Calculated closing = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing.

Use the same physical boundary, period and units. A residual is a reconciliation issue, not automatically a measured loss.

Other required records: Opening storage; inflow; irrigation release; spill; evaporation; closing survey.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

5. Review dam-inspection evidence for engineering referralDEC-DP05-005 · Dam safety

Try this decision

Check dam-inspection evidence before referring an engineering defect.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — dam safety / Laggala Pallegama	Dam ID: Missing	Obtain the missing evidence listed below
Rattota — dam safety / Rattota	seepage: Missing	Obtain the missing evidence listed below
Panvila — dam safety / Panvila	deformation: Missing	Obtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this dam safety case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed

Dam ID: Missing

A completed record is not an engineering safety clearance.

Inputs, method and sources

Supplied input	Value	Unit
Dam ID	Missing
Dam ID evidence reference	Not provided
seepage	Documented
seepage evidence reference	Sample Laggala Pallegama field register / 2025
deformation	Documented
deformation evidence reference	Sample Laggala Pallegama field register / 2025
inspection findings	Documented
inspection findings evidence reference	Sample Laggala Pallegama field register / 2025
approved limits	Documented
approved limits evidence reference	Sample Laggala Pallegama field register / 2025
responsible engineer	Documented
responsible engineer evidence reference	Sample Laggala Pallegama field register / 2025

Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.

Other required records: Dam ID; seepage; deformation; inspection findings; approved limits; responsible engineer.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

6. Check hydrological evidence for response planningDEC-DP05-006 · Flood readiness

Try this decision

Check authorised hydrological evidence and response prerequisites.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — flood readiness / Laggala Pallegama	River levels: Missing	Obtain the missing evidence listed below
Rattota — flood readiness / Rattota	official forecast: Missing	Obtain the missing evidence listed below
Panvila — flood readiness / Panvila	flood exposure: Missing	Obtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this flood readiness case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed

River levels: Missing

The prototype does not predict a flood or issue a warning.

Inputs, method and sources

Supplied input	Value	Unit
River levels	Missing
River levels evidence reference	Not provided
official forecast	Documented
official forecast evidence reference	Sample Laggala Pallegama field register / 2025
flood exposure	Documented
flood exposure evidence reference	Sample Laggala Pallegama field register / 2025
warning protocol	Documented
warning protocol evidence reference	Sample Laggala Pallegama field register / 2025
evacuation constraints	Documented
evacuation constraints evidence reference	Sample Laggala Pallegama field register / 2025
Documented unresolved critical condition	Unknown
Evidence observation date	2025-06-30
Existing control and its evidence	Sample documented control
Competent recipient	Responsible specialist / duty authority

Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Show the hazard, exposure and verified controls separately. No generic score, probability, diagnosis, site clearance or official warning is derived from a count.

Other required records: River levels; official forecast; flood exposure; warning protocol; evacuation constraints.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

7. Compare feasible drought water-allocation alternativesDEC-DP05-007 · Drought allocation

Try this decision

Compare drought-allocation options using water availability, sector needs and flow constraints.

Validation required

Fictional default example · 2025.

Fictional case / area	Potential benefit · assumption	Resources and adverse effects	Supporting records / conditions	Next check
Prioritize domestic supply and minimum flows / Laggala Pallegama	Reserve the stated supply for domestic needs and environmental conditions.	Requires dependable storage, demands, applicable flow conditions and sector trade-offs.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing
Reduce irrigation rotations / Laggala Pallegama	Reduce or rotate irrigation deliveries during the stated shortage.	Requires crop-stage, farmer-agreement, canal-operation and allocation-rule evidence.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing
Stage sector allocations with review / Laggala Pallegama	Adjust sector allocations in documented review stages.	Requires update triggers, monitored supply, agreed sector needs and authorised operating rules.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing

What the selected record shows. There is not enough information to choose this option. Obtain the records and evidence about conditions listed below. The supplied budget less cost is 300,000 LKR.

Next step. Obtain the missing records before choosing. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed

Records needed: Dependable storage; sector demand; environmental requirements; allocation rules; uncertainty
Applicable conditions, what was checked and the supporting reference

Budget figures cannot determine a feasible water allocation.

Inputs, method and sources

Supplied input	Value	Unit
Option cost	1,500,000	LKR
Available budget	1,800,000	LKR
Mandatory constraints	Met
Potential benefit and its evidence or assumption	Reserve the stated supply for domestic needs and environmental conditions.
Resource needs and adverse effects	Requires dependable storage, demands, applicable flow conditions and sector trade-offs.
Required records available for this option	Not provided
Reference for the required records	Not provided
Applicable conditions, check result and supporting reference	Not provided

Compare each alternative's stated benefit, adverse effects, domain evidence and mandatory constraints. Where cost and budget are supplied, budget balance = budget − option cost. A budget balance alone does not determine domain feasibility or select an option.

Budget figures cannot determine a feasible water allocation.

Other required records: Dependable storage; sector demand; environmental requirements; allocation rules; uncertainty.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

4. Compare reservoir-capacity survey recordsDEC-DP05-008 · Reservoir sedimentation

Try this decision

Compare capacity-survey records before planning bathymetry or desilting appraisal.

Validation required

Fictional default example · 2025.

Fictional case / area	Difference [m³]	Relative change [%]	Next check
Laggala Pallegama — reservoir sedimentation / 2025	-40,000	-4.444	Check the surveys before commissioning bathymetry or desilting appraisal
Rattota — reservoir sedimentation / 2025	-25,000	-2.778	Check the surveys before commissioning bathymetry or desilting appraisal
Panvila — reservoir sedimentation / 2025	-10,000	-1.111	Check the surveys before commissioning bathymetry or desilting appraisal

What the selected record shows. Difference: -40,000 m³. Check the surveys before commissioning bathymetry or desilting appraisal.

Next step. Check the surveys before commissioning bathymetry or desilting appraisal. Prepare change comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Differences require matching datums, dates and uncertainty; they are not all sedimentation.

Example chart

Inputs, method and sources

Supplied input	Value	Unit
Earlier surveyed capacity on the same datum	900,000	m³
Later surveyed capacity on the same datum	860,000	m³

Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive.

A capacity difference alone does not prove sedimentation. Survey coverage, datum and uncertainty must match.

Other required records: Storage survey editions; sediment volume; usable capacity; survey accuracy; dates.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

5. Review overdue irrigation repairsDEC-DP05-009 · Canal rehabilitation

Try this decision

Review overdue repair cases alongside their engineering and budget evidence.

Validation required

Fictional default example · 2025.

Fictional case / area	Open days past due [days]	Calendar age [days]	Next check
Laggala Pallegama — canal rehabilitation / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — canal rehabilitation / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — canal rehabilitation / 2025	29	90	Follow up overdue case; confirm the missing condition evidence

What the selected record shows. Open days past due: 29 days. Follow up overdue case.

Next step. Follow up overdue case; confirm the missing condition evidence. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed

Documented critical unresolved condition: Unknown

Maintenance age alone is not engineering severity or repair priority.

Inputs, method and sources

Supplied input	Value	Unit
Received or defect observed	2025-04-01
Recorded due date	2025-06-01
Assessment date	2025-06-30
Case/work closed	No
Documented critical unresolved condition	Unknown
Responsible office or maintainer	Proposed responsible office
Actual closure date when closed	Not provided

Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately.

Example due dates are not legal service standards. Do not alter statutory deadlines by silently subtracting pauses, or infer severity from age alone.

Other required records: Asset condition; defects; service criticality; repair options; costs; inspection date.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Reference map image

Matale District location in Sri Lanka — published static reference map — **Reference map image — not live.** Matale District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks · CC BY-SA 3.0. Detail crop only; no features added. The example areas are supplied records, not measurements from this image.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

6. Select drainage improvements for persistently waterlogged areasDEC-DP05-010 · Drainage

Try this decision

Compare drainage alternatives using obstruction, outlet, site and resource evidence.

Validation required

Fictional default example · 2025.

Fictional case / area	Potential benefit · assumption	Resources and adverse effects	Supporting records / conditions	Next check
Clear existing drainage obstructions / Laggala Pallegama	Restore the capacity obstructed by recorded debris or vegetation.	Needs an inspection, disposal plan, access and recurring maintenance.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing
Improve the outlet structure / Laggala Pallegama	Address a documented outlet-capacity restriction.	Needs hydraulic and site evidence, downstream checks and construction resources.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing
Stage field and collector-drain repairs / Laggala Pallegama	Repair field and collector drains in compatible stages.	Needs a drainage survey, land agreements, sequencing and upkeep.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing

What the selected record shows. There is not enough information to choose this option. Obtain the records and evidence about conditions listed below. The supplied budget less cost is 300,000 LKR.

Next step. Obtain the missing records before choosing. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed

Records needed: Flood duration; drainage network; outlet capacity; affected hectares; engineering options
Applicable conditions, what was checked and the supporting reference

A lower cost does not establish the best drainage solution.

Inputs, method and sources

Supplied input	Value	Unit
Option cost	1,500,000	LKR
Available budget	1,800,000	LKR
Mandatory constraints	Met
Potential benefit and its evidence or assumption	Restore the capacity obstructed by recorded debris or vegetation.
Resource needs and adverse effects	Needs an inspection, disposal plan, access and recurring maintenance.
Required records available for this option	Not provided
Reference for the required records	Not provided
Applicable conditions, check result and supporting reference	Not provided

A lower cost does not establish the best drainage solution.

Other required records: Flood duration; drainage network; outlet capacity; affected hectares; engineering options.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

7. Check conductivity records for saline-intrusion reviewDEC-DP05-011 · Salinity exclusion

Try this decision

Identify conductivity observations needing saline-intrusion investigation.

Validation required

Fictional default example · 2025.

Fictional case / area	Observed result	Supplied comparison bounds	Next check
Laggala Pallegama — salinity exclusion / Laggala Pallegama	2,500 µS/cm	0 to 2,000 µS/cm	Obtain the missing evidence listed below
Rattota — salinity exclusion / Rattota	2,160 µS/cm	0 to 2,000 µS/cm	Review the sample, analytical method and comparison basis
Panvila — salinity exclusion / Panvila	650 µS/cm	0 to 2,000 µS/cm	Review the sample, analytical method and comparison basis

What the selected record shows. The supplied Irrigation-water electrical conductivity result is 2,500 µS/cm. Its stated comparison range is 0 to 2,000 µS/cm. Outside example comparison bounds.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed

Exact sample and site reference
Sample observation date

Sampling conditions, units and location must support the interpretation.

Inputs, method and sources

Supplied input	Value	Unit
Parameter and applicable use	Irrigation-water electrical conductivity
Measured result	2,500	µS/cm
Example lower comparison bound	0	µS/cm
Example upper comparison bound	2,000	µS/cm
Original and limit unit	µS/cm
Sampling and analytical method/version	Sample laboratory method
Limit source, version and use	Fictional comparison bounds; not a regulatory limit
Parameter, unit, use and averaging period match	Yes
Result is below a reporting/detection limit	No
Averaging interval, sampling depth or process basis	Sample stated sampling/averaging basis
Sample and site reference	Not provided
Sample observation date	Not provided

Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status.

Example bounds establish no compliance or diagnosis. Ambient, drinking-water, effluent, crop, food, air and noise standards are not interchangeable. A censored result is not an exact zero. Physical concentrations and magnitude measurements are non-negative. Signed raw instrument signals need laboratory interpretation; do not silently replace them with zero.

Other required records: Water conductivity; tide stage; gate status; crop use; reviewed salinity limits.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

8. Schedule approved gate operations without conflictsDEC-DP05-012 · Gate scheduling

Try this decision

Check gate-operation tasks for timing and resource conflicts.

Validation required

Fictional default example · 2025.

Fictional case / area	Planned duration [days]	Resource hours remaining [hours]	Next check
Laggala Pallegama — gate scheduling / 2025	3	8	Resolve overlapping resource bookings
Rattota — gate scheduling / 2025	3	8	Resolve overlapping resource bookings
Panvila — gate scheduling / 2025	3	8	Resolve overlapping resource bookings

What the selected record shows. Planned duration: 3 days. Resolve overlapping resource bookings.

Next step. Resolve overlapping resource bookings. Prepare schedule review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

The schedule does not operate gates or grant operating authority.

Inputs, method and sources

Supplied input	Value	Unit
Required resource	Watershed field team
Task start	2025-06-01
Task end	2025-06-04
Earliest permitted start	2025-05-28
Latest permitted finish	2025-06-08
Required resource effort	16	hours
Available resource effort	24	hours
Predecessor task reference	None
Mandatory permits and prerequisites	Met

Check start/end order, operating window, effort, predecessor completion and overlapping bookings for the same resource. A conflict is flagged; no optimal schedule is invented.

Other required records: Release approval; gate capacity; operator availability; downstream constraints; operating windows.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

9. Target schemes with low crop output per water deliveredDEC-DP05-013 · Water productivity

Try this decision

Compare matching crop output and delivered water by scheme.

Validation required

Fictional default example · 2025.

Fictional case / area	Crop water productivity [kg/m³]	Next check
Laggala Pallegama — water productivity / 2025	2.747	Check matching outputs, denominators and operating conditions
Rattota — water productivity / 2025	3.344	Check matching outputs, denominators and operating conditions
Panvila — water productivity / 2025	3.076	Check matching outputs, denominators and operating conditions

What the selected record shows. Saleable crop output: 19,780 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³.

Next step. Check matching outputs, denominators and operating conditions. Prepare performance comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A productivity ratio does not establish a cause or choose an intervention.

Example chart

Crop water productivity — fictional 2025 examples

Inputs, method and sources

Supplied input	Value	Unit
Saleable crop output	19,780	kg
Matching irrigation water input	7,200	m³

Saleable crop output / Matching irrigation water input, for the same product, process and period.

Other required records: Crop output kg; delivered cubic metres; command hectares; crop; season.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

10. Check proposed flows against the stated conditionsDEC-DP05-014 · Environmental flows

Try this decision

Compare a proposed flow with the supplied reviewed flow condition.

Validation required

Fictional default example · 2025.

Fictional case / area	Difference [m³/s]	Relative change [%]	Next check
Laggala Pallegama — environmental flows / 2025	-0.3	-25	Refer the proposed flow and stated condition to the responsible engineer
Rattota — environmental flows / 2025	0.2	16.667	Refer the proposed flow and stated condition to the responsible engineer
Panvila — environmental flows / 2025	-0.1	-8.333	Refer the proposed flow and stated condition to the responsible engineer

What the selected record shows. Difference: -0.3 m³/s. Refer the proposed flow and stated condition to the responsible engineer.

Next step. Refer the proposed flow and stated condition to the responsible engineer. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

The example reference is not an adopted environmental-flow rule.

Example chart

Inputs, method and sources

Supplied input	Value	Unit
Supplied reviewed minimum-flow condition	1.2	m³/s
Proposed flow on the same time and location basis	0.9	m³/s

Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive.

The reference is a fictional supplied condition, not an official environmental-flow standard.

Other required records: Release proposal; flow obligation; dates; monitoring point; measured flow.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

Reference map image

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

11. Check whether model calibration can be reproducedDEC-DP05-015 · Hydrological models

Try this decision

Check model-calibration reproduction using the same inputs and versions.

Validation required

Fictional default example · 2025.

Fictional case / area	Difference [m³/s]	Relative change [%]	Next check
Laggala Pallegama — hydrological models / 2025	-10	-10	Investigate reproduction difference
Rattota — hydrological models / 2025	5	5	Investigate reproduction difference
Panvila — hydrological models / 2025	-2	-2	Investigate reproduction difference

What the selected record shows. Difference: -10 m³/s. Investigate reproduction difference.

Next step. Investigate reproduction difference. Prepare reproduction-check note in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Agreement alone does not establish model fitness for operational use.

Inputs, method and sources

Supplied input	Value	Unit
Earlier/source value	100	m³/s
Independently reproduced value	90	m³/s
Original measurement unit	Sample matching unit
Comparison measurement unit	Sample matching unit
Compared measure and definition	Sample comparable m³/s measure; same input scope
Documented absolute comparison tolerance	0.01	m³/s
Expected input/method version	Sample input1 /method1
Reproduced input/method version	Sample input1 /method1
Original result creator	Preparation officer
Independent reproducer	Independent checking officer

Reproduced minus expected result, within an explicitly supplied absolute tolerance, using the same exact input/method versions and a separate checker. Retain originals, code, parameters and environment evidence.

Other required records: Model version; rainfall; flow; calibration period; validation period; performance criteria.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

12. Compare pumping electricity per water volumeDEC-DP05-016 · Pumping systems

Try this decision

Compare electricity consumed per matching pumped water volume.

Validation required

Fictional default example · 2025.

Fictional case / area	Specific energy use [kWh/m³]	Next check
Laggala Pallegama — pumping systems / 2025	0.174	Check matching outputs, denominators and operating conditions
Rattota — pumping systems / 2025	0.212	Check matching outputs, denominators and operating conditions
Panvila — pumping systems / 2025	0.195	Check matching outputs, denominators and operating conditions

What the selected record shows. Electric energy consumed: 3,128 kWh; Water pumped: 18,000 m³. This gives 0.174 kWh/m³.

Next step. Check matching outputs, denominators and operating conditions. Prepare performance comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Specific energy use is not hydraulic efficiency.

Example chart

Specific energy use — fictional 2025 examples

Inputs, method and sources

Supplied input	Value	Unit
Electric energy consumed	3,128	kWh
Water pumped	18,000	m³

Electric energy consumed / Water pumped, for the same product, process and period.

Other required records: Delivered cubic metres; energy kWh; pumping head; operating hours; station ID.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

13. Compare rehabilitation cash-flow scenariosDEC-DP05-017 · Rehabilitation investment

Try this decision

Compare rehabilitation cash flows using the stated discount assumptions.

Verified published formula · Discounted cash-flow NPV

Fictional default example · 2025.

Fictional case / area	Five-year net present value [LKR]	Next check
Base cash-flow scenario / 2025	109,847.353	Review the cash flows, discount assumptions and constraints
Lower net-receipts scenario / 2025	-497,196.989	Review the cash flows, discount assumptions and constraints
Higher initial-cost scenario / 2025	-370,152.647	Review the cash flows, discount assumptions and constraints

What the selected record shows. At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions.

Next step. Review the cash flows, discount assumptions and constraints. Prepare cash-flow comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A positive present value alone is not an investment approval.

Example chart

Five-year net present value — fictional 2025 examples

Inputs, method and sources

Supplied input	Value	Unit
Initial investment	2,400,000	LKR
Net cash flow year1	400,000	LKR
Net cash flow year2	550,000	LKR
Net cash flow year3	680,000	LKR
Net cash flow year4	720,000	LKR
Net cash flow year5	760,000	LKR
Residual value at end of year5	120,000	LKR
Example discount rate	8	%

NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5.

Match currency, price year, real/nominal basis and cash-flow timing. The example rate and five-year horizon are assumptions, not institutional financing terms; no credit approval follows.

Other required records: Capital cost; maintenance; avoided losses; benefits; discount rate; project life.

Food and Agriculture Organization of the United Nations · Guidelines for defining financial economic environmental and social information
Institution publication · Sections 2.2.2 and 2.2.3, discounting and Net Present Value

The five-year horizon, discount rate and cash assumptions are local settings. Verification does not approve an investment or loan.

Calculation appendix

FAO Guidelines for financial economic environmental and social information — Institution publication. Section2 discounted cash-flow analysis and NPV. Published discounted cash-flow method; local rate, horizon and cash assumptions are separate.
SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

14. Investigate delayed irrigation construction milestonesDEC-DP05-018 · Construction delivery

Try this decision

Identify irrigation milestones whose actual dates differ from plan.

Validation required

Fictional default example · 2025.

Fictional case / area	Calendar date difference [days]	Next check
Laggala Pallegama — construction delivery / 2025	8	Check the matching records and reasons for the difference
Rattota — construction delivery / 2025	8	Check the matching records and reasons for the difference
Panvila — construction delivery / 2025	8	Check the matching records and reasons for the difference

What the selected record shows. Calendar date difference: 8 days.

Next step. Check the matching records and reasons for the difference. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A delay does not establish its cause or contractual liability.

Inputs, method and sources

Supplied input	Value	Unit
Planned milestone/sowing date	2025-06-01
Observed completion/sowing date	2025-06-09

Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar.

Other required records: Approved milestone dates; actual dates; dependencies; contract progress; completion evidence.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

15. Prevent shortages of critical irrigation equipment sparesDEC-DP05-019 · Spare parts

Try this decision

Compare usable spares and commitments with the stated requirement.

Validation required

Fictional default example · 2025.

Fictional case / area	Uncommitted usable stock [spares]	Additional demand gap [spares]	Next check
Laggala Pallegama — spare parts / 2025	310	190	Review replenishment gap
Rattota — spare parts / 2025	310	190	Review replenishment gap
Panvila — spare parts / 2025	310	190	Review replenishment gap

What the selected record shows. Uncommitted usable stock: 310 spares. Review replenishment gap.

Next step. Review replenishment gap. Prepare stock review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A shortage calculation does not authorise procurement.

Inputs, method and sources

Supplied input	Value	Unit
Physical stock	1,200	spares
Quarantined stock	100	spares
Expired stock	50	spares
Committed usable stock	740	spares
Additional demand	500	spares
Supplier lead time	14	days
Remaining shelf life of usable stock	30	days

Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available).

Stock must be compatible by item, lot, condition, expiry and delivery window. Do not allocate quarantined/expired stock or silently erase overcommitment.

Other required records: Part ID; usable stock; asset compatibility; lead time; approved demand; expiry.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

16. Correct missing metadata in published reservoir informationDEC-DP05-020 · Public information

Try this decision

Identify missing source and definition details in reservoir information.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — public information / Laggala Pallegama	Reservoir ID: Missing	Obtain the missing evidence listed below
Rattota — public information / Rattota	reading time: Missing	Obtain the missing evidence listed below
Panvila — public information / Panvila	unit: Missing	Obtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this public information case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed

Reservoir ID: Missing

Metadata completeness does not establish reading accuracy.

Inputs, method and sources

Supplied input	Value	Unit
Reservoir ID	Missing
Reservoir ID evidence reference	Not provided
reading time	Documented
reading time evidence reference	Sample Laggala Pallegama field register / 2025
unit	Documented
unit evidence reference	Sample Laggala Pallegama field register / 2025
datum	Documented
datum evidence reference	Sample Laggala Pallegama field register / 2025
source	Documented
source evidence reference	Sample Laggala Pallegama field register / 2025
review state	Documented
review state evidence reference	Sample Laggala Pallegama field register / 2025
update schedule	Documented
update schedule evidence reference	Sample Laggala Pallegama field register / 2025

Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.

Other required records: Reservoir ID; reading time; unit; datum; source; review state; update schedule.

Calculation appendix

SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

17. Flag a reservoir nearing its agreed storage floorDEC-DP05-021 · Published method

Try this decision

Source. Sri Lanka publication.

Data needed. Reservoir storage, agreed floor, comparable units and the assumed constant daily withdrawal.

Method. Under the constant-withdrawal scenario, divide storage available above the floor by the stated positive daily withdrawal. Record the scenario assumptions.

Worked example. With 27 million m³ in storage, a planning floor of 21 million m³ and withdrawals of 0.6 million m³ per day, the constant-withdrawal scenario leaves 10 days to the floor.

Next step. Review sites with fewer scenario days remaining and request a fuller water balance when conditions are changing.

Irrigation Department, World Water Day technical articles. Padaviya Reservoir drought resilience study, §2 Methodology, printed p. 9.

Confirm the floor and withdrawal assumptions. Obtain an approved operating decision separately.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Reservoir · Water and irrigation

Existing form reference: 4c16fb03e60a6df6

Field	Unit	Required
Source record ID	Confirm if needed	No
Tank Code	Confirm if needed	No
Reservoir name	Confirm if needed	No
Range Code	Confirm if needed	No
Range	Confirm if needed	No
Division Code	Confirm if needed	No
Division	Confirm if needed	No
Type	Confirm if needed	No
River basin	Confirm if needed	No
Scheme	Confirm if needed	No
HFL m MSL	m MSL	No
FSL m MSL	m MSL	No
BTL m MSL	m MSL	No
Catchment Area (ha)	ha	No
Capacity at FSL (MCM)	million m³	No
Dead Storage (MCM)	million m³	No
Live Storage (MCM)	million m³	No
Area at FSL (ha)	ha	No
Capacity at FSL(Acft)	acre-ft	No
Dead Storage (Acft)	acre-ft	No
Live Storage (Acft)	acre-ft	No
Remarks	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Irrigable Area · Water and irrigation

Existing form reference: c16bd1e4f59a2a05

Field	Unit	Required
Source record ID	Confirm if needed	No
Scheme	Confirm if needed	No
Type	Confirm if needed	No
Division	Confirm if needed	No
Range	Confirm if needed	No
Res An Uni	Confirm if needed	No
Code	Confirm if needed	No
Response Officer	Confirm if needed	No
Irrigable Area - Scheme Register (ha)	ha	No
Remarks	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Canal System · Water and irrigation

Existing form reference: 21d2e28388872fa1

Field	Unit	Required
Source record ID	Confirm if needed	No
Scheme	Confirm if needed	No
Subsystem	Confirm if needed	No
Division	Confirm if needed	No
Range	Confirm if needed	No
Canal Type	Confirm if needed	No
Code	Confirm if needed	No
Res An Uni	Confirm if needed	No
Scheme Type	Confirm if needed	No
Source geometry length	Confirm if needed	No

Bund · Water and irrigation

Existing form reference: a834d8c98d70c0a1

Field	Unit	Required
OBJECTID 1	Confirm if needed	No
Reservoir name	Confirm if needed	No
Division	Confirm if needed	No
Type	Confirm if needed	No
Range	Confirm if needed	No
Tank Code	Confirm if needed	No
Division Code	Confirm if needed	No
Bund Top Width (m)	Confirm if needed	No
Maximum Height of Bund (m)	Confirm if needed	No
Length of Bund (m)	Confirm if needed	No
Up Stream Slope	Confirm if needed	No
Down Stream Slope	Confirm if needed	No
Range Code	Confirm if needed	No
Source geometry length	Confirm if needed	No

Tank Coordinate · Water and irrigation

Existing form reference: 1c6cf855f1769bc7

Field	Unit	Required
Source record ID	Confirm if needed	No
X Coordinate (Em)	Confirm if needed	No
Y Coordinate (Nm)	Confirm if needed	No
Reservoir name	Confirm if needed	No
Division	Confirm if needed	No
Type	Confirm if needed	No
Range	Confirm if needed	No
Tank Code	Confirm if needed	No
Division Code	Confirm if needed	No
Range Code	Confirm if needed	No
SLD99 Xm	Confirm if needed	No
SLD99 Ym	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No

Sluice · Water and irrigation

Existing form reference: a4b6d5793605c038

Field	Unit	Required
Location	Confirm if needed	No
Reservoir name	Confirm if needed	No
Reservoir Type	Confirm if needed	No
Range	Confirm if needed	No
Tank Code	Confirm if needed	No
Division Code	Confirm if needed	No
Range Code	Confirm if needed	No
Division	Confirm if needed	No
SLD99 Xm	Confirm if needed	No
SLD99 Ym	Confirm if needed	No
Latitiude	Confirm if needed	No
Longitude	Confirm if needed	No
Chinage Location	Confirm if needed	No
Sluice Sill Level	Confirm if needed	No
Number of Baral	Confirm if needed	No
Size of Baral	Confirm if needed	No
Remarks	Confirm if needed	No

Spill · Water and irrigation

Existing form reference: 52df99673ebef8ff

Field	Unit	Required
OBJECTID 12	Confirm if needed	No
Location	Confirm if needed	No
Division	Confirm if needed	No
Tank Code	Confirm if needed	No
Reservoir name	Confirm if needed	No
Range	Confirm if needed	No
Type	Confirm if needed	No
Range Code	Confirm if needed	No
Division Code	Confirm if needed	No
SLD99 Xm	Confirm if needed	No
SLD99 Ym	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Spill Location in Chainage(km+m)	Confirm if needed	No
Spill Type	Confirm if needed	No
Spill Length m	Confirm if needed	No
No of Gates	Confirm if needed	No
Type of Gate	Confirm if needed	No
Size of Gate m (W x H)	Confirm if needed	No
Spill Crest Level mMSL	Confirm if needed	No
Remarks	Confirm if needed	No
Comments	Confirm if needed	No

river basins · Water and irrigation

Existing form reference: d2774621c4b33eb3

Field	Unit	Required
OID	Confirm if needed	No
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
SymbolID	Confirm if needed	No
AltMode	Confirm if needed	No
Base	Confirm if needed	No
Clamped	Confirm if needed	No
Extruded	Confirm if needed	No
Snippet	Confirm if needed	No
PopupInfo	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Attanagalu Oya Flood 2018; Deduru Oya Flood 2018; Gal Oya Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: 0971c8cf24efd19e

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Yan Oya Flood 2016 · Flood Inundation GND · Water and irrigation

Existing form reference: b2ee7829c7cfc34b

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Yan Oya Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: 71692320f67c8770

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Yan Oya Flood 2016 · Flood Inundation Area · Water and irrigation

Existing form reference: 9d90cd9c5c84a7ba

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 81 · Water and irrigation

Existing form reference: 8ba4ffbddb26f7b5

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Nilwala Ganga Flood 2017 · Flood Inundation GND · Water and irrigation

Existing form reference: cd20f9bf8d1487c0

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Nilwala Ganga Flood 2017 · Flood Inundation DSD · Water and irrigation

Existing form reference: d6e8e9a429825b57

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Nilwala Ganga Flood 2017 · Flood Inundation Area · Water and irrigation

Existing form reference: ce6e0b46bd0534b9

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 76 · Water and irrigation

Existing form reference: 4d62429a56f1e52b

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mundani Aru Flood 2014 · Flood Inundation GND · Water and irrigation

Existing form reference: 54b17c1b976d7b7c

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mundani Aru Flood 2014 · Flood Inundation DSD · Water and irrigation

Existing form reference: de66a3c339d43cc1

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mundani Aru Flood 2014 · Flood Inundation Area · Water and irrigation

Existing form reference: ebc817056ae98de6

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 71 · Water and irrigation

Existing form reference: 7df34748f8dc7a71

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mee Oya Flood 2019 · Flood Inundation GND · Water and irrigation

Existing form reference: 336909700eb1e807

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mee Oya Flood 2019 · Flood Inundation DSD · Water and irrigation

Existing form reference: 977273349cc89bef

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mee Oya Flood 2019 · Flood Inundation Area · Water and irrigation

Existing form reference: 3c769ddf1cd69ffa

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 66 · Water and irrigation

Existing form reference: d6db0e029cc9024f

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Malwathu Oya Flood 2011 · Flood Inundation GND · Water and irrigation

Existing form reference: 17b96434d3bdc3d8

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Malwathu Oya Flood 2011 · Flood Inundation DSD · Water and irrigation

Existing form reference: fa2f19c86d129c30

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Malwathu Oya Flood 2011 · Flood Inundation Area · Water and irrigation

Existing form reference: 785418aca242c75f

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 61 · Water and irrigation

Existing form reference: 75f475250456de4c

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mahaweli Ganga Flood 2012 · Flood Inundation GND · Water and irrigation

Existing form reference: 3d03fbdf1f36a8b0

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mahaweli Ganga Flood 2012 · Flood Inundation DSD · Water and irrigation

Existing form reference: 562d7edfae1efc39

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Mahaweli Ganga Flood 2012 · Flood Inundation Area · Water and irrigation

Existing form reference: 5a3f22d6db739d31

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 56 · Water and irrigation

Existing form reference: bbc4c12de68b1c87

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Maha Oya (102) Flood 2016 · Flood Inundation GND · Water and irrigation

Existing form reference: ccd8becff516f214

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Maha Oya (102) Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: 388a6af26afd09cc

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Maha Oya (102) Flood 2016 · Flood Inundation Area · Water and irrigation

Existing form reference: 9edb436b9dd89dbd

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 51 · Water and irrigation

Existing form reference: e86ead836ff90dea

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kirama Oya Flood 2017 · Flood Inundation GND · Water and irrigation

Existing form reference: f589bf96735f0d23

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kirama Oya Flood 2017 · Flood Inundation DSD · Water and irrigation

Existing form reference: ab1ef79575b445fa

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kirama Oya Flood 2017 · Flood Inundation Area · Water and irrigation

Existing form reference: 5d056dd558b67b64

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 46 · Water and irrigation

Existing form reference: aa5a1be4d7f874a7

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kalu Ganga Flood 2017 · Flood Inundation GND · Water and irrigation

Existing form reference: 23a2949aee5a9a33

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kalu Ganga Flood 2017 · Flood Inundation DSD · Water and irrigation

Existing form reference: 6adfb4fb98a8707e

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kalu Ganga Flood 2017 · Flood Inundation Area · Water and irrigation

Existing form reference: 0082696b49d69c10

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 41 · Water and irrigation

Existing form reference: 03a72f044ebae238

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganag Flood 2016 Major · Flood Inundation DSD · Water and irrigation

Existing form reference: fb02e7976de33449

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganag Flood 2016 Major · Flood Inundation GND · Water and irrigation

Existing form reference: 03ee84fbf008e604

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganag Flood 2016 Major · Flood Inundation Area · Water and irrigation

Existing form reference: 271b1d2b0a139a64

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 36 · Water and irrigation

Existing form reference: 7a5174dfa55bfd27

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 2012 Minor · Flood Inundation GND · Water and irrigation

Existing form reference: cc5d99dd2a1894a4

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganag Flood 2016 Minor · Flood Inundation DSD · Water and irrigation

Existing form reference: 620e0dab3654a548

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 2012 Minor · Flood Inundation Area · Water and irrigation

Existing form reference: 7f5d382712c12acf

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 31 · Water and irrigation

Existing form reference: 05802ebbb2056902

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 1989 Critical · Flood Inundation GND · Water and irrigation

Existing form reference: 317acf986c000ec2

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 1989 Critical · Flood Inundation DSD · Water and irrigation

Existing form reference: a8bf89973a928788

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kelani Ganga Flood 1989 Critical · Flood Inundation Area · Water and irrigation

Existing form reference: 741b82a1161a09af

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 26 · Water and irrigation

Existing form reference: 3a83818903f3f37d

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kala Oya Flood 2016 · Flood Inundation GND · Water and irrigation

Existing form reference: 49c3db841a10343f

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kala Oya Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: 991636cb328c0e85

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Kala Oya Flood 2016 · Flood Inundation Area · Water and irrigation

Existing form reference: b22dc6c49a5a6c32

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 21 · Water and irrigation

Existing form reference: 5aefbeaa988c678e

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gin Ganga Flood 2017 · Flood Inundation GND · Water and irrigation

Existing form reference: aacfac87f71565b1

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gin Ganga Flood 2017 · Flood Inundation DSD · Water and irrigation

Existing form reference: 29a6fdf392f24335

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gin Ganga Flood 2017 · Flood Inundation Area · Water and irrigation

Existing form reference: a0692e188c7ae78c

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 16 · Water and irrigation

Existing form reference: 9f0e3d9806f9372e

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gal Oya Flood 2016 · Flood Inundation GND · Water and irrigation

Existing form reference: 0896be503f933851

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gal Oya Flood 2016 · Flood Inundation DSD · Water and irrigation

Existing form reference: edc275f80f311458

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Gal Oya Flood 2016 · Flood Inundation Area · Water and irrigation

Existing form reference: 621723d9774991dd

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 11 · Water and irrigation

Existing form reference: 66a5f593af6cf0f5

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Deduru Oya Flood 2018 · Flood Inundation DSD · Water and irrigation

Existing form reference: 7babdebde5c3a59f

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Deduru Oya Flood 2018 · Flood Inundation GND · Water and irrigation

Existing form reference: 8ef6df7ed78bd257

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Deduru Oya Flood 2018 · Flood Inundation Area · Water and irrigation

Existing form reference: 6e945531b3cfca82

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 6 · Water and irrigation

Existing form reference: ad60f9303374d50c

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Attanagalu Oya Flood 2018 · Flood Inundation GND · Water and irrigation

Existing form reference: f1156d2a9872139a

Field	Unit	Required
Source record ID	Confirm if needed	No
Grama Niladhari division	Confirm if needed	No
gnd no	Confirm if needed	No
gnd c	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
admin code	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Attanagalu Oya Flood 2018 · Flood Inundation DSD · Water and irrigation

Existing form reference: 64d7a48f5360398d

Field	Unit	Required
Source record ID	Confirm if needed	No
Join Count	Confirm if needed	No
TARGET FID	Confirm if needed	No
Province	Confirm if needed	No
province c	Confirm if needed	No
District	Confirm if needed	No
district c	Confirm if needed	No
Divisional secretariat	Confirm if needed	No
dsd c	Confirm if needed	No
Flood event / area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Attanagalu Oya Flood 2018 · Flood Inundation Area · Water and irrigation

Existing form reference: 23c4010edccc9e62

Field	Unit	Required
Source record ID	Confirm if needed	No
Flood event / area	Confirm if needed	No
Publisher label	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

River Basin · source layer 1 · Water and irrigation

Existing form reference: 9cee3fab75edb4bf

Field	Unit	Required
Source record ID	Confirm if needed	No
Watershed name	Confirm if needed	No
Wshed No	Confirm if needed	No
SubRivBasN	Confirm if needed	No
Sub RivBas	Confirm if needed	No
Area	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

rivers · Water and irrigation

Existing form reference: bddcc1162ffe3b29

Field	Unit	Required
OID	Confirm if needed	No
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
SymbolID	Confirm if needed	No
AltMode	Confirm if needed	No
Base	Confirm if needed	No
Clamped	Confirm if needed	No
Extruded	Confirm if needed	No
Snippet	Confirm if needed	No
PopupInfo	Confirm if needed	No
Source geometry length	Confirm if needed	No

Buffer of hydrostations · Water and irrigation

Existing form reference: a0f586c57ced7d89

Field	Unit	Required
Source record ID	Confirm if needed	No
no	Confirm if needed	No
station	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No
basin	Confirm if needed	No
Buffer distance in Meters	Confirm if needed	No
ORIG FID	Confirm if needed	No
Area in Square Kilometers	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

gauges · Water and irrigation

Existing form reference: 10375802bd0f4154

Field	Unit	Required
Source record ID	Confirm if needed	No
River Basin	Confirm if needed	No
Gauge	Confirm if needed	No
Water Level	station unit; select a station	No
Rain Fall	mm	No
Source record created	Confirm if needed	No
Source record edited	Confirm if needed	No
alertpull	station unit; select a station	No
minorpull	station unit; select a station	No
majorpull	station unit; select a station	No

stations · Water and irrigation

Existing form reference: c0d33ca136364cb4

Field	Unit	Required
Source record ID	Confirm if needed	No
no	Confirm if needed	No
station	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No
basin	Confirm if needed	No
Tributory	Confirm if needed	No
Alert Level	Confirm if needed	No
Minor Flood Level	Confirm if needed	No
Major Flood Level	Confirm if needed	No
Unit	Confirm if needed	No
Elivation m MSL	m MSL	No

groupbySummary · Water and irrigation

Existing form reference: 6a3ee4ad7513e95e

Field	Unit	Required
Source record ID	Confirm if needed	No
Join ID	Confirm if needed	No
gauge	Confirm if needed	No
Sum Rain Fall	mm	No
Count of Points	Confirm if needed	No

Irrigable Area · Water and irrigation

Existing form reference: ec64c51bcb7a13ab

Field	Unit	Required

Reservoir · Water and irrigation

Existing form reference: a4a0cc679fd52fa5

Field	Unit	Required

Bund · Water and irrigation

Existing form reference: 1f490c8006777e68

Field	Unit	Required

Sluice · Water and irrigation

Existing form reference: 1799548d75c1577b

Field	Unit	Required

Spill · Water and irrigation

Existing form reference: 092220ad7d168ad3

Field	Unit	Required

Canal System · Water and irrigation

Existing form reference: 018e6b3de43e55a7

Field	Unit	Required

Flood 30Nov2025 · source layer 0 · Water and irrigation

Existing form reference: d7be90171f7bd605

Field	Unit	Required
OBJECTID 1	Confirm if needed	No
RiverBasin	Confirm if needed	No
Source geometry area	Confirm if needed	No
Source geometry length	Confirm if needed	No

Major reservoirs · current readings · Water and irrigation

Existing form reference: 2942a78ac9121012

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
Week No	Confirm if needed	No
Update Date	Confirm if needed	No
Reservoir	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Range	Confirm if needed	No
Division	Confirm if needed	No
Irrigable area	acres	No
Full supply depth	ft	No
Gross Capacity Acft	acre-ft	No
Dead Storage Acft	acre-ft	No
Active Storage Acft	acre-ft	No
Date	Confirm if needed	No
Water Depth ft	ft	No
Gross Storage Acft	acre-ft	No
Effective Storage Acft	acre-ft	No
Effective storage percentage	%	No
Preceding-day rainfall	mm	No
Spilling	Confirm if needed	No
Remarks	Confirm if needed	No
Downstream impact	Confirm if needed	No
Spill discharge	cusec (publisher)	No
Remaining storage (publisher)	acre-ft	No

Major reservoirs · Maha seasonal history · Water and irrigation

Existing form reference: 620e4a73d4ea0be0

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
UPDATED DATE	Confirm if needed	No
RESERVOIR	Confirm if needed	No
LATITUDE	Confirm if needed	No
LONGITUDE	Confirm if needed	No
RANGE	Confirm if needed	No
Division	Confirm if needed	No
Active Storage (Acft)	acre-ft	No
Long-term average	acre-ft	No
ES 20 21 Acft	acre-ft	No
ES 21 22 Acft	acre-ft	No
ES 22 23 Acft	acre-ft	No
ES 23 24 Acft	acre-ft	No
ES 24 25 Acft	acre-ft	No
ES 25 26 Acft	acre-ft	No
ES 26 27 Acft	acre-ft	No

Major reservoirs · Yala seasonal history · Water and irrigation

Existing form reference: 560087607361a247

Field	Unit	Required
ID	Confirm if needed	No
Publisher reservoir ID	Confirm if needed	No
UPDATED DATE	Confirm if needed	No
RESERVOIR	Confirm if needed	No
LATITUDE	Confirm if needed	No
LONGITUDE	Confirm if needed	No
RANGE	Confirm if needed	No
Division	Confirm if needed	No
Active Storage (Acft)	acre-ft	No
Long-term average	acre-ft	No
EFFECTIVE STORAGE (Acft) 2022	acre-ft	No
EFFECTIVE STORAGE (Acft) 2023	acre-ft	No
EFFECTIVE STORAGE (Acft) 2024	acre-ft	No
EFFECTIVE STORAGE (Acft) 2025	acre-ft	No
EFFECTIVE STORAGE (Acft) 2026	acre-ft	No

Medium reservoirs · Yala seasonal history · Water and irrigation

Existing form reference: c349e5c98d02782a

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
Update Date	Confirm if needed	No
Reservoir	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Range	Confirm if needed	No
Division	Confirm if needed	No
Active Storage (Acft)	acre-ft	No
Long-term average	acre-ft	No
EFFECTIVE STORAGE (Acft) 2023	acre-ft	No
EFFECTIVE STORAGE (Acft) 2024	acre-ft	No
EFFECTIVE STORAGE (Acft) 2025	acre-ft	No
EFFECTIVE STORAGE (Acft) 2026	acre-ft	No

Medium reservoirs · Maha seasonal history · Water and irrigation

Existing form reference: ade3b5a99ab49e1d

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
Update Date	Confirm if needed	No
Reservoir	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Range	Confirm if needed	No
Division	Confirm if needed	No
Active Storage (Acft)	acre-ft	No
Long-term average	acre-ft	No
ES 24 25 Acft	acre-ft	No
ES 25 26 Acft	acre-ft	No
ES 26 27 Acft	acre-ft	No

Medium reservoirs · current readings · Water and irrigation

Existing form reference: 78fedd1e1892ca18

Field	Unit	Required
Publisher reservoir ID	Confirm if needed	No
Week No	Confirm if needed	No
Update Date	Confirm if needed	No
Reservoir	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Range	Confirm if needed	No
Division	Confirm if needed	No
Irrigable area	acres	No
Full supply depth	ft	No
Gross Capacity Acft	acre-ft	No
Dead Storage Acft	acre-ft	No
Active Storage Acft	acre-ft	No
Date	Confirm if needed	No
Water Depth ft	ft	No
Gross Storage Acft	acre-ft	No
Effective Storage Acft	acre-ft	No
Effective storage percentage	%	No
Preceding-day rainfall	mm	No
Spilling	Confirm if needed	No
Remarks	Confirm if needed	No
Remaining storage (publisher)	acre-ft	No

Published project technical details · Water and irrigation

Existing form reference: official-projects

Field	Unit	Required
Project	Confirm if needed	No
Component	Confirm if needed	No
Parameter	Confirm if needed	No
Source page	Confirm if needed	No

Irrigation publications · Water and irrigation

Existing form reference: official-publications

Field	Unit	Required
Publication	Confirm if needed	No
Type	Confirm if needed	No
Publication period	Confirm if needed	No
Data availability	Confirm if needed	No
Publisher document	Confirm if needed	No

5. Documents and images

Your institution has its own document and image library. Use the same library for reports, photos and other evidence.

Open this screen for Irrigation Department See the presentation example

Irrigation Department Documents and images prototype screen — Irrigation Department. Prototype screen. Select the image to enlarge it.

What you can try

Open Documents and images. Check the institution name.
Use All files, Documents or Images to find a file. Open its preview or download the original.
Use a sample file to try Add file. Private is the starting choice. Public needs a source, permission to share and review.
Use Access preview to try the institution reviewer and Public visitor views.

Files added in the prototype stay in this browser. Public sharing is an access preview. Existing public reference links already work online.

What your institution needs to confirm

Does a separate library for your institution meet your needs?Should new files start as Private for the permitted institution team?Should Public access require a review of the file and sharing permission?What documents and images will you store? Give the file types, usual sizes and need for earlier versions.Which job roles may add files, read Private files and approve Public files?Which files must stay Private? What permission, licence or expiry rule is needed for Public files?What else should change in this library?

6. Data structure management

Data structure keeps the existing source tree, records, charts and map. Manage structure adds a place to propose changes to definitions.

Open this screen for Irrigation Department See the presentation example

Irrigation Department Data structure management prototype screen — Irrigation Department. Prototype screen. Select the image to enlarge it.

What you can try

Open Data structure and choose Manage structure.
Use Add base domain for a main information area. Add inside creates a subject area, a nested subject, an entity type or a field under the right parent.
Give the definition a clear name, code and meaning. Reuse an existing definition when the meaning is the same.
For a field, check the data type, unit, required value, limits and missing-value rule. Save a Draft, then try the separate reviewer view.

An entity type means a kind of thing or event, such as a reservoir or an inspection. Drafts stay in this browser. A demo approval does not change real definitions, data, chart links or sharing rights.

What your institution needs to confirm

Do the existing main topics and subject areas match your institution’s work?Should definition changes stay Draft until the responsible reviewer checks them?Is it right to reuse the same entity type or field when its meaning is the same?Which main topics, subject areas, entity types or fields should we add or change?Which units, choices, limits, decimal places and missing-value rules must each new field use?Which job roles may edit definitions and review them? Who owns each main information area?When a meaning, unit or calculation changes, what review and version history does your institution need?

7. Users and access

User management shows example profiles for each institution. People and Roles and access let you review the proposed account screens.

Open this screen for Irrigation Department See the presentation example

Irrigation Department Users and access prototype screen — Irrigation Department. Prototype screen. Select the image to enlarge it.

What you can try

Open User management and choose the institution. The rows are examples, not a list of your staff.
Use View access to check a role. An administrator title alone does not give access to Private files.
Try Preview invitation or Preview access change. Check the role, start date, optional end date and reason.
Review the example permissions and tell us which job roles should receive each one.

These are interface previews only. They create no account, send no email and change no access. Use example details in the preview. Institution verification does not grant a real permission.

What your institution needs to confirm

Do the proposed role names and responsibilities match your institution?Should access be limited to the assigned institution and the agreed dates?Should reading Private files need a separate permission, even for an administrator?Which job roles should view data, add files, review Public requests, edit definitions and manage users?Who should approve new access, set an end date or remove access when someone changes duties?Which user fields, roles or access checks are missing? Give role names rather than passwords or private account details.

9. Anything else we should change?

Which decisions or services are missing?Which forms or fields should change? Give the existing form reference where possible.What should change in the entry, checking, expert, map or report steps?Are the English, Sinhala and Tamil words clear? Give the screen name, current word and your suggested wording.Who should join the next review and what should happen next?

Use the Download answers button at the top of this page. Share the downloaded file or printed copy through your agreed review channel. Nothing is sent automatically.

Irrigation Department

1. Check a decision

2. Try the inputs

3. Check each decision

4. Existing data forms for your institution

5. Documents and images

What you can try

What your institution needs to confirm

6. Data structure management

What you can try

What your institution needs to confirm

7. Users and access

What you can try

What your institution needs to confirm

8. Can you share data regularly?

9. Anything else we should change?