zipcode table - lat - long reverse? [#566792]

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

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

juicytoo CreditAttribution: juicytoo commented 2 September 2009 at 23:24

I used this mysql query :

UPDATE zipcodes SET latitude =(@temp:=latitude), latitude = longitude, longitude = @temp

Comment #2

netsensei CreditAttribution: netsensei commented 10 September 2009 at 13:38

Same 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

Pol

the/that

Brussels

CreditAttribution: Pol commented 31 January 2010 at 10:30

File	Size
zipcodes.be_.mysql_.zip	50.71 KB

Here is the good file.

Comment #4

YesCT CreditAttribution: YesCT commented 11 July 2010 at 08:32

Status:

Active

» Postponed (maintainer needs more info)

I 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.