SignalCrate tools · client-side · nothing uploads
Yield Map Viewer
Drop the yield shapefile you exported from John Deere Operations Center, Climate FieldView, SMS, Ag Leader, Case AFS — or the one your agronomist sent you — and watch your field paint in: a colored yield map with a real legend, summary stats, a histogram, a harvest card, and a clean CSV. Free, no account, no trial clock.
Your file never leaves this device. There is no upload here — no server receives your data. The shapefile is parsed by JavaScript running in your own browser. You can load this page, go offline, and it still works. The only network traffic is this site’s standard visit counter (GoatCounter): a page-view ping plus one anonymous “a file parsed OK” counter event — neither contains anything from your file, not even its name.
Drop your harvest here — the .zip straight from your export, or the .shp + .dbf files together
or click to choose files. Nested folders, batch exports, and macOS zip clutter are all fine. Everything stays on this device.
That export holds more than one shapefile
Ops Center batch exports pack one shapefile per operation, often in per-field folders. Pick the one to view — a merged all-fields view isn’t built yet (it’s on the list).
What was inside what you dropped (exact paths, sizes, types)
Columns are auto-detected from the .dbf; pick a different one if the guess is wrong. Shapefile column names are capped at 10 characters by the format itself — that’s why they look truncated.
Yield map
Summary stats
The CSV holds every record’s coordinates plus all attribute columns — open it in Excel, Sheets, R, whatever you like. Values are exactly as your monitor software exported them; this tool does not recalibrate anything.
Yield histogram
What this reads
ESRI shapefiles — the near-universal export format for yield-monitor data. Point layers (the usual yield export) and polygon layers (swath/boundary exports) both work. Drop a .zip straight from your export, or the loose .shp + .dbf (+ optional .prj) files. Shapefiles buried in nested folders, zips inside zips, and __MACOSX clutter are handled; if one zip holds several shapefiles you get a picker. Yield and moisture columns like DRY_YIELD, Yld_Vol_Dr, Yld_Mass_D, VRYIELDVOL, Moisture are auto-detected, and you can always override the pick in the dropdown above the map.
Got a .jdl file (or a zip full of them)? Here’s the fix
A .jdl is the raw work-data log that a John Deere Gen 4 / G5 CommandCenter™ display writes — Ops Center’s Files page hands these back inside a JD-Data folder when you download raw files (Koenig Equipment’s guide shows that path). There is no public spec for it; only Ops Center itself, the displays, and desktop farm software with Deere’s licensed plugin (SMS, Gatekeeper, GeoPard) can read it. No in-browser tool can honestly open a .jdl — this one included, and a site that claims otherwise is uploading your data to a server to convert it.
The good news: your data is already in Operations Center, and Ops Center exports shapefiles this page does read. In the web app (operationscenter.deere.com — the mobile app has no shapefile export):
- Analyze → Work Analyzer, filter to your harvest operations / year.
- Open the Share/Export dropdown → choose “Work Data” → pick a location and file name → Export Work Data.
- Go to More → Files, select the new export, Download → Desktop or device.
Menu wording follows Premier Crop’s step-by-step with screenshots. Field boundaries have their own path — Setup → Land → Export, file type Shapefile (FieldAlytics guide). Background on the JD-Data/.jdl folder layout: Farmplan’s Gatekeeper PDF.
The download from step 3 is a .zip of shapefiles — drop it here and you’re done.
What v1 does not do (honestly)
- No monitor-native files. It can’t read
.jdl,.dat,.yld, or other proprietary monitor/display formats — no browser tool honestly can. If Ops Center gave you .jdl files, the export fix above takes about two minutes. - No basemap. The map is drawn in your field’s own coordinates, offline. No satellite imagery underneath.
- No reprojection. Projected files draw in their native units; lat/lon files use a flat-earth approximation that is fine at field scale but not for surveying.
- No harvested-acres number. Swath-width and distance units vary between exporters, so v1 refuses to guess. It shows the bounding-box extent instead, clearly labeled as such.
- No data cleaning beyond an optional exclude-zeros toggle — no calibration or flow-delay correction. Stats are computed from the values in your file, as exported.
- One shapefile at a time. If an export holds several, you get a picker and view them one by one — no merged multi-field view yet.
- No comparisons to anyone else’s farm. The harvest card and percentiles are computed from your file alone, on your device.
Why this exists
Farm-data platforms keep making it painful to simply look at data you generated on your own farm. From public app-store reviews of Climate FieldView (collected July 2026 in a scan of 1,448 reviews across 10 farm and job apps; quoted verbatim):
“If you cancel your fieldview plus subscription. Make sure you download your data first. They won’t give it to you without it.”— 1-star App Store review, Climate FieldView
“Been using FieldView cab since 2013 and have been extremely happy with it until you guys forced your way in and rendered my yield information USELESS until I pay $750 for your service. I find no value in Climate for our operation. In the past I was given the option of rejecting a” — 1-star App Store review, Climate FieldView (excerpt)
Farmers have asked for years for a free way to just view an exported yield map — see NewAgTalk’s Precision Talk threads on getting data out of FieldView and free software to view yield maps. The usual answers are crippled desktop trials. This page is the answer we wanted to find: open it, drop the file, see your map. If it saves you a subscription you didn’t want, good.
Found a shapefile it chokes on? That’s a bug we want. Open an issue on the site’s GitHub repo — the “what was inside” panel above gives you the exact paths and sizes to paste; please don’t attach data you consider private.