<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16437"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial>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 </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial>if you are interested in seeing it incorporated into
tiger geocoder.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT size=2
face=Arial><A
href="http://trac.osgeo.org/postgis/">http://trac.osgeo.org/postgis/</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial>Right now what we have can be relatively easily incorporated
in tiger geocoder to be a function of the form:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial>geocode_intersection(roadway1, roadway2, city, state,
zip)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial>Leo and Regina</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial><A
href="http://www.postgis.us">http://www.postgis.us</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=251343821-28112011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B>
postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] <B>On Behalf Of
</B>Aren Cambre<BR><B>Sent:</B> Monday, November 28, 2011 3:14
PM<BR><B>To:</B> PostGIS Users Discussion<BR><B>Subject:</B> Re:
[postgis-users] Geocoding cross streets?<BR></FONT><BR></DIV>
<DIV></DIV>Hey, thanks!
<DIV><BR></DIV>
<DIV>I used this query:</DIV>
<DIV><BR></DIV>
<DIV><B>SELECT g.rating, ST_X(geomout) AS lon, ST_Y(geomout) AS lat, (addy).*
FROM geocode('<SPAN style="BACKGROUND-COLOR: rgb(255,255,0)"
class=Apple-style-span>XXXX</SPAN>') as g;</B></DIV>
<DIV><B><BR></B></DIV>
<DIV>where <B>XXXX</B> is replaced with strings like:</DIV>
<DIV>
<UL>
<LI><B>erin and tralee, dallas, tx</B>
<LI><B>erin & tralee, dallas, tx</B>
<LI><B>sagecanyon & sagegreen, houston, tx</B> </LI></UL></DIV>
<DIV>Those produce lat/longs that are a few miles from the correct
locations.</DIV>
<DIV><B><BR></B></DIV>
<DIV>Aren</DIV>
<DIV><BR>
<DIV class=gmail_quote>On Mon, Nov 28, 2011 at 1:33 PM, Johnathan Leppert
<SPAN dir=ltr><<A href="mailto:johnathan.leppert@gmail.com"
target=_blank>johnathan.leppert@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Cross-streets should be supported. Can you supply your
exact query and what versions of PostGIS and geocoder you are using?
<DIV><BR></DIV>
<DIV>Johnathan<BR><BR>
<DIV class=gmail_quote>
<DIV>
<DIV>On Mon, Nov 28, 2011 at 9:26 AM, Aren Cambre <SPAN dir=ltr><<A
href="mailto:aren@arencambre.com"
target=_blank>aren@arencambre.com</A>></SPAN> wrote:<BR></DIV></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<DIV>I have the TIGER geocoder running with PostGIS 2.0 as per <A
href="http://www.letseehere.com/postgis-geocoder-using-tiger-2010-data"
target=_blank>http://www.letseehere.com/postgis-geocoder-using-tiger-2010-data</A>.
<DIV><BR></DIV>
<DIV>It seems to do well finding street addresses, but it can't seem to
find cross streets. For example, if I geocode <B>sagecanyon and
sagegreen, houston, tx</B>, I get a location on the other side of town.
Here's a Google Map showing both: <A href="http://g.co/maps/nphp9"
target=_blank>http://g.co/maps/nphp9</A></DIV>
<DIV><BR></DIV>
<DIV>Can I even use the TIGER geocoder for cross streets?</DIV>
<DIV><BR></DIV><FONT color=#888888>
<DIV>Aren</DIV></FONT><BR></DIV></DIV>
<DIV>_______________________________________________<BR>postgis-users
mailing list<BR><A href="mailto:postgis-users@postgis.refractions.net"
target=_blank>postgis-users@postgis.refractions.net</A><BR><A
href="http://postgis.refractions.net/mailman/listinfo/postgis-users"
target=_blank>http://postgis.refractions.net/mailman/listinfo/postgis-users</A><BR><BR></DIV></BLOCKQUOTE></DIV><SPAN><FONT
color=#888888><BR><BR clear=all>
<DIV><BR></DIV>-- <BR><I><FONT color=#cccccc>Johnathan</FONT></I>
<DIV><FONT color=#cccccc>Software Engineer</FONT></DIV>
<DIV><FONT color=#cccccc>San Francisco, </FONT><FONT
color=#cccccc>California</FONT></DIV>
<DIV><I><FONT color=#cccccc><A href="http://twitter.com/#!/iamleppert"
target=_blank>Follow me on Twitter:
@iamleppert</A></FONT></I></DIV><BR></FONT></SPAN></DIV><BR>_______________________________________________<BR>postgis-users
mailing list<BR><A href="mailto:postgis-users@postgis.refractions.net"
target=_blank>postgis-users@postgis.refractions.net</A><BR><A
href="http://postgis.refractions.net/mailman/listinfo/postgis-users"
target=_blank>http://postgis.refractions.net/mailman/listinfo/postgis-users</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>