[OSM-talk] Installing your own tileserver on Ubuntu

[Joseph Reeves]

>It is possible that one could catch the errors in slim mode and then only do the expensive diff processing for those node / ways that are >duplicate in the extracts.

Interesting, although I think this is beyond the limits of my OSM
skills. Unfortunately Austria seems to be beyond the capabilities of
my netbook; an import without --slim gives the error:

Node cache size is too small to fit all nodes. Please increase cache size

Presumably a slim import would help, but this would then fail because
of overlapping ways... I can't Google up anyone suffering that error
message before; I guess nobody else is trying to get a number of
European countries into a db on their netbook...

Thanks again,

Joseph




On 18 October 2011 16:59, Kai Krueger <kakrueger at gmail.com> wrote:
> On 10/18/11 9:31 AM, Joseph Reeves wrote:
>>
>> Hi Kai,
>>
>>> The pre-rendered tiles are stored in /var/lib/mod_tile/default. You can
>>> simply delete those files and they will automatically get rerendered the
>>> next time you view them.
>>
>> Great, thanks, that's working great.
>>
>>> I have seen that you appear to need to restart renderd (sudo
>>> /etc/init.d/renderd restart) after a new import, as it otherwise appears
>>> to
>>> still use old data (It is kind of odd, so I might have the wrong
>>> impression
>>> here).
>>
>> Sorry, I should've said in my previous email - I was assuming this to
>> be the case. Out of interest, is there any log output from renderd?
>
> sudo tail -f /var/log/syslog
>
> should give you some output of what renderd is doing, including which tiles
> it is rendering and when it has completed them
>>
>> I'm running this on a netbook so tiles take a while to be produced;
>
> I'd imagine a netbook might struggle a little with rendering tiles on the
> fly... ;-) But eventually they should be done.
>>
>>  it
>> would be interesting to see some logs so that I know it's all working
>> as I expect.
>>
>>> However, what you are trying to do is as far as I know not supported by
>>> osm2pgsql. Although it seems to be a much requested feature, I don't
>>> think
>>> osm2pgsql currently handles importing of multiple extracts. The --append
>>> option doesn't really do what you would think it does.
>>
>> I tried the append flag and got an error about an already existing way
>> - it would be good if osm2pgsql would simply ignore any ways that
>> already exist in the database. I re-ran osm2pgsql without the --slim
>> option, however, and the import was successful. I currently have
>> Bulgaria and Romania working on my netbook :)
>
> Interesting that the non-slim mode works with appending multiple extracts.
>
> It is possible that one could catch the errors in slim mode and then only do
> the expensive diff processing for those node / ways that are duplicate in
> the extracts.
>>
>> Am trying to re-import Turkey now, then onwards with bits of Europe!
>> If it all works out do you mind if I do a bit of wiki fiddling on your
>> instructions?
>
> No go ahead and improve the instructions
>>
>> Thanks again,
>>
>> Joseph
>>
>
>