Assigned
Status Update
Comments
ne...@gmail.com <ne...@gmail.com> #2
Why do you expect the suite/apartment to be shown?
Please readhttps://developers.google.com/maps/faq#geocoder_queryformat
It looks like suites/apartments are not taken into account for address formatting.
Please read
It looks like suites/apartments are not taken into account for address formatting.
pe...@google.com <pe...@google.com>
na...@gmail.com <na...@gmail.com> #3
Support for subpremise elements (apt. / suite) is limited. Place Autocomplete is not intended to support these universally.
Geocoding API will find these places, and return subpremise elements in address_components:
9500 Bryn Mawr Avenue #650:
https://google-developers.appspot.com/maps/documentation/utils/geocoder/#q%3D9500%2520Bryn%2520Mawr%2520Avenue%2520%2523650%2520Redlands%26nfw%3D1
1403/648 Bourke Street:
https://google-developers.appspot.com/maps/documentation/utils/geocoder/#q%3D1403/648%2520Bourke%2520Street%26nfw%3D1
130 Bowdoin st., apt. 1010:
https://google-developers.appspot.com/maps/documentation/utils/geocoder/#q%3D130%2520Bowdoin%2520st.%252C%2520apt.%25201010%26nfw%3D1
Geocoding can be used as a fallback behind Autocomplete for these queries, the Geocoder Tool athttps://google-developers.appspot.com/maps/documentation/utils/geocoder/ does this to some extend: if you hit Enter without picking a suggestion, your input is sent to the Geocoding service. This helps with 1st and 3rd examples above.
If you need to support suite/apt beyond that, there is a somewhat more complex fallback option:
- use the placeIdOnly option of Autocomplete class to capture the suggestion's description (e.g. "1403/648 Bourke Street Melbrourne, Victoria, Australia")
- match this description against a set of regular expressions to detect suite/apt in them, e.g. "\d+/\d+.*Australia" to detect 123/45 ... Australia)
- if there is a match, send the description to the Geocoding service, otherwise, request details for by Place ID
This can still be accomplished without coding your own Autocomplete widget.
Geocoding API will find these places, and return subpremise elements in address_components:
9500 Bryn Mawr Avenue #650:
1403/648 Bourke Street:
130 Bowdoin st., apt. 1010:
Geocoding can be used as a fallback behind Autocomplete for these queries, the Geocoder Tool at
If you need to support suite/apt beyond that, there is a somewhat more complex fallback option:
- use the placeIdOnly option of Autocomplete class to capture the suggestion's description (e.g. "1403/648 Bourke Street Melbrourne, Victoria, Australia")
- match this description against a set of regular expressions to detect suite/apt in them, e.g. "\d+/\d+.*Australia" to detect 123/45 ... Australia)
- if there is a match, send the description to the Geocoding service, otherwise, request details for by Place ID
This can still be accomplished without coding your own Autocomplete widget.
rb...@google.com <rb...@google.com> #4
Reopening as Feature Request, please star this issue if you are interested.
The resolution for the much greater problem inhttps://issuetracker.google.com/35823492 will likely make it more visible that Place Autocomplete does not support subpremise results. As explained in https://issuetracker.google.com/110910555#comment2 the current best approach for subpremise results is to use the Geocoding API.
The resolution for the much greater problem in
Description
cloud partner for tons of lightweight (and heavyweight) applications. Presumably it would scale well
using GAE, and it would provide a language independent (modulo the web's JavaScript) and efficient
WebApp platform using CouchApp. It could also host a thin layer to Google's other services (e.g.,
Google Docs), as long as they provide JSON. It would be a nice alternative to the usual
JRubyOnRails fare for those who want something less elaborate and more relaxing, or those apps
which do not need all the bells and whistles of full ROR.