Well I think on some devices there was a limit of 8 or 12 characters for the .typ file. mkgmap definitely should not change the name if it is short enough. I found it confusing enough that it adds an x before the name if the FID is not adjusted instead of adjusting the FID of the original .typ file. On Fri, 25 Jun 2021, 09:18 Gerd Petermann <GPetermann_muenchen@hotmail.com> wrote:

Hi,

in a private mail from Thomas Morgenstern I was informed that mkgmap may write invalid gmapi data if the typ file has a long name. I can reproduce this problem with a single input file and our sample typ file like this java -jar dist\mkgmap.jar --gmapi resources\typ-files\sameOrder.txt 63240001.o5m

The problem shows up in Mapsource which cannot create gmapsupp files for such a gmap file, it crashes instead

I guess mkgmap should use the same name for the gmapi format that is used for the gmapsupp.img, so SAMEORDE.TYP Or maybe the family id should be used instead, e.g. 6324.TYP?

Gerd

_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev