From f19a606ce75df77756101e3df92496754711fee2 Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Wed, 10 Jul 2013 11:28:45 +0000 Subject: [PATCH] oops more mistakes in link end git-svn-id: http://svn.osgeo.org/postgis/trunk@11657 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/extras_tigergeocoder.xml | 72 +++++++++++++++++++++++++++++++++++- doc/installation.xml | 4 +- 2 files changed, 73 insertions(+), 3 deletions(-) diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml index 4ffb38bf7..b77c9640d 100644 --- a/doc/extras_tigergeocoder.xml +++ b/doc/extras_tigergeocoder.xml @@ -22,7 +22,7 @@ until release. If you have data from tiger_2010 and want replace with tiger_201 New in PostGIS 2.1.0 release is ability to install tiger geocoder with PostgreSQL extension model if you are running PostgreSQL 9.1+. Refer to for details. - Also new in PostGIS 2.1.0 is integration with pagc address standardizer C library which source can be downloaded from PAGC PostgreSQL address standardizer extension and after install and install of the libraray in your PostGIS database, you can use the function as a drop in replacement for in-built . + Also new in PostGIS 2.1.0 is integration with pagc address standardizer C library which source can be downloaded from PAGC PostgreSQL address standardizer extension and after install and install of the libraray in your PostGIS database, you can use the function as a drop in replacement for in-built . @@ -984,6 +984,76 @@ CREATE INDEX idx_tiger_data_ma_faces_countyfp ON tiger_data.ma_faces USING btree + + + Normalize_Address + + Given a textual street address, returns a composite norm_addy type that has road suffix, prefix and type standardized, street, streetname etc. broken into separate fields. This function + will work with just the lookup data packaged with the tiger_geocoder (no need for tiger census data). + + + + + + norm_addy normalize_address + varchar in_address + + + + + + Description + + Given a textual street address, returns a composite norm_addy type that has road suffix, prefix and type standardized, street, streetname etc. broken into separate fields. This is the first step in the geocoding process to + get all addresses into normalized postal form. No other data is required aside from what is packaged with the geocoder. + This function just uses the various direction/state/suffix lookup tables preloaded with the tiger_geocoder and located in the tiger schema, so it doesn't need you to download tiger census data or any other additional data to make use of it. + You may find the need to add more abbreviations or alternative namings to the various lookup tables in the tiger schema. + It uses various control lookup tables located in tiger schema to normalize the input address. + Fields in the norm_addy type object returned by this function in this order where () indicates a field required by the geocoder, [] indicates an optional field: + (address) [predirAbbrev] (streetName) [streetTypeAbbrev] [postdirAbbrev] [internal] [location] [stateAbbrev] [zip] + + + address is an integer: The street number + + + predirAbbrev is varchar: Directional prefix of road such as N, S, E, W etc. These are controlled using the direction_lookup table. + + + streetName varchar + + + streetTypeAbbrev varchar abbreviated version of street type: e.g. St, Ave, Cir. These are controlled using the street_type_lookup table. + + + postdirAbbrev varchar abbreviated directional suffice of road N, S, E, W etc. These are controlled using the direction_lookup table. + + + internal varchar internal address such as an apartment or suite number. + + + location varchar usually a city or governing province. + + + stateAbbrev varchar two character US State. e.g MA, NY, MI. These are controlled by the state_lookup table. + + + zip varchar 5-digit zipcode. e.g. 02109. + + + parsed boolean - denotes if addess was formed from normalize process. The normalize_address function sets this to true before returning the address. + + + + + + + + + See Also + + + + Pprint_Addy diff --git a/doc/installation.xml b/doc/installation.xml index 5e2185e86..7d133c822 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -1235,11 +1235,11 @@ SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep, Using PAGC address standardizer - One of the many complaints of folks is the address normalizer function function that normalizes an address for prepping before geocoding. The normalizer is far from perfect and trying to patch its imperfectness takes a vast amount of resources. As such we have integrated with another + One of the many complaints of folks is the address normalizer function function that normalizes an address for prepping before geocoding. The normalizer is far from perfect and trying to patch its imperfectness takes a vast amount of resources. As such we have integrated with another project that has a much better address standardizer engine. This is currently a separate project, which is a subproject of PAGC. The source code for this PostgreSQL standardizer extension can be downloaded from PAGC PostgreSQL Address Standardizer. To use this new normalizer, you compile the pagc extension and install as an extension in your database with: CREATE EXTENSION address_standardizer; - Once you install this extension in the same database as you have installed postgis_tiger_geocoder, then the can be used instead of . The other nice thing about this extension is that its tiger agnostic, so can be used with other data sources such as international addresses. + Once you install this extension in the same database as you have installed postgis_tiger_geocoder, then the can be used instead of . The other nice thing about this extension is that its tiger agnostic, so can be used with other data sources such as international addresses. -- 2.40.0