[OSM-dev] mapnik image export failures (and fixes?)

[Igor Brejc]

...(forgot to click on the "reply-to-all" button, sorry Frederik)...

Or you can take a look at Maperitive, it enables you to export bitmaps both
from OSM tiles or using a custom rendering (including one similar to
Mapnik's OSM layer).
It uses a local tile caching and download throttling so it should not
overburden the OSM server (no more than a browser, anyway).

http://www.flickr.com/photos/breki74/tags/maperitive/

p.s. as for export button on the OSM map being intended for manual jobs and
not scripting: why not add a CAPTCHA?

Igor

On Mon, Jul 19, 2010 at 9:41 AM, Frederik Ramm <frederik at remote.org> wrote:

> Mikel,
>
>
> Mikel Maron wrote:
>
>> Since the export function is linked from the main site, imo we should
>> consider it a core service that should be available at some service level.
>> Personally, we use this feature often through Map Kibera.
>>
>
> The Mapnik image export works by custom rendering your image, whereas the
> Osmarender image export, and also anything you do via
> openstreetmap.gryph.de/bigmap.cgi, works by stitching together individual
> tiles. If any of these work for you then they will be more reliable than the
> image export (the bigmap service will let you create a Perl script which you
> can then run at any time to update the image).
>
> Generally, "scraping" tiles is frowned upon, but downloading 20 or 30
> pre-rendered tiles will certainly put less load on the tile server than
> requesting a custom render.
>
> Bye
> Frederik
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20100719/07d84bd3/attachment.html>