IssueTracker

Yes please :) Along with a more specific definition of how the Popular Times are determined (how much history? done by mobile device activity? check ins?)

It already is Jeffrey, you can toggle by day on mobile or desktop

I found a workaround for this issue that worked as long as you have a Google geocoding key: e.g. the following would return 'Gamsey Wood' as part of the xml reply:
https://maps.googleapis.com/maps/api/geocode/json?latlng=52.4180698,-0.2029999&result_type=natural_feature&key=YOUR_GOOGLE_GEO_KEY
Unfortunately this has stopped working. It would be interesting to know why Google has made this info progressively harder to access, and now apparently impossible :-(

I am told it's because "natural_feature" was an undocumented item in the api, so presumably could be easily resurrected and documented? I spent hours adding boundaries and names to local nature reserves when Google were asking for assistance and it's extremely frustrating that I can no longer access the info.

Google how is the problem solution going? When would be able to get the sea name throw the google API?

Would be extremely helpful to have access to this data directly via the API.  Is it maybe available via another API?  

No update on here for a while now... Any news on making this available ?

I suppose this falls under this request :

Google's Reverse Map coding API returning wrong results/guesses for Koh Phi Phi, Thailand

Reverse geo coding lookups for addresses such as at lat/lng 7.74,98.77 should return at least one mention that it's part of the island/island group "Koh Phi Phi".

You would expect that it would also return the island name as "Ko Phi Phi" or "Phi Phi Islands" somewhere. Instead it just returns the sub-district name ( Ao Nang ) and the district name ( Krabi ) which are their own famous tourist areas.


However the reverse geocoding api only returns guesses such as :

[ 'route' ] 'Unnamed Road, Tambon Ao Nang, Amphoe Mueang Krabi, Chang Wat Krabi 81000, Thailand'
[ 'postal_code' ] 'Krabi 81000, Thailand'
[ 'country', 'political' ] 'Thailand'

Similar with a street nearby : 7.743,98.774 which returns :

[ 'route' ] 'Soi Chao Koh, Tambon Ao Nang, Amphoe Mueang Krabi, Chang Wat Krabi 81000, Thailand'
[ 'locality', 'political' ] 'Ao Nang, Mueang Krabi District, Krabi, Thailand'
[ 'postal_code' ] 'Krabi 81000, Thailand'
[ 'administrative_area_level_2', 'political' ] 'Mueang Krabi District, Krabi, Thailand'
[ 'administrative_area_level_1', 'political' ] 'Krabi, Thailand'
[ 'country', 'political' ] 'Thailand'


This leads to categorisation errors. It would be great if the reverse geocoding api could add this information in the return values to help solve these categorisation issues in the future. I'm also aware that huge booking companies have currently issues with categorising Ko Phi Phi correctly due to this.

To add on to the replies above:

result_type: "natural_feature" is actually documented nowadays under optional parameters at https://developers.google.com/maps/documentation/geocoding/intro#ReverseGeocoding

However it doesn't return any results.

News? it would be awesome :)

This would be great, we could use for some cool analytics applications...

Would be great to see this opened up so we could use it in app development in iOS and Android.

Hi, those data would be definitely usefull to enable new services like shopping day optimizer and many more.

Any updates?