BotCurrent↗
← Back to examples

Community recipe · Tool workflows

Screen candidate sites against spatial inclusion and exclusion criteria

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Site selection involves overlapping spatial requirements and exclusions that are difficult to evaluate consistently by eye.

Agent job

Check and align spatial layers, apply the supplied proximity and exclusion rules and export candidate areas.

Expected output

Reviewable site-screening geometry based on the stated criteria.

Where this framing comes from
  • Core problem: Editorial purpose framing
  • Agent job: Editorial purpose framing
  • Expected output: Editorial purpose framing
  • Relevant job roles: Editorial purpose framing
  • Benefit type: Editorial purpose framing
Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. A planner applying several geographic criteria may find that individual map layers look sensible while their combined result depends heavily on units, coordinate systems and exclusion definitions. A clean candidate polygon can hide a mismatch between the requested question and the distance method.

  2. This job could prepare a transparent spatial-screening plan with assumptions and review requirements attached. The resulting candidates should remain analytical possibilities for specialist review, not commitments about a site's suitability.

Why an agent / simpler alternative

Useful judgment

Translate explicit spatial criteria into operations, reconcile layer metadata and identify ambiguities that affect the candidate set.

Simpler alternative

Use manual inspection for a very small set of well-known sites with simple criteria.

Unsuitable when

The output would authorize land use or imply safety and legal eligibility without qualified local review.

Proposed inputs

  1. Name

    Site criteria

    Owner

    Planning owner

    Minimum scope

    Inclusion/exclusion rules and intended distance meaning

    Quality check

    Specify units, thresholds and decision scope

  2. Name

    Spatial-layer manifests

    Owner

    Authorized data owner

    Minimum scope

    Layer identities, CRS, dates and coverage

    Quality check

    Check geometry quality, licensing and missing areas

Access and setup — proposed or unknown

Proposed minimum
  1. Review fictional layer metadata and a proposed operation sequence; no GIS execution, downloads or candidate export.

Compatibility unknowns
  1. Current layer quality, GIS versions, coordinate transformations and runtime compatibility are unknown.

External actions requiring approval
  1. Restricted data access, software installation, publishing locations and site-selection commitments require approval.

Expected deliverable and review checks

Proposed artifact

Screening-plan candidate with layer lineage, operation order, unresolved assumptions and geometry-review checklist.

Critical checks
  1. Align CRS/units; confirm distance meaning; preserve excluded/missing coverage; distinguish proposed screening from actual spatial validation.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

  1. Signal

    Distance units do not match the threshold

    Why it matters

    The candidate area can be scaled incorrectly

    Proposed response

    Resolve unit semantics before analysis.

  2. Signal

    An exclusion layer lacks part of the study area

    Why it matters

    A blank region may appear eligible by default

    Proposed response

    Mark coverage unknown and withhold a candidate conclusion.

Effort and cost — unknown

Setup work
  1. Define criteria and authoritative layer scope.

Ongoing review
  1. GIS and planning specialists review geometry and real-world interpretation.

Unknowns
  1. Data completeness, geometric accuracy, legal applicability and analysis costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent station, permitted-zone and exclusion-layer manifests with mismatched CRS and incomplete coverage; draft a preflight plan.

Acceptance checks
  1. Flag both gaps; clarify distance meaning; generate no geometry or site recommendation.

Stop conditions
  1. Stop if coordinate metadata, criteria or coverage is unresolved.

Limits

  1. A spatial plan cannot establish candidate geometry accuracy or permission to acquire, develop or use a site.

Tasks: Planning & operations

Useful for: GIS specialistProperty manager

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Claude CodeIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/Impertio-Studio/QGIS-Claude-Skill-Package/blob/main/skills/source/qgis-agents/qgis-agents-analysis-orchestrator/references/examples.md ↗

Attributed to: OpenAEC Foundation / Impertio-Studio repository maintainers

Community recipe
Original action type
tool_action
What the source supports
Plan a spatial workflow from the user's criteria; load and check station, zoning and flood layers, align coordinate systems, construct a proximity area, intersect permitted zones, remove excluded zones and export the remaining candidate geometry.
Source outcome limits
Instructional recipe with placeholder data, not a reported site selection. Proximity is straight-line distance, not walking access. Supplied zoning/hazard exclusions cannot establish legal buildability, insurability or safety.
Evidence attribution caveat
This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
Source requires planning before coding and geometry/CRS/error checks, but no human decision threshold or authority to make site-selection commitments is specified.
Named tools
Claude Code; QGIS/PyQGIS analysis orchestrator; vector overlay; GeoPackage
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Proposed: screen Canadian sites using licensed/current municipal zoning, transit and hazard layers; confirm local definitions and avoid claiming that a candidate is legally buildable, insurable or safe.
Recommended approval boundaries
Have a planning/GIS professional confirm criteria, source currency, projection and geometry quality; use results only as a screening layer and require independent diligence before property, construction or safety decisions.