Back to How-To
How-To

Territory & Prospecting Tool: Polygon Search + CSV Export for Ag Sales Teams

Draw a polygon over the map, get every quarter section inside with crop and soil data, export to CSV with Salesforce/HubSpot column mapping. Ag Investor only.

Territory & Prospecting Tool

The Territory & Prospecting tool at /app/territory is the Ag Investor tier's biggest differentiator. Draw a polygon over the map, get every parcel inside it with LSRS productivity + 5-year AAFC dominant crop + summary stats, export to CSV with Salesforce / HubSpot column mapping.

The workflow

1. Draw. From the workspace, click "Draw territory" and click vertices on the map. Double-click to close. The polygon snaps cleanly to whatever zoom level you're at; you can draw province-scale or RM-scale.

2. Save. Name the polygon (e.g., "Central Alberta — Lacombe corridor"). The geometry persists in app.territory_polygons so you can come back to it. Each Investor account can save up to 25 named territories.

3. Get the parcel list. Clicking the saved territory in the sidebar runs the spatial query: every parcel centroid inside the polygon, joined to the LSRS productivity layer and the AAFC crop summary layer. The result includes per-parcel:

  • Legal land description (DLS notation)
  • Latitude / longitude
  • Area in acres
  • LSRS productivity score
  • Dominant crop (5-year)

Plus aggregate stats: total parcels, total acres, dominant-crop breakdown by % area, weighted-average LSRS productivity.

4. Export CSV. One click downloads a CSV with column headers pre-mapped for Salesforce Account / Lead imports and HubSpot custom-object imports. Columns:

  • account_name (left blank — fill from the parcel report or provincial registry)
  • legal_land_description
  • province
  • latitude, longitude
  • area_acres
  • dominant_crop
  • lsrs_score
  • notes (left blank for post-import annotation)

The CSV uses RFC-4180 CRLF row separators and properly escapes embedded commas, quotes, and newlines — accepted by Excel, Sheets, Salesforce Data Loader, and HubSpot imports without manual cleanup.

Caps and limits

  • Polygon size: queries cap at 5000 parcels per territory. A multi-RM polygon that exceeds that gets a truncated: true flag in the response so the UI can warn — split-the-territory copy points you at the workaround.
  • Saved territories: 25 per user. Delete an old one to add a new one.

Use cases

Crop input retailer territory planning. Draw the territory you cover from your dealership. Filter the parcel list to canola-dominant + LSRS class 1-2. That's your prospecting universe — already cropping the input you sell, on productive ground. Export and load into the CRM.

Grain company catchment analysis. Draw a 50km radius around an elevator. Get every quarter section that could potentially deliver. Sort by total acres and dominant crop to prioritize grower outreach.

Farmland investor portfolio screening. Draw the geographic area you're shopping. The summary stats give an instant read on the productivity distribution and crop mix; the per-parcel detail feeds individual diligence at /parcel/[lld].

Carbon project boundary scoping. Draw the candidate boundary. The AAFC dominant_crop column tells you the existing rotation, the LSRS column tells you the productivity baseline. Both are inputs to the TIER Conservation Cropping protocol.

What's NOT in the export

  • Operator names — currently blank in the account_name column. Operator inference from AAFC crop continuity + provincial registry data is pending legal sign-off on inference methodology (OQ-6 in the Ag Bundle PRD). The columns are there, ready to populate.
  • Land values — pending the Land Values panel, which is blocked on the free-data path research.
  • Treaty / consultation overlap — surfaced on individual parcel reports but not currently in the CSV export.

Tier

The Territory tool requires Ag Investor ($100 CAD/mo). Server-side gating: every endpoint goes through requireAgPlan(event, PLAN_AG_INVESTOR). Non-Investor users see an upgrade gate.