Capability

Authoritative Data Management

Landica is built on the agency's own authoritative geospatial data. Data managers configure and publish the datasets that power every project screening — and everything the system surfaces is traceable back to those sources.

The Foundation

The quality of the screening depends on the quality of the data behind it.

Landica does not use generic or commercial datasets for project screening. It uses the agency's own authoritative geospatial data, configured to reflect how the agency manages land and evaluates proposals.

The datasets configured here are the direct inputs to automated spatial screening. When a project boundary is uploaded, Landica evaluates it against every published layer — which means the completeness and accuracy of this data directly shapes what staff see when a project enters the system.

Types of data managed
Land StatusOwnership, jurisdiction, and surface management
Existing RightsRights-of-way, leases, permits, and encumbrances
Mineral RecordsMineral estate and split-estate conditions
Special DesignationsWSAs, ACECs, critical habitat, and similar areas
Resource LayersVegetation, soils, hydrology, cultural resources
Regulatory TriggersAreas that initiate specific study or consultation requirements
Management AreasLand use plan allocations and management zones
Infrastructure RecordsRoads, facilities, and existing surface disturbance
What Data Managers Do

Configure, publish, and maintain the datasets that drive screening.

Configure authoritative datasets

Import and configure geospatial datasets from agency source systems. Each dataset is associated with a layer type, category, and intended use within the screening process.

Add metadata and source information

Attach source references, update schedules, and custodian information to each dataset. This information travels with the data and appears in findings traceable back to their origin.

Connect management direction and policy context

Associate management plan allocations, policy thresholds, and decision criteria with specific datasets. This context shapes how intersections are interpreted and how findings are presented to reviewers.

Define screening and interpretation logic

Establish how each dataset should influence the screening output. Define which intersections trigger findings, how severity is assigned, and what language is used to describe each result.

Publish approved information

Move datasets through a structured review and approval workflow before they are available for project screening. Published datasets represent the agency's authoritative operational data.

Maintain and update agency data over time

Update source datasets as agency information changes. Version tracking ensures that findings produced before and after a dataset update can be distinguished and compared.

Dataset Workflow

From source data to published agency layer.

Each dataset follows a structured path from import through configuration and review to publication. Only validated, agency-approved data is used in project screening.

01
Dataset prepared

The dataset is imported from the agency source system and validated for geometry and completeness.

02
Metadata and context attached

Source information, update schedule, and associated management direction are added to the dataset record.

03
Screening logic defined

Intersection rules, severity levels, and output language are configured to reflect how the agency interprets this data.

04
Dataset reviewed internally

The dataset and its screening configuration are reviewed against a set of representative projects to verify accuracy.

05
Dataset published

Once approved, the dataset is published and available for project screening. All subsequent projects are evaluated against the current published version.

06
Updates managed over time

As source data changes, the dataset is refreshed. The update is versioned so that findings history remains interpretable.

Agency Impact

Configured once. Applied consistently across every project.

When a dataset is published, it becomes the authoritative basis for all project screening in that office. Every reviewer works from the same configured information. Every finding traces back to the same source.

Institutional knowledge about how to interpret data is encoded in the platform and applied consistently — regardless of who handles the application.

Reduces variation between reviewers

Screening results are produced from the same configured datasets and rules, not from individual staff research.

Preserves institutional knowledge

Policy interpretation and management direction encoded by experienced staff are applied to every project, even as staff turnover occurs.

Supports defensibility

Each finding is traceable to a published agency dataset with an associated source reference and update date.

What Comes Next

Published data becomes the input to automated spatial screening.

Once a dataset is published here, it is immediately active in the screening pipeline. When a project boundary is uploaded, Landica evaluates it against every published layer simultaneously — surfacing the constraints, rights, and requirements that staff would otherwise assemble over weeks.

Work with us

See Landica with your agency data.

We work directly with agency teams to configure the platform around your authoritative datasets, review processes, and operational context.