Why does a correct map pin return the wrong street address?

You have checked the coordinate order and the pin lands in the intended courtyard. Yet the address returned by a reverse geocoder names the street behind the building. Moving the pin until the label looks right would hide the disagreement. Keep the original point and inspect the feature that supplied the address.

Reverse geocoding associates geographic coordinates with an address or place description. This guide uses Nominatim, an OpenStreetMap-based geocoder, because its documentation explains a particular source of mismatch. It is not an accuracy comparison between map providers.

The address belongs to a selected feature

Nominatim’s reverse-geocoding documentation says it selects the nearest suitable indexed OSM object. That object may have a different street address from the point you supplied. Some small unnamed features are not indexed. This gives a concrete explanation to investigate when a plausible label is spatially misleading.

There are three separate questions: Where did your input place the pin? Which mapped object was returned? Where is the entrance relevant to your task? An answer to one does not automatically settle the others. For a public pavilion, the selected object could be a nearby building while the visitor entrance faces a footpath.

If the pin itself lands in the wrong region, go back to the coordinate-format checks. An order or sign error is an earlier problem. Do not explain it away as a nearest-feature mismatch.

Inspect two positions, not just one address string

Keep the input coordinate unchanged in your notes. Then save the returned record and its observation time. Nominatim’s output-format reference identifies lat and lon as the object’s centroid coordinates, and osm_type with osm_id as its OSM reference. Its internal place_id is not a persistent identifier.

Plot or inspect the returned object separately from the input. If it is an area, look at its outline as well as its center. A center point is not automatically a doorway. Preserve the object link, returned address, source settings and the original query; these let another reader examine the same disagreement.

Changing an output language may change how a name is written. A setting for address detail can change the level of result. Record those choices before comparing two outputs. Do not count a city-level label and a building-level label as contradictory answers to an identical question.

A pavilion with two nearby streets

Invented exercise, not a live lookup. A training map places a pavilion in a courtyard between Oak Lane and Canal Walk. The supplied coordinate sits inside that courtyard. A fictional reverse-geocoder response identifies a neighboring building with an Oak Lane address. A separate visitor notice gives the pavilion entrance on Canal Walk.

The useful finding is not “the coordinate is wrong.” It is: “The query point and returned address feature differ; the visitor notice describes a separate entrance.” None of the three records establishes who occupies a nearby building. The names and layout here exist only to make the reasoning visible.

Now remove the visitor notice from the exercise. Can you still claim the entrance is on Canal Walk? No. The map arrangement suggests a question worth checking, but the geocoder did not answer it. This small change in the packet should change the conclusion.

Keep uncertainty attached to the field it affects

A coordinate copied from a document may be precise in formatting but uncertain in origin. A mapped feature may be correctly identified while its address details need review. An entrance notice may be relevant but old. Avoid collapsing all three into a single confidence score.

If a map feature changed, use the OSM history workflow to examine the relevant versions. If you need to match a public photograph to the place, use the visual geolocation guide. Neither task is completed merely by obtaining a clean postal-looking string.

Finish with a compact comparison note: original coordinate and source → returned object and address → relevant entrance evidence → unresolved question. Keep the original point even when you later find a better address. That preserves how you reached the finding and prevents a convenient label from silently replacing the evidence.