Build a tract research list.
Check boundaries, recorded owners and available tax mailing fields before title research. Identify missing information early.
LANDSIGHT / DATA EVALUATION
Your project needs answers.
Start with the evidence.
Get parcel boundaries, recorded owners and mapped flood and wetland context in one file. Test 50 real records in your own tools before buying a county or scoping a project.
No signup. Three Ohio counties. CSV, JSON and GeoJSON.
OPEN THE FILE. CHECK THE FIT.
Real records. Nothing to unlock.
Each pack includes 50 matching records across all three formats, a field completeness profile, methodology and source-edition manifest. These are the first 50 records in source order, not a representative county sample.
| Parcel ID | Recorded owner | Site address | Mapped acres |
|---|---|---|---|
232-000007 | HICKMAN DAVID | 8610 OPOSSUM RUN RD | 0.012 |
232-000011 | US BANK TRUST N A TR | OPOSSUM RUN RD | 0.8689 |
232-000065 | HUFFMAN BRANDI N | OPOSSUM RUN RD REAR | 0.6185 |
Know the edition
Parcel source dates: not supplied. Owner source dates: not supplied. Parcel retrieval: 2026-09-22; owner retrieval: 2026-09-22. Retrieval and new mapping do not refresh older ownership records.
Full county archive: 494,749 records. Sample completeness is documented in the field profile. Mapped acreage is a geometry calculation, not surveyed acreage.
Verify this download
ZIP size: 50.2 KB. SHA-256:
3f77f45068eb105faa6633a087051f159d5ada6da723d4021ea5884eb13314c7ONE SMALL ERROR. A BROKEN JOIN.
A missing zero can mean a missing property.
Putnam’s assessment spreadsheet stores a parcel number as a number. Its parcel map uses a text identifier with a leading zero. Importing both blindly can lose the connection between the owner and the boundary.
Our prepared file restores the identifier using a unique match against official parcel IDs. Ambiguous matches stay unresolved. Open the source excerpt and the exported record to check it yourself.
Inspect the original assessment values ↗COUNTY SPREADSHEET · NUMERIC VALUE
10010100000PREPARED PARCEL ID · TEXT VALUE
010010100000Matched to official identifiers; not arbitrary zero-padding. Import parcel IDs as text to retain the result.
PUT IT TO WORK
Bring a real project area.
Compare the mapped constraints.
Review parcel-level flood and wetland intersections alongside acreage. Separate records needing further review from your initial shortlist.
Test the join before the import.
Inspect identifiers, geometry, missing values and source dates in your existing tools. Keep the evidence with the output.
A SMALL, DEFINED FIRST PROJECT
Evaluate your area.
Know what you will get.
Request a scoped project pilot for up to 100 agreed parcel records in one covered project area: a comparison CSV, GeoJSON, source references and a missing-data report, with one criteria revision.
We confirm coverage, required fields, acceptance checks, price and delivery date before payment. New source acquisition or additional analysis is quoted separately.
What to check before you decide
Are these current ownership records?
These are dated source snapshots. Download date is not the date ownership was verified. Each pack shows its source dates; Franklin’s source dates were not supplied. Consult current county and title records for ownership decisions.
Why can one parcel ID have several records?
Source records and parcel identifiers are different things. Separate mapped pieces or source records can share a parcel ID. record_id identifies the exported source record. Do not merge geometries or sum acreage solely because IDs match.
Does zero mean missing?
No. The export retains source zero values. Empty CSV cells and JSON null values indicate unavailable values. The field profile counts completeness for these 50 records only, not the entire county.
Does mapped flood or wetland data determine whether I can build?
No. These layers support initial screening. Mapping coverage, source age and geometry quality matter. A lack of mapped overlap is not regulatory clearance, a wetland delineation or proof of buildability.
Why does the map show different counts?
The public ParcelMetric demo uses saved February–March 2026 records. These sample downloads come from separately prepared September 2026 product archives with their own source dates. Compare matching editions before interpreting a difference as a data change.