[postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block

[PostGIS]

#1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block
-----------------------------+----------------------------------------------
  Reporter:  mikepease       |       Owner:  robe         
      Type:  enhancement     |      Status:  reopened     
  Priority:  medium          |   Milestone:  PostGIS 2.0.0
 Component:  tiger geocoder  |     Version:  trunk        
Resolution:                  |    Keywords:               
-----------------------------+----------------------------------------------

Comment(by mikepease):

 For the Open Street Map geocoder, are you referring to Nominatim?
 I tried this query:

 http://nominatim.openstreetmap.org/search?q=3253+32nd+Ave+S,+Minneapolis,+MN&format=xml&polygon=1&addressdetails=1

 Interestingly, the lat/lon result for 3253 32nd Ave S looks like it has
 the same result that your Tiger geocoder does.  It places the point in the
 middle of the block instead of the end of the block.

 Out of curiousity, I tried Yahoo Maps.  Wouldn't you know it?  Yahoo also
 incorrectly puts the address in the middle of the block.

 Then, I tried MapQuest.  Same wrong answer in the middle of the block.

 So, then I tried BING Maps.  That got the right answer, like Google at the
 end of the block.

 I don't know what that tells you, but it's at least interesting to know
 that your geocoder isn't the only one behaving this way.  I wonder if
 Yahoo & Mapquest have this "squishing" effect as often as I'm seeing it
 with the Tiger geocoder.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/1052#comment:20>
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.