Closed (fixed)
Project:
Location
Version:
5.x-1.x-dev
Component:
Data update
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Jun 2007 at 04:09 UTC
Updated:
5 May 2008 at 00:32 UTC
Here is the Australian location data!
It's in a zip because I cant make tar.gz on MSXP. I just renamed it to tgz, so rename it back before you unzip.
| Comment | File | Size | Author |
|---|---|---|---|
| location.tgz | 177.37 KB | cornernote |
Comments
Comment #1
nicolash commentedWhoohoo - many thanks!
Comment #2
bradsw57 commentedI get duplicate row entries when importing the zipcode table dump. From my reading of the schema, the primary key is zip+country - which won't result in unique rows. Have you modified the zipcode table primary key to something like zip+city instead - and if so what were the performance implications, do you know?
Comment #3
cornernote commentedI added city to the primary keys. I have not tested performance, but overall I think this is a bad idea and there should probably only be one entry per postcode.
It's upto you. If you load it in, it will only insert 1 per postcode (and give you duplicate warnings), or you can add city to the PKs.
I think there should be an ID field and indexes on postcode, city, country. However it's not my project to change. Will wait and see what the authors thoughts are.
Comment #4
ivrh commentedHI.
When searching by location, I have the message: No search results; could not determine the location of the submitted postal code.
Do you have any idea of what it can be?
Thanks.
Comment #5
dpmillerau commentedWell here's a fun one. My latitude and longitude data loaded swapped. Would be good for the SQL to be unambiguous!
Comment #6
benbruscella commentedIs this patch supposed to work with Google Maps etc?
After installation, this is what I see in the options:
Country
Australia None supported.
United States
Google Maps (Terms of Use)
Yahoo! Maps (Terms of Use)
MapQuest (Terms of Use)
Comment #7
benbruscella commentedoops, my bad. seems ok.
Comment #8
bdragon commentedChanging component to Data update.
Comment #9
brmassa commentedGuys,
commited on HEAD. Soon on Location 3.
regards,
massa
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #11
OliverColeman commentedThere's what seems to be maintained data for several countries (including Australia), at http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/location/da...