[postgis-tickets] [PostGIS] #2260: Benchmarking speed between built-in tiger normalizer and pagc_address_parser

[PostGIS]

#2260: Benchmarking speed between built-in tiger normalizer and
pagc_address_parser
----------------------------------+-----------------------------------------
  Reporter:  robe                 |       Owner:  robe         
      Type:  task                 |      Status:  reopened     
  Priority:  medium               |   Milestone:  PostGIS 2.1.0
 Component:  pagc_address_parser  |     Version:  trunk        
Resolution:                       |    Keywords:               
----------------------------------+-----------------------------------------

Comment(by woodbri):

 I started looking into writing a function:
 {{{
 standardize_address('lex', 'gaz', 'rules', 'address')
 }}}

 and there is at least one issue to be delta with. parse_address() will
 take the form "street1 @ street2 city state zip" which is for an
 intersection and this would need to be standardized into two separate
 records. This would then require throwing an error or changeing the
 function to be set returning which would require the caller to branch on
 whether it get 1 or 2 records in the result.

 If it would be useful to have a convenience function like the above that
 throws an error if it is passed an intersection, it would be pretty easy
 to all that.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2260#comment:39>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.