Include external TYP-File with mkgmap?

Hello, I would like to include a TYP file in my gmapsupp.img. I know that it is possible e.g. with sendmap. Is it possible (or at least planned in future) to include a typ file directly with mkgmap? Regards, Johann Gail

Hi On Wed, Mar 25, 2009 at 11:47:51PM +0100, Johann Gail wrote:
I would like to include a TYP file in my gmapsupp.img. I know that it is possible e.g. with sendmap. Is it possible (or at least planned in future) to include a typ file directly with mkgmap?
Yes it works fine already with a couple of details you have to take care of. First, each TYP file has a family id and you need to know that. All you then have to do is add the TYP file to the list of files (making sure that the .TYP is in upper-case) and give the correct --family-id argument. Something like this: mkgmap ... --family-id=909 file.osm file.img FILE.TYP with 909 replaced by the family id of the TYP file. This could be improved by dealing with lower case names and by changing the family-id in the TYP when it is copied into the gmapsupp.img. ..Steve

Cool, I was looking for such a function as well :-) Is there somewhere documentation explaining the (functional) differences between family and product id's and the best way to use them? Steve Ratcliffe wrote:
Hi
On Wed, Mar 25, 2009 at 11:47:51PM +0100, Johann Gail wrote:
I would like to include a TYP file in my gmapsupp.img. I know that it is possible e.g. with sendmap. Is it possible (or at least planned in future) to include a typ file directly with mkgmap?
Yes it works fine already with a couple of details you have to take care of.
First, each TYP file has a family id and you need to know that.
All you then have to do is add the TYP file to the list of files (making sure that the .TYP is in upper-case) and give the correct --family-id argument.
Something like this:
mkgmap ... --family-id=909 file.osm file.img FILE.TYP
with 909 replaced by the family id of the TYP file.
This could be improved by dealing with lower case names and by changing the family-id in the TYP when it is copied into the gmapsupp.img.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Johann Gail
-
Lambertus
-
Steve Ratcliffe