National Spatial Data Infrastructure

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. Choose what to handle first: unavailable GIS services by user need 2. Request updates for outdated source metadata 3. Resolve conflicting classifications between publishers 4. Restrict products using withdrawn source permissions 5. Check institutional agreements before publishing a source 6. Reject unverified spatial-reference transformations 7. Choose what to handle first: gaps in fundamental geospatial datasets 8. Route invalid or inconsistent geometries for correction 9. Find GIS endpoints missing approved response targets 10. Review downstream effects of source schema revisions 11. Find products lacking traceable source versions 12. Consolidate duplicate catalogue references without copying data 13. Determine safe access and aggregation for restricted layers 14. Choose what to handle first: services failing documented exchange requirements 15. Assign source-feed failures to accountable custodians 16. Coordinate shared-layer refreshes with consumers 17. Improve discovery of poorly described geospatial resources 18. Check cross-agency joins before publishing combined analyses 19. Choose what to handle first: dataset requests using recorded service demand 20. Test recovery of essential catalogue and service metadata

1. Choose what to handle first: unavailable GIS services by user needDEC-DP15-001 · Published services · Suggested priority: High

Try this decision

Prioritize unavailable GIS services by user need.

Validation required

Method. Time availability =100 ×(scheduled−non-overlapping outage)/scheduled. Request success =100 ×(requests−failed)/requests. Response time is a separate measure.

Next step. Review evidence. Repair recurring faults, revise service capacity, or escalate dependencies.

Inputs, example and sources

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

Analysis inputs. Scheduled observation window [hours]; Union of qualifying outage intervals [hours]; Eligible service requests [requests]; Failed eligible requests [requests]; Measured response time [ms]

Other required evidence. Service ID; subject; access test; owner; intended users; required coverage.

Fictional worked example · 2025

Laggala Pallegama — published services · Laggala Pallegama

Input or result	Value	Unit
Scheduled observation window	168	hours
Union of qualifying outage intervals	13	hours
Eligible service requests	1,000	requests
Failed eligible requests	40	requests
Measured response time	800	ms
Time availability	92.262	%
Request success	96	%
Measured response time	800	ms

State maintenance exclusions, operating window, probe, workload and service objective. Observed response time is not a p95 claim unless the percentile is actually measured.

Proposed checking role. Geospatial custodian, metadata steward and access/security reviewer.

After the action. Verified availability, interruptions and actual service delivery.

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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Request updates for outdated source metadataDEC-DP15-002 · Metadata currency · Suggested priority: Medium

Try this decision

Request updates for outdated source metadata.

Validation required

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

Next step. Check overdue observation. Repair missed observations, contact the owner, or suspend stale evidence from current decisions.

Inputs, example and sources

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

Analysis inputs. Expected observations in the window [observations]; Distinct valid observations [observations]; Latest valid observation; Assessment date; Required observation interval [days]

Other required evidence. Dataset ID; metadata date; source update; expected cadence; custodian.

Fictional worked example · 2025

Laggala Pallegama — metadata currency · Laggala Pallegama

Input or result	Value	Unit
Expected observations in the window	30	observations
Distinct valid observations	24	observations
Latest valid observation	2025-06-28
Assessment date	2025-06-30
Required observation interval	1	days
Completeness	80	%
Age of latest observation	2	days
Missing observations	6	observations

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

Proposed checking role. Geospatial custodian, metadata steward and access/security reviewer.

After the action. Valid observations received on time and recurring gaps.

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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Resolve conflicting classifications between publishersDEC-DP15-003 · Semantic conflicts · Suggested priority: High

Try this decision

Resolve conflicting classifications between publishers.

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. Source class; Source class evidence reference; definition; definition evidence reference; units; units evidence reference; reference vocabulary; reference vocabulary evidence reference; mapping evidence; mapping evidence evidence reference; steward; steward evidence reference

Other required evidence. Source class; definition; units; reference vocabulary; mapping evidence; steward.

Fictional worked example · 2025

Laggala Pallegama — semantic conflicts · Laggala Pallegama

Input or result	Value	Unit
Source class	Missing
Source class evidence reference
definition	Documented
definition evidence reference	Sample Laggala Pallegama field register / 2025
units	Documented
units evidence reference	Sample Laggala Pallegama field register / 2025
reference vocabulary	Documented
reference vocabulary evidence reference	Sample Laggala Pallegama field register / 2025
mapping evidence	Documented
mapping evidence evidence reference	Sample Laggala Pallegama field register / 2025
steward	Documented
steward 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Restrict products using withdrawn source permissionsDEC-DP15-004 · Withdrawn rights · Suggested priority: High

Try this decision

Restrict products using withdrawn source permissions.

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. Source license; Source license evidence reference; derivative lineage; derivative lineage evidence reference; withdrawal date; withdrawal date evidence reference; audience; audience evidence reference; cached product IDs; cached product IDs evidence reference

Other required evidence. Source license; derivative lineage; withdrawal date; audience; cached product IDs.

Fictional worked example · 2025

Laggala Pallegama — withdrawn rights · Laggala Pallegama

Input or result	Value	Unit
Source license	Missing
Source license evidence reference
derivative lineage	Documented
derivative lineage evidence reference	Sample Laggala Pallegama field register / 2025
withdrawal date	Documented
withdrawal date evidence reference	Sample Laggala Pallegama field register / 2025
audience	Documented
audience evidence reference	Sample Laggala Pallegama field register / 2025
cached product IDs	Documented
cached product IDs 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Check institutional agreements before publishing a sourceDEC-DP15-005 · Service onboarding · Suggested priority: High

Try this decision

Check institutional agreements before publishing a source.

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. Provider identity; Provider identity evidence reference; exchange agreement; exchange agreement evidence reference; permission scope; permission scope evidence reference; classification; classification evidence reference; effective dates; effective dates evidence reference

Other required evidence. Provider identity; exchange agreement; permission scope; classification; effective dates.

Fictional worked example · 2025

Laggala Pallegama — service onboarding · Laggala Pallegama

Input or result	Value	Unit
Provider identity	Missing
Provider identity evidence reference
exchange agreement	Documented
exchange agreement evidence reference	Sample Laggala Pallegama field register / 2025
permission scope	Documented
permission scope evidence reference	Sample Laggala Pallegama field register / 2025
classification	Documented
classification evidence reference	Sample Laggala Pallegama field register / 2025
effective dates	Documented
effective dates 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Reject unverified spatial-reference transformationsDEC-DP15-006 · Coordinate standards · Suggested priority: High

Try this decision

Reject unverified spatial-reference transformations.

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. Coordinate reference; datum; transform parameters; control checks; accuracy.

Fictional worked example · 2025

Laggala Pallegama — coordinate standards · 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Choose what to handle first: gaps in fundamental geospatial datasetsDEC-DP15-007 · National coverage · Suggested priority: Medium

Try this decision

Prioritize gaps in fundamental geospatial datasets.

Validation required

Method. 100 × distinct covered eligible units / eligible frame. Known uncovered = frame − covered − unknown.

Next step. Review evidence. Select eligible underserved units for outreach, investigate missing coverage, or revise the verified frame.

Inputs, example and sources

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

Analysis inputs. Required eligible frame [theme-area pairs]; Distinct members of that frame covered [theme-area pairs]; Frame members with unknown coverage [theme-area pairs]

Other required evidence. Required themes; geographic units; available layers; source dates; quality.

Fictional worked example · 2025

Laggala Pallegama — national coverage · Laggala Pallegama

Input or result	Value	Unit
Required eligible frame	100	theme-area pairs
Distinct members of that frame covered	65	theme-area pairs
Frame members with unknown coverage	5	theme-area pairs
Verified coverage	65	%
Known uncovered	30	theme-area pairs
Unknown coverage	5	theme-area pairs

Count each eligible unit once for the selected service and period. Received messages, attendance, adoption and outcomes are separate measures.

Proposed checking role. Geospatial custodian, metadata steward and access/security reviewer.

After the action. Verified eligible units receiving service and remaining unmet need.

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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Route invalid or inconsistent geometries for correctionDEC-DP15-008 · Geometry quality · Suggested priority: High

Try this decision

Route invalid or inconsistent geometries for correction.

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; geometry validity; geometry validity evidence reference; topology rule; topology rule evidence reference; duplicates; duplicates evidence reference; source edition; source edition evidence reference

Other required evidence. Feature ID; geometry validity; topology rule; duplicates; source edition.

Fictional worked example · 2025

Laggala Pallegama — geometry quality · Laggala Pallegama

Input or result	Value	Unit
Feature ID	Missing
Feature ID evidence reference
geometry validity	Documented
geometry validity evidence reference	Sample Laggala Pallegama field register / 2025
topology rule	Documented
topology rule evidence reference	Sample Laggala Pallegama field register / 2025
duplicates	Documented
duplicates evidence reference	Sample Laggala Pallegama field register / 2025
source edition	Documented
source edition 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Find GIS endpoints missing approved response targetsDEC-DP15-009 · Service performance · Suggested priority: Medium

Try this decision

Identify GIS endpoints missing approved response targets.

Validation required

Method. Time availability =100 ×(scheduled−non-overlapping outage)/scheduled. Request success =100 ×(requests−failed)/requests. Response time is a separate measure.

Next step. Review evidence. Repair recurring faults, revise service capacity, or escalate dependencies.

Inputs, example and sources

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

Other required evidence. Endpoint; response time; availability; failure rate; request size; service objective.

Fictional worked example · 2025

Laggala Pallegama — service performance · Laggala Pallegama

Input or result	Value	Unit
Scheduled observation window	168	hours
Union of qualifying outage intervals	13	hours
Eligible service requests	1,000	requests
Failed eligible requests	40	requests
Measured response time	800	ms
Time availability	92.262	%
Request success	96	%
Measured response time	800	ms

State maintenance exclusions, operating window, probe, workload and service objective. Observed response time is not a p95 claim unless the percentile is actually measured.

Proposed checking role. Geospatial custodian, metadata steward and access/security reviewer.

After the action. Verified availability, interruptions and actual service delivery.

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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Review downstream effects of source schema revisionsDEC-DP15-010 · Schema changes · Suggested priority: High

Try this decision

Review downstream effects of source schema revisions.

Validation required

Method. Compare original definitions, identifiers, units and versions against documented equivalence evidence. Preserve conflicts and unresolved mappings; do not subtract category labels or silently merge records.

Next step. Resolve source disagreement. 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 value/definition; Comparison source value/definition; Original version; Comparison version; Documented equivalence evidence

Other required evidence. Schema versions; changed fields; consumers; units; mappings; compatibility tests.

Fictional worked example · 2025

Laggala Pallegama — schema changes · Laggala Pallegama

Input or result	Value	Unit
Original source value/definition	Schema versions: primary register entry
Comparison source value/definition	Schema versions: conflicting source return
Original version	Sample version1
Comparison version	Sample version2
Documented equivalence evidence	Unresolved
Unresolved equivalence items	1	items

Proposed checking role. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Find products lacking traceable source versionsDEC-DP15-011 · Data lineage · Suggested priority: High

Try this decision

Identify products lacking traceable source versions.

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. Product ID; Product ID evidence reference; source IDs; source IDs evidence reference; transformations; transformations evidence reference; edition dates; edition dates evidence reference; permissions; permissions evidence reference; hashes; hashes evidence reference

Other required evidence. Product ID; source IDs; transformations; edition dates; permissions; hashes.

Fictional worked example · 2025

Laggala Pallegama — data lineage · Laggala Pallegama

Input or result	Value	Unit
Product ID	Missing
Product ID evidence reference
source IDs	Documented
source IDs evidence reference	Sample Laggala Pallegama field register / 2025
transformations	Documented
transformations evidence reference	Sample Laggala Pallegama field register / 2025
edition dates	Documented
edition dates evidence reference	Sample Laggala Pallegama field register / 2025
permissions	Documented
permissions evidence reference	Sample Laggala Pallegama field register / 2025
hashes	Documented
hashes 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Consolidate duplicate catalogue references without copying dataDEC-DP15-012 · Duplicate catalogues · Suggested priority: Medium

Try this decision

Consolidate duplicate catalogue references without copying data.

Validation required

Next step. Resolve source disagreement. 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 value/definition; Comparison source value/definition; Original version; Comparison version; Documented equivalence evidence

Other required evidence. Provider ID; canonical URL; dataset identifier; schema; version; equivalence evidence.

Fictional worked example · 2025

Laggala Pallegama — duplicate catalogues · Laggala Pallegama

Input or result	Value	Unit
Original source value/definition	Provider ID: primary register entry
Comparison source value/definition	Provider ID: conflicting source return
Original version	Sample version1
Comparison version	Sample version2
Documented equivalence evidence	Unresolved
Unresolved equivalence items	1	items

Proposed checking role. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Determine safe access and aggregation for restricted layersDEC-DP15-013 · Sensitive layers · Suggested priority: High

Try this decision

Determine safe access and aggregation for restricted layers.

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. Classification; Classification evidence reference; coordinates; coordinates evidence reference; intended purpose; intended purpose evidence reference; rights; rights evidence reference; approved aggregation; approved aggregation evidence reference; audience; audience evidence reference

Other required evidence. Classification; coordinates; intended purpose; rights; approved aggregation; audience.

Fictional worked example · 2025

Laggala Pallegama — sensitive layers · Laggala Pallegama

Input or result	Value	Unit
Classification	Missing
Classification evidence reference
coordinates	Documented
coordinates evidence reference	Sample Laggala Pallegama field register / 2025
intended purpose	Documented
intended purpose evidence reference	Sample Laggala Pallegama field register / 2025
rights	Documented
rights evidence reference	Sample Laggala Pallegama field register / 2025
approved aggregation	Documented
approved aggregation evidence reference	Sample Laggala Pallegama field register / 2025
audience	Documented
audience 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Choose what to handle first: services failing documented exchange requirementsDEC-DP15-014 · Interoperability · Suggested priority: Medium

Try this decision

Prioritize services failing documented exchange requirements.

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. Service specification; Service specification evidence reference; supported formats; supported formats evidence reference; metadata; metadata evidence reference; coordinate system; coordinate system evidence reference; sample requests; sample requests evidence reference

Other required evidence. Service specification; supported formats; metadata; coordinate system; sample requests.

Fictional worked example · 2025

Laggala Pallegama — interoperability · Laggala Pallegama

Input or result	Value	Unit
Service specification	Missing
Service specification evidence reference
supported formats	Documented
supported formats evidence reference	Sample Laggala Pallegama field register / 2025
metadata	Documented
metadata evidence reference	Sample Laggala Pallegama field register / 2025
coordinate system	Documented
coordinate system evidence reference	Sample Laggala Pallegama field register / 2025
sample requests	Documented
sample requests 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Assign source-feed failures to accountable custodiansDEC-DP15-015 · Incident response · Suggested priority: High

Try this decision

Assign source-feed failures to accountable custodians.

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. Incident; affected products; first failure; severity evidence; owner; due date.

Fictional worked example · 2025

Laggala Pallegama — incident response · 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Coordinate shared-layer refreshes with consumersDEC-DP15-016 · Update scheduling · Suggested priority: Medium

Try this decision

Coordinate shared-layer refreshes with consumers.

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. Source cadence; consumer dependency; maintenance window; edition; validation tasks.

Fictional worked example · 2025

Laggala Pallegama — update scheduling · 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Improve discovery of poorly described geospatial resourcesDEC-DP15-017 · Catalogue discovery · Suggested priority: Medium

Try this decision

Improve discovery of poorly described geospatial resources.

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. Dataset title; Dataset title evidence reference; keywords; keywords evidence reference; geography; geography evidence reference; period; period evidence reference; entity definition; entity definition evidence reference; source owner; source owner evidence reference

Other required evidence. Dataset title; keywords; geography; period; entity definition; source owner.

Fictional worked example · 2025

Laggala Pallegama — catalogue discovery · Laggala Pallegama

Input or result	Value	Unit
Dataset title	Missing
Dataset title evidence reference
keywords	Documented
keywords evidence reference	Sample Laggala Pallegama field register / 2025
geography	Documented
geography evidence reference	Sample Laggala Pallegama field register / 2025
period	Documented
period evidence reference	Sample Laggala Pallegama field register / 2025
entity definition	Documented
entity definition 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Check cross-agency joins before publishing combined analysesDEC-DP15-018 · Spatial joins · Suggested priority: High

Try this decision

Verify cross-agency joins before publishing combined analyses.

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 [matched records]; Independently reproduced value [matched records]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [matched records]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer

Other required evidence. Entity keys; boundary editions; spatial predicate; unmatched features; join cardinality.

Fictional worked example · 2025

Laggala Pallegama — spatial joins · Laggala Pallegama

Input or result	Value	Unit
Earlier/source value	100	matched records
Independently reproduced value	90	matched records
Original measurement unit	Sample matching unit
Comparison measurement unit	Sample matching unit
Compared measure and definition	Sample comparable matched records measure; same input scope
Documented absolute comparison tolerance	0.01	matched records
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	matched records
Relative change	-10	%

Proposed checking role. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Choose what to handle first: dataset requests using recorded service demandDEC-DP15-019 · Usage requests · Suggested priority: Lower

Try this decision

Prioritize dataset requests using recorded service demand.

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 ID; theme; geography; purpose; existing coverage; due date.

Fictional worked example · 2025

Laggala Pallegama — usage requests · 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. Geospatial custodian, metadata steward and access/security 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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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. Test recovery of essential catalogue and service metadataDEC-DP15-020 · Disaster resilience · Suggested priority: High

Try this decision

Test recovery of essential catalogue and service metadata.

Validation required

Method. Time availability =100 ×(scheduled−non-overlapping outage)/scheduled. Request success =100 ×(requests−failed)/requests. Response time is a separate measure.

Next step. Review evidence. Repair recurring faults, revise service capacity, or escalate dependencies.

Inputs, example and sources

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

Other required evidence. Recovery plan; backup version; dependency list; restore test; recovery targets.

Fictional worked example · 2025

Laggala Pallegama — disaster resilience · Laggala Pallegama

Input or result	Value	Unit
Scheduled observation window	168	hours
Union of qualifying outage intervals	13	hours
Eligible service requests	1,000	requests
Failed eligible requests	40	requests
Measured response time	800	ms
Time availability	92.262	%
Request success	96	%
Measured response time	800	ms

State maintenance exclusions, operating window, probe, workload and service objective. Observed response time is not a p95 claim unless the percentile is actually measured.

Proposed checking role. Geospatial custodian, metadata steward and access/security reviewer.

After the action. Verified availability, interruptions and actual service delivery.

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

Sri Lanka NSDI reference standards — Government publication. Reference standards page contains text about another jurisdiction; no local mandate inferred. Institutional context; does not establish the calculation or local approval.
Sri Lanka NSDI publication and access FAQ — 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

Protected Area Network · Protected Areas

Existing form reference: d5264d82f6a69e87

Field	Unit	Required
Name	Confirm if needed	No
Type	Confirm if needed	No
ID	Confirm if needed	No
ProCov ID	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No
nsdi.sde.Protected_Area_Network.area	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

Hydro Meteorological Stations · Rainfall & Weather

Existing form reference: 678a3e2dcda3b2df

Field	Unit	Required
Station Name	Confirm if needed	No
River Basin	Confirm if needed	No
Quadrant	Confirm if needed	No
X_Meter	Confirm if needed	No
Y_Meter	Confirm if needed	No
Description	Confirm if needed	No

Agro Meteorological Stations · Rainfall & Weather

Existing form reference: 4404e8d7fb7938f5

Field	Unit	Required
Station ID	Confirm if needed	No
Station Name	Confirm if needed	No
Station Code	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Year	Confirm if needed	No
Description	Confirm if needed	No
qualifier	Confirm if needed	No
elevation	Confirm if needed	No

Rainguage Stations · Rainfall & Weather

Existing form reference: 34f3d59c2619b006

Field	Unit	Required
Serial Number	Confirm if needed	No
Station Name	Confirm if needed	No
District	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Begin Date	Confirm if needed	No
End Date	Confirm if needed	No
Description	Confirm if needed	No
qualifier	Confirm if needed	No
elevation	Confirm if needed	No

Rainfall · Rainfall & Weather

Existing form reference: 1d5963784380e5d7

Field	Unit	Required
stationid	Confirm if needed	No
date	Confirm if needed	No
rainfall_mm	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Synoptic Stations · Rainfall & Weather

Existing form reference: c7953153a5200702

Field	Unit	Required
Serial Number	Confirm if needed	No
Station Name	Confirm if needed	No
District	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
Begin Date	Confirm if needed	No
End Date	Confirm if needed	No
Description	Confirm if needed	No
qualifier	Confirm if needed	No
elevation	Confirm if needed	No

Climate Zones · Rainfall & Weather

Existing form reference: 2fd8102b7732d899

Field	Unit	Required
Zone_Name	Confirm if needed	No
Climate_Classification	Confirm if needed	No
ID	Confirm if needed	No
AGCODE	Confirm if needed	No
AGNAME	Confirm if needed	No
area	Confirm if needed	No
Perimeter	Confirm if needed	No
Terrain	Confirm if needed	No
AGRO_Zone	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Hydro Zones · Rainfall & Weather

Existing form reference: 8645ce85db37fa03

Field	Unit	Required
Zone ID	Confirm if needed	No
Zone Area	Confirm if needed	No
Perimeter	Confirm if needed	No
Hydro_Type	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Man_Holes_CMC · Geospatial Evidence

Existing form reference: 453ce52ffb600951

Field	Unit	Required
objectid_1	Confirm if needed	No
manhole_number	Confirm if needed	No
temp	Confirm if needed	No
manhno	Confirm if needed	No
sheetno	Confirm if needed	No
shno_mn	Confirm if needed	No
x_cord	Confirm if needed	No
y_cord	Confirm if needed	No

Road_Line_CMC · Geospatial Evidence

Existing form reference: e52e30af0703a81f

Field	Unit	Required
objectid_1	Confirm if needed	No
name	Confirm if needed	No
road_class	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Storm_Water_Line_CMC · Geospatial Evidence

Existing form reference: d5eb573af52b4ba8

Field	Unit	Required
objectid_1	Confirm if needed	No
id	Confirm if needed	No
diameter	Confirm if needed	No
from_mh	Confirm if needed	No
to_mh	Confirm if needed	No
description	Confirm if needed	No
height	Confirm if needed	No
width	Confirm if needed	No
from_txt	Confirm if needed	No
to_txt	Confirm if needed	No
sheetno	Confirm if needed	No
frmshno	Confirm if needed	No
pipe_no	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Open_Canal_CMC · Geospatial Evidence

Existing form reference: c6769975e6d94d7b

Field	Unit	Required
objectid_1	Confirm if needed	No
id	Confirm if needed	No
diameter	Confirm if needed	No
from_mh	Confirm if needed	No
to_mh	Confirm if needed	No
description	Confirm if needed	No
height	Confirm if needed	No
width	Confirm if needed	No
from_txt	Confirm if needed	No
to_txt	Confirm if needed	No
sheetno	Confirm if needed	No
frmshno	Confirm if needed	No
pipe_no	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Buildings_CMC · Geospatial Evidence

Existing form reference: e95571bf19a8d065

Field	Unit	Required
main_use	Confirm if needed	No
name	Confirm if needed	No
remarks	Confirm if needed	No
pid	Confirm if needed	No
Number of Floors	Confirm if needed	No
Asst_Number	Confirm if needed	No
condition	Confirm if needed	No
status	Confirm if needed	No
Present_Use	Confirm if needed	No
ass_number	Confirm if needed	No
gnd_name	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Zoning_CMC · Geospatial Evidence

Existing form reference: 29746470c1dcbc7a

Field	Unit	Required
zone	Confirm if needed	No
area_hectare	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Wards_CMC · Geospatial Evidence

Existing form reference: 84980bd1fba7e33b

Field	Unit	Required
ward_number	Confirm if needed	No
ward_name	Confirm if needed	No
dsd_name	Confirm if needed	No
mc_uc_ps_n	Confirm if needed	No
area_hectare	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Landuse_CMC · Geospatial Evidence

Existing form reference: ca11775a213662d5

Field	Unit	Required
objectid_1	Confirm if needed	No
remarks	Confirm if needed	No
Discription	Confirm if needed	No
Description	Confirm if needed	No
Local_Authority	Confirm if needed	No
Area_Hectare	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

GND_CMC · Geospatial Evidence

Existing form reference: 61def4b8bdfd8f09

Field	Unit	Required
id	Confirm if needed	No
province_name	Confirm if needed	No
district_name	Confirm if needed	No
gnd_name	Confirm if needed	No
gnd_code	Confirm if needed	No
dsd_name	Confirm if needed	No
mc_uc_ps_n	Confirm if needed	No
area_hectare	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Industrial · Markets & Value Chains

Existing form reference: 31ff41442970d0e0

Field	Unit	Required

Hotels · Markets & Value Chains

Existing form reference: d198f461e85becd7

Field	Unit	Required
Hotel Category	Confirm if needed	No
Hotel Name	Confirm if needed	No
No of Floors	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
District	Confirm if needed	No
Registration Number	Confirm if needed	No
no of rooms	Confirm if needed	No

Restaurants · Markets & Value Chains

Existing form reference: ff202b3e019c4ef4

Field	Unit	Required
Name	Confirm if needed	No
Type	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
ID	Confirm if needed	No
Stars	Confirm if needed	No
link	Confirm if needed	No
Website	Confirm if needed	No
District	Confirm if needed	No
photo_link	Confirm if needed	No
Hotel_Star_Ratings	Confirm if needed	No
Popup_Desrciption	Confirm if needed	No
Tourism_Webiste_Link	Confirm if needed	No
orig_fid	Confirm if needed	No

ATM · Markets & Value Chains

Existing form reference: 6db8e3996852c92b

Field	Unit	Required
Bank Name	Confirm if needed	No
ATM ID	Confirm if needed	No
Total Machines	Confirm if needed	No
Description	Confirm if needed	No

Banks · Markets & Value Chains

Existing form reference: 1733ee0c541f66f6

Field	Unit	Required
Bank Name	Confirm if needed	No
Bank ID	Confirm if needed	No
Branch Name	Confirm if needed	No
Working Hours	Confirm if needed	No
Working Days	Confirm if needed	No
Description	Confirm if needed	No
GND Name	Confirm if needed	No

Shopping Malls · Markets & Value Chains

Existing form reference: 68c41f6a3ee5d73c

Field	Unit	Required
Name	Confirm if needed	No
Working Hours	Confirm if needed	No

Tourist Spots · Markets & Value Chains

Existing form reference: 398940daf9bc6220

Field	Unit	Required
Name	Confirm if needed	No
Type	Confirm if needed	No
Latitude	Confirm if needed	No
Longitude	Confirm if needed	No
ID	Confirm if needed	No
District	Confirm if needed	No
photo_link	Confirm if needed	No
Popup_Desrciption	Confirm if needed	No
Tourism_Webiste_Link	Confirm if needed	No

Protected Area · Geospatial Evidence

Existing form reference: 820f4db29f0a3679

Field	Unit	Required
Name	Confirm if needed	No
Type	Confirm if needed	No
ID	Confirm if needed	No
ProCov ID	Confirm if needed	No
area	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Educational Institutions · Geospatial Evidence

Existing form reference: 1b3ce68ebc0d514d

Field	Unit	Required
District	Confirm if needed	No
Province	Confirm if needed	No
Census No	Confirm if needed	No
School Name	Confirm if needed	No
School Level	Confirm if needed	No
School Type	Confirm if needed	No
Year Span	Confirm if needed	No
school_sex_report	Confirm if needed	No
available_medium	Confirm if needed	No
zone	Confirm if needed	No
edu_div	Confirm if needed	No
electorate	Confirm if needed	No
DS Division	Confirm if needed	No
GN Division	Confirm if needed	No

Police Stations · Geospatial Evidence

Existing form reference: 1b36a76cf2a59138

Field	Unit	Required
Station 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
GFCCODE	Confirm if needed	No
Description	Confirm if needed	No
Building_ID	Confirm if needed	No

Courts · Geospatial Evidence

Existing form reference: f9c1c6ebf0e515bd

Field	Unit	Required
Court 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

Archeological Sites · Geospatial Evidence

Existing form reference: c6f98934c2a69938

Field	Unit	Required
Site Name	Confirm if needed	No
Site Name Sinhali	Confirm if needed	No
Site Name Tamil	Confirm if needed	No
Site Name English	Confirm if needed	No
Type	Confirm if needed	No
Period	Confirm if needed	No
District	Confirm if needed	No
Code	Confirm if needed	No
Description	Confirm if needed	No
Photo Link	Confirm if needed	No

ArcheologicalSites_Buffer_Zone · Geospatial Evidence

Existing form reference: 846bf4fd0e48eeee

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

Vocational_Institute · Geospatial Evidence

Existing form reference: 9877ff8ee41fee8f

Field	Unit	Required
no	Confirm if needed	No
name_of_th	Confirm if needed	No
branch_nam	Confirm if needed	No
e___mail	Confirm if needed	No
longitudes	Confirm if needed	No
latitudes	Confirm if needed	No
no_of_cour	Confirm if needed	No
student_ca	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

Irrigation Offices · Land Suitability

Existing form reference: b5701ed646f0f063

Field	Unit	Required
name	Confirm if needed	No
category	Confirm if needed	No
district_n	Confirm if needed	No

AgroEcological Zones Point · Land Suitability

Existing form reference: cc316b77dd9398f9

Field	Unit	Required
fid_1	Confirm if needed	No
left	Confirm if needed	No
bottom	Confirm if needed	No
right	Confirm if needed	No
top	Confirm if needed	No
x	Confirm if needed	No
y	Confirm if needed	No
fid_2	Confirm if needed	No
join_count	Confirm if needed	No
target_fid	Confirm if needed	No
id	Confirm if needed	No
gridcode	Confirm if needed	No
final_id	Confirm if needed	No
zone	Confirm if needed	No
climatic_z	Confirm if needed	No
agro_eco_z	Confirm if needed	No
agro_eco_r	Confirm if needed	No
terrain	Confirm if needed	No
major_soil	Confirm if needed	No
land_use	Confirm if needed	No
anualrfmm	Confirm if needed	No

ASC Locations · Land Suitability

Existing form reference: a64b0a6754afd4ed

Field	Unit	Required
ASC Number	Confirm if needed	No
ASC Name	Confirm if needed	No
XCOORD	Confirm if needed	No
YCOORD	Confirm if needed	No
Location Code	Confirm if needed	No
Description	Confirm if needed	No

Agro Ecological Zones · Land Suitability

Existing form reference: 592c3b578787edcd

Field	Unit	Required
Zone	Confirm if needed	No
Climatic_Zone	Confirm if needed	No
Agro_Eco_Zone	Confirm if needed	No
Agro_Eco_R	Confirm if needed	No
Final_ID	Confirm if needed	No
Terrain	Confirm if needed	No
Major_Soil	Confirm if needed	No
Land_Use	Confirm if needed	No
AnualRFmm	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Irrigation Schemes · Land Suitability

Existing form reference: 648a6f28a711dfa9

Field	Unit	Required
System Name	Confirm if needed	No
Systems	Confirm if needed	No
ID	Confirm if needed	No
ID_Systems	Confirm if needed	No
MASL_System	Confirm if needed	No
DSD_Name	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Irrigation Lands · Land Suitability

Existing form reference: e877698582fc591c

Field	Unit	Required
Landuse Type	Confirm if needed	No
Landuse Classification (CropType)	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_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Crops Suitability · Land Suitability

Existing form reference: 54fb1fe96af4f04c

Field	Unit	Required
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
District Name	Confirm if needed	No
District Code	Confirm if needed	No
DS Division Name	Confirm if needed	No
DS Division Code	Confirm if needed	No
GND Name	Confirm if needed	No
GND Number	Confirm if needed	No
MC UC PS Name	Confirm if needed	No
MC UC PS Code	Confirm if needed	No
Polling Division Name	Confirm if needed	No
Polling Division Code	Confirm if needed	No
id	Confirm if needed	No
Area Hectare	Confirm if needed	No
ASC Name	Confirm if needed	No
Area Sq Km	Confirm if needed	No
Square Km	Confirm if needed	No
Crop Type	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Soil Groups Points · Soil & Land Management

Existing form reference: 41336eee89f85706

Field	Unit	Required
name	Confirm if needed	No

Soil · Soil & Land Management

Existing form reference: b7d6f23ee128263f

Field	Unit	Required
Soil_Classification_1	Confirm if needed	No
Soil_Classification_1	Confirm if needed	No
Soil_Classification_1	Confirm if needed	No
Zone	Confirm if needed	No
Description	Confirm if needed	No
area	Confirm if needed	No
Perimeter	Confirm if needed	No
SL SOIL	Confirm if needed	No
SL SOIL ID	Confirm if needed	No
ID	Confirm if needed	No
SOIL TYPE	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Soil Groups · Soil & Land Management

Existing form reference: ce03929a51b9da64

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

Soil Conservation Area · Soil & Land Management

Existing form reference: b4d5a0c029f904d6

Field	Unit	Required
ID	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Soil Erosion · Soil & Land Management

Existing form reference: b8bbd59e75e437b9

Field	Unit	Required
Erosion Site ID	Confirm if needed	No
Erosion Rate	Confirm if needed	No
Latitude_KM	Confirm if needed	No
Longitude_KM	Confirm if needed	No
Description	Confirm if needed	No

Disaster Exposure · Soil & Land Management

Existing form reference: 3c6e0cfb0e978318

Field	Unit	Required
Layer Name RiskInfo	Confirm if needed	No
Category	Confirm if needed	No
Max	Confirm if needed	No
Class Name	Confirm if needed	No
max11	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Geomorphology · Soil & Land Management

Existing form reference: 28a2a5925250def7

Field	Unit	Required

Landslide · Soil & Land Management

Existing form reference: ea62ecace985e67d

Field	Unit	Required
id	Confirm if needed	No
range	Confirm if needed	No
level	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Hospitals · Geospatial Evidence

Existing form reference: 22ef095ceb3e5c97

Field	Unit	Required
Hospital Category	Confirm if needed	No
Hospital Name	Confirm if needed	No
Hospital ID	Confirm if needed	No
No of Wards	Confirm if needed	No
District Name	Confirm if needed	No
Source	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
X Coordinate	Confirm if needed	No
Y Coordinate	Confirm if needed	No
province_name	Confirm if needed	No
GON_Division	Confirm if needed	No
Institute	Confirm if needed	No

MOH Boundary · Geospatial Evidence

Existing form reference: 504ead062b8f86fa

Field	Unit	Required
id	Confirm if needed	No
name	Confirm if needed	No
hascoordin	Confirm if needed	No
hascoord_1	Confirm if needed	No
level	Confirm if needed	No
grandparen	Confirm if needed	No
grandpar_1	Confirm if needed	No
parentgrap	Confirm if needed	No
parentid	Confirm if needed	No
parentname	Confirm if needed	No
style	Confirm if needed	No
labelstyle	Confirm if needed	No
type	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Ground Water Prospect · Water Systems

Existing form reference: ce5ed1b99bb3102f

Field	Unit	Required
ID	Confirm if needed	No
Aquifier	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Ground Water · Water Systems

Existing form reference: 8d60801843516765

Field	Unit	Required
ID	Confirm if needed	No
Aquifier	Confirm if needed	No
Original FID	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Village Tank · Water Systems

Existing form reference: ba56f4a118b8defb

Field	Unit	Required
Number	Confirm if needed	No
ID	Confirm if needed	No
Data	Confirm if needed	No
Sheet	Confirm if needed	No
X	Confirm if needed	No
Y	Confirm if needed	No
XCOORD	Confirm if needed	No
YCOORD	Confirm if needed	No
Sheet Number	Confirm if needed	No
Quantity	Confirm if needed	No
Description	Confirm if needed	No

Village Anicut · Water Systems

Existing form reference: f173e69599dc5331

Field	Unit	Required
Serial Number	Confirm if needed	No
XCOORD	Confirm if needed	No
YCOORD	Confirm if needed	No
Code	Confirm if needed	No
Description	Confirm if needed	No

Basin · Water Systems

Existing form reference: aab19eb1fe26e99f

Field	Unit	Required
Basin Name	Confirm if needed	No
Number	Confirm if needed	No
Boundary	Confirm if needed	No
River Basin	Confirm if needed	No
area	Confirm if needed	No
Perimeter	Confirm if needed	No
Watershed	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

Water Shed · Water Systems

Existing form reference: f0192290b75919c0

Field	Unit	Required
Watershed_Type	Confirm if needed	No
Watershed_Name	Confirm if needed	No
Catchment_Name	Confirm if needed	No
Basin_Name	Confirm if needed	No
Region_Name	Confirm if needed	No
Description	Confirm if needed	No
Perimeter	Confirm if needed	No
area	Confirm if needed	No
Watershed_Number	Confirm if needed	No
Hectares	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Dam · Water Systems

Existing form reference: ccd11935ddd740eb

Field	Unit	Required
Dam Name	Confirm if needed	No
Dam_Type	Confirm if needed	No
Dam Storage Capacity	Confirm if needed	No
Hydraulic Head Size meter	Confirm if needed	No
Dam Size	Confirm if needed	No
Dam Construction Type	Confirm if needed	No
Dam Construction Material	Confirm if needed	No
Dam Structural Behaviour	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
Hydro Point ID	Confirm if needed	No
Description	Confirm if needed	No
st_length(shape)	Confirm if needed	No

River Mouth Locations · Water Systems

Existing form reference: 8123426118305c93

Field	Unit	Required
Name	Confirm if needed	No
Capture_Type	Confirm if needed	No
WB_Number	Confirm if needed	No
Point_X	Confirm if needed	No
Point_Y	Confirm if needed	No
Zone_Name	Confirm if needed	No

Stream · Water Systems

Existing form reference: 46072ad6caa5f83d

Field	Unit	Required
Stream Type	Confirm if needed	No
Stream Name	Confirm if needed	No
Length In Km	Confirm if needed	No
Width In Meters	Confirm if needed	No
Hydro Line ID	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

Pond · Water Systems

Existing form reference: 66361481a1066277

Field	Unit	Required
Pond_Type	Confirm if needed	No
Pond_Name	Confirm if needed	No
Capacity_Acre_Per_Feet	Confirm if needed	No
Perimeter_km	Confirm if needed	No
Area_In_sqkm	Confirm if needed	No
Depth_In_Meters	Confirm if needed	No
Spill_Level_MLS	Confirm if needed	No
Catchment_Area	Confirm if needed	No
Hydro_Area_ID	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_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Canal · Water Systems

Existing form reference: f38ab955cf2f6bd4

Field	Unit	Required
Canal Type	Confirm if needed	No
Canal Name	Confirm if needed	No
Length In Km	Confirm if needed	No
Width In Meters	Confirm if needed	No
Hydro Area ID	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_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Lake · Water Systems

Existing form reference: 1bb76fa1770b0049

Field	Unit	Required
Lake_Type	Confirm if needed	No
Lake_Name	Confirm if needed	No
Capacity_Acre_Per_Feet	Confirm if needed	No
Perimeter_km	Confirm if needed	No
Area_In_sqkm	Confirm if needed	No
Depth_In_Meters	Confirm if needed	No
Spill_Level_MLS	Confirm if needed	No
Catchment_Area	Confirm if needed	No
Hydro_Area_ID	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_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

River · Water Systems

Existing form reference: d15540e8ecb12c69

Field	Unit	Required
River Type	Confirm if needed	No
River Name	Confirm if needed	No
Length_In_Km	Confirm if needed	No
Width_In_Meters	Confirm if needed	No
Hydro_Area_ID	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_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Lagoon · Water Systems

Existing form reference: 0f0d24cef4bd6481

Field	Unit	Required
Lagoon_Type	Confirm if needed	No
Lagoon Name	Confirm if needed	No
Primary Inflows	Confirm if needed	No
Primary_Inflows	Confirm if needed	No
Length_In_Km	Confirm if needed	No
Width_In_Km	Confirm if needed	No
Capacity_Acre_Per_Feet	Confirm if needed	No
Area_In_sqkm	Confirm if needed	No
Depth_In_Meters	Confirm if needed	No
Hydro_Area_ID	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_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Spill Point · Water Systems

Existing form reference: dd591850f1e639e2

Field	Unit	Required
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

Sluice Point · Water Systems

Existing form reference: 70efb0310e727bec

Field	Unit	Required
Type Hydro point	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
hydro_point_id	Confirm if needed	No

Cascades · Water Systems

Existing form reference: a23c11282c20ec1d

Field	Unit	Required
RiverBasin Number	Confirm if needed	No
RiverBasin Name	Confirm if needed	No
SWS Number	Confirm if needed	No
SWS Name	Confirm if needed	No
Tank Cascade Number	Confirm if needed	No
Tank Cascade Name	Confirm if needed	No
Number of Tanks	Confirm if needed	No
Number of Tanks1	Confirm if needed	No
Climatic Zone	Confirm if needed	No
Remarks	Confirm if needed	No
area	Confirm if needed	No
Perimeter	Confirm if needed	No
Hectares	Confirm if needed	No
UP Code	Confirm if needed	No
Color Code	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

Sea Ports · Water Systems

Existing form reference: 7caa76b009c9aa66

Field	Unit	Required
Port Name	Confirm if needed	No
ID	Confirm if needed	No
Port Type	Confirm if needed	No
Description	Confirm if needed	No
GFCODE	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

Water Area · Water Systems

Existing form reference: d89ee67747f1e131

Field	Unit	Required
Type_Classification	Confirm if needed	No
Water Area 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
Hydro_Area_ID	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

LHazard10K_U1 · Hazards

Existing form reference: 5b9dbec4b87332bc

Field	Unit	Required
range	Confirm if needed	No
category	Confirm if needed	No
manual	Confirm if needed	No
area	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

Landuse LUPPD 10K · Land Cover

Existing form reference: 30c67d24f5323223

Field	Unit	Required
Luse_Code	Confirm if needed	No
Main_Category	Confirm if needed	No
Sub_Category	Confirm if needed	No
Tank_Name	Confirm if needed	No
Method_of_Updation	Confirm if needed	No
Year_of_Updation	Confirm if needed	No
Sheet_No	Confirm if needed	No

Coastal Lines · Geospatial Evidence

Existing form reference: 66b62b7102545255

Field	Unit	Required
Coastal Line Type	Confirm if needed	No
ID	Confirm if needed	No
Uncertain	Confirm if needed	No
Group	Confirm if needed	No
Offshore	Confirm if needed	No
Cast Direction	Confirm if needed	No
Date	Confirm if needed	No
Description	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Coastal Boundary · Geospatial Evidence

Existing form reference: 47c4f2535c93502b

Field	Unit	Required
Name	Confirm if needed	No
Area in Hectors	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Coastal Reservations Conservations · Geospatial Evidence

Existing form reference: f2687a66e9e614fe

Field	Unit	Required
name	Confirm if needed	No
category	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Road Right of ways · Geospatial Evidence

Existing form reference: b65e4609a48e9e05

Field	Unit	Required
Type_ROW	Confirm if needed	No
Road_Width	Confirm if needed	No
Road Width	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
Transport_point_ID	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Parcel Fabrics · Geospatial Evidence

Existing form reference: 91738cf582575742

Field	Unit	Required
Parcel ID	Confirm if needed	No
Parcel er	Confirm if needed	No
Parcel st	Confirm if needed	No
Parcel Date	Confirm if needed	No
Parcel tp	Confirm if needed	No
Parcel or	Confirm if needed	No
Sheet ID	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
St Area	Confirm if needed	No
St Length	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No
type	Confirm if needed	No
pcl_id_cov	Confirm if needed	No
lot_no	Confirm if needed	No
sht_id_con	Confirm if needed	No
plan_no	Confirm if needed	No
inset_no	Confirm if needed	No
sup_no	Confirm if needed	No
sheet_no	Confirm if needed	No
di_name	Confirm if needed	No
ds_name	Confirm if needed	No
name	Confirm if needed	No
spcific_pu	Confirm if needed	No
tenure_act	Confirm if needed	No
esri_oid	Confirm if needed	No

SLTDA Parcels · Geospatial Evidence

Existing form reference: ca9e78effa85e080

Field	Unit	Required
Plot Number	Confirm if needed	No
Description	Confirm if needed	No
Area_Sq_Meters	Confirm if needed	No
Present Status	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Landuse · Geospatial Evidence

Existing form reference: c4b2b042a758c3f0

Field	Unit	Required
Landuse_Classification_1	Confirm if needed	No
Landuse_Classification_2	Confirm if needed	No
Classification2_Code	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_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Expressway Network · Geospatial Evidence

Existing form reference: e4807930053b77b7

Field	Unit	Required
status	Confirm if needed	No
name	Confirm if needed	No
route_no	Confirm if needed	No
st_length(shape)	Confirm if needed	No

National Road Network · Geospatial Evidence

Existing form reference: 2c605669435a679b

Field	Unit	Required
tl_nm_tran	Confirm if needed	No
class	Confirm if needed	No
type	Confirm if needed	No
start	Confirm if needed	No
End	Confirm if needed	No
start_km_p	Confirm if needed	No
end_km_pos	Confirm if needed	No
district	Confirm if needed	No
province	Confirm if needed	No
tot_length	Confirm if needed	No
sec_no	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Interchanges · Geospatial Evidence

Existing form reference: 4b2812d427e7335b

Field	Unit	Required
id	Confirm if needed	No
name	Confirm if needed	No
crossing_r	Confirm if needed	No
expressway	Confirm if needed	No

Educational Institutions · Geospatial Evidence

Existing form reference: 3d54deca134ce79e

Field	Unit	Required
District	Confirm if needed	No
Province	Confirm if needed	No
census_no	Confirm if needed	No
school_nam	Confirm if needed	No
school_lev	Confirm if needed	No
school_typ	Confirm if needed	No
year_span	Confirm if needed	No
zone	Confirm if needed	No
electorate	Confirm if needed	No
dsd	Confirm if needed	No
gnd	Confirm if needed	No

Building Footprint · Geospatial Evidence

Existing form reference: 928a85f72e6f51f2

Field	Unit	Required
Building_Type	Confirm if needed	No
Name	Confirm if needed	No
Number_of_Floors	Confirm if needed	No
Present_Use	Confirm if needed	No
Creation_Method	Confirm if needed	No
Year_of_Creation	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
Building_ID	Confirm if needed	No
Revision_Method	Confirm if needed	No
Year_of_Revision	Confirm if needed	No
Building_Number	Confirm if needed	No
Building_Level	Confirm if needed	No
Building_Qy_Linetype	Confirm if needed	No
Building_Qy_Color	Confirm if needed	No
Building_Qy_Linewt	Confirm if needed	No
Building_Elevation	Confirm if needed	No
Main_Use	Confirm if needed	No
Condition	Confirm if needed	No
Status	Confirm if needed	No
Remarks	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Place of Worship · Geospatial Evidence

Existing form reference: eb230b20347d611a

Field	Unit	Required
Place of Worship Category	Confirm if needed	No
Building Name	Confirm if needed	No
Period	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

Building Points · Geospatial Evidence

Existing form reference: 598e594fd4111a41

Field	Unit	Required
Building 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
Building ID	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No

Shelters · Geospatial Evidence

Existing form reference: 9ffd5f93309e0745

Field	Unit	Required
Shelter_Type	Confirm if needed	No
Shelter_Owned_by	Confirm if needed	No
Shelter_Capacity	Confirm if needed	No
Number_of_Floors	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

Helicopter pads · Geospatial Evidence

Existing form reference: 55804b4ffbfb5f7f

Field	Unit	Required
Type_Transport_point	Confirm if needed	No
Name_Transport_point	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
Transport_point_ID	Confirm if needed	No
Description	Confirm if needed	No
transportpoint_from_source	Confirm if needed	No

Airports · Geospatial Evidence

Existing form reference: e122eca5d3ec8046

Field	Unit	Required
Type of Service	Confirm if needed	No
Name	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	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

Railway Infrastructure · Geospatial Evidence

Existing form reference: 1dbb103287c07390

Field	Unit	Required
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
Railway Infrastructure Type	Confirm if needed	No
Name	Confirm if needed	No

Railway Lines · Geospatial Evidence

Existing form reference: fe3a59d09f575c74

Field	Unit	Required
Railway Line Type	Confirm if needed	No
Track Type	Confirm if needed	No
Type Transport Line	Confirm if needed	No
Name	Confirm if needed	No
Additional information	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

Expressway · Geospatial Evidence

Existing form reference: 63814effdfe79fab

Field	Unit	Required
Road_Classification	Confirm if needed	No
Road_Class	Confirm if needed	No
Road Name	Confirm if needed	No
Final Road Number	Confirm if needed	No
Road Type	Confirm if needed	No
Road Condition	Confirm if needed	No
Transport Line ID	Confirm if needed	No
Description	Confirm if needed	No
Drains	Confirm if needed	No
Additional information	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
Road Classification From Source	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Main Road (A) · Geospatial Evidence

Existing form reference: 9fdf3c0134703e38

Field	Unit	Required
Road_Classification	Confirm if needed	No
Road_Class	Confirm if needed	No
Road Name	Confirm if needed	No
Final Road Number	Confirm if needed	No
Road Type	Confirm if needed	No
Road Condition	Confirm if needed	No
Transport Line ID	Confirm if needed	No
Description	Confirm if needed	No
Drains	Confirm if needed	No
Additional information	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
Road Classification From Source	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Main Road (B) · Geospatial Evidence

Existing form reference: f025f10ee78f6dc4

Field	Unit	Required
Road_Classification	Confirm if needed	No
Road_Class	Confirm if needed	No
Road Name	Confirm if needed	No
Final Road Number	Confirm if needed	No
Road Type	Confirm if needed	No
Road Condition	Confirm if needed	No
Transport Line ID	Confirm if needed	No
Description	Confirm if needed	No
Drains	Confirm if needed	No
Additional information	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
Road Classification From Source	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Secondary/Minor Road · Geospatial Evidence

Existing form reference: 608c1654358f2be9

Field	Unit	Required
Road_Classification	Confirm if needed	No
Road_Class	Confirm if needed	No
Road Name	Confirm if needed	No
Final Road Number	Confirm if needed	No
Road Type	Confirm if needed	No
Road Condition	Confirm if needed	No
Transport Line ID	Confirm if needed	No
Description	Confirm if needed	No
Drains	Confirm if needed	No
Additional information	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
Road Classification From Source	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Jeep/Car Track · Geospatial Evidence

Existing form reference: 2bf93735eed2ae14

Field	Unit	Required
Road_Classification	Confirm if needed	No
Road_Class	Confirm if needed	No
Road Name	Confirm if needed	No
Final Road Number	Confirm if needed	No
Road Type	Confirm if needed	No
Road Condition	Confirm if needed	No
Transport Line ID	Confirm if needed	No
Description	Confirm if needed	No
Drains	Confirm if needed	No
Additional information	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
Road Classification From Source	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Footpath · Geospatial Evidence

Existing form reference: d9186953aeba76c4

Field	Unit	Required
Road_Classification	Confirm if needed	No
Road_Class	Confirm if needed	No
Road Name	Confirm if needed	No
Final Road Number	Confirm if needed	No
Road Type	Confirm if needed	No
Road Condition	Confirm if needed	No
Transport Line ID	Confirm if needed	No
Description	Confirm if needed	No
Drains	Confirm if needed	No
Additional information	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
Road Classification From Source	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Road Right of ways · Geospatial Evidence

Existing form reference: 8f4285b885648fbe

Field	Unit	Required
Type_ROW	Confirm if needed	No
Road_Width	Confirm if needed	No
Road Width	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
Transport_point_ID	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Runways · Geospatial Evidence

Existing form reference: cfb6ea1c8530c215

Field	Unit	Required
Type_Transport_line	Confirm if needed	No
Additional_information	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
Transport_point_ID	Confirm if needed	No
Description	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Road Transportation Point · Geospatial Evidence

Existing form reference: a34d7724d99491d9

Field	Unit	Required
Road Transport 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

Terrain_Point_UDA_10K · Geospatial Evidence

Existing form reference: 2907de1536a9868c

Field	Unit	Required
Elevation	Confirm if needed	No
TP_Lb_method_creation	Confirm if needed	No
tp_ye_creation	Confirm if needed	No

Toponym_UDA_10K · Geospatial Evidence

Existing form reference: 57941a75527634bb

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

Hydro_UDA_10K · Geospatial Evidence

Existing form reference: 850b83b2a61b2f35

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

Transport_Point_UDA_10K · Geospatial Evidence

Existing form reference: 060ddbfb752dfd4f

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

Utility_Point_UDA_10K · Geospatial Evidence

Existing form reference: 429061263e7ab414

Field	Unit	Required
Type of Utility point	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
Utility point ID	Confirm if needed	No
Name of Utility Point	Confirm if needed	No

Grid_Line_UDA_10K · Geospatial Evidence

Existing form reference: c857eb353ac37157

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

Hydro_Line_UDA_10K · Geospatial Evidence

Existing form reference: 6b63ecc39255076a

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
HL_Ye_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
st_length(shape)	Confirm if needed	No

Transport_Line_UDA_10K · Geospatial Evidence

Existing form reference: 145ec219b5c70559

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
st_length(shape)	Confirm if needed	No

Terrain_Line_UDA_10K · Geospatial Evidence

Existing form reference: 5716ad8940be10bb

Field	Unit	Required
Type of Terrain line	Confirm if needed	No
Elevation	Confirm if needed	No
TL_Lb_method_creation	Confirm if needed	No
tl_ye_creation	Confirm if needed	No
tl_cd_gfcode	Confirm if needed	No
st_length(shape)	Confirm if needed	No

AD_Boundary_Line_UDA_10K · Geospatial Evidence

Existing form reference: afa2a5618c9af8b7

Field	Unit	Required
BO_Tp_Limit	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
st_length(shape)	Confirm if needed	No

Utility_Lline_UDA_10K · Geospatial Evidence

Existing form reference: ff6ae917cfe88626

Field	Unit	Required
Type of Utility Line	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
Utility line ID	Confirm if needed	No
Name of utility line	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Building_UDA_10K · Geospatial Evidence

Existing form reference: c0f2ba96ac5d152a

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
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Landuse_UDA_10K · Geospatial Evidence

Existing form reference: cebcc95362c0c40b

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
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

UDA Declared Areas · Geospatial Evidence

Existing form reference: 3c35b40ab04ea4e1

Field	Unit	Required
PROVINCE_NAME	Confirm if needed	No
DISTRICT_NAME	Confirm if needed	No
DSD_NAME	Confirm if needed	No
GND_NAME	Confirm if needed	No
GND_CODE	Confirm if needed	No
MC_UC_PS_NAME	Confirm if needed	No
SqKm	Confirm if needed	No
Gazzet	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Tile_Polygon_UDA_10K · Geospatial Evidence

Existing form reference: 5399331e5c6c11b3

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

Hydro_Polygon_UDA_10K · Geospatial Evidence

Existing form reference: 6a4ae615ae79d15e

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
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Reserve_Polygon_UDA_10K · Geospatial Evidence

Existing form reference: 5b2ab727b5aedff7

Field	Unit	Required
Type of reserve	Confirm if needed	No
Name	Confirm if needed	No
RE_Lb_method_creation	Confirm if needed	No
re_ye_creation	Confirm if needed	No
GFCODE	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Clouds_UDA_10K · Geospatial Evidence

Existing form reference: 23f60a02c1f79db8

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

Fire Hydrant · Geospatial Evidence

Existing form reference: 782870abe8b5355f

Field	Unit	Required
Type	Confirm if needed	No
Status	Confirm if needed	No
Installed_on	Confirm if needed	No
Rotation	Confirm if needed	No
Digitization_from	Confirm if needed	No
Map_Number	Confirm if needed	No
Update_Date	Confirm if needed	No
GID	Confirm if needed	No

Water Fittings · Geospatial Evidence

Existing form reference: cf68d810309988ce

Field	Unit	Required
Fitting_Type	Confirm if needed	No
Material	Confirm if needed	No
Status	Confirm if needed	No
Rotation	Confirm if needed	No
Digitization_from	Confirm if needed	No
Map_Number	Confirm if needed	No
Update_Date	Confirm if needed	No
GID	Confirm if needed	No
Description	Confirm if needed	No

Water Meter · Geospatial Evidence

Existing form reference: 14c2ccb3f9d41ece

Field	Unit	Required
Meter_Type	Confirm if needed	No
Importance	Confirm if needed	No
Rotation	Confirm if needed	No
Digitization_from	Confirm if needed	No
Map_Number	Confirm if needed	No
Update_Date	Confirm if needed	No
GID	Confirm if needed	No
Description	Confirm if needed	No

Water Station · Geospatial Evidence

Existing form reference: d0aeab3fd60c3a9d

Field	Unit	Required
Station Type	Confirm if needed	No
Station Name	Confirm if needed	No
Suction Diameter	Confirm if needed	No
Deliver Diameter	Confirm if needed	No
Diameter Units	Confirm if needed	No
Rotation	Confirm if needed	No
Digitization From	Confirm if needed	No
Map Number	Confirm if needed	No
Update Date	Confirm if needed	No
GID	Confirm if needed	No
Description	Confirm if needed	No

Water Storage · Geospatial Evidence

Existing form reference: ae9ab4f456ba5f23

Field	Unit	Required
Storage Type	Confirm if needed	No
Name	Confirm if needed	No
Capacity	Confirm if needed	No
Water Level Top	Confirm if needed	No
Water Level Bottom	Confirm if needed	No
Overflow Level	Confirm if needed	No
Source Level	Confirm if needed	No
Inlet Size	Confirm if needed	No
Outlet Size	Confirm if needed	No
Rotation	Confirm if needed	No
Installed On	Confirm if needed	No
Digitization from	Confirm if needed	No
Map Number	Confirm if needed	No
Update Date	Confirm if needed	No
GID	Confirm if needed	No
Description	Confirm if needed	No

Water Valve · Geospatial Evidence

Existing form reference: c5ac68d0b95359c4

Field	Unit	Required
Valve_Type	Confirm if needed	No
Diameter	Confirm if needed	No
Diameter_Units	Confirm if needed	No
Material	Confirm if needed	No
Valve_ID	Confirm if needed	No
Status	Confirm if needed	No
Number_of_Turns	Confirm if needed	No
Open_Direction	Confirm if needed	No
Installed_Date	Confirm if needed	No
Rotation	Confirm if needed	No
Map_Number	Confirm if needed	No
Digitization_from	Confirm if needed	No
Update_Date	Confirm if needed	No
Description	Confirm if needed	No
GID	Confirm if needed	No

Water Pipe Line · Geospatial Evidence

Existing form reference: 5053ac757bff3e63

Field	Unit	Required
Line Type	Confirm if needed	No
Material	Confirm if needed	No
Diameter	Confirm if needed	No
Diameter Units	Confirm if needed	No
Project Name	Confirm if needed	No
Class	Confirm if needed	No
Laid On	Confirm if needed	No
Status	Confirm if needed	No
Map Number	Confirm if needed	No
Digitization from	Confirm if needed	No
File Number	Confirm if needed	No
Cement line	Confirm if needed	No
Year line	Confirm if needed	No
Update Date	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Sewer Intercepter Manhole · Geospatial Evidence

Existing form reference: d413ae0270c31763

Field	Unit	Required
AccNo	Confirm if needed	No
Remarks	Confirm if needed	No
IC_Name	Confirm if needed	No
GID	Confirm if needed	No
Update_Date	Confirm if needed	No
Description	Confirm if needed	No

Sewer Manhole · Geospatial Evidence

Existing form reference: ff70df5e380dbd80

Field	Unit	Required
Name	Confirm if needed	No
Digitization from	Confirm if needed	No
Manhole Shape	Confirm if needed	No
Manhole Type	Confirm if needed	No
Depth_M	Confirm if needed	No
Internal_S	Confirm if needed	No
Units_of_S	Confirm if needed	No
Structural	Confirm if needed	No
Cover Material	Confirm if needed	No
Number of Stubs	Confirm if needed	No
Over Flow	Confirm if needed	No
Units_of_I	Confirm if needed	No
Units_of_d	Confirm if needed	No
Built on	Confirm if needed	No
Status	Confirm if needed	No
GID	Confirm if needed	No
Update Date	Confirm if needed	No
Remarks	Confirm if needed	No
Description	Confirm if needed	No

Sewer Force Main · Geospatial Evidence

Existing form reference: c5ff0d47bd7b53da

Field	Unit	Required
Line_Name	Confirm if needed	No
Digitization_from	Confirm if needed	No
Diameter	Confirm if needed	No
Diameter_Units	Confirm if needed	No
Laid_on	Confirm if needed	No
Status	Confirm if needed	No
Material	Confirm if needed	No
GID	Confirm if needed	No
Update_Date	Confirm if needed	No
Description	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Sewer Gravity Main · Geospatial Evidence

Existing form reference: da848710feda4d8c

Field	Unit	Required
Line Name	Confirm if needed	No
Diameter	Confirm if needed	No
Diameter Units	Confirm if needed	No
Material	Confirm if needed	No
Slope	Confirm if needed	No
UpstreemIN	Confirm if needed	No
DownStreem	Confirm if needed	No
Laid on	Confirm if needed	No
Digitization from	Confirm if needed	No
Status	Confirm if needed	No
Units of Level	Confirm if needed	No
Gravity Type	Confirm if needed	No
GID	Confirm if needed	No
Update Date	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Sewer Lateral Pipeline · Geospatial Evidence

Existing form reference: 062c4eb5c2ddc8b6

Field	Unit	Required
Pipe_Diameter_MM	Confirm if needed	No
Material	Confirm if needed	No
Buried_Depth_Meters	Confirm if needed	No
Laid_On	Confirm if needed	No
Digitization_from	Confirm if needed	No
Remarks	Confirm if needed	No
GID	Confirm if needed	No
Description	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Telecom Structure · Geospatial Evidence

Existing form reference: 57c7f352bf918f95

Field	Unit	Required
Type	Confirm if needed	No
Operator	Confirm if needed	No
Tower Height	Confirm if needed	No
StructureT	Confirm if needed	No
File NUmber	Confirm if needed	No
District	Confirm if needed	No
X	Confirm if needed	No
Y	Confirm if needed	No

Electrical Substations · Geospatial Evidence

Existing form reference: 24a780e5dcfccd62

Field	Unit	Required
Substation Name	Confirm if needed	No
Operating Voltage	Confirm if needed	No
Description	Confirm if needed	No

11KV Lines · Geospatial Evidence

Existing form reference: b2ccf7365c450c20

Field	Unit	Required
objectid_1	Confirm if needed	No
layer	Confirm if needed	No
linetype	Confirm if needed	No
enabled	Confirm if needed	No
branch	Confirm if needed	No
csc_area	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Branch Office · Geospatial Evidence

Existing form reference: d73473dc37d749a0

Field	Unit	Required
name	Confirm if needed	No
folderpath	Confirm if needed	No
symbolid	Confirm if needed	No
altmode	Confirm if needed	No
base	Confirm if needed	No
snippet	Confirm if needed	No
popupinfo	Confirm if needed	No
haslabel	Confirm if needed	No
labelid	Confirm if needed	No

CSC · Geospatial Evidence

Existing form reference: f5c71ab9b5b52c86

Field	Unit	Required
name	Confirm if needed	No

LV Lines · Geospatial Evidence

Existing form reference: 21e0f684a4baee84

Field	Unit	Required
layer	Confirm if needed	No
branch	Confirm if needed	No
csc_area	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Street Lights · Geospatial Evidence

Existing form reference: 77e199e96accdcdb

Field	Unit	Required
pole_sl	Confirm if needed	No
lamp_type	Confirm if needed	No
wattage	Confirm if needed	No
road_name	Confirm if needed	No
branch	Confirm if needed	No
csc_area	Confirm if needed	No
type	Confirm if needed	No
slpl_id	Confirm if needed	No
enabled	Confirm if needed	No

Transformers · Geospatial Evidence

Existing form reference: 1c973ca9cd462eb4

Field	Unit	Required
layer	Confirm if needed	No
tx11_id	Confirm if needed	No
kva_rate	Confirm if needed	No
ld_type	Confirm if needed	No
enabled	Confirm if needed	No
branch	Confirm if needed	No
csc_area	Confirm if needed	No

CEB_220kV_Line · Geospatial Evidence

Existing form reference: 968750925754c5f2

Field	Unit	Required
OID	Confirm if needed	No
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
Status	Confirm if needed	No
st_length(shape)	Confirm if needed	No

CEB_220kV_Point · Geospatial Evidence

Existing form reference: 7932a9f79ed08f40

Field	Unit	Required
OID	Confirm if needed	No
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
PopupInfo	Confirm if needed	No
Status	Confirm if needed	No

CEB_132kv_line · Geospatial Evidence

Existing form reference: c4cce427ffb436a5

Field	Unit	Required
OID	Confirm if needed	No
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
SymbolID	Confirm if needed	No
AltMode	Confirm if needed	No
Base	Confirm if needed	No
Clamped	Confirm if needed	No
Extruded	Confirm if needed	No
Snippet	Confirm if needed	No
PopupInfo	Confirm if needed	No
st_length(shape)	Confirm if needed	No

CEB_132kv_Point · Geospatial Evidence

Existing form reference: 8d4f9075f174afd5

Field	Unit	Required
OID	Confirm if needed	No
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
SymbolID	Confirm if needed	No
AltMode	Confirm if needed	No
Base	Confirm if needed	No
Snippet	Confirm if needed	No
PopupInfo	Confirm if needed	No
HasLabel	Confirm if needed	No
LabelID	Confirm if needed	No

CEB_Grid_Substations_Switching_Stations_and_Power_Stations · Geospatial Evidence

Existing form reference: a584291877caf43f

Field	Unit	Required
Name	Confirm if needed	No
FolderPath	Confirm if needed	No
SymbolID	Confirm if needed	No
AltMode	Confirm if needed	No
Base	Confirm if needed	No
Snippet	Confirm if needed	No
PopupInfo	Confirm if needed	No
HasLabel	Confirm if needed	No
LabelID	Confirm if needed	No

Public source inventory, October 2026 · Source Coverage · Calculated

Existing form reference: a9b8c8efe788ee9a

Field	Unit	Required
Source identity	Confirm if needed	No
Source name	Confirm if needed	No
Publisher	Confirm if needed	No
Subject	Confirm if needed	No
Acquisition status	Confirm if needed	No
Captured rows	rows	No
Published rows	rows	No
Captured UTC	Confirm if needed	No
Coverage	Confirm if needed	No
Time field	Confirm if needed	No
Source URL	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 National Spatial Data Infrastructure See the presentation example

National Spatial Data Infrastructure Documents and images prototype screen — National Spatial Data Infrastructure. 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 National Spatial Data Infrastructure See the presentation example

National Spatial Data Infrastructure Data structure management prototype screen — National Spatial Data Infrastructure. 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 National Spatial Data Infrastructure See the presentation example

National Spatial Data Infrastructure Users and access prototype screen — National Spatial Data Infrastructure. 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.

National Spatial Data Infrastructure

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?