Status Update
No update yet.
Comments
je...@google.com
xa...@google.com
[Deleted User] <[Deleted User]>
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]
jh...@themeetgroup.com
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
to...@googlemail.com
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
dr...@gmail.com
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
ga...@google.com
jh...@themeetgroup.com
You can report missing postal codes to Google as described in the following support doc:
bi...@google.com
bi...@google.com
lo...@gmail.com
bi...@google.com
lo...@gmail.com
componentRestrictions: {country: "AU", postalCode: "2000"}
Has there been any movement on this issue? I have 6 maps with traffic exceeding 1000 visits per day.
au...@google.com
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
bi...@google.com
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.
au...@google.com
"country:BE" and "postal_code:1000" it continues to return zero results.
za...@google.com
formatted_address: "1000 Brussels, Belgium",
place_id: "ChIJX6UHPofEw0cRXd0IVgg8wQA",
types: ["postal_code"]
The viewport can be obtained by geocoding the country:
dr...@gmail.com
lo...@gmail.com
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
dr...@gmail.com
Above still returns 0 result.
lo...@gmail.com
xa...@google.com
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.
Description
It would be great if android library plugin would inter-op with Gradle maven-publish plugin and publish sources along side of aars. Gradle Java plugin has: java { withSourcesJar() }
Today androidx build do some hardcoding of "main" sourceset name, it would be great if we did not have to do that.https://android.googlesource.com/platform/frameworks/support/+/androidx-master-dev/buildSrc/src/main/kotlin/androidx/build/SourceJarTaskHelper.kt#36