Use case: ag tech software

Add field boundaries, parcels, and soils to your ag software in an afternoon.

For product and engineering teams at farm management, agronomy, crop insurance, and ag lending platforms who need real agricultural layers in the app they already ship—without hiring a GIS engineer or standing up a tile pipeline.

Why this is hard

Current CLU field boundaries are not public. Section 1619 of the 2008 Farm Bill ended USDA distribution, so the free CLU layers still circulating are frozen 2008 vintage.

Parcels and ownership live in 3,000+ independent county assessor systems with no shared schema—PIN, APN, and PARCEL_NUM all mean parcel ID, and freshness ranges from weeks to a year behind.

Soils are not one dataset but roughly 3,400 separate survey downloads, mapped at scales from 1:12,000 to 1:63,360, with seams between survey areas that USDA ships its own QA toolbox to find.

Crop history arrives as a 9.8 GB national raster every season, and USDA itself says vectorizing it is only practical for a single county or smaller.

Then the format fights you: vector tiles split every polygon that crosses a tile seam, so hit-testing returns fragments and duplicates and labels repeat—before you have tuned a tile pyramid or a CDN.

Solution

LandMapMagic serves every one of those layers as standard vector tiles behind a single API key. You point the map you already ship—Google Maps, Mapbox, MapLibre, deck.gl, ArcGIS, Leaflet—at a tile URL, and the layer draws with the same normalized schema in every county. The demo beside this is exactly that integration, nothing more.

Ship the first layer in an afternoon: it is addSource plus addLayer, not a data engineering project.

Keep your existing map SDK. These are ordinary MVT tile URLs, so nothing about your frontend has to change.

One normalized schema nationwide means your code never branches per county or per state.

Ask a single AOI endpoint for soils and crop history inside any boundary your users draw, instead of doing geoprocessing in the browser.

We absorb the annual CDL, SSURGO, and county assessor refreshes while your tile URLs stay exactly the same.

Time to first layer

One afternoon

Two calls on the map you already have

Sources you never touch

3,000+ counties, ~3,400 soil surveys

Normalized to one schema and refreshed for you

Crop raster you don't host

9.8 GB per year

Served as tiles, not downloaded

Map layers are table stakes in ag software, not your differentiator. Rent the pipeline and keep your engineers on the product your customers actually pay for.

Interactive demo

Every layer on this map is one tile URL

Toggle layers, click fields or parcels, or search place / PLSS / address / parcel.
Loading live map layers...

Live in the map above

CLU field boundaries

z12+

USDA FSA common land units

Field polygons with calculated acres, ready to select and label.

Parcels + ownership

z14+

County assessor records, normalized

Owner name, parcel ID, acreage, and address on one schema nationwide.

PLSS survey grid

z0+

BLM townships and sections

States, counties, townships, and sections with labels at every zoom.

Search + geocode

any

One endpoint, no type flags

Places, counties, townships, sections, addresses, and parcel IDs.