Skip to main content

Supported File Types in INVISION Web

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

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

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.

Feature Accepted files Use
Bulk grower enrollment .csv, .xls, .xlsx Create or enroll grower records through the bulk template workflow.
Client or website logo .png, .jpg, .jpeg Add a supported branding image where logo management is enabled.
Document signing .pdf Upload the PDF that will be used in the document-signing workflow.
Help Desk attachment .png, .jpg, .jpeg Attach an image or screenshot to a support request.

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.

Protocol step Accepted upload Expected data
Planting Original .zip package Georeferenced planting records, including available crop, variety, seed rate, population, date, and equipment information
Application Original .zip package Georeferenced application records, including available product, rate, units, date, and equipment information
Harvest Original .zip package Georeferenced point-based harvest records, including available yield, moisture, crop, date, and equipment information

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.

Component Purpose
.shp Geometry
.shx Geometry index
.dbf Attribute data
.prj Coordinate reference system

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.

Back to top