GeoJSON vs CSV for a parcel shortlist: which format fits your workflow

You've got a shortlist of parcels in a submarket and now someone asks: can you send that over as a CSV, or does it need to be GeoJSON? It sounds like a small question. It isn't, because the answer changes what the next person on your team can do with the file.

What CSV gets you

A CSV is a spreadsheet. Each row is a parcel, each column is an attribute: APN, acreage, zoning code, owner name, last sale date, whatever fields you've pulled together. Anyone can open it in Excel without installing anything, sort by lot size, filter out anything under half an acre, and hand it to an analyst who's never touched a GIS tool in their life.

The problem shows up the moment someone needs to see where the parcels sit. A CSV can carry a latitude and longitude, maybe a centroid point, but it has no idea what shape the parcel is. You can plot dots on a map from a CSV. You can't plot the actual boundary, which matters a lot when a parcel is irregular, when it's split by a right-of-way, or when you need to check adjacency to a parcel next door that might make a two-lot assemblage worth a second look.

What GeoJSON gets you

GeoJSON carries the geometry. Each parcel is a polygon with real vertices, so when you drop the file into QGIS or ArcGIS Pro it draws the actual lot lines, not an approximation. You can run a spatial join against a flood zone layer, clip against a zoning overlay, or measure true frontage instead of eyeballing it off an aerial. If your next step after the shortlist is "check this against our GIS layers," GeoJSON is the format that doesn't make you redo work.

The tradeoff is that GeoJSON is dense to read. It's a text file built around nested coordinate arrays, which makes skimming a list of parcels slow going. Open it in a plain text editor and you'll see raw brackets and coordinate pairs, not a readable table. Open it in Excel and you'll get something, but not the columns you want. It's built for software that understands geometry, not for a quick scroll during a Monday pipeline review.

Which one actually fits your acquisition workflow

In practice, most acquisition teams need both, just at different points in the process.

The CSV is for the fast pass. It's what you forward to a partner who wants a ranked list with price and acreage, what you paste into a tracking sheet, what you scan on your phone between site visits. Nobody needs the polygon to decide whether a 2-acre infill lot clears the minimum size threshold.

The GeoJSON is for the moment the shortlist becomes a workplan. Once a handful of parcels survive the first cut, someone on your team opens them in a GIS tool and checks them against easements, utility lines, or a comp set tied to specific boundaries. That work runs on real polygon geometry, pulled straight from the file.

That's why a parcel list worth building a pipeline around should come in both formats from the start, rather than making you convert one into the other and hope nothing gets lost in the process. Development Capacity delivers its ranked parcel shortlists as GeoJSON and CSV together, so the fast-pass list and the GIS-ready layer are the same dataset, not two versions that drift apart after the first edit.

A few things worth checking before you commit a workflow to one format or the other:

• Does the downstream tool need geometry, or just attributes? If the next step is filtering and sorting, CSV. If it's spatial analysis or mapping against other layers, GeoJSON.
• Who's the next person touching the file? An analyst in Excel versus a GIS tech in QGIS will have very different opinions about which format is "the good one."
• Will the shortlist get re-cut later? If parcels get added or dropped as due diligence narrows the list, having both formats in sync from one source beats manually rebuilding a CSV from a shapefile every time something changes.

Neither format is wrong. The question is just which one matches what happens to the file after it leaves your inbox.

If you're screening a submarket and want the shortlist to arrive ready for both the spreadsheet review and the GIS pass, that's the gap Development Capacity is built to close.