[Geocoding] Problems while creating your own gazetteer server

[Brian Quinion]

> Thanks for that info, indeed my osm2pgsql source was almost 2 months old.
> After a svn up evrything is fine, from that point of view at least.
>
> The good news is that I managed to get the service up and running, but I had
> run into different problems to get it there. The first one is that I get an
>
> I hope all this information is helpful for you (to update the
> documentation/code where you think is necessary) but also for others as
> well.

Thanks for all the feedback, I've worked through it and updated the
code to try to fix all the issue you mentioned.  A lot of it was just
that I hadn't been very good in committing consistent sets of files.

If you can stand the thought it might be worth updating everything and
re-indexing Romania again - there where quite a lot of changes in the
commit I've just done, some that fix some fairly significant problems.

> In the end I have another question related to the way the buildings
> are indexed: I understand that the current code doesn't process addr:* tags
> on buildings other than addr:street because of performance issues. Can it
> work just fine if the dataset is limited to a small country (like Romania)?
> And if it will work without a big performance penalty, how difficult will be
> to activate this functionality?

I think that commenting out the INSERT and RETURN lines just after the
comment 'Just be happy with inheriting from parent road only' in
gazetteer-functions.sql should be all that is required to let it do
this.  But it's not been tested.

With a small data set the performance impact should be small -
probably double the time to index building level values.  It only
really has an impact on planet sized data sets.

--
 Brian