Output Providers

There are several ways how to handle a tile after the rendering itself has finished. The most obvious way is to store the tile into an image file. However there are other output variants available. Each one is implemented as an output provider.

<jobs> 
    <job name="demo"> 
        <configuration>C:\maprender\configs\osm-styles\style-demo.xml</configuration> 
        <output imagetype="png"> 
            <file folder="C:\maprender\output\tiles\demo"></file>
            <ftp folder="/var/www/tiles/demo"></ftp>
            <dbCache folder="C:\maprender\output\dbcache\demo"></dbCache> 
            <sqlitedb></sqlitedb>
            <image folder="C:\maprender\output\tiles\demo"></image>
        </output> 
    </job> 
</jobs>

• File Output Provider: saves the tiles in a slippymap campatible folder structure.
• FTP Output Provider: Similar to the File Output Provider but saves the tiles over FTP directly to a server.
• DBCache Output Provider: Does not save the tiles but the result of the db queries from which the tile will be rendered. The cache can then be used to speed up rendering at the cost of massive disk space usage.
• SQLiteDB Output Provider: Saves the tiles into a single SQLiteDB database file. This can be used in some third party apps like Locus as an offline Map.
• Image Output Provider: Saves all the tiles of the given bounding box as a single big image.

All output providers are independend from each other so you can combine them anyway you like.

Configuration options

The output tag has also the optional attribute “imagetype” where you can define the image type to be used when saving the output. If you do not define this attribute png will be used as default.