[Geocoding] Problems while creating your own gazetteer server
cipriantalaba at gmail.com
Tue Dec 1 20:25:46 GMT 2009
On Sat, Nov 28, 2009 at 11:05 PM, Brian Quinion <
openstreetmap at brian.quinion.co.uk> wrote:
> 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.
I have restarted from scratch using new code and instructions and things
have gone a lot smoother. I have not encountered major issues, usually
copy-paste worked great :). Nice work!
> > 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:*
> > 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
> > And if it will work without a big performance penalty, how difficult will
> > 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.
I will try that pretty soon, and I will let you know how things are going.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Geocoding