[mkgmap-dev] bounds and sea on pleiades

Tue Feb 4 17:52:30 GMT 2014

Yes something went wrong ... I tried to optimize my build chain by 
parallelizing things, but I managed to schedule two processes that want 
all available RAM at the same time. That didn't go well. :p

So I killed the sea generator and will run that one later.

On 04-02-14 18:42, Patrik Brunner wrote:
> Lambertus,
>
> I've seen that the 'bounds' is already handled with the new concept:
>
>     http://osm2.pleiades.uni-wuppertal.de/bounds/latest/bounds.zip
>
> But the sea boundaries are not yet done the same way even though there 
> is a new version of that file in the date specific directory:
>
>     http://osm2.pleiades.uni-wuppertal.de/sea/latest/sea_20140127.zip
>
> Will this be done later or did something go 'wrong' with the new build 
> process of the sea boundaries ?
> ... don't want to be stressing you, it's just a question.
>
> Thanks
> Patrik
>
> On 31.01.2014 19:18, Lambertus wrote:
>> This is not hard to achieve and I'll add an easier link with the next 
>> update.
>>
>>
>> On 31-01-14 15:37, Patrik Brunner wrote:
>>> Lambertus,
>>>
>>> Actually you have a directory ./latest in both your sea and bounds 
>>> directory in which we can find the latest version of the sea and and 
>>> the bounds file.
>>>
>>> Unfortunately these files still have the date tag in the name which 
>>> makes an automatic 'fix' download of the latest boundaries quite 
>>> hard..... there's no need to change these files, but wouldn't it be 
>>> possible to have a file just called 'bounds.zip' and 'sea.zip' (and 
>>> respective for bz2 files) being a link to the actually latest file ?
>>>
>>> So one could always download the latest file from the paths 
>>> ./bounds/latest/bounds.zip and ./sea/latest/sea.zip
>>>
>>> Not sure how complex it is to achieve this during your automated 
>>> generation/preparation/publishing, but guessing from my scripting 
>>> experience it shouldn't be that hard.
>>>
>>> Thanks for having a look at this.
>>> Cheers
>>> Patrik
>>> _______________________________________________
>>> mkgmap-dev mailing list
>>> mkgmap-dev at lists.mkgmap.org.uk
>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140204/2fdb50a4/attachment.html>