Survey 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 Example input to change a sample. Use Source input to check the fields and source details. 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. Select the authoritative survey edition for a case 2. Check differences in registered and surveyed parcel area 3. Find terrain requiring detailed site survey 4. Choose what to handle first: features needing ground verification 5. Choose what to handle first: pending cadastral survey requests 6. Schedule geodetic control inspection and restoration 7. Validate transformations before combining spatial datasets 8. Refer surveys failing approved accuracy specifications 9. Schedule aerial imagery for priority mapping gaps 10. Support formal review of conflicting boundary evidence 11. Choose what to handle first: map sheets with significant feature changes 12. Check required access and survey approvals 13. Select elevation datasets fit for intended analysis 14. Find areas needing authoritative boundary re-establishment 15. Balance crew instrument and travel requirements 16. Track survey products through independent checking 17. Resolve inconsistent parcel identifiers across institutions 18. Compare costs for equivalent survey work types 19. Clear delayed requests for permitted map products 20. Retain superseded survey editions with traceable revisions

1. Select the authoritative survey edition for a caseDEC-DP14-001 · Boundary selection · Suggested priority: High

Try this decision

Select the authoritative survey edition for a case.

Validation required

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

Next step. Complete the evidence. Accept a fit source for a defined use, restrict it, or request metadata/schema correction.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Boundary ID; Boundary ID evidence reference; legal source; legal source evidence reference; survey date; survey date evidence reference; scale; scale evidence reference; supersession; supersession evidence reference; intended use; intended use evidence reference

Other required evidence. Boundary ID; legal source; survey date; scale; supersession; intended use.

Fictional worked example · 2025

Laggala Pallegama — boundary selection · Laggala Pallegama

Input or result	Value	Unit
Boundary ID	Missing
Boundary ID evidence reference
legal source	Documented
legal source evidence reference	Sample Laggala Pallegama field register / 2025
survey date	Documented
survey date evidence reference	Sample Laggala Pallegama field register / 2025
scale	Documented
scale evidence reference	Sample Laggala Pallegama field register / 2025
supersession	Documented
supersession evidence reference	Sample Laggala Pallegama field register / 2025
intended use	Documented
intended use evidence reference	Sample Laggala Pallegama field register / 2025
Evidence gaps	1	items

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Resolved interoperability issues and current verified metadata.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Check differences in registered and surveyed parcel areaDEC-DP14-002 · Parcel reconciliation · Suggested priority: High

Try this decision

Investigate differences in registered and surveyed parcel area.

Validation required

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

Next step. Review evidence. Assign discrepancies to the custodian, accept documented corrections, or retain unresolved versions.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Original source measurement [ha]; Independent comparison measurement [ha]; Original measurement unit; Comparison measurement unit; Compared measure and definition

Other required evidence. Parcel ID; registered hectares; surveyed geometry; accuracy; edition; date.

Fictional worked example · 2025

Laggala Pallegama — parcel reconciliation · Laggala Pallegama

Input or result	Value	Unit
Original source measurement	100	ha
Independent comparison measurement	90	ha
Original measurement unit	Sample matching unit
Comparison measurement unit	Sample matching unit
Compared measure and definition	Sample comparable ha measure; same input scope
Difference	-10	ha
Relative change	-10	%

Keep both originals, units, scope, method, calibration and correction history. A difference does not identify which source is correct; no automatic averaging or overwrite.

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Discrepancies resolved with evidence and repeat error rate.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Find terrain requiring detailed site surveyDEC-DP14-003 · Terrain screening · Suggested priority: High

Try this decision

Identify terrain requiring detailed site survey.

Validation required

Method. 100 × union of constraint overlap / proposal footprint. Count intersecting constraint areas once.

Next step. Review evidence. Refer affected sites for technical/legal review, revise the footprint, or request a field survey.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Proposal footprint [ha]; Union of overlapping constraint areas [ha]; Boundary edition; Constraint definition

Other required evidence. Elevation model; resolution; slope; proposed footprint; accuracy; constraints.

Fictional worked example · 2025

Laggala Pallegama — terrain screening · Laggala Pallegama

Input or result	Value	Unit
Proposal footprint	75	ha
Union of overlapping constraint areas	18	ha
Boundary edition	Sample boundary1
Constraint definition	Sample constraint class
Overlap share	24	%
Overlapping area	18	ha

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.

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Resolved constraints and independently checked site conditions.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Choose what to handle first: features needing ground verificationDEC-DP14-004 · Field verification · Suggested priority: High

Try this decision

Prioritize features needing ground verification.

Validation required

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

Next step. Complete the evidence. Request correction, refer mandatory failures, or accept the inspected item with conditions.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Feature ID; Feature ID evidence reference; source date; source date evidence reference; positional uncertainty; positional uncertainty evidence reference; reported mismatch; reported mismatch evidence reference; survey request; survey request evidence reference

Other required evidence. Feature ID; source date; positional uncertainty; reported mismatch; survey request.

Fictional worked example · 2025

Laggala Pallegama — field verification · Laggala Pallegama

Input or result	Value	Unit
Feature ID	Missing
Feature ID evidence reference
source date	Documented
source date evidence reference	Sample Laggala Pallegama field register / 2025
positional uncertainty	Documented
positional uncertainty evidence reference	Sample Laggala Pallegama field register / 2025
reported mismatch	Documented
reported mismatch evidence reference	Sample Laggala Pallegama field register / 2025
survey request	Documented
survey request evidence reference	Sample Laggala Pallegama field register / 2025
Evidence gaps	1	items

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Evidence-backed corrective closure and recurring nonconformances.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Choose what to handle first: pending cadastral survey requestsDEC-DP14-005 · Cadastral backlog · Suggested priority: High

Try this decision

Prioritize pending cadastral survey requests.

Validation required

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

Next step. Follow up overdue case. Assign the next permitted case, escalate an overdue case, request evidence, or close with proof.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed

Other required evidence. Request ID; receipt date; statutory priority; due date; dependencies; survey crew.

Fictional worked example · 2025

Laggala Pallegama — cadastral backlog · Laggala Pallegama

Input or result	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
Open days past due	29	days
Calendar age	90	days

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Response time, aged cases, completion and reopened cases.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Schedule geodetic control inspection and restorationDEC-DP14-006 · Control network · Suggested priority: High

Try this decision

Schedule geodetic control inspection and restoration.

Validation required

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

Next step. Follow up overdue case. Authorize feasible repair through the proper work process, inspect further, or restrict unsafe use.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Other required evidence. Control point; stability; last check; observed error; access; maintenance need.

Fictional worked example · 2025

Laggala Pallegama — control network · Laggala Pallegama

Input or result	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
Open days past due	29	days
Calendar age	90	days

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Verified defect closure, service availability and repeat failures.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Validate transformations before combining spatial datasetsDEC-DP14-007 · Coordinate transformation · Suggested priority: High

Try this decision

Validate transformations before combining spatial datasets.

Validation required

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

Next step. Investigate reproduction difference. Accept reproducible evidence for review, investigate differences, or withhold an unsupported result.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Earlier/source value [m]; Independently reproduced value [m]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [m]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer

Other required evidence. Source datum; target datum; transformation; control points; residual error; tolerance.

Fictional worked example · 2025

Laggala Pallegama — coordinate transformation · Laggala Pallegama

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Independent reproduction within the approved tolerance.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Refer surveys failing approved accuracy specificationsDEC-DP14-008 · Survey accuracy · Suggested priority: High

Try this decision

Refer surveys failing approved accuracy specifications.

Validation required

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

Next step. Outside example comparison bounds. Refer a confirmed nonconformance for authorized response, resample, or investigate the method.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Parameter and applicable use; Measured result [m]; Example lower comparison bound [m]; Example upper comparison bound [m]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis

Other required evidence. Survey observations; closures; residuals; instrument calibration; approved accuracy class.

Fictional worked example · 2025

Laggala Pallegama — survey accuracy · Laggala Pallegama

Input or result	Value	Unit
Parameter and applicable use	Horizontal survey residual
Measured result	0.12	m
Example lower comparison bound	0	m
Example upper comparison bound	0.1	m
Original and limit unit	m
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
Measured value	0.12	m

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.

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Follow-up compliance, exposure/service condition and corrective closure.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Schedule aerial imagery for priority mapping gapsDEC-DP14-009 · Aerial acquisition · Suggested priority: Medium

Try this decision

Schedule aerial imagery for priority mapping gaps.

Validation required

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

Next step. Resolve overlapping resource bookings. Assign a feasible timetable, redistribute resources, or escalate the blocked dependency.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites

Other required evidence. Coverage area; resolution need; cloud season; permissions; platform; budget.

Fictional worked example · 2025

Laggala Pallegama — aerial acquisition · Laggala Pallegama

Input or result	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
Planned duration	3	days
Resource hours remaining	8	hours

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. On-time completion with verified outputs and resource use.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Support formal review of conflicting boundary evidenceDEC-DP14-010 · Boundary disputes · Suggested priority: High

Try this decision

Support formal review of conflicting boundary evidence.

Validation required

Method. 100 × distinct respondents / invited people. Record unresolved issues individually; one respondent may raise several issues.

Next step. Resolve participation barriers and issues. Address concerns, revise the proposal, seek required responses, or escalate unresolved conditions.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Distinct relevant people invited [people]; People who responded [people]; Unresolved issues [issues]; Proposal/version being discussed; Required participation channels accessible

Other required evidence. Parcel surveys; monument evidence; legal records; objections; survey editions.

Fictional worked example · 2025

Laggala Pallegama — boundary disputes · Laggala Pallegama

Input or result	Value	Unit
Distinct relevant people invited	95	people
People who responded	68	people
Unresolved issues	16	issues
Proposal/version being discussed	Sample proposal1
Required participation channels accessible	Unknown
Response share	71.579	%
Unresolved issues	16	issues

Response, attendance and silence are not consent. Participation does not transfer decision authority or settle rights.

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Resolved concerns, participation and compliance with recorded commitments.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Choose what to handle first: map sheets with significant feature changesDEC-DP14-011 · Topographic updates · Suggested priority: Medium

Try this decision

Prioritize map sheets with significant feature changes.

Validation required

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

Next step. Review evidence. Accept a genuine change for planning review, investigate a discontinuity, or defer comparison.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Earlier/source value [changed features]; Later/comparison value [changed features]

Other required evidence. Map sheets; dated imagery; change evidence; usage demand; survey capacity.

Fictional worked example · 2025

Laggala Pallegama — topographic updates · Laggala Pallegama

Input or result	Value	Unit
Earlier/source value	100	changed features
Later/comparison value	90	changed features
Difference	-10	changed features
Relative change	-10	%

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Comparable change after the chosen action and unresolved discrepancies.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Check required access and survey approvalsDEC-DP14-012 · Survey permissions · Suggested priority: High

Try this decision

Check required access and survey approvals.

Validation required

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

Next step. Complete the evidence. Grant only scoped authorized access, aggregate/redact, refuse, or request approval.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Survey purpose; Survey purpose evidence reference; property access; property access evidence reference; permissions; permissions evidence reference; restrictions; restrictions evidence reference; expiry; expiry evidence reference; authority; authority evidence reference

Other required evidence. Survey purpose; property access; permissions; restrictions; expiry; authority.

Fictional worked example · 2025

Laggala Pallegama — survey permissions · Laggala Pallegama

Input or result	Value	Unit
Survey purpose	Missing
Survey purpose evidence reference
property access	Documented
property access evidence reference	Sample Laggala Pallegama field register / 2025
permissions	Documented
permissions evidence reference	Sample Laggala Pallegama field register / 2025
restrictions	Documented
restrictions evidence reference	Sample Laggala Pallegama field register / 2025
expiry	Documented
expiry evidence reference	Sample Laggala Pallegama field register / 2025
authority	Documented
authority evidence reference	Sample Laggala Pallegama field register / 2025
Evidence gaps	1	items

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Permitted use, expiry compliance and investigated disclosure incidents.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Select elevation datasets fit for intended analysisDEC-DP14-013 · Elevation products · Suggested priority: Medium

Try this decision

Select elevation datasets fit for intended analysis.

Validation required

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

Next step. Complete the evidence. Accept a fit source for a defined use, restrict it, or request metadata/schema correction.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Resolution; Resolution evidence reference; vertical datum; vertical datum evidence reference; accuracy; accuracy evidence reference; acquisition date; acquisition date evidence reference; coverage; coverage evidence reference; intended scale; intended scale evidence reference

Other required evidence. Resolution; vertical datum; accuracy; acquisition date; coverage; intended scale.

Fictional worked example · 2025

Laggala Pallegama — elevation products · Laggala Pallegama

Input or result	Value	Unit
Resolution	Missing
Resolution evidence reference
vertical datum	Documented
vertical datum evidence reference	Sample Laggala Pallegama field register / 2025
accuracy	Documented
accuracy evidence reference	Sample Laggala Pallegama field register / 2025
acquisition date	Documented
acquisition date evidence reference	Sample Laggala Pallegama field register / 2025
coverage	Documented
coverage evidence reference	Sample Laggala Pallegama field register / 2025
intended scale	Documented
intended scale evidence reference	Sample Laggala Pallegama field register / 2025
Evidence gaps	1	items

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Resolved interoperability issues and current verified metadata.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Find areas needing authoritative boundary re-establishmentDEC-DP14-014 · Encroachment surveys · Suggested priority: High

Try this decision

Identify areas needing authoritative boundary re-establishment.

Validation required

Method. 100 × union of constraint overlap / proposal footprint. Count intersecting constraint areas once.

Next step. Review evidence. Refer affected sites for technical/legal review, revise the footprint, or request a field survey.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Proposal footprint [ha]; Union of overlapping constraint areas [ha]; Boundary edition; Constraint definition

Other required evidence. Legal boundary; occupation geometry; monuments; uncertainty; request reference.

Fictional worked example · 2025

Laggala Pallegama — encroachment surveys · Laggala Pallegama

Input or result	Value	Unit
Proposal footprint	75	ha
Union of overlapping constraint areas	18	ha
Boundary edition	Sample boundary1
Constraint definition	Sample constraint class
Overlap share	24	%
Overlapping area	18	ha

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.

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Resolved constraints and independently checked site conditions.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Balance crew instrument and travel requirementsDEC-DP14-015 · Survey resources · Suggested priority: Medium

Try this decision

Balance crew instrument and travel requirements.

Validation required

Method. Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand.

Next step. Review capacity shortfall. Redistribute usable resources, propose expansion, or manage demand within authorized limits.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Demand in the selected period [crew days]; Rated capacity for that period [crew days]; Unavailable or restricted capacity [crew days]

Other required evidence. Survey workload; skills; equipment; travel hours; available crew days.

Fictional worked example · 2025

Laggala Pallegama — survey resources · Laggala Pallegama

Input or result	Value	Unit
Demand in the selected period	150	crew days
Rated capacity for that period	180	crew days
Unavailable or restricted capacity	45	crew days
Usable capacity minus demand	-15	crew days
Usable capacity	135	crew days

Match peak/average basis, time window, skill, staffing, accessibility and other binding constraints. One aggregate capacity does not override a safety constraint.

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Actual usable capacity, unmet demand and service quality.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Track survey products through independent checkingDEC-DP14-016 · Map delivery · Suggested priority: Medium

Try this decision

Track survey products through independent checking.

Validation required

Method. 100 × verified completed members / original unique cohort. Keep unknown follow-up separate; stages are nested, not independent populations.

Next step. Review evidence. Address stage bottlenecks, follow up dropouts, or revise service delivery.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Unique original cohort entrants [cases]; Entrants reviewed [cases]; Entrants with verified completion [cases]; Entrants with unknown follow-up [cases]

Other required evidence. Request cohort; field completion; computation; checking; approval; delivery dates.

Fictional worked example · 2025

Laggala Pallegama — map delivery · Laggala Pallegama

Input or result	Value	Unit
Unique original cohort entrants	180	cases
Entrants reviewed	132	cases
Entrants with verified completion	96	cases
Entrants with unknown follow-up	12	cases
Verified completion share	53.333	%
Not verified complete	84	cases

Attendance, receipt, adoption, delivered service and outcomes are distinct stages. Repeated visits must not become new people.

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Verified progression, waiting times and outcomes for the same cohort.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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. Resolve inconsistent parcel identifiers across institutionsDEC-DP14-017 · Land information · Suggested priority: High

Try this decision

Resolve inconsistent parcel identifiers across institutions.

Validation required

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

Next step. Complete the evidence. Approve a documented mapping, keep it Draft, or create a governed concept after review.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Cadastral ID; Cadastral ID evidence reference; land-register ID; land-register ID evidence reference; geometry; geometry evidence reference; legal evidence; legal evidence evidence reference; source owner; source owner evidence reference

Other required evidence. Cadastral ID; land-register ID; geometry; legal evidence; source owner.

Fictional worked example · 2025

Laggala Pallegama — land information · Laggala Pallegama

Input or result	Value	Unit
Cadastral ID	Missing
Cadastral ID evidence reference
land-register ID	Documented
land-register ID evidence reference	Sample Laggala Pallegama field register / 2025
geometry	Documented
geometry evidence reference	Sample Laggala Pallegama field register / 2025
legal evidence	Documented
legal evidence evidence reference	Sample Laggala Pallegama field register / 2025
source owner	Documented
source owner evidence reference	Sample Laggala Pallegama field register / 2025
Evidence gaps	1	items

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Unmapped/conflicting concepts and history preserved across revisions.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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?

18. Compare costs for equivalent survey work typesDEC-DP14-018 · Survey cost · Suggested priority: Medium

Try this decision

Compare costs for equivalent survey work types.

Validation required

Method. Sum non-overlapping costs, then divide by the matching verified quantity for the same currency and accounting period.

Next step. Review evidence. Investigate cost drivers, compare suppliers/practices, or revise the budget proposal.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Labour cost [LKR]; Material/input cost [LKR]; Other non-overlapping cost [LKR]; Verified output or service quantity [survey units]; Equivalent survey work/terrain class

Other required evidence. Crew cost; travel; instrument cost; surveyed units; terrain class; period.

Fictional worked example · 2025

Laggala Pallegama — survey cost · Laggala Pallegama

Input or result	Value	Unit
Labour cost	180,000	LKR
Material/input cost	255,000	LKR
Other non-overlapping cost	62,000	LKR
Verified output or service quantity	5.4	survey units
Equivalent survey work/terrain class	Sample comparable survey class
Cost per matching unit	92,037.037	LKR/survey unit
Total cost	497,000	LKR

An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable.

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Actual comparable unit cost and service/output quality.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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?

19. Clear delayed requests for permitted map productsDEC-DP14-019 · Map distribution · Suggested priority: Lower

Try this decision

Clear delayed requests for permitted map products.

Validation required

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

Next step. Follow up overdue case. Assign the next permitted case, escalate an overdue case, request evidence, or close with proof.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Other required evidence. Request; product edition; payment or exemption evidence; rights; due date.

Fictional worked example · 2025

Laggala Pallegama — map distribution · Laggala Pallegama

Input or result	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
Open days past due	29	days
Calendar age	90	days

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

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Response time, aged cases, completion and reopened cases.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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?

20. Retain superseded survey editions with traceable revisionsDEC-DP14-020 · Historical integrity · Suggested priority: High

Try this decision

Retain superseded survey editions with traceable revisions.

Validation required

Next step. Investigate reproduction difference. Accept reproducible evidence for review, investigate differences, or withhold an unsupported result.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Earlier/source value [features]; Independently reproduced value [features]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [features]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer

Other required evidence. Survey edition; predecessor; amendment reason; approval; geometry hash; effective date.

Fictional worked example · 2025

Laggala Pallegama — historical integrity · Laggala Pallegama

Input or result	Value	Unit
Earlier/source value	100	features
Independently reproduced value	90	features
Original measurement unit	Sample matching unit
Comparison measurement unit	Sample matching unit
Compared measure and definition	Sample comparable features measure; same input scope
Documented absolute comparison tolerance	0	features
Expected input/method version	Sample input1 /method1
Reproduced input/method version	Sample input1 /method1
Original result creator	Preparation officer
Independent reproducer	Independent checking officer
Difference	-10	features
Relative change	-10	%

Proposed checking role. Authorized survey professional and geospatial quality reviewer.

After the action. Independent reproduction within the approved tolerance.

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.

Institution and data context

Survey Department responsibilities — Government publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

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.

Country Boundary · Geospatial Evidence

Existing form reference: 8731a23fc188dcb7

Field	Unit	Required
Country_Name	Confirm if needed	No
ISO Alpha 2 Code	Confirm if needed	No
ISO Alpha 3 Code	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Forest Boundary · Administrative & Planning Areas

Existing form reference: 4e74cc389edc2305

Field	Unit	Required
Forest Type	Confirm if needed	No
Forest Name	Confirm if needed	No
Range	Confirm if needed	No
Beat	Confirm if needed	No
Division	Confirm if needed	No
FA Division	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
Area Final	Confirm if needed	No
District	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Gram Niladhari Divisions · Administrative & Planning Areas

Existing form reference: 6ffaab5927d760f2

Field	Unit	Required
GND Name	Confirm if needed	No
GND Code	Confirm if needed	No
GND Number	Confirm if needed	No
GND Name Gazetted	Confirm if needed	No
DS Division Name	Confirm if needed	No
DS Division Code	Confirm if needed	No
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
MC UC PC Name	Confirm if needed	No
GND Officer Name	Confirm if needed	No
Dispute	Confirm if needed	No
Province Census Code	Confirm if needed	No
District Census Code	Confirm if needed	No
DS Division Census Code	Confirm if needed	No
GND Census Code	Confirm if needed	No
GND No Census	Confirm if needed	No
GND Name Census	Confirm if needed	No
Admin Code	Confirm if needed	No
CM Index	Confirm if needed	No
GND Number Gazetted	Confirm if needed	No
Year Created	Confirm if needed	No
Data Source	Confirm if needed	No
Method Of Creation	Confirm if needed	No
Extent	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Divisional Secretariat Boundary · Administrative & Planning Areas

Existing form reference: 38b3db2354e6f075

Field	Unit	Required
DS Division Name	Confirm if needed	No
DS Division Code	Confirm if needed	No
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
Adjusted Area	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

District Boundary · Administrative & Planning Areas

Existing form reference: 3e275a626091b924

Field	Unit	Required
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
Adjusted Area	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Province Boundary · Administrative & Planning Areas

Existing form reference: c2c98ee086137a9b

Field	Unit	Required
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
ISO Alpha 2 Code	Confirm if needed	No
Area True	Confirm if needed	No
Area Adjust	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Political · Administrative & Planning Areas

Existing form reference: b4321ffd8103c957

Field	Unit	Required

Planning Areas · Administrative & Planning Areas

Existing form reference: a216ede898036945

Field	Unit	Required

Statistical Areas · Administrative & Planning Areas

Existing form reference: b9addcdb23f83f55

Field	Unit	Required

Sensitive Areas · Administrative & Planning Areas

Existing form reference: 10fbe912859cef22

Field	Unit	Required
Area_Sq_KM	Confirm if needed	No
Area_New	Confirm if needed	No
DSD_Name	Confirm if needed	No
District_Name	Confirm if needed	No
Province_Name	Confirm if needed	No
ID	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Contours · Geospatial Evidence

Existing form reference: 93cc638735e23c72

Field	Unit	Required
Contour Type	Confirm if needed	No
Elevation	Confirm if needed	No
Creation Method	Confirm if needed	No
Year of Creation	Confirm if needed	No
Revision Method	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
st_length(shape)	Confirm if needed	No

SpotHeights · Geospatial Evidence

Existing form reference: 568cf4c5db707e09

Field	Unit	Required
Elevation_Meters	Confirm if needed	No
Creation_Method	Confirm if needed	No
Year_of_Creation	Confirm if needed	No
Description	Confirm if needed	No

Elevation Regime · Geospatial Evidence

Existing form reference: 5a55e896f86c8187

Field	Unit	Required
Contour	Confirm if needed	No
Elevation_Zone	Confirm if needed	No
Zone	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Place Name · Geospatial Evidence

Existing form reference: 66e6c6001ba803cc

Field	Unit	Required
Toponym Type	Confirm if needed	No
Toponym_Name	Confirm if needed	No
Creation_Method	Confirm if needed	No
Year_of_Creation	Confirm if needed	No
Revision_Method	Confirm if needed	No
Year_of_Revision	Confirm if needed	No
GFCODE	Confirm if needed	No

Post Office · Geospatial Evidence

Existing form reference: eb28b45421d1d6fd

Field	Unit	Required
Post Office Type	Confirm if needed	No
Name	Confirm if needed	No
Creation Method	Confirm if needed	No
Year of Creation	Confirm if needed	No
Revision Method	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
Building_ID	Confirm if needed	No

DEM_1m_Point_Cloud · Geospatial Evidence

Existing form reference: 0270f612b0cbab4a

Field	Unit	Required
point_x	Confirm if needed	No
point_y	Confirm if needed	No
point_z	Confirm if needed	No

Building_polygon_10k · Geospatial Evidence

Existing form reference: 806833baabf4f714

Field	Unit	Required
building_type	Confirm if needed	No
name	Confirm if needed	No
height	Confirm if needed	No
cid	Confirm if needed	No
frequency	Confirm if needed	No
mean_z	Confirm if needed	No
creation_method	Confirm if needed	No
year_of_creation	Confirm if needed	No
gfcode	Confirm if needed	No
building_id	Confirm if needed	No
revision_method	Confirm if needed	No
year_of_revision	Confirm if needed	No
description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Grama_Niladhari_Division_10K · Geospatial Evidence

Existing form reference: 426e426930d92ec8

Field	Unit	Required
GND Name	Confirm if needed	No
GND Code	Confirm if needed	No
GND Number	Confirm if needed	No
GND Name Gazetted	Confirm if needed	No
DS Division Name	Confirm if needed	No
DS Division Code	Confirm if needed	No
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
MC UC PC Name	Confirm if needed	No
GND Officer Name	Confirm if needed	No
Dispute	Confirm if needed	No
Province Census Code	Confirm if needed	No
District Census Code	Confirm if needed	No
DS Division Census Code	Confirm if needed	No
GND Census Code	Confirm if needed	No
GND No Census	Confirm if needed	No
GND Name Census	Confirm if needed	No
Admin Code	Confirm if needed	No
CM Index	Confirm if needed	No
GND Number Gazetted	Confirm if needed	No
Year Created	Confirm if needed	No
Data Source	Confirm if needed	No
Method Of Creation	Confirm if needed	No
Extent	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Divisional_Secretariat_10K · Geospatial Evidence

Existing form reference: 6571f8cc88a68adb

Field	Unit	Required
DS Division Name	Confirm if needed	No
DS Division Code	Confirm if needed	No
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
Adjusted Area	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

District_Boundary_10K · Geospatial Evidence

Existing form reference: 3ce83bfecf52a582

Field	Unit	Required
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
Adjusted Area	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Province_Boundary_10K · Geospatial Evidence

Existing form reference: 720aef694503f77e

Field	Unit	Required
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
ISO Alpha 2 Code	Confirm if needed	No
Area True	Confirm if needed	No
Area Adjust	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

TR_Transport_Pt · Geospatial Evidence

Existing form reference: 2dc5dd54789f82bb

Field	Unit	Required
Type of Transport point	Confirm if needed	No
Subtype of Transport pit	Confirm if needed	No
Name	Confirm if needed	No
Method of creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Transport point ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No

TE_Terrain_Pt · Geospatial Evidence

Existing form reference: 689f43051866dc70

Field	Unit	Required
Elevation	Confirm if needed	No
Year of creation	Confirm if needed	No
Type of Terrain Point	Confirm if needed	No
GFCODE	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
Year of Creation Source	Confirm if needed	No

HY_Hydro_Pt · Geospatial Evidence

Existing form reference: 13f33e0f07b724b6

Field	Unit	Required
Type of Hydro point	Confirm if needed	No
Subtype of Hydro point	Confirm if needed	No
Name	Confirm if needed	No
Method of creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Hydro point ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No

CO_Building_Pt · Geospatial Evidence

Existing form reference: def7cb4f5387db97

Field	Unit	Required
GFCODE	Confirm if needed	No
Building Category	Confirm if needed	No
Building Name	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
Building ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No

CA_Toponym_Pt · Geospatial Evidence

Existing form reference: 08f6677965be7c42

Field	Unit	Required
Type of Toponym	Confirm if needed	No
Name	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No

TE_Terrain_Li · Geospatial Evidence

Existing form reference: 64ee7dfa3baa634e

Field	Unit	Required
Type of Terrain line	Confirm if needed	No
Elevation	Confirm if needed	No
Year of Creation	Confirm if needed	No
TL_Cd_GFCODE	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
st_length(shape)	Confirm if needed	No

TR_Transport_Li · Geospatial Evidence

Existing form reference: 2c67d1c1e47ead9e

Field	Unit	Required
Type of Transport line	Confirm if needed	No
Name	Confirm if needed	No
Additional info	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Transport line ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Nmae	Confirm if needed	No
st_length(shape)	Confirm if needed	No

HY_Hydro_Li · Geospatial Evidence

Existing form reference: 46186cf703c41f7f

Field	Unit	Required
Type of Hydro line	Confirm if needed	No
Subtype of Hydro line	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Hydro line ID	Confirm if needed	No
Name of Hydro Line	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No
st_length(shape)	Confirm if needed	No

CA_Grid_Li · Geospatial Evidence

Existing form reference: be817df34fd152ae

Field	Unit	Required
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
st_length(shape)	Confirm if needed	No

LU_Landuse_Pg · Geospatial Evidence

Existing form reference: e119f4245d3aec14

Field	Unit	Required
Landuse Classif 1	Confirm if needed	No
Landuse Classif 2	Confirm if needed	No
Method of creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
LU_Cd_GFCODE	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
Name	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

HY_Hydro_Pg · Geospatial Evidence

Existing form reference: a51bbdb82cc71cfa

Field	Unit	Required
Type of Hydro area	Confirm if needed	No
Name	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Hydro area ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

CA_Tile_Pg · Geospatial Evidence

Existing form reference: ce9ea4c4673574d0

Field	Unit	Required
Tile code	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Provinces · Administrative & Planning Areas

Existing form reference: 34b688f04ba12422

Field	Unit	Required
id	Confirm if needed	No
name	Confirm if needed	No
code	Confirm if needed	No

Districts · Administrative & Planning Areas

Existing form reference: f25025b360be4121

Field	Unit	Required
id	Confirm if needed	No
name	Confirm if needed	No
code	Confirm if needed	No
province DTO / id	Confirm if needed	No
province DTO / name	Confirm if needed	No
province DTO / code	Confirm if needed	No

Ds divisions · Administrative & Planning Areas

Existing form reference: b89e70ac83fb5930

Field	Unit	Required
id	Confirm if needed	No
code	Confirm if needed	No
name	Confirm if needed	No
district DTO / id	Confirm if needed	No
district DTO / name	Confirm if needed	No
district DTO / code	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No

Gn divisions · Administrative & Planning Areas

Existing form reference: 8f42b4909736031c

Field	Unit	Required
id	Confirm if needed	No
name	Confirm if needed	No
code	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
land Area	Confirm if needed	No
agricultural Land Area	Confirm if needed	No
non Agricultural Land Area	Confirm if needed	No
crop Area	Confirm if needed	No
agro Ecological Zone DTO / id	Confirm if needed	No
agro Ecological Zone DTO / ae Zone Id	Confirm if needed	No
agro Ecological Zone DTO / name	Confirm if needed	No
agro Ecological Zone DTO / average Rainfall	Confirm if needed	No
ai Regions DTO / id	Confirm if needed	No
ai Regions DTO / region Id	Confirm if needed	No
ai Regions DTO / description	Confirm if needed	No
ai Regions DTO / asc Region Id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / province Segment Id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / description	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / provincial Dd Id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / description	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / pro Director Id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / description	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / city	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / latitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / longitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / city	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / latitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / longitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / city	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / latitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / longitude	Confirm if needed	No
ds Division DTO / id	Confirm if needed	No
ds Division DTO / code	Confirm if needed	No
ds Division DTO / name	Confirm if needed	No
ds Division DTO / district DTO / id	Confirm if needed	No
ds Division DTO / district DTO / name	Confirm if needed	No
ds Division DTO / district DTO / code	Confirm if needed	No
ds Division DTO / district DTO / province DTO / id	Confirm if needed	No
ds Division DTO / district DTO / province DTO / name	Confirm if needed	No
ds Division DTO / district DTO / province DTO / code	Confirm if needed	No
arpa DTO / id	Confirm if needed	No
arpa DTO / arpa Id	Confirm if needed	No
arpa DTO / name	Confirm if needed	No
arpa DTO / asc Dto / id	Confirm if needed	No
arpa DTO / asc Dto / asc Id	Confirm if needed	No
arpa DTO / asc Dto / name	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / id	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / district Comm Id	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / name	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / do Agrarian Development DTO	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / created Date	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / modified Date	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / city	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / latitude	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / longitude	Confirm if needed	No
arpa DTO / asc Dto / created Date	Confirm if needed	No
arpa DTO / asc Dto / modified Date	Confirm if needed	No
arpa DTO / asc Dto / city	Confirm if needed	No
arpa DTO / asc Dto / latitude	Confirm if needed	No
arpa DTO / asc Dto / longitude	Confirm if needed	No
arpa DTO / created Date	Confirm if needed	No
arpa DTO / modified Date	Confirm if needed	No
arpa DTO / city	Confirm if needed	No
arpa DTO / latitude	Confirm if needed	No
arpa DTO / longitude	Confirm if needed	No
gn Division Type	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / segment Id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / description	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / dd Id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / description	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / doa Id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / description	Confirm if needed	No
mahaweli Unit DTO / id	Confirm if needed	No
mahaweli Unit DTO / unit Id	Confirm if needed	No
mahaweli Unit DTO / description	Confirm if needed	No
ds Division DTO / district DTO / province DTO / created Date	Confirm if needed	No
ds Division DTO / district DTO / province DTO / modified Date	Confirm if needed	No
scs Sub Region Id	Confirm if needed	No
scs Sub Region Dto / id	Confirm if needed	No
scs Sub Region Dto / code	Confirm if needed	No
scs Sub Region Dto / description	Confirm if needed	No
scs Sub Region Dto / scs Region	Confirm if needed	No

Provincial director divisions · Administrative & Planning Areas

Existing form reference: 2337b92f31770ba9

Field	Unit	Required
id	Confirm if needed	No
pro Director Id	Confirm if needed	No
description	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Provincial deputy director level · Administrative & Planning Areas

Existing form reference: ca12c4d677b5003c

Field	Unit	Required
id	Confirm if needed	No
provincial Dd Id	Confirm if needed	No
description	Confirm if needed	No
pro Director Level DTO / id	Confirm if needed	No
pro Director Level DTO / pro Director Id	Confirm if needed	No
pro Director Level DTO / description	Confirm if needed	No
pro Director Level DTO / city	Confirm if needed	No
pro Director Level DTO / latitude	Confirm if needed	No
pro Director Level DTO / longitude	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Doa divisions · Administrative & Planning Areas

Existing form reference: eb2b3109790a85b0

Field	Unit	Required
id	Confirm if needed	No
doa Id	Confirm if needed	No
description	Confirm if needed	No

Inter-provincial ada divisions · Administrative & Planning Areas

Existing form reference: 3c4b7ca01eae2c96

Field	Unit	Required
id	Confirm if needed	No
segment Id	Confirm if needed	No
description	Confirm if needed	No
inter Province Deputy Director Level DTO / id	Confirm if needed	No
inter Province Deputy Director Level DTO / dd Id	Confirm if needed	No
inter Province Deputy Director Level DTO / description	Confirm if needed	No

Mahaweli authorities · Administrative & Planning Areas

Existing form reference: a928ea0c164539db

Field	Unit	Required
id	Confirm if needed	No
authority Id	Confirm if needed	No
description	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Mahaweli systems · Administrative & Planning Areas

Existing form reference: 8e71c080613ac3a4

Field	Unit	Required
id	Confirm if needed	No
system Id	Confirm if needed	No
description	Confirm if needed	No
mahaweli Authority DTO / id	Confirm if needed	No
mahaweli Authority DTO / authority Id	Confirm if needed	No
mahaweli Authority DTO / description	Confirm if needed	No
mahaweli Authority DTO / city	Confirm if needed	No
mahaweli Authority DTO / latitude	Confirm if needed	No
mahaweli Authority DTO / longitude	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Mahaweli blocks · Administrative & Planning Areas

Existing form reference: 1b6608ff1b096b55

Field	Unit	Required
id	Confirm if needed	No
code	Confirm if needed	No
mahaweli System DTO / id	Confirm if needed	No
mahaweli System DTO / system Id	Confirm if needed	No
mahaweli System DTO / description	Confirm if needed	No
mahaweli System DTO / mahaweli Authority DTO	Confirm if needed	No
mahaweli System DTO / city	Confirm if needed	No
mahaweli System DTO / latitude	Confirm if needed	No
mahaweli System DTO / longitude	Confirm if needed	No
description	Confirm if needed	No
land Area	Confirm if needed	No
cultivated Area	Confirm if needed	No
irrigated Area	Confirm if needed	No
non Irrigated Area	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
district DTO / id	Confirm if needed	No
district DTO / name	Confirm if needed	No
district DTO / code	Confirm if needed	No
ds Division DTO / id	Confirm if needed	No
ds Division DTO / code	Confirm if needed	No
ds Division DTO / name	Confirm if needed	No
ds Division DTO / created Date	Confirm if needed	No
ds Division DTO / modified Date	Confirm if needed	No

Mahaweli units · Administrative & Planning Areas

Existing form reference: b2dbe12695570d5c

Field	Unit	Required
id	Confirm if needed	No
unit Id	Confirm if needed	No
description	Confirm if needed	No
mahaweli Block DTO / id	Confirm if needed	No
mahaweli Block DTO / description	Confirm if needed	No
mahaweli Block DTO / land Area	Confirm if needed	No
mahaweli Block DTO / cultivated Area	Confirm if needed	No
mahaweli Block DTO / irrigated Area	Confirm if needed	No
mahaweli Block DTO / non Irrigated Area	Confirm if needed	No

Agrarian development divisions · Administrative & Planning Areas

Existing form reference: fc991a6c3bc249f6

Field	Unit	Required
id	Confirm if needed	No
do Agrarian Development Id	Confirm if needed	No
name	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

District commissioner divisions · Administrative & Planning Areas

Existing form reference: 57c890c642eab82c

Field	Unit	Required
id	Confirm if needed	No
district Comm Id	Confirm if needed	No
name	Confirm if needed	No
do Agrarian Development DTO / id	Confirm if needed	No
do Agrarian Development DTO / do Agrarian Development Id	Confirm if needed	No
do Agrarian Development DTO / name	Confirm if needed	No
do Agrarian Development DTO / created Date	Confirm if needed	No
do Agrarian Development DTO / modified Date	Confirm if needed	No
do Agrarian Development DTO / city	Confirm if needed	No
do Agrarian Development DTO / latitude	Confirm if needed	No
do Agrarian Development DTO / longitude	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Asc divisions · Administrative & Planning Areas

Existing form reference: 0bb5ed17e5cdc863

Field	Unit	Required
id	Confirm if needed	No
asc Id	Confirm if needed	No
name	Confirm if needed	No
district Commissioner Level DTO / id	Confirm if needed	No
district Commissioner Level DTO / district Comm Id	Confirm if needed	No
district Commissioner Level DTO / name	Confirm if needed	No
district Commissioner Level DTO / do Agrarian Development DTO	Confirm if needed	No
district Commissioner Level DTO / created Date	Confirm if needed	No
district Commissioner Level DTO / modified Date	Confirm if needed	No
district Commissioner Level DTO / city	Confirm if needed	No
district Commissioner Level DTO / latitude	Confirm if needed	No
district Commissioner Level DTO / longitude	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	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 Survey Department See the presentation example

Survey Department Documents and images prototype screen — Survey 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 Survey Department See the presentation example

Survey Department Data structure management prototype screen — Survey 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 Survey Department See the presentation example

Survey Department Users and access prototype screen — Survey 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.

Survey Department

1. Check a decision

2. Try the inputs

3. Check each decision

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

Fictional worked example · 2025

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?