# Supported File Types in INVISION Web

This guide explains which file types can be uploaded through the INVISION web application and where each format should be used.

> **Scope:** This guide applies to INVISION Web. Mobile upload options are documented separately.

## Quick reference

<table id="bkmrk-what-you-are-uploadi"><thead><tr><th>What you are uploading</th><th>Where to upload it</th><th>Supported formats</th></tr></thead><tbody><tr><td>A field boundary</td><td>Enrollment or Bulk Field Import</td><td>GeoJSON, zipped shapefile, KML, KMZ; bulk import also supports CSV and Excel</td></tr><tr><td>A photo or document response</td><td>Upload-type question in a survey or field visit</td><td>JPEG, PNG, HEIC/HEIF, PDF, Word</td></tr><tr><td>A field-note attachment</td><td>Field Notes</td><td>JPEG, PNG, HEIC/HEIF, PDF, Word</td></tr><tr><td>Planting, application, or harvest data</td><td>The matching protocol step</td><td>ZIP</td></tr><tr><td>An EC map</td><td>EC Map / SWAT step</td><td>Zipped shapefile or the four required shapefile components</td></tr><tr><td>A permission-based administrative file</td><td>Grower enrollment, branding, document signing, or Help Desk</td><td>CSV/Excel, JPEG/PNG, or PDF, depending on the feature</td></tr></tbody></table>

> **Key rule:** A supported extension is only the first check. The file must also contain the data, geometry, and companion files required by the selected upload area.

## Before you upload

- Confirm that you are using the upload control for the correct workflow.
- Keep the original file extension. For machine data, preserve the original folder and file structure inside the ZIP.
- Do not password-protect or encrypt ZIP files.
- For shapefiles, include all required companion files from the same dataset.
- If the upload fails, keep the original file so it can be reviewed without losing source information.

## 1. Field boundaries

Field boundary uploads are available during field enrollment and bulk field import. Boundary files must contain polygon geometry.

### Single-field enrollment

Accepted formats:

- GeoJSON: `.geojson`, `.json`, `.gjson`
- Zipped shapefile: `.zip`
- KML: `.kml`
- KMZ: `.kmz`

Requirements:

- Polygon geometry only
- Field boundary must not exceed approximately 2,000 acres
- A shapefile ZIP should include the matching `.shp`, `.shx`, `.dbf`, and `.prj` files

### Bulk field import

Bulk field import supports all single-field formats plus:

- CSV: `.csv`
- Excel: `.xlsx`, `.xls`

CSV and Excel imports may provide boundaries as WKT or through latitude/longitude columns, using the format required by the import template.

### Boundary validation

INVISION validates that uploaded geometry can be used as a field boundary. A file can have a supported extension and still be rejected if its geometry is missing, invalid, not a polygon, incorrectly projected, or incomplete.

## 2. Survey and field-visit uploads

An Upload-type question allows a user to attach a photo or document as the response to a survey or field-visit question in INVISION Web.

Accepted image formats:

- JPG/JPEG: `.jpg`, `.jpeg`
- PNG: `.png`
- HEIC/HEIF: `.heic`, `.heif`

Accepted document formats:

- PDF: `.pdf`
- Microsoft Word: `.doc`, `.docx`

The Upload-type question must be included in the configured survey or field-visit step. Available questions depend on the protocol assigned to the field.

## 3. Field-note attachments

Field notes use the same supported attachment types as Upload-type questions:

- Images: JPG/JPEG, PNG, HEIC, and HEIF
- Documents: PDF, DOC, and DOCX

Use field-note attachments for supporting context. Use an Upload-type question when the file is a required, structured response within a survey or field visit.

## 4. Additional web uploads

The following upload areas are available only to users with the applicable role, feature access, or website configuration.

<table id="bkmrk-feature-accepted-fil"><thead><tr><th>Feature</th><th>Accepted files</th><th>Use</th></tr></thead><tbody><tr><td>Bulk grower enrollment</td><td>`.csv`, `.xls`, `.xlsx`</td><td>Create or enroll grower records through the bulk template workflow.</td></tr><tr><td>Client or website logo</td><td>`.png`, `.jpg`, `.jpeg`</td><td>Add a supported branding image where logo management is enabled.</td></tr><tr><td>Document signing</td><td>`.pdf`</td><td>Upload the PDF that will be used in the document-signing workflow.</td></tr><tr><td>Help Desk attachment</td><td>`.png`, `.jpg`, `.jpeg`</td><td>Attach an image or screenshot to a support request.</td></tr></tbody></table>

### 5. Planting, application, and harvest data

INVISION supports raw precision-agriculture data from commonly used equipment monitors, farm-management platforms, and desktop export tools. This includes data originating from systems such as:

- John Deere Operations Center and GreenStar displays
- Climate FieldView
- Ag Leader displays and SMS
- Trimble
- Raven
- Case IH AFS and New Holland PLM
- Other supported planting, application, and harvest monitor formats

The original data package must be uploaded as a `.zip` file to the matching Planting, Application, or Harvest protocol step.

Raw packages may contain proprietary machine files such as `.dat` files, shapefile components, equipment-specific folders, XML files, or other supporting files. These internal files work together as a complete dataset. The `.zip` file is the upload container; users should not remove, rename, convert, or reorganize its contents.

<div class="TyagGW_tableContainer" id="bkmrk-protocol-step-accept"><div class="group TyagGW_tableWrapper flex flex-col-reverse w-fit" tabindex="-1"><table class="w-fit min-w-(--thread-content-width)" data-end="1464" data-start="925"><thead data-end="976" data-start="925"><tr data-end="976" data-start="925"><th class="last:pe-10" data-col-size="sm" data-end="941" data-start="925">Protocol step</th><th class="last:pe-10" data-col-size="sm" data-end="959" data-start="941">Accepted upload</th><th class="last:pe-10" data-col-size="lg" data-end="976" data-start="959">Expected data</th></tr></thead><tbody data-end="1464" data-start="991"><tr data-end="1153" data-start="991"><td data-col-size="sm" data-end="1002" data-start="991">Planting</td><td data-col-size="sm" data-end="1028" data-start="1002">Original `.zip` package</td><td data-col-size="lg" data-end="1153" data-start="1028">Georeferenced planting records, including available crop, variety, seed rate, population, date, and equipment information</td></tr><tr data-end="1306" data-start="1154"><td data-col-size="sm" data-end="1168" data-start="1154">Application</td><td data-col-size="sm" data-end="1194" data-start="1168">Original `.zip` package</td><td data-col-size="lg" data-end="1306" data-start="1194">Georeferenced application records, including available product, rate, units, date, and equipment information</td></tr><tr data-end="1464" data-start="1307"><td data-col-size="sm" data-end="1317" data-start="1307">Harvest</td><td data-col-size="sm" data-end="1343" data-start="1317">Original `.zip` package</td><td data-col-size="lg" data-end="1464" data-start="1343">Georeferenced point-based harvest records, including available yield, moisture, crop, date, and equipment information</td></tr></tbody></table>

</div></div>When enabled for the account, users may also import data directly through supported John Deere Operations Center or Climate FieldView integrations instead of manually uploading a ZIP.

### Shapefile data in operation uploads

Planting and application ZIP uploads may contain shapefile data. INVISION handles the upload based on its geometry:

- Point geometry can be handled as operation data when it contains the required attributes.
- Polygon geometry is treated as zone-style data and may open the zone workflow instead of the standard operation-data workflow.
- Harvest uploads are expected to contain point-based source data.

### Integrated data sources

Where an approved data integration is enabled, users may select the source directly instead of manually uploading a ZIP. Available integrations depend on the client configuration and user permissions.

## 6. EC map data

EC Map / SWAT uploads use the ESRI shapefile format. Upload either:

- One `.zip` containing the matching `.shp`, `.shx`, `.dbf`, and `.prj` files; or
- The `.shp`, `.shx`, `.dbf`, and `.prj` files together.

All components must share the same base filename and belong to the same shapefile dataset.

<table id="bkmrk-component-purpose-.s"><thead><tr><th>Component</th><th>Purpose</th></tr></thead><tbody><tr><td>`.shp`</td><td>Geometry</td></tr><tr><td>`.shx`</td><td>Geometry index</td></tr><tr><td>`.dbf`</td><td>Attribute data</td></tr><tr><td>`.prj`</td><td>Coordinate reference system</td></tr></tbody></table>

## Troubleshooting an upload

If a supported file does not upload or process successfully, check the following:

1. **Correct upload area:** Make sure the file is being uploaded to the workflow it was created for.
2. **Complete source package:** For ZIP and shapefile uploads, confirm that all original and required companion files are present.
3. **Correct geometry:** Boundaries require polygons. Harvest operation data requires point-based records. Other shapefile workflows may behave differently based on geometry.
4. **Usable coordinate system:** Spatial files must include enough coordinate reference information to place the data correctly on the map.
5. **Readable file:** Confirm that the file opens in its source application and is not damaged, empty, encrypted, or password-protected.

Upload options can vary by protocol configuration, account permissions, and enabled features. If an expected upload control is not visible, contact your INVISION administrator or support contact.