Welcome to Mobile Atlas Creator read-me file for end users.
Before January 2010 this project was known as "TrekBuddy Atlas Creator".
Mobile Atlas Creator is an open source project hosted on
SourceForge.net:
http://mobac.sf.net
Mobile Atlas Creator is under GNU General Public License Version 2
(GPL). For details on the GPL see the license file gpl.txt.
The source code is available on the SourceForge.net
for download and in the project's
source code Subversion repository.
Mobile Atlas Creator creates atlases for several applications. For example TrekBuddy and Mobile Trail Explorer (MTE), the Android applications AndNav, Maverick, Big Planet Tracks, RMaps, OruxMaps, the Pocket PC application Glopus and the commercial Windows application OziExplorer. The map image created for OziExplorer can also be used with any PNG capable image viewer (map image in one large PNG file).
This application requires that a Java SE Runtime Environment 7 or higher is installed on the computer.
If you have the choice between different Java Runtimes you should prefer the Java Runtime provided by Sun/Oracle. Especially the OpenJDK has some bugs regarding MOBAC and tends to crash on certain situations.
For reducing the color depth of downloaded tiles the library files ( jai_core.jar and jai_codec.jar ) of the "Java Advanced Imaging" (JAI) have to be present on the system respectively in the same directory as Mobile_Atlas_Creator.jar. Ready to use binary builds of the Java Advanced Imaging library can be obtained at http://download.java.net/media/jai/builds/release/1_1_3/jai-1_1_3-lib.zip
Copy or move the unzipped files to a folder where you would like to have Mobile Atlas Creator installed. On computers running Windows please make sure not to install MOBAC into Program Files sub-directory!
The application is started by executing the Mobile Atlas Creator.exe . During the first application start all necessary files and folders are automatically created by the application.
You can start MOBAC by executing the start-up script start.sh . Before starting MOBAC the first time it may be necessary to set the executable bit for start.sh e.g. by executing the following command:
chmod u+x start.sh
During the first application start all necessary files and folders are automatically created by the application.
For creating atlases compatible with AFTrack (Symbian S60) you have to select AFTrack (OSZ) as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
OSZ is a ZIP-archive. Within this zip archive a (large) number of tiles with the calibrated folder structure (coordinates) are stored. OSZ only works if each tile has got a resolution of 256x256 Pixels. So be sure to uncheck Recreate/adjust map tiles (CPU intensive).
The output format is one file for each layer in the corresponding folder.
Depending on the device free memory the file maybe not work. So more then 80000 tiles should not be used.
Sorry no further details are available for this atlas format.
For creating atlases compatible with AndNav you have to select AndNav
atlas format as format in atlas format selection dialog that appears
when starting a new atlas (menu Atlas entry New Atlas).
As atlases for AndNav do not support all features provided by Mobile
Atlas Creator the following settings are ignored when creating atlases
for AndNav:
For creating offline atlases compatible with Big Planet
Tracks (Android application) you have to select Big Planet
Tracks SQLite as format in atlas format selection dialog that appears
when starting a new atlas (menu Atlas entry New Atlas).
The atlas format BigPlanet SQLite does not support all features
provided by Mobile Atlas Creator the following settings can not be
used or are ignored when creating atlases using this output format:
For creating atlases compatible with CacheWolf you have to select CacheWolf WFL as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
Maps that have custom tile processing options set are saved as tiled images with one WFL calibration file for each tile. All processing options such as image format and tile size can be used.
In this mode automatic tiling is disabled and the same restrictions and the warning as for the OziExplorer output format apply.
The output format of an "atlas" for CacheWolf is one subdirectory per layer and within this subdirectory one PNG image and one WFL file per defined map.
For creating atlases of Creating Garmin Custom maps you have to select
Garmin Custom Map (KMZ) as format in atlas format selection
dialog that appears when starting a new atlas (menu Atlas entry
New Atlas).
Details about the Garmin Custom Map format
can be found in the Garmin
Forums
Using this atlas output format the following features are ignored when creating atlases:
The output format of an "atlas" for Garmin Custom maps is one KMZ file per layer containing all maps (max 100) as seperate JPG image files. The JPEG compression rate can be specified for each map/image using image format selector in the custom tile processing section. The Garmin Custom Map format defines a maximum image size of 1024x1024 pixels. If a map is larger it will be automatically scaled down to fit into this size. You can prevent scaling when setting the max map size in the settings dialog to 1024.
For creating atlases compatible with Glopus you have to select Glopus (PNG & KAL) or Glopus Map File (GMF) as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
Using this atlas output format the same restrictions and the warning as for the OziExplorer output format apply.
The output format of an "atlas" for Glopus is one subdirectory per layer and within this subdirectory one PNG image and one KAL file per defined map.
Within this file a (large) number of tiles with its calibrated coordinates are stored. Glopus works best if each tile has a resolution of 1024x1024 pixels. So check Recreate/adjust map tiles (CPU intensive). Width and height should be set to 1024.
The output format is one file for each layer in the corresponding folder.
For creating atlases compatible with AFTrack (Symbian S60) you have to select Glopus Map File (GMF) as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
Within this file a (large) number of tiles with its calibrated coordinates are stored. AFTrack works best if each tile has got a resolution of 256x256 Pixels. So uncheck Recreate/adjust map tiles (CPU intensive).
The output format is one file for each layer in the corresponding folder.
AFTrack can handle a maximum of 4096 tiles - so be sure not to select more.
For creating Google Earth Overlays you have to select Google Earth Overlay (KMZ) as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
Using this atlas output format the following features are ignored when creating atlases:
The Google Earth Overlay atlas format uses JPG images. The image size depends on the selected maximum map size (see settings dialog). The theoretical maximum map size for this atlas format is 25000. However it is strongly recommended not to set the maximum map size higher than 10000 (this will result in a image with uncompressed size about 286 MB).
For creating atlases of Creating Garmin Custom Maps you have to select Magellan (RMP) as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
Using this atlas output format the following features are ignored when creating atlases:
Additionally some other limitations may apply, based on which device and firmware version you are using. Mobile Atlas Creator does not chek those limitations - therefore it may work or not if you are using:
The output format of an "atlas" for Magellan is one RMP file in the atlas directory. You can directly load this file in Magellan VantagePoint or transfer it onto your device.
For creating atlases compatible with MAPLORER you have to select the Maplorer atlas format as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas). You have to choose JPG image format under Layer settings/tile format (PNG is not supported by Maplorer).
There are no specific limits on tile sizes and/or numbers; good results for hiking/biking can be obtained using zoom level 15, custom tile size of 1024x1024 (check Recreate/adjust map tiles (CPU intensive) under Layer settings. For good performance, avoid using too big or too many tiles (the maximum number of columns in Maplorer is currently 26 ('A' to 'Z'), but it is preferable to use less).
After defining the maps and layers (select region and click Add selection under Atlas Content) for the atlas, click the button Create Atlas. Once atlas download and creation has completed, all necessary files belonging to the atlas can be found in the directory atlases\[atlas name]_[current date and time] .
To install the atlas on your device, simply connect it to your PC and copy the content of the respective atlas subdirectory (i.e. all .jpg and .pos files generated) to the Maplorer directory (the one which contains maplorer.exe) on your device. Starting Maplorer on the device will automatically read all tiles and create the index map. Detailed instructions on making maps for Maplorer can be found at http://maplorer.com
For creating atlases compatible with Maverick you have to select Maverick
atlas format as format in atlas format selection dialog that appears
when starting a new atlas (menu Atlas entry New Atlas).
As atlases for Maverick do not support all features provided by Mobile
Atlas Creator the following settings are ignored when creating atlases
for AndNav:
For further information how to use offline atlases with Maverick please see Maverick Online Help on Setting up offline maps.
For creating atlases compatible with MGMaps you have to select MGMaps as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas). Select a name for the maps, this is important as you will use it to view the maps in MGMaps.
MGMapsCache MGMapsCache\cache.conf MGMapsCache\macos_10 MGMapsCache\macos_11 MGMapsCache\macos_12 MGMapsCache\macos_10\59_53.mgm MGMapsCache\macos_11\150_106.mgm MGMapsCache\macos_11\150_107.mgm MGMapsCache\macos_11\151_106.mgm MGMapsCache\macos_11\151_107.mgm MGMapsCache\macos_12\365_213.mgm MGMapsCache\macos_12\365_214.mgm MGMapsCache\macos_12\366_213.mgm MGMapsCache\macos_12\366_214.mgm
Avoid using names native to MGMaps such as google, each name used must be defined as a custom map so the directory structure below must have macos,macroad and macsat defined as custom map types.
MGMapsCache MGMapsCache\cache.conf MGMapsCache\macos_10 MGMapsCache\macos_11 MGMapsCache\macroad_11 MGMapsCache\macsat_11 MGMapsCache\macos_12 MGMapsCache\macroad_12 MGMapsCache\macsat_12
For creating atlases compatible with Mobile Trail Explorer you have to
select Mobile Trail Explorer Cache as format in atlas format
selection dialog that appears when starting a new atlas (menu Atlas
entry New Atlas).
If a map source uses an image format
different to PNG the tiles will be automatically converted to the PNG
format.
The output is one
MTEFileCache
file per atlas which contains all maps. An existing cache file can not
be updated. If you want to add maps to an existing
MTEFileCache
please use the atlas format Mobile Trail Explorer which creates
a file structure identical to JTileDownloader and then process the
maps using MTE
CacheCreator.
As atlases for Mobile Trail Explorer does not
support all features provided by Mobile Atlas Creator the following
settings are ignored when creating atlases for Mobile Trail Explorer:
For creating atlases, compatible with NaviComputer, you have to select
NaviComputer (NMAP) as format in atlas format selection dialog
that appears when starting a new atlas (menu Atlas entry New
Atlas).
After defining the maps and layers for the atlas to
be created, start atlas download and creation via the button Create
Atlas. Once download and creation has completed, the generated file
with the extension nmap can be found in the MOBAC output directory.
This *.nmap-file is the required input file for NaviComputer.
For creating atlases, compatible with nfComPass,
you have to click Atlas -> New Atlas, select nfComPass
and give your Atlas a name.
By default atlases with a
tilesize of 64x64 are created (recommended). For different tile sizes
check Recreate/adjust map tiles (CPU intensive) under Layer
settings. Set Tileformat can not be changed - it is always png. Maybe
you must tryout, what is the best tilesize for your device. Choose
your layer and zoomlevels and click Add selection. Then click Create
atlas. Once download and creation has completed, the generated
folders can be found in the MOBAC output directory. You must copy the
data from the
nfComPass.dat
to your nfComPass.dat and fill in the path to your mapdirectory. After
that, copy the folder(s) to your device. If it is possible, you should
not copy the files with Active Sync to your device.
For creating atlases compatible with OruxMaps as format you have to select OruxMaps as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
Using this atlas output format the following features are ignored when creating atlases:
The output format of an "atlas" for OruxMaps is one or more map directories in the atlas directory. You have to copy those maps onto your device (default directory: /oruxmaps/mapfiles/).
For creating atlases compatible with OSMAND you have to select OSMAND
tile storage or OSMAND SQlite as format in atlas format
selection dialog that appears when starting a new atlas (menu Atlas
entry New Atlas).
As atlases for OSMAND do not support
all features provided by Mobile Atlas Creator the following settings
are ignored when creating atlases for OSMAND:
For creating atlases compatible with Osmdroid you have to select
either Osmdroid ZIP, Osmdroid SQLite or Osmdroid
GEMF as format in atlas format selection dialog that appears when
starting a new atlas (menu Atlas entry New Atlas).
The mentioned three formats are "single file" atlases. One
of the other possible atlas formats might also be acceptable for
Osmdroid. Also, there is other software that is able to deal with GEMF
archives.
As atlases for Osmdroid do not support all features
provided by Mobile Atlas Creator the following settings are ignored
when creating atlases for Osmdroid:
For creating atlases compatible with OSMTracker you have to select OSMTracker
tile storage as format in atlas format selection dialog that appears
when starting a new atlas (menu Atlas entry New Atlas).
As atlases for OSMTracker do not support all features provided by
Mobile Atlas Creator the following settings are ignored when creating
atlases for OSMTracker:
For creating atlases compatible with OziExplorer you have to select OziExplorer (PNG & MAP) as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
As OziExplorer does not support tiled maps some features are ignored when creating atlases in this format:
The output format of an "atlas" for OziExplorer is one subdirectory per layer and within this subdirectory one PNG image and one MAP file per defined map. For opening a map in OziExplorer select the menu File → Load from File → Load from MAP file, browse to the layer directory of the created atlas and select the MAP file.
If you are only interested in the map image you can safely delete the created map file.
Mobile Atlas Creator uses a highly sophisticated and optimized algorithm for creating the PNG files for OziExplorer use. This algorithm allows to create very large maps images at low memory usage. OziExplorer and most image viewers do not use such sophisticated algorithms which can lead to the situation that you can create very large map images - but OziExplorer and other image viewers are not able to open the image.
For creating atlases compatible with PathAway you have to select PathAway
tile cache as format in atlas format selection dialog that appears
when starting a new atlas (menu Atlas entry New Atlas).
As atlases for PathAway do not support all features provided
by Mobile Atlas Creator the following restrictions apply when creating
atlases for PathAway:
For creating offline atlases compatible with RMaps
(Android application) you have to select RMaps SQLite as format
in atlas format selection dialog that appears when starting a new
atlas (menu Atlas entry New Atlas).
The atlas
format RMaps does not support all features provided by Mobile Atlas
Creator the following settings can not be used or are ignored when
creating atlases using this output format:
For creating atlases compatible with Sports Tracker(ST) you have to select Sports Tracker (NOT GPS Sportstracker) as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
Do not select Recreate/adjust map tiles.
Maximum Zoomlevel of Sports Tracker is 17, default is 13.
Copy the created atlas (the whole folder) into the following folder of youre phone (depending of the Sports Tracker version):
For changing the zoom level inside Storts Tracker press 5 to zoom in and 0 to zoom out.
For creating atlases compatible with Touratech QV you have to select Touratech QV as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
As Touratech QV does not support tiled maps some features are ignored when creating atlases in this format:
The output format of an "atlas" for Touratech QV is one subdirectory per layer and within this subdirectory one PNG image and one CAL file per defined map.
If you are only interested in the map image you can safely delete the created cal file.
Mobile Atlas Creator uses a highly sophisticated and optimized algorithm for creating the PNG files for Touratech QV use. This algorithm allows to create very large maps images at low memory usage. Touratech QV and most image viewers do not use such sophisticated algorithms which can lead to the situation that you can create very large map images - but Touratech QV and other image viewers are not able to open the image.
TBD
For creating atlases compatible with TrekBuddy you have to select TrekBuddy tared atlas or TrekBuddy untared atlas as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
After defining the maps and layers for the atlas to be created start atlas download and creation via the button Create Atlas. Once atlas download and creation has completed all necessary files belonging to the atlas can be found in the directory atlases\[atlas name]_[current date and time] .
The atlas itself consists of the atlas startup file cr.tar (tar format) or cr.tba (regular/untared format) and the subdirectories containing the different maps of the atlas. For using the atlas with TrekBuddy copy the whole directory onto your J2ME device. Then use the Load Atlas function of TrekBuddy and open cr.tar / cr.tba (in the atlas root directory).
To create atlases compatible with TwoNav software you have to select TwoNav (RMAP) as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas). Atlases created for TwoNav are stored in a format called rmap. It's a binary format that holds the same map data stored at different resolutions - in order to make zooming in and out on low performance mobile devices fast and efficient. However, this causes some restrictions which have to be taken into account:
If there are several layers in one atlas, each layer will be stored as a separate rmap file.
The easiest way to create a correct atlas content is: first select the appropriate grid zoom (combobox next to the zoom slider), then pick zoom levels from the selected grid zoom up to the zoom level of the desired most detailed level, and finally add a selection to the Atlas content by clicking on the "Add selection" button.
Rmap format also requires no gaps in a zoom level range from the maximum to the minimum selected zoom level. If there are missing zoom levels, they will be created internally by shrinking the existing downloaded tiles. If the missing zoom levels contain a lot of tiles, this operation could take a while.
Finally copy the layer.rmap file from the atlases\[atlas name]_[current date and time] folder to your TwoNav maps folder.
As TwoNav does not support all available features provided my MOBAC, some features can not be used when creating atlases in this format:
For creating atlases compatible with Viewranger(VR) you have to select Viewranger as format in atlas format selection dialog that appears when starting a new atlas (menu Atlas entry New Atlas).
Maximum Zoomlevel of Viewranger is 18, minimum is 3.
After creating youre atlas the folder structure looks like:
Now we have to Create a Folder Structure on the Device:
If you youre VR Folder is on E: it is on Symbian located in E:/ViewRanger/MapCache/_PAlbTN/
In this folder create following Subfolders, if not already present:
84,85,87,88,89,129
e.g. /ViewRanger/MapCache/_PAlbTN/84
Copy the content of "OSM" into 84, "google" into 85 and so on.
Now it looks like: E:/ViewRanger/MapCache/_PAlbTN/13/4308/2687 , 2687 is a tile
VR has different Online Mapsources which are assigned to the Numbers as shown:
Of course you can fill the Tilecache with different Maps.
I use the Open Piste Map eg. as "OSM Public Transport"
If you are missing the map provider of your choice or have other enhancement ideas for Mobile Atlas Creator feel free to open an Feature Request Ticket at SourceForge.
If have a new online map which is not available in Mobile Atlas Creator there my be change to add it. Before opening a Feature Request please take a look into the list of map sources known to incompatible with Mobile Atlas Creator.
In case of unexpected errors while executing Mobile Atlas Creator you may get presented a exception dialog containing detailed information about the problem. In such a case please create a new ticket in the Bug Tracker at SourceForge. Please add the detailed exception information and a detailed description of your last performed actions.
By default Mobile Atlas Creator records all errors of the current session into it's error log file Mobile Atlas Creator.log . This log file is located on Windows system in the directory %APPDATA%\Mobile Atlas Creator\ and on Linux/Unix/OSX system in the directory ~/.mobac/
If the recorded errors in the error log do not indicate a problem you
can activate the overall message logging mechanism of Mobile Atlas
Creator:
Download the file log4j.xml and save
it in the directory where the jar file of Mobile Atlas Creator is
installed to.
The next start Mobile Atlas Creator will create a log file in the current directory (on Windows this is usually the directory where the JAR file is located on Linux usually the profile directory). Please note that the log file is erased on each program start. If you think you have found a bug please file it in the bug tracker at SourceForge.
Mobile Atlas Creator is limited to map sources that provide their maps
if form of map tiles. Each of that map tiles has to be of size 256x256
pixels. Additionally the map source has to use the spherical Mercator
projection and the number of tiles forming the world on each zoom
level has to be one of the following values: 20, 21,
22 ... 221, 222.
For more
details see OpenStreetMap Wiki: Slippy
map tilenames, Mercator,
Height
and width of a map and Zoom levels
Due to bugs in Java you should not do the following:
The following steps are necessary if MOBAC is installed to to a directory that is not writable for reguar users:
For changing the directory configuration pattern for all users of a MOBAC installation save this file into the same directory where Mobile_Atlas_Creator.jar has been installed into and change it's name to directories.ini . For more details read the comments in this configuration file.
Usually the tile store directory where Mobile Atlas Creator saves all
downloaded images in is automatically determined.
In case you
want to select a different directory perform the following steps:
<settings>
<directories>
<tileStoreDirectory>E:/tiles</tileStoreDirectory>
</directories>
...
</settings>
This specified the windows directory
E:\tiles
as new tile store directory. The previously used tile store will not
be used anymore.
Deleting the
<tileStoreDirectory>
tag restores the old behavior (automatically tile store directory
selection).
External tools like scripts or other executable programs can be
started from the Tools menu from within MOBAC. This menu is
only visible if external programs have been configured. The advantage
of starting a program from within MOBAC is that certain information
about selected map source, selected region ... can be transmitted as
parameters to the executed program.
This allows you for
example to create your own maps (render tiles) with external tools
like OSMFILTER,
OSMCONVERT,
MAPERITIVE...
For defining an external program, create an xml file for each external program to be called. The content of the xml file has to be like one of the following examples. The file-name of the xml is not relevant - it only has to end with .xml
Demonstrates how to execute an Windows batch file.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ExternalTool> <name>Name shown in tools menu</name> <command>cmd.exe /c start .\tools\mybatch.cmd</command> <parameters>MIN_LON MIN_LAT MAX_LON MAX_LAT MIN_ZOOM MAX_ZOOM MAPSOURCE_NAME MAPSOURCE_DISPLAYNAME NAME_EDITBOX </parameters> <debug>true</debug> </ExternalTool>
Annotated sample file download
Demonstrates how to execute an regular windows program.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ExternalTool> <name>Name shown in tools menu</name> <command>C:\sample-path\program.exe</command> <parameters>MIN_LON MIN_LAT MAX_LON MAX_LAT MIN_ZOOM MAX_ZOOM MAPSOURCE_NAME MAPSOURCE_DISPLAYNAME NAME_EDITBOX </parameters> <debug>true</debug> </ExternalTool>
The most interesting section is the content of <parameters>. It contains a space separated list of parameters the specified command will be executed with. The following values can be used:
Custom map sources which uses a similar URL scheme as Google/OpenStreetMap can be added by saving for each custom map source the definition in form of an xml file in the mapsources directory.
The following section shows is an example how the xml file has to be formatted. It defines an additional map source named "Custom OSM Mapnik" which shows map tiles identical to the predefined map source "OpenStreetMap Mapnik".
Note:The name specified in there has to be unique among all available map sources within MOBAC. The list of all available map sources can be obtained via command Show all map source names in the menu Debug.
<?xml version="1.0" encoding="UTF-8"?>
<customMapSource>
<name>Custom OSM Mapnik</name>
<minZoom>0</minZoom>
<maxZoom>18</maxZoom>
<tileType>png</tileType>
<tileUpdate>None</tileUpdate>
<url>http://tile.openstreetmap.org/{$z}/{$x}/{$y}.png</url>
<backgroundColor>#000000</backgroundColor>
</customMapSource>
The most important part of this definition is the url. It is a template containing specific placeholders which are encapsulated by curly brace:
Note: If the url contains the ampersand character & you have to encode it as &. Otherwise it not be valid XML and therefore can not bo loaded by MOBAC.
Example file for download: Example custom map source.xml
Similar a WMS map source can be defined. Currently only EPSG:4326 as coordinatesystem is supported.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<customWmsMapSource>
<name>TerraServer WMS</name>
<minZoom>12</minZoom>
<maxZoom>18</maxZoom>
<tileType>JPG</tileType>
<version>1.1.1</version>
<layers>DRG</layers>
<url>http://terraserver-usa.com/ogcmap6.ashx?</url>
<coordinatesystem>EPSG:4326</coordinatesystem>
<aditionalparameters>&EXCEPTIONS=BLANK&Styles=</aditionalparameters>
<backgroundColor>#000000</backgroundColor>
</customWmsMapSource>
Example file (with comments) for download: Example custom WMS map source.xml
The same way as custom map sources map sources which consist of two or more layers can be defined as well. Note that all except the background map source layer (first in the list) must have transparent parts - otherwise layers in the list before will not be visible.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<customMultiLayerMapSource>
<name>Custom OSM Mapnik with Hills (Ger)</name>
<tileType>PNG</tileType>
<backgroundColor>#000000</backgroundColor>
<layers>
<customMapSource>
<name>Custom OSM Mapnik</name>
<minZoom>0</minZoom>
<maxZoom>18</maxZoom>
<tileType>PNG</tileType>
<tileUpdate>None</tileUpdate>
<url>http://tile.openstreetmap.org/{$z}/{$x}/{$y}.png</url>
</customMapSource>
<customMapSource>
<name>Custom transparent hillshade</name>
<minZoom>0</minZoom>
<maxZoom>18</maxZoom>
<tileType>PNG</tileType>
<tileUpdate>None</tileUpdate>
<url>http://www.wanderreitkarte.de/hills/{$z}/{$x}/{$y}.png</url>
</customMapSource>
</layers>
</customMultiLayerMapSource>
Example file for download: Example custom multi-layer map source.xml
The CloudMade map service offers a large number of OpenStreetMap based maps with different styles. Each style is accessible through it's styleID . Custom CloudMade maps can be added to MOBAC via a simple XML file containing a map name used by MOBAC and a styleID:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cloudMade>
<displayName>CloudMade blackout</displayName>
<styleID>1960</styleID>
</cloudMade>
Example file for download: Example CloudMade1960.xml
BeanShell map sources as the can be developed using MapEvaluator can be used by MOBAC. To do so place the saved BeanShell code file (file extension .bsh ) in the mapsources directory. It will be loaded on next start-up of MOBAC.
It is recommended to add a line defining the map source name (must be unique).
name = "Your map source name here";
Example file for download: Example beanshell map source.bsh
Developing a custom map pack requires at least basic Java skills. Therefore the description on how to develop a custom map pack is only part of the source code release of MOBAC. You can get the source code of MOBAC by using the latest src release available in the files section at Sourceforge or you can get it directly from the Subversion code repository using the latest trunk version.
Since version 2.0 MOBAC includes the mapsforge rendering engine. This allows MOBAC to render bitmap tiles on-the-fly using Mapsforge vector data files. Those vector data files can be downloaded pre-generated for a large number of regions world-wide. Alternatively you can convert OpenStreetMap data to mapsforge format on your own. The map rendering of the vector data can be configured using xml base render themes.
For using mapsforge vector data within MOBAC the following steps are required:
<?xml version="1.0" encoding="UTF-8"?> <mapsforge> <!-- name of the map - as shown in map source list --> <name>Custom Mapsforge</name> <!-- optional --> <minZoom>0</minZoom> <!-- optional --> <maxZoom>20</maxZoom> <!-- absolute or relative file name --> <mapFile>mapsforge-test.map</mapFile> <!-- optional default OSMARENDERER Theme --> <!-- <xmlRenderTheme>mytheme.xml</xmlRenderTheme> --> <transparent>false</transparent> <!-- text size scale factor --> <textScale>1.0</textScale> </mapsforge>
Existing atlases or locally rendered tiles can be directly integrated
into MOBAC as custom map source without having to set-up a local
web-server.
At the moment the formats used by OSMTracker,
AndNav, Maverick and OSMAND are supported. For adding such an atlas as
map source download the Example
custom tile files source.xml file, adapt the
<sourceFolder>
entry and place it in the
mapsources
directory.
Tiles can also be packed into one or more zip files and directly used
by MOBAC. For details please see the Example
custom tile zip source.xml.
Note: When working with
large ZIP files (more than 4 GB) it is required to use Java 7.
SQLite based atlas formats (RMaps, MBTiles, BigPlanetTracks, NaviComputer or OSMAND) can also be used directly by MOBAC. For details please see the Example custom tile SQLite source.xml