Guide

CSV or GeoJSON? Choosing a Parcel Data Workflow

Use CSV for parcel tables and GeoJSON for mapped boundaries. Preserve parcel IDs, inspect samples, and carry source and coverage fields into your shortlist.

September 30, 20264 min readUSA-wide parcel + GIS

CSV and GeoJSON serve different parts of parcel research. A table helps compare attributes; a geographic file adds the shape and location of the records. Many projects benefit from keeping both versions together.

Use CSV to compare and filter records

Start with a table when the questions involve recorded owners, acreage, addresses, property classifications, or documented overlap measurements. Import parcel IDs as text to preserve leading zeros and avoid spreadsheet number conversion. Check the field definitions before sorting: a missing value is not the same as zero, and a tax mailing address is not necessarily the property address.

Use GeoJSON when the boundary matters

A GeoJSON parcel file combines feature geometry with properties. Use a compatible GIS to inspect shape, location, adjacent features, and mapped context. Review the product's coordinate and geometry notes before analysis. Parcel boundaries in a research file do not substitute for a survey or establish title.

Join on documented identifiers

Before joining a table to a map, confirm that the identifier represents the same record type in both sources. Check uniqueness and duplicates. One property account, common lot, or condominium relationship can involve a different structure from a one-row-per-parcel file. Do not join solely on a formatted street address when a documented parcel key is available.

Retain evidence in the output

A useful shortlist carries source dates, coverage flags, and references along with the selected properties. LandSight's included browser shortlist tool filters the full county CSV and exports matching rows with their original columns. The free preview uses a sample; it is not the complete purchased county file.

Check the sample before buying the full county

Open a county product page and inspect the sample CSV and available geometry preview. Compare the schema with your intended workflow. Ready county products list record counts, fields, price, and source limitations. Use the buyer checklist to decide whether that file fits or whether a custom research scope is needed.

When a file becomes an ongoing data operation

If the recurring problem is collecting sources, normalizing records, checking quality, and tracking changes, evaluate ParcelMetric. The software discussion covers the sources and workflows for your environment; a one-time county download is a separate purchase.

Back to resources
Previous: Screening Parcels with Flood, Wetland & Zoning DataNext: Replace Legacy GIS Parcel Workflows with an AI Parcel Intelligence Stack

Want to see this in action?

Get a ParcelMetric demo tailored to your workflow.

We will show nationwide coverage, automated data quality checks, and change intelligence for your use case.