Status Update
Comments
xe...@google.com <xe...@google.com>
[Deleted User] <[Deleted User]> #3
xe...@google.com <xe...@google.com> #4
Searching for just the postal code is an ambiguous query that may lead to unexpected results. I would suggest to try to follow the Geocoding best practices[1]
[1]
[2]
[Deleted User] <[Deleted User]> #5
Thanks for the quick response! I do not think this is a duplicate of 35828437.
- Interestingly enough it worked until a couple of days ago. Were there any changes?
- How is Country: AU, Postcode: 2000 an ambiguous query? And why is it working for all other postcodes?
Gero
xe...@google.com <xe...@google.com>
xe...@google.com <xe...@google.com> #6
I am reopening this case and we’ll continue to investigate this.
Meanwhile, we strongly recommend adding region biasing to your component filtering query as a workaround, you may refer to this similar case:
Sample request URLs of postal_code with region bias:
I've also provided a working JSBin Geocoding service since your scenario is specific to JS API.
We appreciate your patience on this matter
[Deleted User] <[Deleted User]> #7
Thanks! "I've also provided a working JSBin Geocoding service ..." -> Actually this has the same problem, even if "country: 'AU'," is used in componentRestrictions ZERO_RESULTS is returned for postcode 2000. Postcode 4000 e.g. works just fine.
Maybe the 2000-2030 numbers are interpreted as year at some point?
Gero
xe...@google.com <xe...@google.com> #8
You can report missing postal codes to Google as described in the following support doc:
xe...@google.com <xe...@google.com>
xe...@google.com <xe...@google.com>
[Deleted User] <[Deleted User]> #9
ve...@g-experts.net <ve...@g-experts.net> #10
al...@gmail.com <al...@gmail.com> #11
componentRestrictions: {country: "AU", postalCode: "2000"}
Has there been any movement on this issue? I have 6 maps with traffic exceeding 1000 visits per day.
ha...@gmail.com <ha...@gmail.com> #12
If I search from google map 2016 postcode, it points to Redfern NSW 2016 which is correct.
When I try
It returns nothing.
Please help
mi...@google.com <mi...@google.com> #13
We are investigating a systemic issue that appears to make postal codes with 4 digits particularly difficult to find in the Geocoding API.
For best result, the recommended request format is to use Component Filtering and Region Biasing towards the desired country:
In Australia in particular, if feasible in your implementation, adding the administrative_area: filter helps with most postal codes in the 2000-2020 range.
(taking into account that postal codes 2001-2005 and 2012-2014 are not in Google Maps at all)
In other countries, wherever possible adding the locality filter would also help, as noted in #10.
We will keep you posted here.
rs...@gmail.com <rs...@gmail.com> #14
"country:BE" and "postal_code:1000" it continues to return zero results.
mi...@google.com <mi...@google.com> #15
formatted_address: "1000 Brussels, Belgium",
place_id: "ChIJX6UHPofEw0cRXd0IVgg8wQA",
types: ["postal_code"]
The viewport can be obtained by geocoding the country:
rs...@gmail.com <rs...@gmail.com> #16
tr...@lmg.broker <tr...@lmg.broker> #17
The alternative solution (with bounds parameter) still doesn't work for AU, please see below as an example
Bounds parameter value is from:
It is a valid postal code for Australia as per earlier comments.
Thanks,
Tran
tr...@lmg.broker <tr...@lmg.broker> #18
Above still returns 0 result.
ke...@clickzoom.com <ke...@clickzoom.com> #19
mi...@google.com <mi...@google.com> #20
The above workarounds are not guaranteed to always find every single postal code. This is because a 4-digit or 5-digit number is often an ambiguous query, even within the context of a single country.
The combination of postal_code
& country
) and
There are still postal codes that evade this request format though:
Note: this comment was edited on July 12, 2023 to replace types=(regions)
with types=postal_code
which works better for this purpose but was previously not supported in Place Autocomplete.
[Deleted User] <[Deleted User]> #22
vi...@wago.com <vi...@wago.com> #27
cl...@viessmann.com <cl...@viessmann.com> #28
Si...@avensia.com <Si...@avensia.com> #29
I tried the workaround with adding both region and country and it worked for a day but now it stopped working again
[Deleted User] <[Deleted User]> #30
ka...@kk-grp.jp <ka...@kk-grp.jp> #31
st...@gmail.com <st...@gmail.com> #32
I'm using a workaround now so if anyone is having the same issue with DK and has experienced more than the zipcodes I've listed, please let me know which ones I'm missing.
Funny thing is, when I call from Chrome,
mj...@mapspeople.com <mj...@mapspeople.com> #33
Workaround is implemented by using Places API
gf...@gtempaccount.com <gf...@gtempaccount.com> #34
[Deleted User] <[Deleted User]> #35
mi...@google.com <mi...@google.com>
[Deleted User] <[Deleted User]> #36
-
-
-
th...@mediaa.be <th...@mediaa.be> #37
ca...@gmail.com <ca...@gmail.com> #38
EDIT: Should also be mentioned that I can't use Google Places as a work around. I've had to use GeoNorge instead for a half assed attempt at a fix.
[Deleted User] <[Deleted User]> #39
ve...@gmail.com <ve...@gmail.com> #40
.geocode({
region: "NZ",
componentRestrictions: {
country: "NZ",
postalCode: "2013"
},
})
Any solutions?
km...@gmail.com <km...@gmail.com> #41
I do have this issue as well on some postcodes in Belgium, i.e. 1933.
Is there any update on this subject ?
Thanks
ed...@gmail.com <ed...@gmail.com> #43
mi...@google.com <mi...@google.com> #44
Merging this with
en...@google.com <en...@google.com> #45
Canonical bug task has added attached cases from this bug to
Description
----------------
returns no result, while
returns the correct data.