Incorrect coordinates for australian zipcodes

Slightly different issue, but I've noticed that neither of these files (your new one or the one that is shipped) can be imported because of duplicate keys....

The table is setup with country and zip as the primary keys so these will not import beyond the first two entries. As the primary key (zip) is identical in many of them - only the lat long, etc. is different

So either the zipcodes table should be setup differently, or I am missing something?

Have you changed your database settings to get this to work?

For an international site, I don't think that would work as an overall fix. In the US each city within a particular state might have many zipcodes.

So your fix will work in countries where the same zip is used in multiple cities, but not in countries where multiple zips are used for the same city.....

Just fixed the primary key issue by dropping the key. Looking at the patch now.

Actually, the problem with the dump is it doesn't specify the columns... I can't guarantee that the columns of zipcodes are in the same order...

#42901: Zipcodes are not necessarily unique WITHIN a country mentions Australia, so it might be related. Also, people searching for location.xx.inc might be interested in this issue. And, .... regarding bdragon's last comment, is some change to the sql script needed? Something to specify the column names?

Anyone, is this data update still needed?

closed. no one has responded. if someone has more information, please update the status to reopen it. thanks.