Opened 13 years ago
Closed 13 years ago
#1147 closed defect (duplicate)
geocoded points bunching up northwards
Reported by: | darkblueb | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.0.0 |
Component: | tiger geocoder | Version: | master |
Keywords: | Cc: |
Description
using a test set near the University of California, Berkeley - observe how the result is bunched up towards the North
Attachments (1)
Change History (6)
by , 13 years ago
Attachment: | geocodes_29jul11.png added |
---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
the data is similar to the data ref'd in #1148 ie taken directly from the rolls of the County Assessor several snapshots of which are download.osgeo dot org/postgis
I have put a recent revision of the test harness there, too alameda_geocode_2.py and for data a3.csv.bz2
comment:3 by , 13 years ago
Milestone: | PostGIS 2.0.0 → PostGIS Future |
---|
comment:4 by , 13 years ago
Milestone: | PostGIS Future → PostGIS 2.0.0 |
---|
refer to ticket #1052 for more details
Note:
See TracTickets
for help on using tickets.
Replying to darkblueb:
Without any knowledge of the data that is being used in the geocoder and the data that is being geocoded and the processes used to build the geocoder and to run the geocoding, I cannot see how anyone could respond to this ticket.