The order the parts of the address field is printed out in confuses services like google api.

Here is an example address:

235 Saunders Drive,K6H 5V2,Cornwall,CA

This should be sent like this:

235 Saunders Drive,Cornwall,CA,K6H5V2

(removing the space from the postal code seems to make a difference)

CommentFileSizeAuthor
#2 data-prepare-address-2701493-2.patch1.02 KBgeekygnr
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

geekygnr created an issue. See original summary.

geekygnr’s picture

Status: Active » Needs review
FileSize
1.02 KB

Here is a solution that has worked for me.

NWOM’s picture

Status: Needs review » Needs work

This will cause problems with Open Street Maps (OSM Nominatim) since the postal code must be directly after the city. See my issue here for 7x.1.x-dev: #2682507: OSM Nominatim Address Parse Order - postal code needs to be directly after city

Most likely a patch will need to be done dependent on handler.

Pol’s picture

Status: Needs work » Postponed (maintainer needs more info)

Could you try with the latest dev version and report back ?

Thanks!

Pol’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)
drupalfan2’s picture

This patch is outdated.

How can I patch the same thing and change the order (postalcode after city!) in the news version (8.x-3-14) of geocoder?