Download & Extend
Location » Issues

zipcode table - lat - long reverse?

Posted by juicytoo on September 2, 2009 at 10:29pm
Project:Location
Version:6.x-3.x-dev
Component:Data update
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (duplicate)

Issue Summary

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

Login or register to post comments

Comments

#1

Posted by juicytoo on September 2, 2009 at 11:24pm

I used this mysql query :

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

#2

Posted by netsensei on September 10, 2009 at 1:38pm

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.

#3

Posted by Pol on January 31, 2010 at 10:30am

Here is the good file.

AttachmentSize
zipcodes.be_.mysql_.zip 50.71 KB

#4

Posted by YesCT on July 11, 2010 at 8:32am
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.

#5

Posted by pfrenssen on August 1, 2011 at 10:44am
Status:postponed (maintainer needs more info)» closed (duplicate)

This has been fixed in #830352: postcode database files for au & be have lat/lon reversed.

#6

Posted by Moove on October 16, 2011 at 7:36pm

Thank you Pol !