[postgis-devel] [PostGIS] #1077: Regression tests for tiger geocoder
PostGIS
trac at osgeo.org
Wed Jun 29 14:29:41 PDT 2011
#1077: Regression tests for tiger geocoder
----------------------------+-----------------------------------------------
Reporter: robe | Owner: robe
Type: task | Status: new
Priority: high | Milestone: PostGIS Future
Component: tiger geocoder | Version: trunk
Keywords: |
----------------------------+-----------------------------------------------
Comment(by robe):
There are a couple of issues. I think anything is fairgame. If you look
at Mike Pease tickets -- that gives you a general sense of the pitfall
areas:
http://trac.osgeo.org/postgis/query?status=assigned&status=new&status=reopened&component=tiger+geocoder&order=priority&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone
We are working on fixing these particularly Highway and misspellings. But
while doing so we need to make sure that
1) We don't slow down the geocoding of things that used to be fast by
adding in more checks
2) We don't break things that used to work like addresses that returned
right answers now returning wrong answers.
So as long as you have a base line of some sort -- which you would from
above that would be good enough.
I'm not even so concerned about random access because genrally I think for
speed people will sort the data in some sort of meaning full order like
zip, street etc to get faster speeds.
So first stab is just to make sure the goecoding is still right
Second stab hasn't lost speed (which is trickier to test because of
differences in caching behavior depening on sort, speed of server, and
other server stuff happening)
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1077#comment:5>
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.
More information about the postgis-devel
mailing list