Geocoding turns an address into a geographic location. A useful result includes both the coordinates and enough evidence to judge whether they represent the place you intended. Start with a small sample, inspect the matches, and keep unresolved records visible.
This workflow suits students, researchers, and small organizations preparing a location map. Use public addresses for practice. Before uploading customer, patient, or other personal addresses to any service, establish that the disclosure is permitted and check the provider’s handling and retention terms.
What a coordinate represents
A geocoder may locate a building, parcel, estimated position along a street, or the center of a larger area, depending on its reference data and the input. Treat those as different result types. A point suitable for summarizing a neighborhood may be too coarse for locating an entrance.
The Census Bureau’s public geocoder estimates coordinates using TIGER address ranges. Its output therefore needs interpretation as an address-range location. Decimal places describe how a number is stored; they do not establish survey accuracy.
Forward geocoding starts with an address. Reverse geocoding generally starts with coordinates and seeks a nearby address or place. Census’s coordinate-based geographic lookup returns containing geographies; that is a different operation from finding a street address. Choose the service operation that answers your question.
Keep a clean input and an unchanged original
- Assign a stable record ID, so results can be joined back even when a provider standardizes the address.
- Retain the original address and create separate cleaned fields. Correct known spelling errors while preserving street direction, house number, and other meaningful components.
- Store postal codes and identifiers as text to preserve leading zeros. Keep an apartment or suite separately when the service does not use it.
- Flag incomplete addresses for review. A postal box describes mail delivery and may not represent the site you want to map.
- Choose the service for the country and location detail required. Test known public places before submitting a larger file.
Resolve duplicates according to the task. Two records at one building may be two valid observations. Removing one because its address repeats could change a count or rate. Keep the person or event identifier distinct from a location identifier.
Try the Census Bureau’s public example
The Census service covers the United States, Puerto Rico, and U.S. Island Areas. Its API documentation provides an example address, 4600 Silver Hill Rd, Washington, DC 20233, and explains benchmarks and geography vintages.
- Open the Census Geocoder, choose Find Locations, then One Line Address Processing.
- Enter that public example address and record the selected benchmark. Alternatively, open the same example as a JSON request.
- Compare the returned matched address with the submitted address, then inspect the coordinate pair.
- Record the service, request date, benchmark, matched address, and coordinates together.
For a GIS import, assign longitude to the X field and latitude to Y. Check the reference-system documentation of your source and import tool, then inspect the point in the expected region. If a point lands far away, first check swapped axes, a missing minus sign, and an incorrectly assigned coordinate system.
Review every kind of outcome
| Outcome | Check | Next action |
|---|---|---|
| One plausible match | House number, street, locality, postal code, and expected area. | Accept only if its location detail suits the task. |
| Several candidates | Which candidates agree with independent address evidence? | Review; preserve the alternatives if unresolved. |
| No match | Missing components, spelling, coverage, or recent development. | Correct from evidence and retry; retain the failed attempt. |
| Unexpected position | Axis order, signs, reference system, and coarse fallback type. | Investigate before moving or accepting the point. |
Use a basemap as a plausibility check and official address or site records when exact placement matters. Satellite imagery may have a different date from the address data. A point appearing on a roof still needs a documented basis before it is described as a rooftop match.
For an invented audit of 20 records, suppose 17 have been accepted, two remain ambiguous, and one is unmatched. Report 17/20 = 85% accepted, with all three unresolved records retained. Calling the two ambiguous results “matched” would produce 95%, but it would describe a different measure. State the numerator and denominator explicitly.
Make the result reproducible
Deliver record IDs, original and cleaned addresses, matched addresses, coordinate fields and reference information, provider result types, review decisions, and reasons. Save the request date and benchmark; for Census geographic assignments, also record the selected geography vintage. Keep unmatched rows in a separate review view rather than deleting them from the master dataset.
Decide how much location detail belongs in the final map. An internal analysis can require precise points while its public presentation uses aggregated areas. Verify that the chosen aggregation and any suppression rules fit the data’s sensitivity and the intended audience.
Download a geocoding audit worksheet with the checked public example, a record template, and the fictional acceptance-rate exercise.
Related reading
- Shared mapping: Validate record joins and assign responsibility for updates after locating your addresses.
- Transportation GIS: Compare address coordinates with locations defined by a route and milepoint.
- Map colors: Choose a clear visual treatment for the checked records.