Ticket #1460 (new defect)

Opened 17 months ago

Last modified 5 months ago

Tiger Geocoder can't handle concatenated street names

Reported by: arencambre Owned by: robe
Priority: medium Milestone: PostGIS Future
Component: tiger geocoder Version: trunk
Keywords: Cc: aren@…, woodbri

Description

In tx_edges, the street name is S Belt Line Rd. I can't geocode if my data instead has S. Beltline.

This works:

SELECT ST_AsEWKT(geomout) FROM geocode_intersection('S. Belt Line', 'Dividend', 'TX', 'Coppell') ORDER BY rating ASC LIMIT 1;

This gives no results:

SELECT ST_AsEWKT(geomout) FROM geocode_intersection('S. Beltline', 'Dividend', 'TX', 'Coppell') ORDER BY rating ASC LIMIT 1;

Change History

Changed 17 months ago by robe

  • milestone changed from PostGIS 2.0.0 to PostGIS Future

this one is an even messier one to deal with as there are many streets that have road types as part of their name.

Changed 16 months ago by arencambre

OK, but note that the road type isn't being concatenated with the name here. This is where the name in the database is Belt Line Rd, but the name that I was trying to geocode was Beltline Rd..

I think you may have a point with roads like Buffalo Speedway in Houston. Speedway is the apparent road type, although the road is never referred to as just Buffalo. (Truly, the road is indistinguishable from other low speed, Houston-area inner loop collectors.)

Changed 5 months ago by woodbri

  • cc woodbri added
Note: See TracTickets for help on using tickets.