[postgis-users] Geocoding cross streets?

[Aren Cambre]

I think that *geocode_intersection* function would be perfect!

I just entered an enhancement request at
http://trac.osgeo.org/postgis/ticket/1333.

I totally understand about merging into the existing *geocode* function.
A counter-strategy might be to require the *&* symbol? But if you're
requiring that, then seems like it wouldn't be much more work for the
developer to split into cross streets rather than having postgis figure
that out upon every geocode.

Aren

On Mon, Nov 28, 2011 at 4:08 PM, Paragon Corporation <lr at pcorp.us> wrote:

> **
> It doesn't geocode cross streets or if it is its share accident.  I think
> what it's doing is just picking the first one most likely so you are
> getting at the beginning of a street with that name and it's ignoring the
> second street at best.
>
> The cross streets feature takes a different algorithm.  We do have that
> coded as a sub process in one of our projects, but it's not committed in
> tiger geocoder.  Feel free to post a ticket under tiger_geocoder
> if you are interested  in seeing it incorporated into tiger geocoder.
>
> http://trac.osgeo.org/postgis/
>
>
> Right now what we have can be relatively easily incorporated in tiger
> geocoder to be a function of the form:
>
> geocode_intersection(roadway1, roadway2, city, state, zip)
>
>
> Would that work for you?  I would hesitate to try to merge into the
> existing geocode function since I'm not sure how much unnecessary
> processing that would add if people know they aren't dealing with cross
> street addresses.
>
> Thanks,
> Leo and Regina
> http://www.postgis.us
>
>
>  ------------------------------
> *From:* postgis-users-bounces at postgis.refractions.net [mailto:
> postgis-users-bounces at postgis.refractions.net] *On Behalf Of *Aren Cambre
> *Sent:* Monday, November 28, 2011 3:14 PM
> *To:* PostGIS Users Discussion
> *Subject:* Re: [postgis-users] Geocoding cross streets?
>
> Hey, thanks!
>
> I used this query:
>
> *SELECT g.rating, ST_X(geomout) AS lon, ST_Y(geomout) AS lat, (addy).*
> FROM geocode('XXXX') as g;*
> *
> *
> where *XXXX* is replaced with strings like:
>
>    - *erin and tralee, dallas, tx*
>    - *erin & tralee, dallas, tx*
>    - *sagecanyon & sagegreen, houston, tx*
>
> Those produce lat/longs that are a few miles from the correct locations.
> *
> *
> Aren
>
> On Mon, Nov 28, 2011 at 1:33 PM, Johnathan Leppert <
> johnathan.leppert at gmail.com> wrote:
>
>> Cross-streets should be supported. Can you supply your exact query and
>> what versions of PostGIS and geocoder you are using?
>>
>> Johnathan
>>
>>  On Mon, Nov 28, 2011 at 9:26 AM, Aren Cambre <aren at arencambre.com>wrote:
>>
>>>  I have the TIGER geocoder running with PostGIS 2.0 as per
>>> http://www.letseehere.com/postgis-geocoder-using-tiger-2010-data.
>>>
>>> It seems to do well finding street addresses, but it can't seem to find
>>> cross streets. For example, if I geocode *sagecanyon and sagegreen,
>>> houston, tx*, I get a location on the other side of town. Here's a
>>> Google Map showing both: http://g.co/maps/nphp9
>>>
>>> Can I even use the TIGER geocoder for cross streets?
>>>
>>> Aren
>>>
>>> _______________________________________________
>>> postgis-users mailing list
>>> postgis-users at postgis.refractions.net
>>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>>
>>>
>>
>>
>> --
>> *Johnathan*
>> Software Engineer
>> San Francisco, California
>> *Follow me on Twitter: @iamleppert <http://twitter.com/#!/iamleppert>*
>>
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>
>>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20111128/c6c96544/attachment.html>