geospatial-analysis10.6 KB
View saved version →
---
name: geospatial-analysis
description: "Create a square study area from a named place, run or continue GeoRetina AI environmental risk and conservation analyses, and inspect their maps, tables, downloads, and reports. Use for GeoRetina requests involving an area or an existing analysis. General GIS explanations, coding, and workflows using another provider do not require this skill."
---
# Analyze an area with GeoRetina AI
Complete the requested work through the connected GeoRetina tools. Explicit user
instructions take precedence over these workflow defaults. Respect permissions,
user limits, and the tool schemas actually available in the host. Use real IDs
from the user or authorized tool results. For an authentication challenge, use
the host's connection flow; never request credentials in chat.
## Establish the study area and intent
- Preserve the requested analysis, dates or season, units, and mode. Ask only for
missing information that affects the outcome or that GeoRetina requests. Let
GeoRetina select the workflow and identify analysis-specific inputs.
- For supplied boundaries, pass `roi` as GeoJSON Feature, FeatureCollection, or
Polygon/MultiPolygon geometry in WGS84 (EPSG:4326), longitude before latitude.
Preserve boundaries and holes; do not relabel projected coordinates as WGS84
or silently substitute a bounding box.
- General questions, retrieving results, and reports about existing analyses
need no new boundary. Host attachments and web-app selections are not transferred
to MCP: read a supplied boundary file with available host tools and pass its actual
geometry. Do not claim other attached datasets were uploaded to GeoRetina without
a supported upload path and confirmation that it succeeded.
## Create or reuse a region of interest
For a named place without supplied geometry, ask GeoRetina to create an ROI in the
`message`, with the place and any requested size. Do not make up coordinates,
assume device location, or send the user to the web app because no GeoJSON exists.
The ROI is a **square around a geocoded location**, not an official boundary or a
circular buffer, so never present it as either. Without a stated size, GeoRetina
picks the size itself within the account's area limit, so a large place may be only
partly covered. For an exact or non-square shape, get a GeoJSON boundary.
If the place is ambiguous, clarify it. Unless the user already asked for or accepted
a square, explain this and agree on the extent before analyzing. You can request
creation alone and review the returned area first. Once accepted, one message can
do both: "Create a square ROI around downtown Ottawa and map land cover for summer
2023."
- Tell the user the matched address and actual area from `createdRois`. A
creation-only `completed` outcome does not mean the analysis ran.
- A created ROI stays selected in the conversation. Supplied geometry must be resent
on each analysis turn. For a different place, request a new ROI explicitly. To
return to an earlier ROI or use one elsewhere, pass its geometry as `roi`.
- Preserve explicit sizes. If creation fails, relay the returned reason and ask for a
more precise location, an allowed size, or a GeoJSON boundary. Never shrink the
area, change its shape, or claim success without returned evidence.
## Choose Core or Super
- **Core** (`agentMode: "core"`) is the default for standard, faster analysis
with map layers and metrics; it supports a single registered analysis per plan.
- **Super** (`agentMode: "super"`) supports deeper, multi-step workflows,
multiple analyses, and richer outputs for follow-up work, subject to the chosen
workflow and account access. **Super takes longer than Core in general and can
use more credits.** Set that expectation briefly when choosing Super, without
promising a fixed completion time or treating a long-running job as failed.
- Honor the user's mode choice. If none is specified, use Core; explain when a
reque
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
