<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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 class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><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>