ArcGIS Online ACTION
Find Intersecting Features by Geometry
Query target layers in a Feature Service for records whose geometry intersects an Esri JSON boundary you provide. Supports polygon (
rings), polyline (paths), and point (x / y) geometries and returns per-layer attribute arrays. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's ArcGIS Online account once, then configure and run Find Intersecting Features by Geometry from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "arcgis_online-query-intersecting-features-by-geometry",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
arcgis_online: { authProvisionId: "apn_xxxxxxx" },
featureService: "Feature Service",
targetLayerIds: ["Target Layers"],
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "arcgis_online-query-intersecting-features-by-geometry",
"configured_props": {
"arcgis_online": { "authProvisionId": "apn_xxxxxxx" },
"featureService": "Feature Service",
"targetLayerIds": ["Target Layers"]
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "arcgis_online",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "arcgis_online-query-intersecting-features-by-geometry",
arguments: {
featureService: "Feature Service",
targetLayerIds: ["Target Layers"],
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
featureService Feature Service | string | The Feature Service to use: a 32-character portal item ID (e.g. "0123456789abcdef0123456789abcdef"), a full FeatureServer URL (e.g. "https://services.arcgis.com/.../FeatureServer/0"), or a service title that matches search results Required Dynamic |
targetLayerIds Target Layers | string[] | Layers in the same Feature Service: each entry is a numeric layer id as a string and/or a layer name (e.g. ["0", "Parcels", "2"]); names are matched case-insensitively Required Dynamic |
geometry Geometry | object | Esri geometry JSON ( rings, paths, or x/y) with spatialReference (wkid or latestWkid), or a Feature Layer query-style object whose geometry property holds that shape (other keys like outFields are ignored). Can be an object or a JSON string Required |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- arcgis_online-query-intersecting-features-by-geometry
- Version
- 0.0.3
- App
- ArcGIS Online
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗