Hello,
Sorry I don't have any test code up at the moment, but this seems to be something inherent to the Places Autocomplete code and not my implementation... I'm developing a web app in sync with another developer who's doing it for iOS. We're using the Places Autocomplete libraries (me the JS and he the Web Service). The site/app is centered on NYC so we're mostly searching around Manhattan. I noticed a few days ago and he recently confirmed that certain searches that come up in the autocomplete predictions don't return a latitude and longitude - sometimes. I think my coworker has narrowed it down a bit since he was playing with the predictions.
With the map bounded to NYC, typing in 'H' brings up 'Home Depot, 3rd Avenue, NY' as an option. If you select that, it doesn't return the Lat/Lng. Now with it selected if you click on the autocomplete textbox it brings up 'Home Depot, 3rd Avenue, NY' as a suggestion again. Clicking that will now return the Lat/Lng. My coworker noticed that if you type in 'Hom' and click it it will respond with the Lat/Lng so he's not calling the autocomplete code until they have entered at least 3 characters to get around this, but I don't seem to have that luxury using the JS version.
Is this something I should report as a bug or is something else going on here that I'm missing?
Thanks,
Jim