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.
Hi,
I'm not sure if its just me.
But according to the zipcode..mysql files
the coordinates are listed in this order:
- longitude
- latitude.
But the schema seems to list them as:
- latitude
- longitude.
ie. the latitude and longitude needs to swap places for proximity search to work properly.
Can someone confirm this analysis is correct?
cheers
Comment | File | Size | Author |
---|---|---|---|
#3 | zipcodes.be_.mysql_.zip | 50.71 KB | Pol |
Comments
Comment #1
juicytoo CreditAttribution: juicytoo commentedI used this mysql query :
Comment #2
netsensei CreditAttribution: netsensei commentedSame here for zipcodes.be.sql.
juicytoo's trick worked perfectly to solve this.
I think we could go two ways with this:
1. change all the zipcodes in the SQL and make sure the data matches the correct columns
2. be lazy and just add juicytoo's query to the end of the affected sql files.
I'd go for 1. Should be doable with a bit of regex magic.
Comment #3
PolHere is the good file.
Comment #4
YesCT CreditAttribution: YesCT commentedI remember a recent issue about this... Please check to see if this is still a problem in the new release. If it is, reply with a new summary and set the status back to active.
Comment #5
pfrenssenThis has been fixed in #830352: postcode database files for au & be have lat/lon reversed.
Comment #6
jbfelix CreditAttribution: jbfelix commentedThank you Pol !