logo separator

[mkgmap-dev] Tiles pruned in DEM map

From Gerd Petermann gpetermann_muenchen at hotmail.com on Fri Dec 18 10:48:19 GMT 2020

Hi Carlos,

not sure if I understand what the problem is. The two screenshots show completely different tile boundaries, so they were not created from the same splitter output.


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cardavilam at gmail.com>
Gesendet: Donnerstag, 17. Dezember 2020 23:44
An: Development list for mkgmap
Betreff: [mkgmap-dev] Tiles pruned in DEM map

I build several types of map (OSM, OSM+contour lines, maps for trucks
and OSM+DEM) for the same area, using same input files. I split
country.o5m with splitter and then use the same template.args output by
splitter for all maps, just changing mapname for the different types of
map. Given that, all resulting mapsets should have the same tiles, but
tiles in DEM map are smaller than in the other types. They share part of
the boundaries (usually two of them) with other types, but other
boundaries are moved in, reducing displayed tile size. See attached
screenshots. However, file size is the same (discounting *.DEM) for each
tile in *.gmap subfolders.

Command is quite similar for OSM and OSM+DEM maps:

java -Xmx27G -ea -Dlog.config=logging.properties -jar mkgmap.jar -c
opciones_comunes $CODEPAGE --gmapi --bounds=bounds.zip
--precomp-sea=sea.zip --route --country-name=$PAIS --country-abbr=${ABR}
--area-name=$MAPA --family-name="OpenStreetMap $MAPA"
--family-id=1${FID} --product-version=$VERSION --series-name="OSM-$MAPA"
--overview-mapname=${ABR}1${FID} --overview-mapnumber=${GRUPO}1${FID}000
--name-tag-list=$NAMETAG --process-destination --process-exits
--housenumbers --reduce-point-density=4 --polygon-size-limits="24:12,
18:10, 16:0" --order-by-decreasing-area --add-pois-to-areas
--report-similar-arcs --report-dead-ends=2 --link-pois-to-ways
--location-autofill=is_in,nearest --drive-on=detect,$DRIVEON
--check-roundabouts --check-roundabout-flares --license-file=license_OSM
--copyright-file=copyright $LANGUAGE --road-name-config=${CONFIG}
--style=mio --check-styles -c $pais.args tmp/${ABR}1${FID}.txt

java --Xmx27G -ea -Dlog.config=logging.properties -jar mkgmap.jar
--dem-poly=polygons/$pais.poly --dem-dists=3312,6624,9936,13248,26512
--overview-dem-dist=128000 -c opciones_comunes $CODEPAGE --gmapi
--show-profiles=1 --bounds=bounds.zip --precomp-sea=sea.zip --route
--country-name=$PAIS --country-abbr=${ABR} --area-name="$MAPA"
--family-name="OSM $MAPA DEM" --family-id=5${FID}
--product-version=$VERSION --series-name="OSM-$MAPA-DEM"
--overview-mapname=${ABR}5${FID} --overview-mapnumber=${GRUPO}5${FID}000
--name-tag-list=$NAMETAG --process-destination --process-exits
--housenumbers --reduce-point-density=4 --polygon-size-limits="24:12,
18:10, 16:0" --order-by-decreasing-area --add-pois-to-areas
--link-pois-to-ways --location-autofill=is_in,nearest
--drive-on=detect,$DRIVEON --check-roundabouts --check-roundabout-flares
--license-file=license_OSM_${HGT} --copyright-file=copyright $LANGUAGE
--road-name-config=${CONFIG} --style=mio --remove-ovm-work-files=true -c
${pais}-DEM.args tmp/${ABR}5${FID}.txt

Both OSM and OSM+DEM maps can be downloaded from

Any idea why this happens?

More information about the mkgmap-dev mailing list