Maps | Farm Manager

Sample workflow only. No real coordinates, boundaries, parcel IDs, KML/KMZ contents, routes, access notes, gate details, or private map files are shown here.

Layer readiness

7 sample lanes

Layer planning is visible without loading any real GIS data.

sample

Boundary blockers

3 review lanes

Source-of-truth and approval questions stay obvious before any drawing happens.

review

Sensitive map items

4 guarded lanes

Field access, private-layer, and file-handling warnings stay in front of the workflow.

high

Real map data loaded

0 by design

This workflow prepares for future map data without introducing it now.

do not build yet

Readiness-only guardrail

Prepare for future map data without loading real map records yet

This workflow should make map readiness practical now by showing status, missing pieces, source questions, sensitivity warnings, and safe next actions. It should not load real coordinates, boundaries, imagery, files, or access detail.

Map Layer Readiness

Sample layer lane

Public reference layer planning

Sample

Map layer readinessAvailable metadataPublic GIS

Owner Review NeedReady for layout review

Next ActionKeep public reference layers labeled as concepts until the owner approves real sources.

Future Supabase Tablemap_layers

Workflow Note

Future Supabase path: `map_layers` can later hold sample layer labels, status, and visibility notes without storing real geometry.

Sample layer lane

Private owner layer separation

Needs owner review

Map layer readinessMetadata onlyPrivate owner layer

Owner Review NeedRequired before any real map sync

Next ActionKeep private owner notes separate from public-reference concepts so sharing rules stay clear later.

Future Supabase Tablemap_layers

Workflow Note

This keeps future layer permissions from drifting into family-safe views too early.

Sample layer lane

Offline-first layer catalog

Review later

Local-first planLocal-first plannedSample

Owner Review NeedOptional before first read-only sync

Next ActionDefine what minimum metadata should stay local even if read-only Supabase layer summaries are introduced later.

Future Supabase Tablemap_layers

Workflow Note

The first live read should still respect the static-first and local-first fallback pattern.

Boundary Status

Boundary readiness lane

Working boundary source question

Needs owner review

Boundary statusMetadata onlySensitive

Owner Review NeedChoose source before drawing anything

Next ActionKeep the workflow focused on source choice, not on rendering a real line or parcel outline.

Future Supabase Tablemap_layers

Boundary readiness lane

Recorded-survey dependency hold

In review

Boundary statusMissing metadataSensitive

Owner Review NeedReview before Supabase read

Next ActionTrack whether the boundary source question is unresolved without showing a survey, parcel ID, or coordinates.

Future Supabase Tablemap_layers

Boundary readiness lane

Coordinate guardrail remains active

Do not build yet

Boundary statusBlocked pending approvalMetadata only

Owner Review NeedBlocked until owner approves real data use

Next ActionKeep the page explicit that coordinate-based map detail is still out of scope.

Future Supabase Tablemap_layers

Source Status

Sample source lane

Public GIS source labeling

Sample

Source statusAvailable metadataPublic GIS

Owner Review NeedReady for sample review

Next ActionKeep public-source labels visible so future Supabase rows can explain where a layer concept came from.

Future Supabase Tablemap_layers

Sample source lane

Private source approval boundary

Needs owner review

Source statusMetadata onlyPrivate owner layer

Owner Review NeedRequired before any real import

Next ActionMark private-source concepts as blocked from sync until the owner approves how they should be handled.

Future Supabase Tablemap_layers

Sample source lane

Source confidence note

Review later

Source statusLocal-first plannedSample

Owner Review NeedHelpful before field workflows connect

Next ActionMake confidence labels part of future map-layer metadata so Property Overview and Documents can reference them later.

Future Supabase Tablemap_layers

GIS File Checklist

File-readiness hold

KML/KMZ handling checklist

Future task

GIS file checklistMetadata onlyPrivate owner layer

Owner Review NeedBefore any file workflow exists

Next ActionKeep file handling scoped to checklist steps only; do not expose contents, geometry, or private file names.

Future Supabase Tablemap_layers

File-readiness hold

File-source separation checklist

Sample

GIS file checklistAvailable metadataSensitive

Owner Review NeedKeep source-of-truth distinct from file transport

Next ActionMake sure a future map file never becomes the source-of-truth decision by accident.

Future Supabase Tablemap_layers

File-readiness hold

Missing file intake hold

Needs owner review

GIS file checklistMissing fileSensitive

Owner Review NeedBefore developers test imports

Next ActionKeep missing-file states visible without suggesting uploads or drag-and-drop are supported now.

Future Supabase Tablemap_layers

Imagery Placeholders

Imagery placeholder

Imagery approval placeholder

Needs owner review

Imagery placeholderMetadata onlyPublic GIS

Owner Review NeedBefore any imagery is shown

Next ActionKeep imagery discussion limited to approval, licensing, and usefulness questions.

Future Supabase Tablemap_layers

Imagery placeholder

Parcel-context placeholder

Do not build yet

Imagery placeholderDo not build yetSensitive

Owner Review NeedBlocked until owner approves parcel-style data

Next ActionDo not drift from placeholder language into parcel IDs, outlines, or live map tiles.

Future Supabase Tablemap_layers

Imagery placeholder

Field-photo separation reminder

Review later

Imagery placeholderReview before sharingPrivate

Owner Review NeedHelpful before visit workflow links in

Next ActionKeep field imagery and map imagery clearly separate so the visit workflow does not become a map upload lane.

Future Supabase Tablemap_layers

Missing Items

Readiness gap

Approved working boundary source still missing

Needs owner review

Missing itemMissing metadataSensitive

Owner Review NeedBefore any boundary-ready state

Next ActionCapture the missing approval as a workflow blocker rather than guessing a source.

Future Supabase Tablemap_layers

Readiness gap

Safe layer-sharing rules still undefined

Review later

Missing itemIn reviewPrivate owner layer

Owner Review NeedBefore family-safe layer views

Next ActionDecide which sample layers could ever be family-safe before building a sharing concept.

Future Supabase Tablemap_layers

Readiness gap

Sample GIS file intake flow not approved

Future task

Missing itemMissing fileSensitive

Owner Review NeedBefore any developer import test

Next ActionTreat import readiness as a checklist, not as permission to handle private map files.

Future Supabase Tablemap_layers

Field & Access Sensitivity Warnings

Required

Field and access sensitivity warning

Do not add routes, gate details, parking notes, lock instructions, or field-access guidance to map readiness work.

Next Safe Action

Keep access-sensitive detail routed through approval rules instead of map layers.

Do not build yet

Boundary and parcel sensitivity warning

Do not add real parcel IDs, boundary lines, coordinates, or legal-source map records during this preparation stage.

Next Safe Action

Use placeholder status labels and source questions only.

Needs owner review

Private file sensitivity warning

Do not expose KML/KMZ names, folder structures, exports, or private GIS file contents in the page.

Next Safe Action

Keep file readiness abstract until the owner approves a real file workflow.

Connected Workflows

Related workflow

Property Overview

Use Property Overview to keep map readiness connected to the central property summary and workflow status.

Related workflow

Document Vault

Use Document Vault for map-source packets, held file metadata, and missing record placeholders.

Related workflow

Conservation & Land Health

Use Conservation to keep stewardship questions linked to map-readiness decisions without exposing locations.

Related workflow

Visit Planning

Use Visit Planning to keep field observations and access-sensitive notes out of the map workflow.

Future Supabase Connection Path

map_layers

Sample layer labels, readiness state, source status, sensitivity notes, missing items, and next-action metadata for future read-only map workflow summaries.

Next Safe Actions

Required

Start with read-only layer metadata later

The first live map integration should read only safe layer labels, source status, readiness state, and next actions.

Next Safe Action

Use `map_layers` metadata first before any real geometry, tiles, or files are considered.

Sample

Keep source decisions separate from file handling

A good map workflow should distinguish source-of-truth questions from file transport and import questions.

Next Safe Action

Preserve both concepts separately when static helpers eventually give way to Supabase reads.

Do not build yet

Hold access-sensitive detail outside maps

Maps should not become a hidden place for route, access, or gate instructions during this stage.

Next Safe Action

Keep field-access detail blocked and route those concerns back through Visit Planning and owner approval.

Page sample-data boundary

No real coordinates, parcel IDs, boundaries, KML/KMZ contents, routes, access notes, gate details, imagery files, or private map records are included.