cartodb4/data-services
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

postal-codes

Browse Source
This commit is contained in:
Carla 2014-08-26 11:24:43 +02:00
parent b57b9679dc
commit 8482759057
1 changed files with 43 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

65
geocoder/postal-codes/README.md
View File

@ -3,8 +3,14 @@ Postal code geocoder (polygons)
### Function
By following the next steps a table is populated with zipcodes from Australia, Canada, USA and France (identified by iso3) related with their spatial location in terms of polygons.
### Creation steps
1. Import the four files attached in the section "Datasources".
2. Run sql/build_data_table.sql. Notice that table "postal_code_polygons" should exist in advance with columns: _the_geom_, _adm0_a3_ and _postal_code_.
### Data Sources
Australian polygons - http://www.abs.gov.au/AUSSTATS/abs@.nsf/DetailsPage/2033.0.55.0012011?OpenDocument
@ -17,45 +23,60 @@ USA polygons - http://www2.census.gov/geo/tiger/TIGER2013/ZCTA5/tl_2013_us_zcta5
French polygons - http://www.data.gouv.fr/dataset/fond-de-carte-des-codes-postaux
All countries points [GeoNames](www.geonames.org) - http://download.geonames.org/export/zip/allCountries.zip
### Preparation details
The names of the imported files are:
- doc for Australia table
- gfsa000a11a_e for Canada table
- tl_2013_us_zcta510 for USA table
- codes_postaux for France table
# Postal code geocoder (points)
Download the allCountries.zip file from [GeoNames](www.geonames.org). Import and rename the table as tmp_zipcode_points. You can follow the manual process explained below instead.
### Function
This dataset includes data for the following countries:
````
CH, ES, GU, ZA, MX, SJ, NL, RU, AX, TH, AR, MY, RE, LK, GB, IS, GL, JE, DK, IN,
SI, GP, MQ, BR, SM, BG, NZ, MP, CZ, DO, MD, PK, TR, VI, BD, GG, LT, PM, MC, US,
IT, LU, SK, LI, PR, IM, NO, PT, PL, FI, JP, CA, DE, HU, PH, SE, VA, YT, MK, FR,
MH, RO, FO, GF, AD, HR, DZ, GT, AU, AS, BE, AT
````
By following the next steps a table is populated with zipcodes of different countries (identified by iso3) related with their spatial location in terms of points.
The columns that are loaded are the following ones:
This dataset includes data for the following countries:
- field_1: corresponding to ISO2
- field_10: corresponds to latitude
- field_11: corresponds to longitude
- field_2: corresponds to ZIP code
````
CH, ES, GU, ZA, MX, SJ, NL, RU, AX, TH, AR, MY, RE, LK, GB, IS, GL, JE, DK, IN,
SI, GP, MQ, BR, SM, BG, NZ, MP, CZ, DO, MD, PK, TR, VI, BD, GG, LT, PM, MC, US,
IT, LU, SK, LI, PR, IM, NO, PT, PL, FI, JP, CA, DE, HU, PH, SE, VA, YT, MK, FR,
MH, RO, FO, GF, AD, HR, DZ, GT, AU, AS, BE, AT
````
1. Georeference the table using field11 as longitude and field10 as latitude in order to construct the_geom.
### Creation steps
2. Add column iso3 (text) and run sql/build_zipcode_points_table.sql.
1. Download the allCountries.zip file from [GeoNames](www.geonames.org). Import and rename the table as tmp_zipcode_points. You can follow the manual process explained below instead.
The columns that are loaded are the following ones:
field_1: corresponding to ISO2
field_10: corresponds to latitude
field_11: corresponds to longitude
field_2: corresponds to ZIP code
2. Georeference the table using field11 as longitude and field10 as latitude in order to construct the_geom.
3. Add column iso3 (text) and run sql/build_zipcode_points_table.sql.
**Alternative manual process**
1. Open the allCountries.txt file with Excel an add a new row on top.
Open the allCountries.txt file with Excel an add a new row on top. Delete columns C-I and L.
2. Delete columns C-I and L.
In the first row, add the following columns: iso2, zipcode, lat, long.
3. In the first row, add the following columns: iso2, zipcode, lat, long.
Import the file ignoring step 2.
4. Import the file ignoring step 1.
### Data Sources
All countries points [GeoNames](www.geonames.org) - http://download.geonames.org/export/zip/allCountries.zip
### Preparation details
_The big size of the dataset may cause interruptions in the processing of the coordinates after uploading the file, manipulating the file before importing is a faster workaround._