Issue 3538 - gmaps-api-issues - Allow Places types in autocomplete - Google Maps API bug reports and feature requests

Issue 3538:	Allow Places types in autocomplete	‹ Prev 83 of 2100 Next ›
	26 people starred this issue and may be notified of changes.	Back to list

Status:	PendingFurtherReview
Owner:	----
ApiType-PlacesAPI Type-Enhancement

Reported by [email protected], Aug 13, 2011

Now only 2 types are supported: establishment or geocode.

I would like to be able to specify any type of the Places API specified in 
https://code.google.com/apis/maps/documentation/places/supported_types.html

For example, ['point_of_interest', 'hindu_temple'].

Thanks!

Sep 30, 2011

#1 [email protected]

Really want this. Specifically to just return 'locality'. This would be useful when you want a user to input a general area. i.e. 'Hackney, United Kingdom'. If they type in 'Mare Street, Hackn...' it would not return 'Mare Street, Hackney, United Kingdom' as it is a road type - only the locality it is in - 'Hackney, United Kingdom'.

Jul 30, 2012

#2 [email protected]

(No comment was entered for this change.)

Owner: [email protected]

May 5, 2014

#3 [email protected]

As a user case:

Currently 4 types can be specified in autocomplete: 'geocode", 'establishment', '(cities)' and '(countries)'. I would like to be able to specify all except 'geocode' (I just do not want the user to autocomplete addresses).

Mar 3, 2015

#4 [email protected]

Really need this since we have an outdoor app.  I'd like to filter on outdoor related places like lakes, trails, campgrounds, mountains, point of interests.

Apr 6, 2015

Project Member #5 [email protected]

(No comment was entered for this change.)

Status: Triaged
Owner: ---

Apr 8, 2015

Project Member #6 [email protected]

(No comment was entered for this change.)

Status: PendingFurtherReview

Apr 21, 2015

Project Member #7 [email protected]

 Issue 7787  has been merged into this issue.

Aug 10, 2015

Project Member #8 [email protected]

 Issue 6915  has been merged into this issue.

Sep 28, 2015

Project Member #9 [email protected]

 Issue 4891  has been merged into this issue.

Sep 29, 2015

Project Member #10 [email protected]

 Issue 4532  has been merged into this issue.

Dec 14, 2015

#11 [email protected]

Need this too! It would be very great to have this feature for better search results!

Dec 19, 2015

#12 [email protected]

8.4 added fix for TYPE_FILTER_ADDRESS in AutocompleteFilter #8034. I'm surprised (disappointed) not to see full type filtering support as there is in the web service API. Is there some technical reason that is not obvious?

Also, the place types returned with AutocompletePredictions are also limited. So it's not even possible to implement a workaround by implementing a second layer of filtering on the returned predictions.

Feb 4, 2016

Project Member #13 [email protected]

 Issue 9248  has been merged into this issue.

Feb 4, 2016

#14 [email protected]

yes this is a pretty important issue, please fix. Thanks!

Apr 4, 2016

#15 [email protected]

Any updates to this, lots of people seem to need this but not much action or decision on if this will be implemented?

May 2, 2016

Project Member #16 [email protected]

 Issue 9663  has been merged into this issue.

► Sign in to add a comment