This guide covers how to prepare machine files for manual upload to Leaf. Following the correct folder structure and format for each equipment type ensures your data processes successfully.
General requirements
All files must be uploaded as ZIP files. Leaf extracts and processes the contents automatically. Maximum file size is 3 GB.
ZIP the folder directly from your monitor or USB drive. Each equipment manufacturer uses specific folder names and structures that must stay intact. Don’t create new folders, rename folders, or move files around. Leaf expects these specific structures and looks for files in the correct locations.
Leaf looks up to two levels deep inside nested ZIP files, so you can upload a single ZIP containing multiple folders or a ZIP containing other ZIP files.
Use original monitor files when possible
Original monitor files contain richer data and process more reliably than exported shapefiles. If you’re using Ag Leader SMS, export the native .agdata, .ilf, or .yld files from your monitor rather than creating shapefile exports.
John Deere
GreenStar 2 (2600)
Locate the RCD folder on your USB drive, ZIP it, and upload.
GreenStar 3 (2630)
GS3_2630/
└── RCD/
└── EIC/
└── global.ver/
└── documentation/
└── .../
├── *.fdd
└── *.fdl
Locate the GS3_2630 or RCD folder on your USB drive, ZIP it with the complete folder hierarchy, and upload.
GreenStar 4 (Gen 4 — 4600/4630)
JD-Data/
└── log/
└── *.jdl
Locate the JD-Data folder, ZIP it, and upload.
MyJohnDeere shapefile exports are supported, but native monitor files are preferred.
Climate FieldView / Precision Planting
These are the same 20|20 monitors listed under both brands.
20|20 SeedSense Generation 1 and 2
├── harvest_*.dat
├── field_map_*.dat
└── liquid_map_*.dat
20|20 SeedSense Generation 3
Locate the folder containing these files, ZIP it, and upload.
CNHi (Case IH / New Holland)
Pro 700 / IntelliView IV (Voyager 2)
<name>.cn1/
├── index.vy1
└── (other data files)
The .cn1 folder contains all operation data. ZIP the entire folder and upload.
Pro 1200 / IntelliView 12 (ISOXML)
TASKDATA/
├── TASKDATA.XML
└── *.bin
Locate the TASKDATA folder, ZIP it (keeping the folder name), and upload.
Ag Leader
INTEGRA (v3.5+), VERSA, or COMPASS
├── *.agdata
└── *.agsetup
Both files must be present together. ZIP the folder containing both files and upload.
Edge, Insight, or INTEGRA (v3.4)
PF Advantage, PF 3000, PF 3000 Pro, YM2000
If you must export from SMS, use the native monitor file formats above instead of shapefiles.
Trimble
FMX or CFX monitors (AgData format)
Agdata/
├── Fields/ (*.agf)
├── implements/ (*.agi)
├── prescriptions/ (*.agm)
├── Tasks/ (*.agt)
├── Users/ (*.agu)
└── vehicles/ (*.agv)
Locate the Agdata folder, ZIP it with the complete folder structure, and upload.
GFX-750, TMX-2050 monitors (AgGPS format)
AgGPS/
└── Data/
└── Grower/
└── Farm/
└── Field/
└── Task/
├── *.cpg
├── *.dbf
├── *.shp
└── *.shx
Locate the operation folder, ZIP it, and upload. See the shapefile requirements section below.
Raven Slingshot
Raven FMIS
Both .xml and .tab files should be present.
Raven JDP
ISOXML equipment
Supported brands include CLAAS, Kuhn, Kverneland Group, Müller-Elektronik, Teknomika, and Topcon.
TASKDATA/
├── *.XML
└── *.bin
The folder must be named TASKDATA. Don’t rename it.
Shapefile exports from SMS
If you don’t have original monitor files, you can export shapefiles from Ag Leader SMS. Original monitor files are strongly preferred — they contain richer data and produce fewer processing issues.
Required shapefile components
├── *.shp (geometry — required)
├── *.dbf (attributes — required)
├── *.shx (index — required)
├── *.prj (projection — required)
└── *.cpg (encoding — optional)
All four required files must be present, must share the same base name (e.g., field_harvest.shp, field_harvest.dbf, etc.), and must be placed at the root level of the ZIP — not nested in subfolders.
Recognized column names
The .dbf file must include columns that Leaf can map to standard properties. SMS truncates column names to 10 characters, so many names below reflect that truncation. If your column names don’t match any listed here, contact support.
Harvest operations:
- Crop (required for moisture-based yield calculations):
crop, Crop, Crop_Type, CROP_NM, Product_Pr, Product___, h_crop
- Moisture:
Moisture__, Moisture, moisture, MOISTURE, Moisture_P, moisture_p, 013A
- Yield — volume per area (e.g., bu/ac):
Yld_Vol_We, Yield__Wet, WET_YIELD
- Yield — mass per area (e.g., lb/ac):
Yield_Mass, Yld_Mass_W (wet); Yld_Mass_D, dryyldlba (dry)
- Yield — total wet mass (e.g., lb):
WetMass, wetMass, Harvest_We
- Yield — total wet volume (e.g., bu):
wetVolume
- Yield — dry volume per area (e.g., bu/ac):
Yld_Vol_Dr, DryYldbuac
Leaf calculates missing dry/wet yield properties automatically when a crop column is present.
Planting operations:
- Crop: same names as harvest
- Seed rate:
seedRate, AmntPerAc, SeedCount, Seed Count, Rt_Apd_Ct_, SeedFlow_k, SeedFlow__, SeedFlow_s, Seed_Cnt__, AVE_SEEDS, Count/Time Act, Application Count
Application operations:
- Applied rate:
AppliedRat, Liq_Rt_ga, Rt_Apd_Liq, Rt_Apd_Ms_, actualRate, Application Mass, Application Volume
- Product:
product, Product, Products, Product___, ProductName
Exporting from SMS
- In SMS Project Workspace, right-click the operation and select Export, then click the paper icon for “Export to a Generic File Format.”
- Choose Generic and Shape as the file type.
- Click Export Selections and Settings to verify column names. You can rename columns here if needed — for example, add Crop Type and rename it to “Crop.”
- Save to your Desktop or Documents folder. You’ll get four files:
.shp, .dbf, .prj, .shx.
- Select all four files, compress into a ZIP, and upload.
Common issues
Upload fails — confirm the file is a ZIP, contains all required components for the file type, and is under 3 GB. For shapefiles, check that the .dbf includes required columns.
Missing or incomplete data — verify original folder structure is intact, folder names haven’t been renamed, and files aren’t nested too deeply (Leaf checks up to 2 levels). For Ag Leader INTEGRA, both .agdata and .agsetup must be present. For ISOXML, both .XML and .bin files must be in the TASKDATA folder.
Processing errors — double-check the folder structure matches the expected format for your equipment. Don’t manually reorganize files or flatten the hierarchy. Last modified on March 24, 2026