You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure which geosearch repo to flag this in, so hoping this is a reasonable spot...
In using the API to search a very specific address (with city, state, borough, & zip code), but where the building number/street name occur in multiple boroughs, I was surprised to see GeoSearch returned occurrences of the building number/street NYC.
For example, as a sample here is the address of the Staten Island Zoo: 614 Broadway, Staten Island, NY 10310
The API call of this seems to parse all fields correctly. However, results returned include 614 Broadway locations in Manhattan and Brooklyn as well as in Staten Island.
@mtreg commented on Tue Mar 06 2018
Not sure which geosearch repo to flag this in, so hoping this is a reasonable spot...
In using the API to search a very specific address (with city, state, borough, & zip code), but where the building number/street name occur in multiple boroughs, I was surprised to see GeoSearch returned occurrences of the building number/street NYC.
For example, as a sample here is the address of the Staten Island Zoo: 614 Broadway, Staten Island, NY 10310
The API call of this seems to parse all fields correctly. However, results returned include 614 Broadway locations in Manhattan and Brooklyn as well as in Staten Island.
(Searching for the specific address for the Staten Island Zoo returned by the api yields the same result.
I wasn't sure if this was expected behavior, but it surprised me given the specificity of the search, so figured I would flag.
Hope this helps!
(PS - in case it's useful to know, I'm not using this for development/production, more just exploring the functionality)
The text was updated successfully, but these errors were encountered: