Options are not changeable.

[PlusOne]

options: street_number, street, city

13, MunichRoad, Munich

example:

options: street, street_number, city

MunichRoad, 13, Munich

If you change the order, it doesnt change the order.

[rikroe]

This a a "common" problem with Google's location APIs (see here).

I found a solution (and have some working code available) that requires a second API call to Google's Places API:

1. Call https://maps.googleapis.com/maps/api/geocode/json?latlng=LAT,LON and extract the first results.placeid
2. Now call https://maps.googleapis.com/maps/api/place/details/json?key=API_KEY&placeid=PLACEID and extract results.adr_address. This call does not work without API key.
3. As this is pseudo-html code, one now needs to extract the data from XML.

Unfortunately, except for some adr_address and some other data, the original geocoding API contains the same info (especially all the address_component data) but there does not seem to be a mapping description of country-specific address formats...

@gregoryduckworth would you accept a PR with this code added? I could imagine controlling it with an additional configuration option (i.e. use_formatted_address which default to False).

On a sidenote: the house number could of course be wrong, depending on the accuracy of your location data :)

EDIT: Wow. I kinda feel I overkilled - though about it again. We of course could use the input order of the user as well... Or if we feel like, provide a Jinja template (the engine is there anyhow)... This way the second API call wouldn't be needed.

[gregoryduckworth]

Yeah, happy to accept a PR for this.