Create Offline Raster & Vector Maps

With OsmAndMapCreator there are many ways how to create and customize Raster & Vector maps for your needs.

In this article


OsmAndMapCreator can be used to create any maps supported by OsmAnd yourself. You can download latest version from website. OsmAndMapCreator has UI capabilities to create raster & vector maps. To create vector map you will need OSM file (*.pbf, *.osm.gz, *.osm.bz2) and to create online sqlite map file you will need a base tile url.

Raster maps (simple)

Once you selected the tiles you want to create a map from in the menu Source of tiles and they are loaded successfully in OsmAndMapCreator. You can select with right click the area you would like to preload. After that you can create .sqlitedb file in Source of tilesCreate sqlite database.

Download raster maps

Create sqlitedb maps

Vector maps (simple)

Steps to create vector map via OsmAndMapCreator UI:

  1. OSM File
  2. Select checkboxes whether you want to produce Maps including Address / Routing / Transport / Map data
  3. Select in FileCreate .obf from file.
  4. Once process is completed you will have .obf file in the working directory.

Create vector maps

More parameters how to generate vector maps could be specified in the shell .

Vector maps (shell script)

The most typical & the most powerful way to create maps used by developers is via shell script packaged within OsmAndMapCreator. It also has many other utilities methods to create some custom maps such as basemap or map with region names & boundaries (regions.ocbf).

Example script:

wget -N
unzip -d OsmAndMapCreator
OsmAndMapCreator/ generate-poi albania_europe.pbf --chars-build-poi-nameindex=3

Generation script takes only 1 file OSM file to process at a time (.pbf, .osm.gz, osm.bz2, .osm) and many optional parameters specified as --xxxxxx.

Main commandDescription
generate-obfGenerates full obf with map, address, poi, transport, routing information
generate-obf-no-addressGenerates full obf but without address information
generate-addressGenerates map with only address information
generate-poiGenerates map with only poi information
generate-mapGenerates map with only map rendering information
generate-roadsGenerates map with only routing information

All extra parameters could be found in the code in case they are not documented properly Main Utilities. All parameters are optional!

--add-region-tagsSlows down map creation process by adding to each way a region name tag where it processed. It's needed only for worldwide basemap or when you process multinational regions, in all other cases it's easier to have proper name for your file i.e. germany... , us.... If you don't have this parameter and you don't specify add this parameter, it's likely you will see non-localized road / public transport route badges in OsmAnd.
--keep-only-sea-objectsRemoves object that are not part of ocean / see, it's used to produce nautical map
--ram-processSpecifies that creation will be using RAM SQlite DB instead of disk - more information.
--srtm=<FOLDER>Specifies folder with TIF-DEM images, so information about height & slope will be encoded into roads
--rendering-types=<FILE>rendering_types.xml location with rules & OSM tags needs to be encoded in OBF - more information.
--poi-types=<FILE>poi_types.xml location with rules & OSM tags needs to be encoded in OBF for POI - more information.
--extra-relations=<FILE>OSM file with polygons like Low Emission Zones which tags should be propagated to the ways.

Note: Creating maps with batch.xml is deprecated, please use shell methods mentionned above and combine with downloads / for cycles using standard shell script capabilities.

RAM to process maps

Creating maps is memory hungry and I/O intensive. In other words: it takes very long and could run out of memory! Please check generation on small maps first. In order to give more memory to JVM, you can declare env JAVA_OPTS variable.

export JAVA_OPTS="-Xms256M -Xmx6400M"
OsmAndMapCreator/ generate-obf ....

What can you do to improve performance:

  • Use SSD disks.
  • Use multiple disks.
  • Use "in memory" processing. If you want to avoid using disk space and use only RAM to speed up process - specify --ram-process parameter. This "in memory" processing will speed up the map generation by 10-50%, but requires a lot of memory. 10% to 50% depends on the map size. Smaller maps benefit less from in memory processing than larger maps, as disk access for initial reading and final map writing plays a bigger role, while larger maps require more "calculation".

In normal "on disk" processing a nodes.tmp.odb file is created from your .osm or .osm.pbf file. This nodes.tmp.odb file is a sqlite database file and it is about 15 to 25 times as big as the original .osm.pbf file which you downloaded from So if your original .osm.pbf file is 300MB, your nodes.tmp.odb file will be 5GB to 6GB! Note that smaller maps will be around the 15x factor whereas big maps (>350MB) will end up in the 20x to 25X space increase.

With "in memory" processing this nodes.tmp.odb file will be created in your working memory. You will need "the size of the nodes.tmp.odb" + 20-25%. Please note that that you don't need to increase -Xmx parameter cause SQLite in memory won't occupy JVM memory and use only native operating memory.

Example: for a 250MB .osm.pbf a ~4.5GB nodes.tmp.odb file will be generated.

Custom vector map (tags)

OsmAnd rendering and POI search relies on information written to OBF. It has different structure than other OSM formats and optimized for mobile usage. You can inspect the contents using Binary Inspector. 3 Most important parts of OBF file are

  • Map section used for Map Rendering defined by Rendering types
  • POI section used for POI search and Object information defined by POI types
  • Routing section used for Routing defined by Routing types - same file as rendering types but has own section <category name="routing"> - routing_type.

rendering_types.xml and poi_types.xml could be overridden during map creation process in OsmAndMapCreator UI settings or as command line parameters --rendering-types=<path>, --poi-types==<path> to generate-obf (packaged with OsmAndMapCreator).

  • Main map object type (<type tag="abandoned:highway" value="track" minzoom="13"/>) is registered per OSM entity (node or way or multipolygon). There could be many main types registered per 1 entity (i.e. road + tram + route_bus), tag order will sort types within entity.
  • Additional map object type (<type tag="service" value="driveway" minzoom="13" additional="true"/>) is additional information attached for OSM entity, so in case OSM entity is not registered with main type it won't be stored inside OBF. Usually it stores information to display extra features like color, smoothness.
  • Text map object type (<type tag="int_ref" additional="text" minzoom="1" order="32"/>), stores text information about object so it could be later displayed on the map
  • entity_convert represents simple tag transformation scripts (<entity_convert pattern="tag_transform" from_tag="bridge" if_tag1="highway" if_value1="proposed" routing="no"/>). It is often used to combine tags into specific types, so it's easier to display with custom rendering style. Also it allows to give region specific tag transformation and allows to have different features rendering per country.
  • Relation tag propagation. OsmAnd doesn't index relation objects (except multipolygons - stored as area objects) but it allows to propagate, push tags from relation onto members. Obviously 1 member could have multiple parent relations and tags conflicts are possible. OsmAnd supports 3 ways to deal with conflicts: 1) combine all tags as long comma-separated line (good for rendering bus route names as a long string on the way - nameTags, namePrefix), 2) sort values and keep the highest value (good for rendering routes local vs international - relationGroupSort, additionalTags, additionalNamePrefix), 3) generates unique tags for each relation (not used for now but stores information without loss - relationGroupNameTags, relationGroupAdditionalTags, relationGroupPrefix). More information you can find in Rendering types.

Read more: usually custom vector maps combined with custom rendering style.

Raster maps (advanced)

OSM is a large database for maps, however, the necessary information is not always available there (eg deserts). Sometimes the information you need is available from other sources, such as paper maps or satellite images.

There are special programs for preparing, converting, calibrating any source maps (image format maps, pdf format, raster online maps) to OsmAnd online maps.

About some of them below.


Mobile Atlas Creator (MOBAC) is an open source (GPL) program which creates offline atlases. As source for an offline atlas Mobile Atlas Creator can use a large number of different online maps such as OpenStreetMap and other online map providers.

Just download the program, then run it.

In the format choosing dialogue pick OsmAnd SQLite or OsmAnd tile storage. SQLite is a single file with the selected area while tiles are separate pieces of the map gathered on your device. SQLite often happens to be more convenient as it is stored in one place and occupies less storage space.

Pick the map source, zoom levels, and other features. Select an area, then choose the menu 'Selection' -> 'Add selection'.

After that, you can create your SQLite file: 'Atlas' -> 'Create Atlas'.


MAPC2MAPC is a Windows program to manipulate digital maps and convert them between different platforms and software.

For example, you can convert and calibrate any image format & pdf maps to OsmAnd online map.

Video tutorial of using the program.


SASPlanet is a freeware, opensource navigation software with the capability of viewing and downloading maps and satellite images of Earth from various on-line services to OsmAnd online map.

Download the program, English guideline.

Common Issues

OutOfMemoryError issue

Issue: OsmAndMapCreator fails with message - OutOfMemoryError.

The file you try to process with OsmAndMapCreator is too large. Either try to process a smaller file, or increase the memory for OsmAndMapCreator in the .sh or .bat file. The -Xmx parameter specifies how much memory the program can consume. Settings can be different for 64bit (more than 1.5GB) and 32bit (max around 1.5GB) machines.

Empty file issue

Issue: After converting an .osm to .obf with only a POI index, the .obf is empty, although original .osm file did contain POIs.

It could be that a crucial tag was missing for OsmAndMapCreator to recognize a POI when you converted the osm from another source, like Garmin. If a point in the OSM file looks like this:

  <node id='-24' visible='true' lat='1.3094000' lon='103.7784000'>
    <tag k='created_by' v='GPSBabel-1.4.2'/>
    <tag k='name' v='Street-Soccer Court'/>

change it to contain an additional 'amenity' tag, like:

  <node id='-24' visible='true' lat='1.3094000' lon='103.7784000'>
    <tag k='created_by' v='GPSBabel-1.4.2'/>
    <tag k='name' v='Street-Soccer Court'/>
    <tag k='amenity' v='point' />

Then convert the file using OsmAndMapCreator. You can check on the OSM site what tags are good ones to use and you can also verify which tags are supported by OsmAnd.

Did this doc help you?

Privacy policy

Help us make these docs great!

All OsmAnd docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.