logo separator

[mkgmap-dev] City search problem

From Gerd Petermann gpetermann_muenchen at hotmail.com on Thu Oct 4 06:20:58 BST 2018

Hi Valentin,

no idea if we can solve that problem in mkgmap, sounds more like a problem in the Garmin software.
I suggest to use a different way to split the maps so that you don't have empty areas. In other words, don't use the admin boundary but a
vertical line to split the OSM file. I think you can use splitter for that with the polygon-desc-file option.


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von ValentinAK <valentin_k at inbox.ru>
Gesendet: Donnerstag, 4. Oktober 2018 01:58
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: [mkgmap-dev] City search problem

I release daily assemblies of all countries that were part of the ex-USSR
and several other countries ( maptourist.org <https://maptourist.org>  ).
The amount of data becomes very large and will soon reach 4GB of the maximum
size of one gmapsupp container. Therefore, I decided to divide my assembly
into two parts - Eastern and Western. I made the separation along the border
(admin_level = 3). But I found a problem when searching for cities. Now I
will try to explain what I discovered:

I prepared two parts of the OSM data with a common border and compiled
east-gmapsupp.img and west-gmapsupp.img. I use Splitter v591 & Mkgmap v4240.
Splitter processing the western part of the data makes several rectangular
areas. The data clipping boundary crossing several tiles. As a result, half
the area of ​​these tiles contains no data.
The empty space of these tiles covers a non-empty map from the eastern part.
Now I activate east-gmapsupp.img and west-gmapsupp.img in my Garmin
Nuvi-1490 and on the empty space of the described western tiles, I get a
problem when searching for all eastern cities in this area of ​​overlap.
Only the search for cities does not work. Address search and routing work
fine. I tried the same and different FID. The problem is still here.

I plan to compile more maps of many other countries, but this problem makes
it difficult to use two adjacent maps simultaneously.
What solution?

Links for try this on my fresh files:

Best regards


Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk

More information about the mkgmap-dev mailing list