feat: add Export Boundaries button for GeoJSON/KML download

[speed-velocity]

Summary

Related Issue

Closes #

Changes

Testing

• Added/updated tests
• Tested locally (describe steps)

Checklist

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

Summary by CodeRabbit

• New Features

  • Added an “Export Boundaries” dropdown to let users export current farm field boundaries as GeoJSON or KML files for use in external mapping and analysis tools.

• Bug Fixes

  • Addressed a small character/encoding artifact in the dashboard component that could affect rendering consistency.

[vercel]

@speed-velocity 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, @speed-velocity!

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

— The AgroNavis team

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: dda538b8-0d26-4efb-922e-7447a00f49db

📥 Commits

Reviewing files that changed from the base of the PR and between 813dc61 and e0dc589.

📒 Files selected for processing (1)

• frontend/src/components/Dashboard.tsx

✅ Files skipped from review due to trivial changes (1)

• frontend/src/components/Dashboard.tsx

---

📝 Walkthrough

Walkthrough

Adds a new exportUtils.ts module for GeoJSON and KML field-boundary exports with browser download helpers. Dashboard.tsx also has non-functional BOM/whitespace changes.

Changes

Field Boundary Export Feature

Layer / File(s)	Summary
Polygon export utilities frontend/src/utils/exportUtils.ts	Defines ExportableField, converts field polygons to GeoJSON and KML, adds filename slugging and browser download helpers, and exports the GeoJSON/KML download entry points.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 Hop, hop, I sniffed the new export trail,
GeoJSON and KML set sail.
Fields in neat polygons now fly away,
With a download hop and a bunny yay!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main feature: exporting boundaries as GeoJSON/KML via a new button.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[speed-velocity]

@jpdevhub please review it, and if it works update my points in dashboard

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/src/components/Dashboard.tsx`:
- Line 71: The Dashboard.tsx file has widespread character encoding corruption
where Unicode characters have been incorrectly encoded as mojibake (UTF-8 bytes
interpreted as Latin-1). Replace all corrupted character sequences throughout
the file: replace `â€"` with em dashes (—), replace `°` with degree symbols
(°), replace `·` with middle dots (·), replace `â†'` with arrows (→), and
replace `â"€` with box drawing characters. These corrupted sequences appear
across lines 71, 82, 103, 113, 210, 216, 251, 295, 390-391, 406, 496, 499, 566,
575, 586, 615, 689, 703, 724, 768, 823, 878, 882, 952, and 972-974. Ensure the
file is saved with UTF-8 encoding to prevent this corruption from recurring.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0f573b55-05fa-4d5f-8200-76d771f3bbbf

📥 Commits

Reviewing files that changed from the base of the PR and between fe43800 and 813dc61.

📒 Files selected for processing (2)

• frontend/src/components/Dashboard.tsx
• frontend/src/utils/exportUtils.ts

[jpdevhub]

tag the issue no.

[jpdevhub]

Thanks for this great feature! The GeoJSON and KML export logic looks perfect and is extremely useful. However, it looks like your text editor saved Dashboard.tsx with the wrong character encoding, which corrupted several typographic characters across the file (e.g. · became · and — became —). Could you please revert those unintended character changes in Dashboard.tsx? Once that's fixed, we'd love to merge this in!

[jpdevhub]

Are you doing ?

[speed-velocity]

@jpdevhub yup man I'm in. just got stuck in some unavoidable stuffs ,I'll do it by today.

[speed-velocity]

@jpdevhub
Fixed the character encoding issue — restored Dashboard.tsx from upstream and reapplied only the export feature changes. Build passes cleanly with no errors.