id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc
1125,"pprint_addy fix display of highways, routes and other pretyabbrev",robe,robe,"To solve the highway geocoding problem I cheated a bit by just throwing the highway designations in the streetTypeAbbrev with the argument that highways don't ever have streettypes anyway that I can think of and what tiger calls a pretypeabrv, I essentially consider a streetType that happens to be in front of the streetname instead of the back.  I have a flag in streettype lookup that traps the nature of this for geocoding called isHighway.

For outputting, I also now cheat by just gluing this in front of the streetname so the pprint_addy behaves right.

I'm swaying back and forth between the decision of adding a true pretypeabrv field to norm_addy and changing pprint_addy to be aware of this field (and basically redoing a good chunk of my work),

OR  (which is sounding pretty appealing to me because I am incredibly lazy)

Just have pprint_addy check if the streetypeabrev is a highway type and then just stuff it in front of the address if it is.  That solution does make me feel a bit dirty though.  So My angel and demons are fighting (angel: ""keep clean, everything in its proper place"",  demon: ""be lazy and just stuff the remnants under the covers so no one is the wiser.  Really why do we need yet another field"").  I'm afraid my demon side is winning this game.

",defect,closed,medium,PostGIS 2.0.0,tiger geocoder,1.5.X,fixed,,