feat: multi-farm polygon management

[Shade555]

Title:

feat: multi-farm polygon management

Description:

Summary

Allows a single farmer to draw and manage multiple distinct named field polygons (e.g. "Wheat Field", "Rice Paddy") per farm, backed by a dedicated database table.

Related Issue

Closes #23

Changes

Database

• Added farm_fields table (id, farm_id, name, area_acres, area_hectares generated, polygon JSONB, center_latitude, center_longitude, created_at, updated_at)
• RLS policies scoped to farm owner for SELECT, INSERT, UPDATE, DELETE
• Index on farm_id for fast field lookups, partial index on centre coordinates
• Trigger trg_sync_farm_total_area auto-updates farms.total_area on any field insert/update/delete — no application-level bookkeeping needed
• Migration script migrates any existing JSONB fields from farms.location.fields into the new table
• Migration: backend/supabase/migrations/20260607000000_farm_fields_table.sql

Backend (backend/main.py)

• Rewrote GET /api/farms/{id}/fields to query farm_fields table directly
• Rewrote POST /api/farms/{id}/fields to insert into farm_fields table
• Rewrote DELETE /api/farms/{id}/fields/{field_id} to delete from farm_fields table
• Removed manual JSONB array manipulation and manual total_area recalculation (now handled by DB trigger)
• Added FieldResponse Pydantic model for typed field responses
• Removed area_hectares from FieldCreate (now a generated column in DB)
• Fixed pre-existing double-index bug (owned.data[0][0] → owned.data[0]) in old field endpoints
• Fixed pre-existing res.data.get() bug on list type in get_fields
• Added -> dict return type annotations and user: dict parameter type on all three field endpoints

Frontend

• PolygonMapper (frontend/src/components/map/PolygonMapper.tsx):

  • Added required "Field Name" text input above the map with inline validation
  • onPolygonComplete callback now includes fieldName in the payload
  • Component auto-resets name and polygon after each confirmed field so multiple fields can be drawn without a page reload
  • Updated UI copy to correctly say "4 corners" matching the usePolygonArea hook threshold
  • Removed unused showInstructions prop and locationLoading state

• Dashboard Field Manager tab (frontend/src/components/Dashboard.tsx):

  • Added fields: Field[] state loaded from GET /api/farms/{id}/fields
  • Fields refresh automatically when selected farm changes and after add/delete
  • Replaced handleSavePolygon (which called updateFarm) with handleAddField (calls addFarmField) and handleDeleteField (calls deleteFarmField)
  • Pending field confirm panel shows field name and area before saving
  • "Mapped Fields" list shows all saved fields with coloured dot, name, area, and per-field Remove button with individual loading state
  • Removed stale farm.location.fields JSONB reads — all field data now comes from the API
  • Farm cards show field count for the currently selected farm
  • Removed the wrapper border around PolygonMapper

• FarmMap (frontend/src/components/FarmMap.tsx):

  • Fetches fields from GET /api/farms/{id}/fields (new table) instead of reading farm.location.fields
  • Each named field polygon renders in a distinct colour from the shared FIELD_COLORS palette
  • Clicking a field polygon opens a popup with field name, area, and parent farm name
  • Legacy farms.location.polygon still renders for farms with no named fields yet (backwards compatible)
  • Parallel field loading for all farms when showAllFarms is true

• frontend/src/utils/mapUtils.ts (new file):

  • Extracted FIELD_COLORS palette into a shared utility so Dashboard and FarmMap use the same colours

Testing

• Tested locally (describe steps)

  1. Run npm run dev from the project root
  2. Log in → go to Field Manager tab
  3. Select a farm from the dropdown
  4. Enter "Wheat Field" in the Field Name input, drop 4 pins on the map, click Add field →, then Save Field — field appears in the Mapped Fields list
  5. Repeat with "Rice Paddy" — second field appears with a different colour dot
  6. Click Remove on one field — it disappears and total area updates
  7. Navigate to My Farms tab — farm card shows correct field count
  8. Verify via GET /api/farms/{id}/fields in FastAPI docs (http://localhost:8000/docs) that fields are stored in the farm_fields table
  9. Verify farms.total_area in Supabase Studio (http://127.0.0.1:54323) matches the sum of field areas

Checklist

• Code follows the project's TypeScript / Python style conventions
• No secrets or .env values are committed
• CI passes

[vercel]

@Shade555 is attempting to deploy a commit to the karan3431's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

🎉 Thanks for your contribution, @Shade555!

Please make sure CI passes and the checklist in the PR template is complete. A maintainer will review this soon.

— The AgroNavis team

[jpdevhub]

their is merge conflict in the main.py pull the all latest changes and fix the issue if persists.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agronavis-ai-farm-assiatant	Ready	Preview, Comment	Jun 6, 2026 2:35pm

[Shade555]

@jpdevhub pulled the latest changes, the conflict is resolved now

[jpdevhub]

I will be fixing and merging tonight. Thanks for contribution.

[jpdevhub]

Hey Shade555! We had a small Git hiccup on our end and had to revert the main branch, which accidentally closed this PR. Your code is perfect! Could you please open a brand new PR from your feat/multi-farm-polygon-management branch? It will pass the CI checks now and I will merge it immediately!

[Shade555]

@jpdevhub ahh i see, i have created another PR: #39