Farm and field labels distinguish where this educational draft is intended to be reviewed.
Interactive learning workspace
Build the map.
Question every cell.
Define a conceptual study area, paint management zones, assign target values, compare a baseline, simplify noisy geometry, check obvious draft problems, and preflight a shapefile handoff—all inside your browser.
Define the map before editing the map.
Keep the decision attached to the numbers.
Record the human and operational context a reviewer needs before interpreting any target. Completing this brief improves traceability; it does not make the draft geospatially or machine ready.
These values preserve the meaning of each numeric target across a human handoff.
Name the responsible decision owner and the evidence or reference layer used.
Every included grid cell needs an explicit target or a documented decision to remain unassigned.
This conceptual grid has no CRS, surveyed boundary, polygon topology, or real-world area.
No display, task controller, implement, product setup, response behavior, or file conversion has been verified.
Context completeness does not create machine readiness. CRS, real geometry, equipment capability, product setup, transfer format, and operator approval remain separate checks.
Make every zone explain itself.
A colored polygon is not a reason. Attach a plain-language purpose, its supporting evidence, and the current review state to each target zone so a later reviewer can challenge the decision instead of guessing what the color meant.
“Reviewed evidence” records a human workflow state only. It does not prove causation, agronomic suitability, legal compliance, or machine readiness.
Inspect a draft before it touches the workspace.
Import World Farm Tech educational JSON or CSV drafts. The file is read locally, checked for structural conflicts, and held in preview until you approve it.
Choose a review draft
JSON restores the complete workspace and prescription brief. CSV restores the grid and unit while retaining the current brief, palette, and review band.
Files stay on this device and are not uploaded.Export this workspace first if you want a known-good sample.
Catch handoff problems before the cab.
Inspect a shapefile manifest, declare its spatial meaning, and expose unresolved review work. Fixed SHP/SHX headers, bounded index evidence, projection and encoding text, DBF row markers, and the selected numeric column are read locally. Geometry bodies and unrelated attribute values stay unopened. This is not a GIS validator or compatibility certificate.
Choose .shp, .shx, .dbf, .prj, .cpg, or .zip files. Names, sizes, projection text, and bounded geometry, index, encoding, and selected-field evidence stay in this browser session and are never uploaded.
No local file metadata selected.
Select exactly one matching .shp, .shx, and .dbf family. Add its matching .prj file to expose coordinate-system evidence.
These counts describe checklist evidence only. They are not a score, agronomic approval, spatial validation, or machine certification.
Choose loose shapefile components so their names can be compared without opening file contents.
Record the coordinate reference system or include a matching projection definition before spatial review.
Confirm whether the receiving prescription workflow accepts the layer geometry before transfer.
Confirm that SHP and SHX headers agree and that SHX index entries match DBF header-declared records.
Select one complete shapefile family to inspect every 8-byte SHX index entry locally.
A valid, bounded SHX audit is required before the browser can read the corresponding eight-byte SHP record headers.
Select a numeric DBF field and keep it paired with its unit so the receiver does not have to guess what the values mean.
Select one complete file family and a numeric target field to inspect DBF rows locally.
Use GIS software to inspect validity, overlaps, gaps, exclusions, and field-boundary alignment; this manifest check cannot do that work.
Name the target display, FMIS, or controller workflow and plan an operator-visible preview before field use.
A clean manifest still requires independent GIS inspection, receiver-specific documentation, equipment setup, calibration, field ownership checks, and responsible human approval.
Reduce map noise without inventing agronomy.
These operations change geometry and target formatting only. Every result still needs evidence review, field ownership checks, machine-resolution checks, and approval.
Smooth isolated cells
Replace a cell only when at least three orthogonal neighbors agree.
Fill unassigned cells
Estimate from adjacent assigned cells for review; never treat this as field truth.
Read the draft as a distribution, not only a surface.
Every value below is derived from equal-sized educational grid cells. Cell share is not geographic area, product quantity, cost, or an agronomic recommendation.
| Target | Relative cell frequency | Cells | Assigned share |
|---|---|---|---|
| 80 units/area | 31 | 34.1% | |
| 100 units/area | 27 | 29.7% | |
| 120 units/area | 6 | 6.6% | |
| 140 units/area | 27 | 29.7% |
Run the quality gate before export.
Passing these checks does not make the map agronomically correct or machine-ready. It only makes obvious draft problems easier to see.
No missing in-area cells
The study-area mask and target assignments are checked separately so outside cells are never treated as prescription gaps.
Targets are inside the review band
Current draft range 80–140 units/area; review band 70–150 units/area.
40 adjacent target transitions
No universal transition threshold is assumed. Inspect whether each boundary follows evidence and can be resolved by the intended workflow.
0 cells differ from the baseline
Compare every change with the evidence, approval, machine resolution, and expected field transition behavior.
Make every change visible before handoff.
The comparison uses the saved baseline and current draft. Counts and target deltas are descriptive only; World Farm Tech does not decide whether a change is agronomically appropriate.
Keep recoverable milestones on this device.
Save named drafts in this browser, restore one into the workspace, or use one as the comparison baseline. Snapshots are device-local convenience copies—not synchronized records or approved prescriptions.
0 saved in this browser
Browser storage can be cleared by the user, browser, or device. Export JSON for a file you need to retain or transfer.
Export an inspectable draft—not a machine command.
JSON preserves the educational grid and prescription brief. CSV is a grid-only row-and-column review table and does not carry the brief. Neither file is ISOXML, a shapefile, a prescription recommendation, or a validated control file.
Follow the draft into a bounded variable-rate workflow.
A prescription expresses spatial intent. Positioning, task exchange, machine control, calibration, as-applied records, field verification, and governance determine what happens next.