Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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)
Comment | File | Size | Author |
---|---|---|---|
#2 | data-prepare-address-2701493-2.patch | 1.02 KB | geekygnr |
Comments
Comment #2
geekygnr CreditAttribution: geekygnr at GiantGoat Web Development Inc. commentedHere is a solution that has worked for me.
Comment #3
NWOM CreditAttribution: NWOM commentedThis 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.
Comment #4
PolCould you try with the latest dev version and report back ?
Thanks!
Comment #5
PolComment #6
drupalfan2 CreditAttribution: drupalfan2 as a volunteer commentedThis 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?