<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Thanks for the anwser Stephen and Regina,<br></div><div class="gmail_default" style="font-family:monospace,monospace">it really helps to provide some broader context about a project history and purpose.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace">@Stephen I'll contact you in private about that.<br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Cheers,<br></div><div class="gmail_default" style="font-family:monospace,monospace">Rémi-C<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-06-17 7:30 GMT+02:00 Regina Obe <span dir="ltr"><<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> On Thu, Jun 16, 2016 at 6:10 AM, Rémi Cura <<a href="mailto:remi.cura@gmail.com">remi.cura@gmail.com</a>> wrote:<br>
<br>
> Hey dear list,<br>
> I'm currently considering extending postgis geocoder.<br>
<br>
> I have two needs:<br>
> - to work with French data<br>
</span> > - to perform temporal geocoding (you give an addresses and a date, you<br>
<span class="">get geographic position).<br>
<br>
> For the moment I'm trying to understand how the geocoder works with USA<br>
data.<br>
<br>
> I imported Massachusetts for a test, and everything seems okay except<br>
that my tiger.state table is empty, which prevents geocoding.<br>
<br>
> Notwithstanding the import step, and the adress normaliser, it seems to<br>
boil down to a large query in the function tiger.geocode_address().<br>
<br>
<br>
> I would be delighted to have some pointers on the design of the<br>
postgis_tiger_geocoder extension.<br>
</span>> In perticular, I don't understand the address standardizer business at<br>
<span class="">all (yeah, I found some doc, no, I don't understand it well)<br>
<br>
<br>
> Many thanks for help,<br>
> Cheers,<br>
> Rémi-C<br>
<br>
</span>Just adding to what Steve has already said.<br>
<br>
Don't try to use the postgis tiger geocoder as a model of how to set up a<br>
geocoder.<br>
The structure of it is very tied to how the US Census Tiger data is setup.<br>
The irony is because it is setup like US Census, I think people try to use<br>
it for more than a geocoder and I get bug reports on fields I ignored<br>
because they really aren't relevant as far as geocoding is concerned or not<br>
relevant to me (in other moneywise ways). I can't blame them since I do use<br>
it myself on other projects for more than just geocoding. E.g. census tract<br>
work or just joining with the states, counties etc when I need a county<br>
list.<br>
<br>
If I had started from scratch instead of inheriting the code this is not how<br>
I would do it.<br>
But without enough traction of people willing to devote time/fund a more<br>
generic geocoder, the more globally useful solution will not go anywhere.<br>
<br>
<br>
Thanks,<br>
Regina<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
postgis-devel mailing list<br>
<a href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/postgis-devel</a></div></div></blockquote></div><br></div>