<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16437"></HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space">
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011>Rene,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011>The PostGIS tiger geocoder portion still works
fine with PostGIS 1.5. In fact for production use, we are using
it against PostGIS 1.5 for some of our clients.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011>Given you have loaded your data already, and if all you
need is a reverse geocoder, might be easiest to look at what we have int he
reverse geocoder function and see what you can use of
it.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011> I think the reverse geocoder function is fairly
standalone except the assumptions about the tables.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011>The tiger geocoder has loading scripts. We changed some
of the field names to be generic like stripping off those year designators in
all the columns that census found the need to add in so that we could reuse much
of the existing infrastructure from before and not have to rename the fields
each year.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011>Aside form that the structure is the same as
tiger.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011>As far as the speed of the reverse geocoder. I
haven't stress tsted it that much and we needed it to run on commodity
windows xp boxes with about 2-4GB ram and 3.5 GHz processor. On those we
get about 60 ms per call. It also varies how close the items you are
geocoding are as I recall since data already loaded in memory seems to be more
easily accessible.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011>Thansk,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN
class=683282820-18102011>Regina</SPAN></FONT></DIV>
<DIV dir=ltr align=left><BR></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> René Fournier [mailto:m5@renefournier.com]
<BR><B>Sent:</B> Tuesday, October 18, 2011 1:53 PM<BR><B>To:</B> PostGIS Users
Discussion; Paragon Corporation<BR><B>Subject:</B> Re: [postgis-users] Tiger
Line 2010 - Edges<BR></FONT><BR></DIV>
<DIV></DIV>Hi Regina,
<DIV><BR></DIV>
<DIV>Yes, I was looking at that project, and it looks awesome. However, I'm not
yet running PostGIS 2.0. I only really need reverse-geocoding for the US (I've
gotten it working in Canada -- thanks). Until recently, it seemed like I was
close to end -- since I can get the state and then nearest street. I'm just
missing the city/town. All the other features of the PostGIS Tiger Geocoder
aren't really needed by me.</DIV>
<DIV><BR></DIV>
<DIV>However, it appears now that simply getting the town/city for any given
street is fairly complex due to the broken-up nature of the Tiger Line data…
Which makes me wonder if I shouldn't just jump into PostGIS 2.0. A couple
questions:</DIV>
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px"
class=webkit-indent-blockquote>
<DIV><BR></DIV>
<DIV>1. Is the current prerelease version of PostGIS 2.0 relatively
stable?</DIV>
<DIV><BR></DIV>
<DIV>2. Since Macports doesn't yet offer PostiGIS 2.0, is there a Mac binary
distribution you can recommend? (<A
href="http://www.kyngchaos.com/software/postgres">http://www.kyngchaos.com/software/postgres</A>
has a nice package of everything, except PostGIS 2.0...) Or should I build
from source? Although I've compiled various packages in the past, I'm trying
to avoid it now in order to simplify and automate the my MAMP-stack build
process -- which is why I'm fond of Macports.</DIV>
<DIV><BR></DIV>
<DIV>3. I have downloaded all the Tiger Line 2010 data (~40GB compressed) --
is it relatively easy to get all that data into a fresh PostGIS
2.0?</DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Now, having said I only *really* need reverse-geocoding for USA, I wouldn't
be unhappy to have forward-geocoding if it wasn't too painful to get working.
One important thing I need though is high performance reverse-geocoding. On my
Core i7 laptop, I can reverse-geocode ~500/second… Can I expect similar
performance from the Tiger Geocder in PostGIS 2.0?</DIV>
<DIV><BR></DIV>
<DIV>So for so many questions. Although I already really love the design of
Postgresql and the power of PostGIS, it's been one long learning curve getting
to this point (which I thought was near the end). Looks like there's a ways to
go.</DIV>
<DIV><BR></DIV>
<DIV>Thanks.</DIV>
<DIV><BR></DIV>
<DIV>…Rene</DIV>
<DIV><BR></DIV>
<DIV><BR>
<DIV>
<DIV>On 2011-10-18, at 11:26 AM, Paragon Corporation wrote:</DIV><BR
class=Apple-interchange-newline>
<BLOCKQUOTE type="cite">
<DIV>Rene,<BR><BR>Did you see the email Leo had posted<BR><BR><A
href="http://www.postgis.org/pipermail/postgis-users/2011-October/031132.html">http://www.postgis.org/pipermail/postgis-users/2011-October/031132.html</A><BR><BR>The
reverse_gecoder packaged with PostGIS 2.0 Tiger 2010 does output
the<BR>city names.<BR><BR>As Dan pointed out -- you need to join with the
faces to get that. Faces<BR>also helps for determining which side of
street a point falls in.<BR><BR>-- I've reposted Leo's email for
completeness<BR><BR>Please let us know if anything is
unclear.<BR><BR>Thanks,<BR>Regina<BR>http://www.postgis.us<BR><BR>--- LEO's
email ---<BR><BR>Actually we implemented a reverse geocoding function too for
tiger 2010.<BR>That might be more what you are looking
for.<BR><BR>http://trac.osgeo.org/postgis/browser/trunk/extras/tiger_geocoder/tiger_2010<BR>/geocode/reverse_geocode.sql<BR><BR>The
function usage is described
here:<BR><BR>http://www.postgis.org/documentation/manual-svn/Reverse_Geocode.html<BR><BR>As
far as installing the functions. A lot fo the functions
have<BR>dependencies on other functions withing tiger schema. <BR><BR>If
you download the latest PostGIS 2.0 tar ball, that might be the easiest<BR>way
to get started.
<BR>http://www.postgis.org/download/postgis-2.0.0SVN.tar.gz<BR><BR>There is a
create_geocode.sh/bat scripts that install all the functions in<BR>the
extras\tiger_geocoder\tiger_2010<BR> folder and a README which I think is
more or less up to date detailing<BR>installation
etc.<BR><BR>Leo<BR>http://www.postgis.us<BR><BR>-- END
Email<BR><BR>-----Original Message-----<BR>From:
postgis-users-bounces@postgis.refractions.net<BR>[mailto:postgis-users-bounces@postgis.refractions.net]
On Behalf Of Dan<BR>Putler<BR>Sent: Tuesday, October 18, 2011 12:55 PM<BR>To:
PostGIS Users Discussion<BR>Subject: Re: [postgis-users] Tiger Line 2010 -
Edges<BR><BR>Hi Rene,<BR><BR>The edges also include TFIDL and TFIDR fields.
These are the foreign keys<BR>that identify the topological faces on the left-
and right-side of an edge.<BR>If you combine this with the attribute data of
the TIGER FACE layers (the<BR>topological faces), you can then determine the
"place" <BR>(city, town, or Census Designated place) FIPS code associated with
the<BR>topological face that is bounded by a road edge. To get the name of
the<BR>"place", you then need to use the TIGER PLACE layers. However, many
road<BR>segments don't have road segments that fall into a "PLACE", so you
need to<BR>devise another strategy to deal with them.<BR><BR>All in all,
working with TIGER data is not straight forward.<BR><BR>Dan<BR><BR>On
10/18/2011 09:24 AM, René Fournier wrote:<BR>
<BLOCKQUOTE type="cite">Having imported the Edges shape files, I'm able to
get quickly find the<BR></BLOCKQUOTE>closest street to a given latlng point
(reverse-geocode). From this row, I<BR>get the street name and house number
ranges, and state (FIPS code) -- but<BR>not the city name. Any suggestions on
the best way to find the town/city?<BR>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">…Rene<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE
type="cite">_______________________________________________<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">postgis-users mailing list<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">postgis-users@postgis.refractions.net<BR></BLOCKQUOTE>
<BLOCKQUOTE
type="cite">http://postgis.refractions.net/mailman/listinfo/postgis-users<BR></BLOCKQUOTE><BR>_______________________________________________<BR>postgis-users
mailing
list<BR>postgis-users@postgis.refractions.net<BR>http://postgis.refractions.net/mailman/listinfo/postgis-users<BR><BR><BR>_______________________________________________<BR>postgis-users
mailing
list<BR>postgis-users@postgis.refractions.net<BR>http://postgis.refractions.net/mailman/listinfo/postgis-users<BR></DIV></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>