Closed (fixed)
Project:
Location
Version:
6.x-3.0
Component:
Data update
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Sep 2007 at 23:50 UTC
Updated:
1 Dec 2015 at 23:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bdragon commentedChanging component to Data update.
Comment #2
yesct commentedmarked #159945: US zip code map as a duplicate. [edit: i corrected a typo in the issue number, previewing this time]
Comment #3
yesct commentedmarked #174946: Canadian MapQuest links do not support postal codes as duplicate
Comment #4
yesct commentedmarked
#158833: Geocoding for France. Please:)
as duplicate
I marked #40614: Implementing Support For Ireland - Updating location.ie.inc as a duplicate, but it was for 4.x so I closed it too.
This one looks like it is to be part of a batch of data updates, but is not a duplicate:
#31191: Better Support for Austria (AT)
I marked these as need more information
#21529: UK regions not showing
#154467: We want to provude zip codes for Ukraine
Comment #5
yesct commentedrelated: I marked them as needing more information
#230421: FIPS codes in location.us.inc
#73714: Support for the Netherlands (NL) location.nl.inc location.xx.inc has a good overview of services and concerns that need to be addressed, might be relevant to more than just netherlands.
#245641: Zip codes for Denmark has more discussion about attribution of the source of the data, this time about Denmark.
#158101: UK Geocoding with google and search has an old patch for UK.
this is not about zip data updates, but is related. #214244: Some country have many location for 1 postcode
#132541: refactor google geocoding brings up geocoding
and #66887: Better geocoding support talks about it in general
related:
#128606: Malaysia is not supported
Comment #6
yesct commentedthis might be related #42901: Zipcodes are not necessarily unique WITHIN a country
Comment #7
yesct commentedmarked #242765: update US zipcodes database as a duplicate of this issue. (It had a comment http://drupal.org/node/242765#comment-1256637 about adding US zip code 92011).
Comment #8
yesct commentedrelated to #383200: Zipcodes for Austria
Comment #9
yesct commentedrelated #386058: Support for Finnish postal codes location.fi.inc (has location.fi.inc file and database dump)
Comment #10
yesct commentedmarked #399150: UK County list is not complete (Berkshire missing) as a duplicate
Comment #11
yesct commentedrelated #255995: Canadian postal codes for MySQL zipcodes table
Comment #12
yesct commentedrelated: #326665: UK cities are in state/province field (not a zip code issue, deals with counties and cities in the right fields)
Comment #13
darrellduane commented-The state for zip code 10004 is incorrect, it should be NY.
-Also, in order to facilitate proximity searches by City & State, rather than by zip code, additional fields or data should be added to catalog the latitude and longitude of centroids of City,ST combinations and centroids of States only. Perhaps an additional column should indicate whether the record is for a Zip Code, a City/State a State, or a Country.
Comment #14
da.eddy@gmail.com commentededit, sorry wrong thread.
Comment #15
yesct commentedmarked #729638: Why does location hate Stevens Point, WI (zipcodes.us.mysql wildly out of date, missing 54482, others) as a duplicate. (see that issue for details on the missing data)
Comment #16
yesct commentedmarking #661338: Longitude & latitude are swapped in zipcodes.mysql for BE and AU (location.xx.inc) as duplicate/related (see that issue for detail)
Comment #17
summit commentedHi,
http://drupal.org/node/540704 is also related. My latest admission: http://drupal.org/node/540704#comment-3085134
Wouldn't it be great to use the google gmap api as webservice, instead of keeping own lists on location as location.fr.inc for example?
I see this old code about this I think: http://drupal.org/files/issues/location-fr.patch
greetings, Martijn
Comment #18
rooby commented#830352: postcode database files for au & be have lat/lon reversed. also relates to this issue but I didn't see this one before I started that one.
That issue will sort out AU & BE having lat/lon around the wrong way and makes the formatting of the files more uniform.
I'll leave the other problems with this issue.
Also, a couple of the smaller things in here can also easily be done before the next release.
* 10004 should be NY not NJ
* Add new zipcode: 92011, Carlsbad, CA, 33.121944, -117.296944, -8, 1, us
Comment #19
rooby commentedCommitted a fix for us zipcode 10004 should be NY insteadl of NJ.
See #13.
http://drupal.org/cvs?commit=383938
http://drupal.org/cvs?commit=383940
http://drupal.org/cvs?commit=383942
Comment #20
rooby commentedCommitted a fix adding a us zipcode entry for 92011.
See #7.
http://drupal.org/cvs?commit=383948
http://drupal.org/cvs?commit=383950
http://drupal.org/cvs?commit=383952
Comment #21
ankur commentedComment #22
steveoliver commentedI am finding a zipcode not in the US database (7.x-5.x latest) -- 85295 (Gilbert, AZ), and I am guessing we may be missing others.
How do we get to the root of this issue and make sure we always have the latest zipcodes? Where does this info come from?
Comment #23
steveoliver commentedJust a patch for the missing zip I found. Note I could only find precision to the 4th decimal place (from http://www.zip-info.com/cgi-local/zipsrch.exe?ll=ll&zip=85295&Go=Go).
Comment #24
SeanA commentedRevert status & close stale issue.