Dont worry, that wouldn’t make any difference, so you can still render them with one ID and give each country mapset another FID. The family IDs are stored in the index files, not in the tiles.
There might be a problem, if you put two overlapping country mapsets with duplicate tile img on your GPS. But maybe this was already an issue.
Great!
I could rename the tiles before combining them… will that work?
Im not sure if this is necessary and if there are issues at all, lets first see if it works. If I put two neighbouring and overlapping country mapsets on my GPS I dont see any problem (and I havent heard anyone complaining too).
I only know there was an issue with my OFM maps, when you put two identical mapsets of different version dates on your GPS, the map becomes invisible. Maybe it is caused by an index problem?
No. It’s not just the file name; the tile id is also embedded in the file.
Ok, so no renaming of tile id’s.
How about the typ files? These have now the family id, should the typ file name be updated for each country?
Yes. Why: when combining more than one map in a single gmapsupp.img file you can’t have two different files with the same name inside (a typ file is incorporated in an img file).
-For the typ file name you can use %FID%.typ
-you copy the “master” typfile.txt to %FID%.txt
-mkgmap will automatically convert this FID.txt to FID.typ with the right family ID (dont have to adapt the txt typ file first).
Example (dos batch):
set FID=10143
set typfile=%DIR%\resources\%FID%.txt
copy %DIR%\resources\10140.txt %typfile%
set argsfile=mkgmap.args g:\Maps\%FID%*.img
java -Xmx8000m -jar %MKGMAP% --family-id=%FID% -c %argsfile% %typfile%
First attempt, be nice 
How does this look?
http://osm.pleiades.uni-wuppertal.de/garmin/generic/25-03-2014/f60af8b8fd9782fc7f68562e1a471166
/me should be in bed hours ago…
I’m afraid something went wrong there Lambertus.
The FID does not match with the index files.
I suppose you used 23108 for FID, but in the gmapsupp.img I read FID 39328?
In the nsi files the French and Spanish accents are messed up. Something wrong with the codepage I guess.
Yes, 23108 is the combination of family base id 23 (generic map) and country code 108 (Burundi). I’ll check the gmapsupp.img FID generation tonight, hopefully.
Basecamp doesn’t seem to like the Windows installer either…
yes, same Family ID 39328 is in the Mapsource index files. Dont know how it got there 
Maybe you’ve you used a FID in you mkgmap args list as well as in the --family-id java command?
Another thing what we must watch for is the family name, which is now OSM generic routable(Burundi_25-03-2014).
This version is installed at “C:\Garmin\Maps\OSM generic routable(Burundi_25-03-2014)”
The next version has the same ID but it will be installed in a different folder, eg C:\Garmin\Maps\OSM generic routable(Burundi_09-04-2014).
I’m not sure the uninstaller will find and uninstall the previous version because it has another Family name (but same FID).
Of course we can adapt the uninstaller but I think it is better always use the same family name for a mapset:
-The family name should get OSM generic routable(Burundi) without date.
-Other parameters like series name and description will get OSM generic routable(Burundi_25-03-2014)
In your combine.php you use “description” string for all those parameters, maybe add a different one for “family name” (without $version)
In a next update the installer will remove the previous version, like it has done before.
It is also possible to integrate the uninstaller with the installer, now you get two popup windows which is confusing.
I think I can fix this (see your e-mail and the mkgmap list).
Good points, all of them. Thanks, ligfietser.
I see you’re looking over my shoulder 
If you want to see the latest development: /data/garmin/scripts/test/
But, perhaps you already found it?
Yeah I already checked it out, not saying that I understand it all
BTW noticed some typos in the US state list, check Florida, Illinois, North Carolina
Heh, it was late and I was tired. Not a good combo I guess 
Re the problem with the family-id. This is the commandline:
java -Xmx6144M -jar mkgmap.jar
--index
--overview-mapname=23108000
--overview-mapnumber=23108000
--family-name='OSM generic routable(Burundi)'
--family-id=23108000
--series-name='OSM generic routable(Burundi_08-04-2014)'
--latin1
--description='OSM generic routable(Burundi_08-04-2014)'
--product-id=6
--tdbfile
--nsis
--copyright-message='Map data © openstreetmap.org and contributors'
--gmapsupp 63*.img ovm_63*.img
This is what JaVaWa GMTK says:
I think the family-id overflows.
So, how about:
family id: 23 (generic map)
product id: 108 (Burundi)
overview map: 23108000
At least, this is how I think a /family/product/ id is intended to work…
Edit:
Hmm, that’s not what the Mkgmap documentation says:
product id: 23108 (generic map/Burundi)
Edit:
Yes, that’s better. GMTK doesn’t complain anymore and BaseCamp shows the map. Guess I wrong about this. 
Yep, family-id 23108000 are too many digits FID=23108 / PID=1 should work, hope you have enough unique ID numbers? The mapnumber should have 8 digits, so 23108000.img for the overview map is ok.
BTW Multiple PID’s for one FID doesnt work either.
Ah, that’s why my maps have all different FID’s, I forgot. Guess the MapSource programming team never understood how to properly implement families with products, tssk. 
The family ID should be in the range from 1 to 65535 (because it’s stored as a 16 bit uint in the TDB file).
Don’t use 2041; that’s the family ID of the global basemap in BaseCamp.
multiple PID’s were only used for special combined maps like the old Bluechart, or for maps without a FID.
New attempt:
http://osm.pleiades.uni-wuppertal.de/garmin/generic/08-04-2014/2a8075f123ad0f288ac168d572a74125/
Both BaseCamp and JaVaWa GMTK don’t complain. I would appreciate it if someone with OSX can check out the Mac version. I haven’t checked on the GPS yet too, my GPSmap 60 isn’t feeling well since I dropped it on the road at high speed 
Note: the country says Burundi, but the area looks more like Qatar. This is not a but, it is because I updated the version but didn’t update the tile list in my test request.