IssueTracker

This issue affects addresses with prefixes such as 21-3 29th St, Queens.

The issue manifests only when Place Autocomplete returns an interpolated result based on a road segment, rather than a one-building result.

The examples in comment #1 (23-30 29th St, Queens) no longer manifests the issue, hence the following example is in Long Island:

Place Autocomplete match for "21-3 29th St, Queens":

description: "21-3 29th St, Queens, Long Island City, NY, USA",
place_id: "Ei8yMS0zIDI5dGggU3QsIFF1ZWVucywgTG9uZyBJc2xhbmQgQ2l0eSwgTlksIFVTQSIwEi4KFAoSCYmcYWwyWcKJERjuUGwY5zQ1EBUqFAoSCXMCA7MtWcKJEXqTUSpxGhp4",

Place Details results for this Place ID:

formatted_address: "52-21 29th St, Long Island City, NY 11101, USA",

The issue is that Place Autocomplete does not support address with road-segment prefixes, which results in the term 21- being interpreted as building number and the term 3 being discarded. This results in a prediction for an address with building number 21 in a segment that matches the rest of the query, regardless of the segment's prefix (e.g. 52-21).

This format is currently only supported in Colombia, where it is used for most addresses.

To mitigate this issue, developers can allow users to geocode their input verbatim, rather than force them to always pick an Autocomplete prediction. There may be other scenarios where Place Autocomplete will not find the desired prediction, e.g. addresses that do not include a street/road name at all (Långskär 1, Svartsjö). Allowing direct geocoding of original user input provides a different way of finding addresses that may succeed.

This is demonstrated (on purpose) in the Geocoder Tool at https://developers.google.com/maps/documentation/utils/geocoder/

• Enter "21-3 29th St, Queens" and click on Autocomplete prediction for "21-3 29th St, Queens, Long Island City, NY, USA" details are fetched for the Place ID from Autocomplete and the result is "52-21 29th St, Long Island City, NY 11101, USA".
• Enter "21-3 29th St, Queens" and press the Enter key, the input is sent to the Geocoding service as an address geocoding request, and the result is "21-3 29th St, Astoria, NY 11105, USA".

Note (updated): there were two issues in comment #3:

1. 42-41 247th Street, Little Neck becoming 66-42 247th Street, Little Neck which is the general issue at hand here. However, this seems to no longer be reproducible.
2. 42-41 247th Street, Little Neck becoming 42-41 247th St, Flushing appears to be unrelated to this. It is only result with place_id: ChIJd-jXBPqJwokRk12c9zDQZYM that has Flushing as its neighborhood address component. This can be fixed by using the "suggest an edit" facility on Google Maps: https://maps.google.com/maps/?cid=0x89c289fa04d7e877%3A0x8365d030f79c5d93