[postgis-devel] [PostGIS] #1131: Make geocoder faster

[PostGIS]

#1131: Make geocoder faster
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  robe         
     Type:  defect          |      Status:  new          
 Priority:  high            |   Milestone:  PostGIS 2.0.0
Component:  tiger geocoder  |     Version:  1.5.X        
 Keywords:                  |  
----------------------------+-----------------------------------------------
 I'm working on making the geocoder faster.

 I have the reverse_geocoder pretty fast  (used to take a second or 2 for
 each, but now have that down to 20-40 ms)

 mostly by correcting the edges tlid (which was numeric making bigint like
 the others) and getting rid of use of addr.

 However this somehow screwed up the speed of the regular geocoder at least
 on my windows db. I'm almost done reworking.  I've decided to get rid of
 the use of addr altogether and the speed seems much better but I have to
 fix some regress failures resulting mostly from my mistyping of left and
 right.

 The data in addr is in most cases (if not all for roads) redundant with
 what is already in edges.  I think in 2008 the lfrom/toadd fields in edges
 were blank which I think was the main reason why addr was used.  In 2010
 they are filled in.

 If we have more than  2 addr records per tlid the interpolate would be
 screwed up anyway the way its computed right now.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1131>
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.