WHAT DOES YOUR TEAM NEED TO DO?
Choose the work, then the data.
These packages define useful project scopes. Ready county files provide the starting data described below where fields are available. Additional research is quoted after location, source coverage, reuse rights and acceptance checks are confirmed.
Brokers & property investorsAn owner list worth reviewing.
Find properties matching a market and property type, with a usable route back to the recorded source.
The output to ask for
Property shortlist + owner/mailing completeness report + source links + unresolved-record queue.
See available data, missing inputs and next steps
Start with ready county data
Recorded owner and available mailing/property fields, parcel geometry, source dates and coverage reports. Filter acreage and mapped context with the shortlist tool. DC also includes a separate condominium relationship review and a queue of missing or multiple links.
Often missed
Repeated parcel IDs, stale owner dates and missing mailing fields can quietly weaken a list. A tax mailing address does not establish occupancy or willingness to sell.
Additional research to scope
Owner-name normalization, duplicate review, parcel groupings and source-verified property classifications. Sales/comparable evidence needs a separate source check.
Source candidates
County assessor and recorder records · Customer-authorized CRM or portfolio export
Build a project brief →Builders, developers & civil engineersA site shortlist with the next question attached.
Compare candidate parcels before spending time on detailed site work.
The output to ask for
Candidate matrix + mapped-constraint evidence + jurisdiction questions + prioritized follow-up list.
See available data, missing inputs and next steps
Start with ready county data
Parcel size, FEMA mapping and available local zoning/NWI overlays, with measured coverage and source dates. Five Ohio county packs also include NRCS soils, drainage, water-table estimates and dwelling/septic survey ratings. Check the county sample for included fields.
Often missed
A parcel may span several zoning districts. Low mapped flood overlap does not establish usable acreage; wetlands, access, setbacks, utilities and terrain may still matter.
Additional research to scope
Source-verified zoning ordinances, soils, elevation/slope, road context and utility inquiry tracking. Engineering, boundary and entitlement decisions remain professional work.
Source candidates
Local planning/zoning authority · USDA NRCS soils · USGS elevation · Utility and road authorities
Build a project brief →Commercial real estate & site selectorsComparable candidates with comparable evidence.
Assemble a location shortlist instead of comparing disconnected property records.
The output to ask for
Site comparison table + ownership context + evidence gaps + custom map or dashboard scope.
See available data, missing inputs and next steps
Start with ready county data
County property classifications where populated, recorded owners, parcel boundaries and available mapped constraints. The DC pack adds final-zone and special-overlay review with source links.
Often missed
Assessor use codes are not zoning permissions. A nearby road or utility line does not demonstrate capacity, connection rights or truck access.
Additional research to scope
Permitted-use research, published traffic counts, aggregate market context and customer-supplied access/capacity requirements. Licensed listings and comps are scoped separately.
Source candidates
Local planning and assessor records · State DOT traffic data · Census aggregate statistics · Customer-licensed listing/comparable sources
Build a project brief →Solar, energy & utility teamsA siting screen that exposes the unknowns.
Narrow a search area while keeping ownership, land constraints and technical feasibility separate.
The output to ask for
Candidate land matrix + land-control questions + mapped evidence + interconnection/utility follow-up register.
See available data, missing inputs and next steps
Start with ready county data
Parcel geometry, acreage, recorded owners and available flood, wetland and zoning context for a first-pass land screen. Five Ohio county packs add NRCS drainage, hydric-component and soil-slope estimates for follow-up research.
Often missed
Distance to a line is not interconnection capacity. Mapped open acreage does not prove contiguous usable land, control of the site or an available connection.
Additional research to scope
Terrain and soils, published infrastructure context, local siting rules and project-specific exclusion layers after source and reuse checks.
Source candidates
DOE siting guidance · USGS elevation and USDA soils · Local siting authority · Utility/ISO published information and direct confirmation
Build a project brief →Telecom, transportation & right-of-way teamsA corridor parcel register your team can work through.
Identify parcels and jurisdictions along a proposed route and coordinate the next research steps.
The output to ask for
Route-to-parcel register + jurisdiction handoffs + missing-owner queue + source-linked review map.
See available data, missing inputs and next steps
Start with ready county data
County parcel geometry and recorded owner fields can seed a route intersection workflow. Ready downloads do not include a completed route study.
Often missed
A parcel intersection is not an easement. Broadband availability is provider-reported; address-level source licensing and permitted reuse need separate review.
Additional research to scope
Customer corridor intersections, agency road/ROW layers, permit authority research and licensed service-location inputs where authorized.
Source candidates
Customer route geometry · County recorder and road authority · FCC public broadband map and applicable licensed sources
Build a project brief →Assessors, planners & GIS departmentsA repair queue, not another unexplained layer.
Know which records can be joined and which require human review before a map or report is used.
The output to ask for
Join/conflict report + geometry and completeness review + field mapping + repeatable update specification.
See available data, missing inputs and next steps
Start with ready county data
CSV/GeoJSON, explicit record identifiers, source metadata and field-level coverage reports. Nantucket and the Boston portion of Suffolk include dated assessment comparisons with unresolved and unmatched records kept separate. DC includes exact condominium-to-assessment/common-lot/approval relationships, all candidate IDs and a review queue. QA records describe checks and limitations.
Often missed
A valid geometry may still belong to the wrong place. Duplicate IDs, changed boundaries and conflicting source dates can survive a simple import check.
Additional research to scope
Schema normalization, identifier crosswalks, multi-vintage change comparisons and custom dashboards using agency-authorized inputs.
Source candidates
Agency authoritative parcel/assessment sources · FGDC cadastral framework · Customer prior-vintage data
Build a project brief →Environmental & conservation teamsA source-linked field-review queue.
Organize mapped environmental context and the locations that need closer investigation.
The output to ask for
Mapped-feature intersection register + source-vintage report + field-review questions and evidence links.
See available data, missing inputs and next steps
Start with ready county data
Available NWI overlap, classifications, imagery years and project coverage, plus FEMA mapping and parcel ownership context.
Often missed
No mapped wetland overlap is not evidence of wetland absence. Imagery age and project-footprint coverage affect what a screen can tell you.
Additional research to scope
Published environmental-record searches, conservation layers and customer-defined study buffers. Regulatory determinations and Phase I assessments require the appropriate professional process.
Source candidates
USFWS National Wetlands Inventory · FEMA flood mapping · EPA and state environmental records
Build a project brief →Agriculture, forestry & land managersA land-management comparison with source context.
Compare holdings or candidate land using consistent boundaries and relevant physical context.
The output to ask for
Holding/parcel crosswalk + acreage comparison + mapped-constraint table + field-verification checklist.
See available data, missing inputs and next steps
Start with ready county data
Parcel acreage and ownership context with available flood/wetland mapping and dated source evidence. Five Ohio county packs add NRCS farmland classes, drainage and map-unit soil estimates, with measured survey coverage.
Often missed
Recorded acres, mapped acres and usable acres can differ. Soil map units contain variability; survey interpretations are not site-specific field findings.
Additional research to scope
NRCS soils, USGS terrain, public land-cover data and customer management boundaries after coverage checks.
Source candidates
USDA NRCS Web Soil Survey · USGS elevation/land-cover sources · Customer management records
Build a project brief →Portfolio, insurance & lending analystsAn exposure review with visible data gaps.
Match a portfolio to parcels and see which properties need additional evidence.
The output to ask for
Match-confidence review + mapped-exposure table + unmapped/ambiguous queue + source-date summary.
See available data, missing inputs and next steps
Start with ready county data
Parcel geometry, source dates, match identifiers and available mapped flood/wetland context. These data support research, not eligibility or coverage decisions.
Often missed
An address match can point to the wrong parcel. An unmapped location must not be treated as zero exposure, and map overlap is not a loss estimate.
Additional research to scope
Authorized portfolio matching, manual exception review and customer-defined aggregation. Modeling or policy-specific conclusions need a separately agreed methodology.
Source candidates
Customer-authorized portfolio · Authoritative county records · FEMA mapping and metadata
Build a project brief →Appraisers, surveyors & land researchersA traceable research packet before the site visit.
Bring parcel records, source links and unresolved questions together for professional review.
The output to ask for
Parcel/source packet + record discrepancy list + missing-document checklist + GIS-ready exports.
See available data, missing inputs and next steps
Start with ready county data
Available assessor attributes, ownership context, parcel geometry, coverage reports and links to original records.
Often missed
Tax parcel geometry is not a boundary survey. Recorded sale values, tax assessments and market value are different evidence types and may have different dates.
Additional research to scope
Recorder/assessor reconciliation, authorized comparison records and client-specific map exhibits. Boundary and value opinions remain professional work.
Source candidates
County assessor and recorder · Official plats and recorded instruments · Customer-authorized professional research
Build a project brief →