Issue 4433 - gmaps-api-issues - allow componentRestrictions to filter same components as the geocoding API service - Google Maps API bug reports and feature requests

Issue 4433:	allow componentRestrictions to filter same components as the geocoding API service
	112 people starred this issue and may be notified of changes.	Back to list

Status:	NeatIdea
Owner:	----
Type-Enhancement ApiType-PlacesAPI Internal-31289065 QueryType-PlaceAutocomplete

Reported by [email protected], Sep 18, 2012

The geocoding API allows to filter  using
route, locality, administrative_area, postal_code and country 
(https://developers.google.com/maps/documentation/geocoding/#ComponentFiltering)

This is a Feature Request to allow such filtering in the Places API autocomplete.

Feb 24, 2013

Project Member #1 [email protected]

(No comment was entered for this change.)

Labels: Type-Enhancement ApiType-Geocoder

Jul 8, 2013

Project Member #2 [email protected]

(No comment was entered for this change.)

Labels: -ApiType-Geocoder ApiType-PlacesAPI

Apr 16, 2015

Project Member #3 [email protected]

(No comment was entered for this change.)

Status: PendingFurtherReview

Apr 16, 2015

Project Member #4 [email protected]

 Issue 4550  has been merged into this issue.

Aug 10, 2015

Project Member #5 [email protected]

 Issue 6913  has been merged into this issue.

Sep 22, 2015

Project Member #6 [email protected]

 Issue 8648  has been merged into this issue.

Sep 22, 2015

Project Member #7 [email protected]

 Issue 5392  has been merged into this issue.

Dec 15, 2015

#9 [email protected]

Hello, this will be a great feature for addresses when postcode or city is already known to have sooner something good in autocomplete suggestions!

Any news about when this will be reviewed?

Apr 26, 2016

Project Member #10 [email protected]

 Issue 9634  has been merged into this issue.

Jun 18, 2016

#12 [email protected]

sometime postal code didn't get correctly and sometime didn't show postal code.what i do for solve this issue??

Sep 5, 2016

Project Member #13 [email protected]

 Issue 10417  has been merged into this issue.

Sep 5, 2016

Project Member #14 [email protected]

(No comment was entered for this change.)

Status: NeatIdea
Labels: Internal-31289065

Sep 21, 2016

Project Member #15 [email protected]

 Issue 4230  has been merged into this issue.

Sep 30, 2016

Project Member #16 [email protected]

 Issue 10582  has been merged into this issue.

Oct 31, 2016

Project Member #17 [email protected]

 Issue 10778  has been merged into this issue.

Nov 9, 2016

Project Member #18 [email protected]

 Issue 8118  has been merged into this issue.

Nov 9, 2016

Project Member #19 [email protected]

 Issue 9242  has been merged into this issue.

Nov 9, 2016

Project Member #20 [email protected]

 Issue 7002  has been merged into this issue.

Nov 9, 2016

Project Member #21 [email protected]

 Issue 7798  has been merged into this issue.

Dec 5, 2016

Project Member #22 [email protected]

 Issue 5783  has been merged into this issue.

Dec 6, 2016

Project Member #23 [email protected]

(No comment was entered for this change.)

Labels: QueryType-PlaceAutocomplete

Dec 6, 2016

Project Member #24 [email protected]

 Issue 8844  has been merged into this issue.

Dec 7, 2016

Project Member #25 [email protected]

 Issue 7636  has been merged into this issue.

Dec 7, 2016

Project Member #26 [email protected]

 Issue 9323  has been merged into this issue.

Dec 7, 2016

Project Member #27 [email protected]

 Issue 10401  has been merged into this issue.

Dec 14, 2016

Project Member #29 [email protected]

 Issue 11075  has been merged into this issue.

Jan 6, 2017

Project Member #30 [email protected]

 Issue 11207  has been merged into this issue.

Jan 30, 2017

#31 [email protected]

It is great to see strictbounds option having been added to 3.27 (currently 3.exp) so results aren’t biased and are now fixed to the bounds or location+radius options.  This does help to reduce the issue raised with this request though many boundaries that could be filtered on are far from a perfect rectangles or circles so this request is still really needed.

The biggest trouble I’ve encountered that is part of this issue is undertaking work for non-country based government bodies.  E.g. State, council and county bodies.  There are many of these, all who usually have strict requirements to service specifically their area and any integration of autocomplete for them, at the moment, is troublesome with results being returned outside their area of service.

Feb 9, 2017

Project Member #32 [email protected]

 Issue 11434  has been merged into this issue.

► Sign in to add a comment