Address geocoding vs. parcel boundaries: checking a site before you map it

Use an address geocoder to find a starting location, then identify the intended parcel separately before making a site-level conclusion. Keep the original address, returned match, parcel identifier and source together. If they disagree, retain the disagreement for review instead of silently moving the pin.

The distinction matters when a location flows through several tasks: a broker sends an address, an analyst maps it, and someone else uses that point to retrieve surrounding data. Each person needs to know what the point represents.

Find out how the point was produced

The Census Bureau says its geocoder approximates coordinates using TIGER address ranges. A returned match therefore needs to be read as an address-range result, rather than assumed to be a surveyed corner, building entrance or parcel center. That describes the Census service; other providers can use different methods. Read the documentation for the provider that produced your result. Census Geocoder documentation

Ask the supplier for the location method and any available match-quality field. Keep “unknown” as a valid answer. A precise-looking decimal coordinate alone does not explain how it was obtained.

A reproducible public-address example

On October 5, 2026, we submitted the Census documentation's public example address, 4600 Silver Hill Rd, Washington, DC 20233, to the Census API with benchmark Public_AR_Current.

The response included:

Matched address: 4600 SILVER HILL RD, WASHINGTON, DC, 20233
Longitude (x): -76.92836638093
Latitude (y): 38.84505589808
Address range: 4600 to 4700
TIGER line ID: 657091557
Side: L
Benchmark: Public_AR_Current (ID 4)

This is an actual retrieved response, not an invented property example. It demonstrates the fields returned by the service. We did not measure its positional error, verify a driveway, or establish a parcel boundary. The location response does not contain a parcel identifier or polygon.

Run the same public-address query. Census explains that the data behind a “Current” benchmark can change, so save the response and retrieval date if you need to reproduce your analysis. Its API documentation also distinguishes location results from the additional geographic areas returned by a geography lookup. Census API reference

Match the intended property separately

Open the relevant assessor or parcel-record source and search the address. Record the jurisdiction and parcel identifier, then compare the situs address and mapped extent with the property being offered. Ask the sender to identify the intended tract when the address points to several plausible records.

Keep a separate field for the parcel identifier. Do not replace it with a street address, and do not treat the first polygon containing the point as automatic confirmation of the transaction's boundaries. The task is to reconcile the records and the intended site.

For example, a hypothetical broker package might describe a corner tract while the address lookup produces a point along one frontage. The analyst should ask for the parcel IDs and a marked exhibit. Moving the pin to the visually convenient corner would hide the unresolved question from the next reviewer.

Parcel-map and acreage questions have their own limits. Our guide to deeded and GIS acreage provides a separate worksheet for documenting those discrepancies.

Choose the geometry for the next question

A point-based lookup answers a question about the selected point. If the next task concerns the site's extent, use the identified site geometry and the relevant source's rules for that analysis.

Write the choice into the handoff. “Address result used for initial location search” is more useful than an unexplained pin. “Parcel geometry used for this overlay review” tells the next analyst what was screened. Neither statement establishes legal access or a surveyed boundary.

If someone needs a meeting location, record the entrance or agreed arrival point separately. A research location and a visitor's destination need not be the same coordinate.

Copy this location-review worksheet

Original address exactly as received:
Sender / public source:
Intended site description:

Geocoder and query date:
Benchmark or dataset version:
Matched address:
Longitude / latitude:
Location method and match quality, if provided:
Saved response filename:

Parcel-record authority and retrieval date:
Parcel identifier(s), preserved as text:
Situs address in that source:
Mapped extent checked against offering:
Mismatch or ambiguity:
Person responsible for resolving it:

Geometry used in the next analysis:
Reason for that choice:
Separate arrival point, if needed:
Status: unresolved / response received / reviewed

Retain both the original and corrected record if a mismatch is resolved. Note who supplied the correction and the evidence used. That lets another person follow the decision without rerunning the search and guessing why the location changed.

For the rest of an initial property review, continue with the desktop site-screening checklist.