You are not logged in.

#1 2020-04-05 20:42:25

englishbob2020
Member
Registered: 2020-04-05
Posts: 5

Self created maps are not always visible on Garmin Device (Dakota 20)

I hoping to get some advice. I am trying to create my own maps for my Garmin Dakota 20. I've downloaded the .osm.pbf files for the countries I want. I have split them and then modified the 'template.args' file to have a unique family-id. I then make the map using mkgmap and the map is built. During this whole process no errors are displayed.

I then rename the gmapsupp.img file to be gmapsuppBE.img, gmapsuppFR.img etc. and place them on the microSD card in the 'Garmin' directory in the root of the microSD card. When I turn on my Dakota 20 on the map for Belgium is not visible and I don't understand why. Can someone please point me in the right direction? 

These are the commands I used for downloading the map data.

curl http://download.geofabrik.de/europe/belgium-latest.osm.pbf --output BE.osm.pbf

curl http://download.geofabrik.de/europe/france-latest.osm.pbf --output FR.osm.pbf

These are the commands I use for splitting the downloaded map data.

java -Xmx1500m -jar ../splitter-r597/splitter.jar --max-nodes=1100000 ./BE.osm.pbf 

java -Xmx1500m -jar ../splitter-r597/splitter.jar --max-nodes=1100000 ./FR.osm.pbf 

I edit the template.args file to set a unique family id. I've chosen 6324 followed by the international dialing code for the respective country 0044, 0033, 0032, 0031 etc.

user@laptop:~/Downloads/FR$ head template.args 
#
# This file can be given to mkgmap using the -c option
# Please edit it first to add a description of each map.
#

# You can set the family id for the map
family-id: 63240033
product-id: 1

# Following is a list of map tiles.  Add a suitable description

and

user@laptop:~/Downloads/BE$ head template.args 
#
# This file can be given to mkgmap using the -c option
# Please edit it first to add a description of each map.
#

# You can set the family id for the map
family-id: 63240032
product-id: 1

# Following is a list of map tiles.  Add a suitable description

I then create the maps with the following commands.

mkgmap --route --gmapsupp -c template.args --mapname=63240033 --area-name="France" --description="OSM France" --split-name-index --series-name="OSM France" --housenumbers --country-name="France" --country-abbr="FR"  --latin1 --overview-mapname="OSM France" --overview-mapnumber=63240033

and

mkgmap --route --gmapsupp -c template.args --mapname=63240032 --area-name="Belgium" --description="OSM Belgium" --split-name-index --series-name="OSM Belgium" --housenumbers --country-name="Belgium" --country-abbr="BE"  --latin1 --overview-mapname="OSM Belgium" --overview-mapnumber=63240032

What I don't understand is in the list of installed map the Belgian map is not listed but the French one is. Can someone help please?

Last edited by englishbob2020 (2020-04-06 18:39:43)

Offline

#2 2020-04-06 10:10:16

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

Your family-id contains 8 digits, which is probably out of range. Narrow it down to 4, max 5 digits?
See also this table https://wiki.openstreetmap.org/wiki/OSM_Garmin_ID to prevent overlap with other existing maps if you plan to publish your maps later.

Offline

#3 2020-04-06 10:47:28

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

I have found somewhere this:
The highest number in the family-id (FID) is 65535, which corresponds to HEX "FFFF" (4 characters).
I will add this info to the wiki table.

Offline

#4 2020-04-06 12:13:22

GerdP
Member
Registered: 2015-12-18
Posts: 1,140

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

englishbob2020 wrote:

I then create the maps with the following commands.

mkgmap --route --gmapsupp -c template.args --mapname=63240033 --area-name="France" --description="OSM France" --split-name-index --series-name="OSM France" --housenumbers --country-name="France" --country-abbr="FR"  --latin1 --overview-mapname="OSM France" --overview-mapnumber=63240033

and

mkgmap --route --gmapsupp -c template.args --mapname=63240032 --area-name="Belgium" --description="OSM Belgium" --split-name-index --series-name="OSM Belgium" --housenumbers --country-name="Belgium" --country-abbr="BE"  --latin1 --overview-mapname="OSM Belgium" --overview-mapnumber=63240032

What I don't understand is in the list of installed map the Belgian map is not listed but the French one is. Can someone help please?

1) The argument -c templates.args comes too early. Most options should appear before it.
2) It is not clear to me if you have two different directories for the two maps or not. You should have.

Offline

#5 2020-04-06 21:53:41

englishbob2020
Member
Registered: 2020-04-05
Posts: 5

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

Thanks for the pointers. I'm re-creating the maps and will let you know the results. I am creating each map from it's own directory into which I split the map data for the respective countries. I've invoked mkgmap with -c  template.args as the last parameter and the map 'numbers' as 1033 for France, 1032 for Belgium, 1031 for Netherlands etc. These are less than #ffff and are not already in use either.

I'll post my results later. Is there a specification for all these parameters? I'm wondering if the text labels I defined might also have overrun the reserved space and caused corruption? I've not looked at the source code for mkgmap but not validating input can lead to all sorts of problems (buffer/stack overflows etc.)

Offline

#6 2020-04-06 22:18:03

GerdP
Member
Registered: 2015-12-18
Posts: 1,140

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

The help http://www.mkgmap.org.uk/doc/options says

--family-id=integer
    This is an integer that identifies a family of products. Range: [1..9999]
    Default: 6324 

I found no code that actually checks this limit.
Reg. your splitter options: It is probably best to use the corresponding value for splitter, so that tiles for the map with id 1032 start with 10320001 :--mapid=10320001

Offline

#7 2020-04-07 08:34:37

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

GerdP wrote:

The help http://www.mkgmap.org.uk/doc/options says

--family-id=integer
    This is an integer that identifies a family of products. Range: [1..9999]
    Default: 6324 

I found no code that actually checks this limit.
Reg. your splitter options: It is probably best to use the corresponding value for splitter, so that tiles for the map with id 1032 start with 10320001 :--mapid=10320001

Gerd, maybe add a warning if the Fam ID > 65535 in mkgmap? All my ID's are above 9999 and they work fine. I haven't tested the 65535 limit myself but I remember that not all numbers with 5 digits were supported.

Offline

#8 2020-04-07 09:19:03

GerdP
Member
Registered: 2015-12-18
Posts: 1,140

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

Yes, a check would be good. The value is finally stored in a 16 bit field. I would assume the value is used as an unsigned 16 bit int by Garmin, but maybe values > 32767 given to mkgmap already cause problems with the current code.

Offline

#9 2020-04-07 10:50:19

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

GerdP wrote:

Yes, a check would be good. The value is finally stored in a 16 bit field. I would assume the value is used as an unsigned 16 bit int by Garmin, but maybe values > 32767 given to mkgmap already cause problems with the current code.

Glad to hear that, so I can continue labeling my maps with 20xxx for quite some years wink

Offline

#10 2020-04-07 21:20:11

englishbob2020
Member
Registered: 2020-04-05
Posts: 5

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

Still not working I'm afraid. I've made 6 maps with the following command

mkgmap --route --gmapsupp  --mapname=1031 -c template.args

and not all maps were visible

Then I tried

mkgmap --route --gmapsupp  -c template.args

And only three of the six maps I made were visible

If I download maps from garmin.openstreetmap.nl then they show up so I know the Garmin Dakota 20 is capable of handling 6 maps.

Could people possibly post their versions of how the invoke the mkgmap command please? Maybe I can learn something from them, especially if someone knows how garmin.openstreetmap.nl invokes the command.

Thanks for all responses to date.

Offline

#11 2020-04-08 00:30:03

SomeoneElse
Member
Registered: 2010-10-13
Posts: 1,353

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

When I've needed to do it, I think that rather than create separate maps I've always merged the files that I've created into one before running splitter and mkgmap.  I've not needed to do it for a while though - it's rare that I visit non-contiguous countries!

Consequently I've never worried about the family ID et al because I've only ever got one user-created map to worry about.  https://www.openstreetmap.org/user/Some … iary/38613 is something I wrote a while back; while that's not exactly what I run on a monthly basis I think it's close.  https://github.com/SomeoneElseOSM/mkgma … p_etrex.sh is similar.

Offline

#12 2020-04-08 16:54:08

englishbob2020
Member
Registered: 2020-04-05
Posts: 5

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

Thanks for the tip. I tried running split in the downloaded map data and got this:

java -Xmx3G -jar ../splitter-r597/splitter.jar --max-nodes=1100000  *.osm.pbf > output.log
Warning: --keep-complete is only used for the first input file. Further files must use higher ids.
Error: Node ids are not sorted. Use e.g. osmosis to sort the input data.
This is not supported with keep-complete=true or --problem-list
uk.me.parabola.splitter.SplitFailedException: Node ids are not sorted
        at uk.me.parabola.splitter.MultiTileProcessor.storeCoord(MultiTileProcessor.java:497)
        at uk.me.parabola.splitter.MultiTileProcessor.processNode(MultiTileProcessor.java:126)
        at uk.me.parabola.splitter.AbstractMapProcessor.consume(AbstractMapProcessor.java:82)
        at uk.me.parabola.splitter.OSMFileHandler.execute(OSMFileHandler.java:157)
        at uk.me.parabola.splitter.ProblemLists.calcMultiTileElements(ProblemLists.java:255)
        at uk.me.parabola.splitter.Main.useProblemLists(Main.java:499)
        at uk.me.parabola.splitter.Main.start(Main.java:127)
        at uk.me.parabola.splitter.Main.main(Main.java:81)

Will retry with keep-complete=false to see what happens

Last edited by englishbob2020 (2020-04-08 20:24:42)

Offline

#13 2020-04-08 17:16:51

GerdP
Member
Registered: 2015-12-18
Posts: 1,140

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

The best way is to merge the files first. Use e.g. osmconvert for that.
https://wiki.openstreetmap.org/wiki/Osmconvert

Offline

#14 2020-04-08 20:29:44

englishbob2020
Member
Registered: 2020-04-05
Posts: 5

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

Could you explain a bit more please?
Should I merge the .osm.pbf files into one big .osm.pbf file and then run split on that followed by mkgmap to create gmapsupp.img?

 
osmconvert NL.osm.pbf BE.osm.pbf LU.osm.pbf  -o Benelux.osm.pbf

Is this what you are suggesting?

Offline

#15 2020-04-08 20:36:50

GerdP
Member
Registered: 2015-12-18
Posts: 1,140

Re: Self created maps are not always visible on Garmin Device (Dakota 20)

Yes, that's what I would do.

Offline

Board footer

Powered by FluxBB