Field boundary files: import and acreage checks

Identify what the boundary is meant to represent

Ask the supplier what the outline describes before importing it. A property parcel, a management field, a planted area and a program reporting unit can share edges without representing the same land. Record the intended use and the source system. A recognizable shape does not establish that its acreage fits the current report.

Keep the original filename, supplier, received date and any accompanying map or explanation. If the supplier exported only selected fields, record that selection. Ask about known exclusions, separate pieces and the season the file describes. An older boundary may still be useful, but the reviewer needs to know what could have changed.

USDA’s Crop Acreage Reporting Information explains acreage reports and access to farm records, maps and common land unit boundary exports. It describes a reporting process that includes crop and intended use. A boundary file imported into another app does not by itself file or amend that acreage report.

Keep shapefile components and source metadata

A shapefile is a set of companion files, not just the file ending in .shp. Keep the geometry, index and attribute files together, along with coordinate-reference information supplied with the package. Archive the received package unchanged. If you need a cleaned import copy, name it separately and record what changed.

The coordinate reference system tells software how to place the coordinates. A file can contain valid numbers while appearing in the wrong place if that information is missing or misinterpreted. Ask the supplier for the source reference when it is unclear. Guessing until the shape looks familiar can conceal a larger coordinate error.

For KML, KMZ, GeoJSON or CSV, retain the source export and its field definitions. Names, identifiers and coordinate columns need their own checks. A compressed file can contain multiple layers or unrelated data; do not assume the largest file inside is the intended field layer. Ask for a clean export when the package cannot be understood confidently.

Keep supporting documents with their own provenance. An FSA map, survey, drainage map and hand sketch answer different questions. They should not become interchangeable attachments labeled only “map.” Describe which document was used to check location and which remains the authority for a legal or program question.

Import into PropelMapper and check the result

PropelMapper’s web app accepts CSV, KML, KMZ, GeoJSON and zipped shapefile place imports up to 20 MB. Use Places in the browser for the import workflow. The phone can also draw or walk a boundary, but it does not automatically draw a field from a visit. Keep the source file available while reviewing the imported places.

Before adding visits, compare each imported outline with the supplied map and a recognizable location. Check the field name and parent place so neighboring fields do not end up under the wrong farm. Where supplied agency identifiers matter, preserve them in the working record and verify their association with the shape.

Inspect the shape at a scale where lanes, building sites and waterways can be distinguished. Check both the broad location and the detailed edges. A whole-farm view can hide a missing hole or an unexpected included lane. A close view alone can make a correctly shaped field look plausible even when it belongs to another property.

Use a review list rather than relying on a quick visual impression:

• Confirm the expected fields and separate pieces are present.
• Compare entrances, roads and neighboring fields with the source map.
• Check internal exclusions and included uncropped areas.
• Match names and supplied identifiers to the corresponding shapes.
• Record unresolved geometry or acreage differences before using the result.

Recognize coordinate and geometry problems

A large shift, mirrored-looking placement, collapsed shape or unexpected scale warrants checking the source and coordinate reference. Do not start redrawing until you understand whether the import was incomplete or the export was wrong. Otherwise the edited copy can hide the reason the original failed.

Look for duplicate outlines, slivers, overlaps and separate pieces joined in an unexpected way. Ask whether those features are deliberate. An irregular corner might follow a real management exclusion rather than a digitizing mistake. Compare with the dated source and the grower’s explanation before changing it.

If a file contains more detail than the work requires, ask the supplier for a simpler export; PropelMapper does not repair or simplify geometry automatically. Importing a supported file does not repair broken shapes, convert every coordinate system or merge duplicate fields for you. A successful upload still needs a checked map.

Reconcile mapped, planted and reported acreage

State the acreage basis wherever the number informs a decision. Mapped acres describe the chosen geometry. Planted acres describe the planted area for the stated crop and date. Reported acres follow the relevant program or insurance process. The numbers may differ because exclusions, crop splits or definitions differ, not because one calculation is necessarily wrong.

USDA FSA’s June 2024 acreage-reporting notice lists the information used in reporting and notes that deadlines vary by county and crop. Use the applicable agency process for corrections. Do not replace a program figure with an app’s mapped area without understanding and documenting the difference.

Keep both figures when they describe different selections. Write the excluded feature, its area source and the date of the edited outline. If the difference remains unexplained, make it a follow-up item. There is no universal acceptable acreage mismatch across every reporting purpose. The agency, insurer or assignment should determine any required tolerance and review.

Check boundaries before interpreting field layers

A boundary affects which ground is included in a field summary. PropelMapper clips supported soil, crop-history and NDVI layers to saved field boundaries. An outline that includes a waterway can therefore describe different acres from a cropped-only outline. Check the selection before interpreting the layer.

USDA NRCS’s SSURGO description explains how soil map units connect to component tables and why map scale matters. Clipping that survey to a more detailed outline does not create a more detailed soil investigation. The geometry selection and the underlying dataset’s resolution are separate limits.

Use the same checked boundary when comparing summaries, or explain the changed selection. A difference between years can come from an edited outline as well as a changed dataset or crop. Preserve the earlier file so the reviewer can separate those possibilities. Do not overwrite the only copy of the geometry that produced a prior report.

Worked example: an included lane in PropelMapper

Start the phone visit at North Field and say which boundary file is under review. Take a context photo of the lane and record what the grower said about the export. Use a typed note to list the missing planted-area record. A location recorded from the truck should be distinguished from the feature being described.

After upload, read the draft and add the source filename, received date and unresolved acreage basis. Create an assigned Follow-up task to obtain the source map. Export the checked report for the reviewer who needs it. The visit record explains the discrepancy; it does not certify a legal boundary or submit an acreage amendment.

Review timing and the next handoff

Check a boundary immediately after import, before using acreage or clipped-layer summaries, and again when the source or reporting purpose changes. These are practical review points for the workflow. For an agency filing or insurance decision, confirm the actual deadline and required evidence with the responsible office or agent.

The handoff should include the original package, checked working copy, source map, identifier crosswalk and explanation of edits. Say which geometry was used in each report. A new advisor should be able to identify the field, reproduce the selected area and understand why its acreage differs from another record without guessing which file is current.