Land Use Policy Planning Department

Sri Lanka decision proposal

Tell us what to change or add.

Archived decisions

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. Land-use change over timeChoose where to investigate and explain why
Open prototype

Find land-use changes, check the evidence and choose the next investigation.

CompareChoose the area, years and class. View hectares, percentages and annual change.
InspectOrder by hectares or percentage. Check decreases, increases and parcel transitions.
Follow upReview a division and prepare a decision example with its reason, action and proposed role.

One fictional example: the annual records, transition table and decision record use the same example data. Static reference images have their own published sources and dates. An explicit balanced edit updates the example in the current page only.

Data and available sources

Natural forest, Forest plantations, Paddy land, Other annual crops, Tea and other permanent crops, Settlements, Water, Other land, Unclassified / missing. Keep natural forest, forest plantations and agricultural tree crops separate. Ambiguous source categories stay unresolved; they cannot be silently relabelled.

SourceTime coverageUse and limits
NSDI Landuse / LUPPDObservation years must be confirmedPolygon classes include forest, paddy, tea, rubber, coconut and other uses. Creation/revision years are metadata. They do not confirm a comparable annual observation series. Obtain complete project coverage.
NSDI Forest BoundaryObservation years not stated in the inspected layerForest polygons, forest type and forest name. Two dated versions, local completeness and accuracy need confirmation. A forest-only layer cannot fill all land-use classes.
Copernicus annual land cover, C3 v3.0.1Annual 2015–2019 · nominal 100 mConsistent annual broad land-cover maps and quality layers. Tree crops can enter forest/shrub classes. Temporary cropland is not split into paddy and other crops. Global accuracy is not local accuracy.
DCS paddy statisticsMaha / Yala seasonal district seriesSown/harvested extent, yield and production; extent definitions differ. Context only for this land-stock comparison. Seasonal sown/harvested extent is not a forest or field-boundary map. Do not add seasons as unique physical land area.

Inputs retain the native category/code, observed year, division and analysis-boundary version, original area/unit, dataset and classification versions, measure, method, coverage and quality reference. A creation or revision year is not automatically an observation year. Seasonal crop extents stay separate from mapped physical land area.

Comparison and decision rules
  • Match the analysis boundary, class scheme, method, measure and source series. Show the actual area covered inside each division; do not silently substitute the full division for the project area.
  • Class areas plus unclassified area must equal the fixed analysis area. A blank is missing, not zero. Incomplete endpoints block whole-area change and transitions.
  • Net change = later minus earlier. Percentage change = 100 times net change divided by earlier area; unavailable for a zero baseline. Annual change = net change divided by elapsed years, not a forecast.
  • Show both hectares and percentages. The selected sort and direction explain the review order; they do not set a material-change threshold.
  • Transitions require matched parcel or pixel histories. Gross loss leaves a class; gross gain enters it. Net = gain minus loss. Count a changed parcel once for total converted extent.
  • The example retains fictional parcel histories for the numerical transition table only. No map is generated from these records. Static published map images provide separate geographic context.
  • A decision example records the selected scope and period, dataset/boundary/class/method versions, figures, reason, next action, proposed role, follow-up and source references. No assignment is sent.
Client and expert checks — pending

Client: confirm the project area, observation years, data owner and sharing rights, what changes deserve attention, and the responsible decision-making roles.

Expert: confirm the local class crosswalk, comparable source maps, map scale, accuracy and uncertainty, minimum detectable change and action thresholds.

Published definitions and methods retain their sources. Local choices stay here for confirmation; the developer checks arithmetic, mappings and data handling.

Future system: preparing analytical maps
  1. Obtain the agreed project boundary, division boundaries, dated land-use layers and original metadata.
  2. Check observation periods, class definitions, geometry and coverage. Align boundaries, classification, resolution and coordinate systems.
  3. Calculate hectares with a suitable area-preserving projection or documented geodesic method. Do not treat square degrees or an undocumented source area field as hectares.
  4. Overlay compatible dated layers to retain from/to classes and calculate class totals, losses, gains, stable area and unknown coverage. Assess local accuracy with suitable reference evidence.
  5. Keep the input versions and processing method. Deliver permitted map layers and summary records through the API for the web views.

This example in the prototype uses fictional records. Official-source file selections remain previews; no institution data is uploaded or saved.

Historical map references

Genuine Copernicus forest-class map images for 2015 and 2018 are available as historical context. They do not match or authenticate the fictional division records. Comparable local land-use images for the selected example years are still missing.

View historical map references

Published references and local calculation notes

Official publications supply native classifications and context. IPCC explains consistent land representation and net versus gross change. The complete LAND-CHANGE-1 comparison, mapping and review-order rules are project proposals. Their local use requires validation in this review.

Detailed calculation rules and worked example

Your review
Other checks and responsibilities
2. Check development overlap with mapped constraintsDEC-DP01-002 · Development screening
Try this decision

Check reported development overlap before preparing a planning referral.

Validation required

Fictional default example · 2025.

Fictional case / areaOverlap share [%]Overlapping area [ha]Next check
Laggala Pallegama — development screening / 20252418Check the matching footprint, source boundary and applicable conditions
Rattota — development screening / 20252418Check the matching footprint, source boundary and applicable conditions
Panvila — development screening / 20252418Check the matching footprint, source boundary and applicable conditions

What the selected record shows. The supplied overlap is 18 ha within the 75 ha assessed footprint, or 24%. Check the cited boundary and source records before interpreting the overlap.

Next step. Check the matching footprint, source boundary and applicable conditions. Prepare overlap review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Supplied overlap and a matching constraint edition do not grant development permission.

Inputs, method and sources
Supplied inputValueUnit
Assessed footprint or frame75ha
Reported common overlap, counted once18ha
Boundary editionSample boundary1
Constraint definitionSample constraint class
Matching source frame, boundary and period evidenceProvided
Area/count source and matching definition referenceFictional matched survey return / edition 1

100 × union of constraint overlap / proposal footprint. Count intersecting constraint areas once. The areas/counts are supplied records; this decision view does not calculate intersections, distances or locations.

Geometry preparation must use matching coordinate systems, dated boundary editions and valid spatial predicates. Overlap supports referral; it does not determine ownership, permission or site safety. A static reference image does not verify these supplied measurements or boundaries.

Other required records: Proposal polygon; zoning edition; conservation boundaries; restriction type; overlap hectares.

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.
Your checks for this decision
3. Check evidence for proposed land usesDEC-DP01-005 · Agricultural suitability
Try this decision

Check the land, soil, slope, rainfall and crop evidence needed to compare proposed uses.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — agricultural suitability / Laggala PallegamaLand polygon: MissingObtain the missing evidence listed below
Rattota — agricultural suitability / Rattotasoil depth: MissingObtain the missing evidence listed below
Panvila — agricultural suitability / Panvilaslope degrees: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this agricultural suitability 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
  • Land polygon: Missing

Complete records alone do not establish agricultural suitability.

Inputs, method and sources
Supplied inputValueUnit
Land polygonMissing
Land polygon evidence referenceNot provided
soil depthDocumented
soil depth evidence referenceSample Laggala Pallegama field register / 2025
slope degreesDocumented
slope degrees evidence referenceSample Laggala Pallegama field register / 2025
rainfallDocumented
rainfall evidence referenceSample Laggala Pallegama field register / 2025
water accessDocumented
water access evidence referenceSample Laggala Pallegama field register / 2025
crop requirementsDocumented
crop requirements evidence referenceSample 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: Land polygon; soil depth; slope degrees; rainfall; water access; crop requirements.

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.
Your checks for this decision
4. Check land-conversion applications before referralDEC-DP01-006 · Land conversion
Try this decision

Check the application, existing use, ownership and objections before a conversion referral.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — land conversion / Laggala PallegamaApplication ID: MissingObtain the missing evidence listed below
Rattota — land conversion / Rattotacurrent use: MissingObtain the missing evidence listed below
Panvila — land conversion / Panvilaproposed use: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this land conversion 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
  • Application ID: Missing

The responsible authority must determine whether conversion is permitted.

Inputs, method and sources
Supplied inputValueUnit
Application IDMissing
Application ID evidence referenceNot provided
current useDocumented
current use evidence referenceSample Laggala Pallegama field register / 2025
proposed useDocumented
proposed use evidence referenceSample Laggala Pallegama field register / 2025
ownership evidenceDocumented
ownership evidence evidence referenceSample Laggala Pallegama field register / 2025
applicable rulesDocumented
applicable rules evidence referenceSample Laggala Pallegama field register / 2025
objectionsDocumented
objections evidence referenceSample 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: Application ID; current use; proposed use; ownership evidence; applicable rules; objections.

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.
Your checks for this decision
5. Compare potential settlement areasDEC-DP01-007 · Settlement planning
Try this decision

Compare settlement options using service access, constraints, costs and stated trade-offs.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Infill near existing services / Laggala PallegamaUse existing nearby roads and services.Check vacant-site capacity, tenure and pressure on existing services.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Small serviced extension / Laggala PallegamaAdd serviced space in a limited extension.Needs access, utilities, drainage and affordable servicing.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Staged peripheral extension / Laggala PallegamaSpread expansion and servicing over stages.Later stages may remain without services; requires staged funding and access.Records: Not provided; condition evidence: Not providedObtain 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: Candidate polygon; service capacity; access cost; hazard evidence; environmental constraints
  • Applicable conditions, what was checked and the supporting reference

A budget surplus does not establish a suitable settlement location.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionUse existing nearby roads and services.
Resource needs and adverse effectsCheck vacant-site capacity, tenure and pressure on existing services.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot 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.

A budget surplus does not establish a suitable settlement location.

Other required records: Candidate polygon; service capacity; access cost; hazard evidence; environmental 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.
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.
Your checks for this decision
6. Check activities reported over mapped wetlandsDEC-DP01-009 · Wetland protection
Try this decision

Check reported activity overlap with the cited wetland record.

Validation required

Fictional default example · 2025.

Fictional case / areaOverlap share [%]Overlapping area [ha]Next check
Laggala Pallegama — wetland protection / 20252418Check the matching footprint, source boundary and applicable conditions
Rattota — wetland protection / 20252418Check the matching footprint, source boundary and applicable conditions
Panvila — wetland protection / 20252418Check the matching footprint, source boundary and applicable conditions

What the selected record shows. The supplied overlap is 18 ha within the 75 ha assessed footprint, or 24%. Check the cited boundary and source records before interpreting the overlap.

Next step. Check the matching footprint, source boundary and applicable conditions. Prepare overlap review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

An overlap figure does not establish the wetland boundary or permission conditions.

Inputs, method and sources
Supplied inputValueUnit
Assessed footprint or frame75ha
Reported common overlap, counted once18ha
Boundary editionSample boundary1
Constraint definitionSample constraint class
Matching source frame, boundary and period evidenceProvided
Area/count source and matching definition referenceFictional matched survey return / edition 1

100 × union of constraint overlap / proposal footprint. Count intersecting constraint areas once. The areas/counts are supplied records; this decision view does not calculate intersections, distances or locations.

Geometry preparation must use matching coordinate systems, dated boundary editions and valid spatial predicates. Overlap supports referral; it does not determine ownership, permission or site safety. A static reference image does not verify these supplied measurements or boundaries.

Other required records: Activity geometry; wetland boundary edition; wetland class; proposal 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.
Your checks for this decision
7. Check activities reported inside river reservationsDEC-DP01-010 · Riparian protection
Try this decision

Check an activity against the cited river-reservation survey and basis.

Validation required

Fictional default example · 2025.

Fictional case / areaOverlap share [%]Overlapping area [ha]Next check
Laggala Pallegama — riparian protection / 20252418Check the matching footprint, source boundary and applicable conditions
Rattota — riparian protection / 20252418Check the matching footprint, source boundary and applicable conditions
Panvila — riparian protection / 20252418Check the matching footprint, source boundary and applicable conditions

What the selected record shows. The supplied overlap is 18 ha within the 75 ha assessed footprint, or 24%. Check the cited boundary and source records before interpreting the overlap.

Next step. Check the matching footprint, source boundary and applicable conditions. Prepare overlap review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

No universal reservation width or legal breach is inferred.

Inputs, method and sources
Supplied inputValueUnit
Assessed footprint or frame75ha
Reported common overlap, counted once18ha
Boundary editionSample boundary1
Constraint definitionSample constraint class
Matching source frame, boundary and period evidenceProvided
Area/count source and matching definition referenceFictional matched survey return / edition 1

100 × union of constraint overlap / proposal footprint. Count intersecting constraint areas once. The areas/counts are supplied records; this decision view does not calculate intersections, distances or locations.

Geometry preparation must use matching coordinate systems, dated boundary editions and valid spatial predicates. Overlap supports referral; it does not determine ownership, permission or site safety. A static reference image does not verify these supplied measurements or boundaries.

Other required records: River geometry; legally reviewed reservation width; activity footprint; boundary edition.

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.
Your checks for this decision
8. Review changes in agricultural land areaDEC-DP01-013 · Urban expansion
Try this decision

Compare agricultural class losses and gains within the same mapped extent.

Validation required

Fictional default example · 2025.

Fictional case / areaNet class-area change [ha]Relative class-area change [%]Gross loss from class [ha]Gross gain to class [ha]Next check
Laggala Pallegama — urban expansion / 2025-10-10188Check the matching source records before interpreting the change
Rattota — urban expansion / 202554.16738Check the matching source records before interpreting the change
Panvila — urban expansion / 2025-2-2.564Check the matching source records before interpreting the change

What the selected record shows. The recorded Agricultural land — demonstration class definition area changes from 100 to 90 ha. Net change is -10 ha; supplied gross loss is 18 ha and gross gain is 8 ha.

Next step. Check the matching source records before interpreting the change. Prepare change comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Aggregate class changes do not identify individual conversions or their causes.

Example chart
Net class-area change — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Earlier mapped class area100ha
Later mapped class area90ha
Matched area leaving the class18ha
Matched area entering the class8ha
Same fixed analysis extent200ha
Native class and mapping versionAgricultural land — demonstration class definition
Earlier observation date2024-06-30
Later observation date2025-06-30

Net=later−earlier; percentage=100×net/earlier when earlier>0. Matched transitions must reproduce net=gain−loss. Net totals alone do not establish conversion.

Same boundary, definitions, observation basis and adequate map quality are required. Coverage changes and classification error are not proven land-use change. Example boundaries and transitions are fictional.

Other required records: Matched land-cover maps; built hectares; agricultural hectares; map years.

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.
Your checks for this decision
9. Compare restoration land-use alternativesDEC-DP01-015 · Restoration planning
Try this decision

Compare restoration choices using site constraints, benefits, resources and costs.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Assisted natural regeneration / Laggala PallegamaAllow existing native regeneration to recover.Needs suitable seed sources, protection and time; recovery is uncertain.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Agroforestry buffer / Laggala PallegamaCombine farm use with a planted tree buffer.Needs farmer agreement, crop compatibility and long-term maintenance.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Mixed native planting / Laggala PallegamaEstablish a specified mix of native trees.Needs suitable species, planting resources, maintenance and survival checks.Records: Not provided; condition evidence: Not providedObtain 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: Site condition; restoration options; tenure; costs LKR; benefits; constraints
  • Applicable conditions, what was checked and the supporting reference

No option is preferred solely because it costs less.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionAllow existing native regeneration to recover.
Resource needs and adverse effectsNeeds suitable seed sources, protection and time; recovery is uncertain.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot 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.

No option is preferred solely because it costs less.

Other required records: Site condition; restoration options; tenure; costs LKR; benefits; 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.
Your checks for this decision
10. Prepare a detailed soil-loss assessmentDEC-DP01-016 · Land degradation
Try this decision

Use the supplied soil-loss factors to identify where a detailed assessment is needed.

Verified published formula · USLE factor product

Fictional default example · 2025.

Fictional case / areaEstimated annual sheet/rill loss [t/ha/year]Next check
Laggala Pallegama — land degradation / 202515.641Check local factor and site evidence before selecting a detailed erosion assessment
Rattota — land degradation / 20253.259Check local factor and site evidence before selecting a detailed erosion assessment
Panvila — land degradation / 202539.102Check local factor and site evidence before selecting a detailed erosion assessment

What the selected record shows. Estimated annual sheet/rill loss: 15.641 t/ha/year.

Next step. Check local factor and site evidence before selecting a detailed erosion assessment. Prepare assessment brief in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

The estimate covers sheet and rill erosion, not landslides or all sediment delivery.

Example chart
Estimated annual sheet/rill loss — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Rainfall erosivity950MJ mm/(ha h year)
Soil erodibility0.035t ha h/(ha MJ mm)
Slope-length and steepness factor2.8ratio
Cover-management factor0.24fraction
Support-practice factor0.7fraction

R × K × LS × C × P, using a mutually consistent SI factor set.

This USLE factor product is not a full RUSLE2 run, measured loss, delivered sediment, gully loss or landslide forecast. Local factors and uncertainty need review.

Other required records: Rainfall erosivity; erodibility; slope factors; land cover; conservation practices.

United States Department of Agriculture Forest Service · A Guide for Predicting Sheet and Rill Erosion on Forest Land
Government publication · 1980 technical publication SA-TP 11; Universal Soil Loss Equation, printed page 2; metric conversion appendix, printed page 40

The historical source verifies the factor product. Local factor choice and suitability still need confirmation; this is not a full RUSLE2 implementation.

Calculation appendix

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.
Your checks for this decision
11. Investigate differences between planned and actual useDEC-DP01-017 · Plan implementation
Try this decision

Compare planned and observed hectares of the same land-use class.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [ha]Relative change [%]Next check
Laggala Pallegama — plan implementation / 2025-10-10Check the class, period and implementation evidence
Rattota — plan implementation / 202555Check the class, period and implementation evidence
Panvila — plan implementation / 2025-2-2Check the class, period and implementation evidence

What the selected record shows. Difference: -10 ha. Check the class, period and implementation evidence.

Next step. Check the class, period and implementation evidence. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A difference needs source and implementation checks before assigning a cause.

Example chart
Difference — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Hectares planned for the selected land-use class100ha
Hectares observed in that same class90ha

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

Other required records: Approved use plan; parcel ID; implementation date; observed use; hectares.

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.
Your checks for this decision
12. Find missing land-use map detailsDEC-DP01-019 · Map documentation
Try this decision

Find missing source, scale, coordinate and classification details in a land-use layer.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — map documentation / Laggala PallegamaLayer ID: MissingObtain the missing evidence listed below
Rattota — map documentation / Rattotascale: MissingObtain the missing evidence listed below
Panvila — map documentation / Panvilacoordinate system: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this map documentation 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
  • Layer ID: Missing

Complete metadata do not certify map accuracy.

Inputs, method and sources
Supplied inputValueUnit
Layer IDMissing
Layer ID evidence referenceNot provided
scaleDocumented
scale evidence referenceSample Laggala Pallegama field register / 2025
coordinate systemDocumented
coordinate system evidence referenceSample Laggala Pallegama field register / 2025
classification editionDocumented
classification edition evidence referenceSample Laggala Pallegama field register / 2025
ownerDocumented
owner evidence referenceSample Laggala Pallegama field register / 2025
survey dateDocumented
survey date evidence referenceSample 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: Layer ID; scale; coordinate system; classification edition; owner; survey 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.
Your checks for this decision
13. Check land-use survey schedulesDEC-DP01-020 · Survey scheduling
Try this decision

Check survey tasks against staff windows, effort and predecessors.

Validation required

Fictional default example · 2025.

Fictional case / areaPlanned duration [days]Resource hours remaining [hours]Next check
Laggala Pallegama — survey scheduling / 202538Resolve overlapping resource bookings
Rattota — survey scheduling / 202538Resolve overlapping resource bookings
Panvila — survey scheduling / 202538Resolve 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.

A feasible example schedule does not assign work or authorise a survey.

Inputs, method and sources
Supplied inputValueUnit
Required resourceWatershed field team
Task start2025-06-01
Task end2025-06-04
Earliest permitted start2025-05-28
Latest permitted finish2025-06-08
Required resource effort16hours
Available resource effort24hours
Predecessor task referenceNone
Mandatory permits and prerequisitesMet

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: Map edition; change evidence; survey effort days; team availability; update due 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.
Your checks for this decision
14. Decide where to check the accuracy of a land-change mapDEC-DP01-021 · Published method
Try this decision

Source. International publication.

Data needed. Map classes, map area by class, independently interpreted reference labels and a probability sample.

Method. Draw reference samples from mapped change and stable classes. Estimate accuracy with an area-weighted error matrix and report uncertainty.

Worked example. Divide the map into changed and stable areas. Sample both groups, then weight the accuracy results by the area each group covers. Recheck areas with weak reference evidence.

Next step. Send a class with weak agreement for independent interpretation or field verification.

Olofsson et al., Good practices for estimating area and assessing accuracy of land change. Sections 3–5, stratified sampling and area-adjusted accuracy.

Confirm the reference imagery, sample design and accuracy required for the intended use.

Your checks for this decision

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Landuse LUPPD 10K · Land Cover

Existing form reference: 30c67d24f5323223

FieldUnitRequired
Luse_CodeConfirm if neededNo
Main_CategoryConfirm if neededNo
Sub_CategoryConfirm if neededNo
Tank_NameConfirm if neededNo
Method_of_UpdationConfirm if neededNo
Year_of_UpdationConfirm if neededNo
Sheet_NoConfirm if neededNo
Road Right of ways · Geospatial Evidence

Existing form reference: b65e4609a48e9e05

FieldUnitRequired
Type_ROWConfirm if neededNo
Road_WidthConfirm if neededNo
Road WidthConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
Transport_point_IDConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Parcel Fabrics · Geospatial Evidence

Existing form reference: 91738cf582575742

FieldUnitRequired
Parcel IDConfirm if neededNo
Parcel erConfirm if neededNo
Parcel stConfirm if neededNo
Parcel DateConfirm if neededNo
Parcel tpConfirm if neededNo
Parcel orConfirm if neededNo
Sheet IDConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
St AreaConfirm if neededNo
St LengthConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
typeConfirm if neededNo
pcl_id_covConfirm if neededNo
lot_noConfirm if neededNo
sht_id_conConfirm if neededNo
plan_noConfirm if neededNo
inset_noConfirm if neededNo
sup_noConfirm if neededNo
sheet_noConfirm if neededNo
di_nameConfirm if neededNo
ds_nameConfirm if neededNo
nameConfirm if neededNo
spcific_puConfirm if neededNo
tenure_actConfirm if neededNo
esri_oidConfirm if neededNo
SLTDA Parcels · Geospatial Evidence

Existing form reference: ca9e78effa85e080

FieldUnitRequired
Plot NumberConfirm if neededNo
DescriptionConfirm if neededNo
Area_Sq_MetersConfirm if neededNo
Present StatusConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Landuse · Geospatial Evidence

Existing form reference: c4b2b042a758c3f0

FieldUnitRequired
Landuse_Classification_1Confirm if neededNo
Landuse_Classification_2Confirm if neededNo
Classification2_CodeConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo

5. Documents and images

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

Land Use Policy Planning Department Documents and images prototype screen
Land Use Policy Planning Department. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open Documents and images. Check the institution name.
  2. Use All files, Documents or Images to find a file. Open its preview or download the original.
  3. Use a sample file to try Add file. Private is the starting choice. Public needs a source, permission to share and review.
  4. 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

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.

Land Use Policy Planning Department Data structure management prototype screen
Land Use Policy Planning Department. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open Data structure and choose Manage structure.
  2. 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.
  3. Give the definition a clear name, code and meaning. Reuse an existing definition when the meaning is the same.
  4. 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

7. Users and access

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

Land Use Policy Planning Department Users and access prototype screen
Land Use Policy Planning Department. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open User management and choose the institution. The rows are examples, not a list of your staff.
  2. Use View access to check a role. An administrator title alone does not give access to Private files.
  3. Try Preview invitation or Preview access change. Check the role, start date, optional end date and reason.
  4. 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

8. Can you share data regularly?

We currently use public data and published reports where available. Please confirm whether your institution can provide data directly, so we can avoid retyping or reading figures from PDFs.

Do not enter passwords, access keys or private account details.

9. Anything else we should change?

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.