input file has a different sort order
When I'm trying to combine two img tiles from different maps mkgmap gives this warning: input file ...img has a different sort order Both maps are created with --code-page=1252 and --latin1 compiled with mkgmap-r2379. I even get this warning when combining two (or more) img tiles from the same mapset! This issue is only when I use gmapsupp in my args file and only when processing img's (not with osm.pbf files) and without gmapsupp it is ok. Consequence is that the address index is not readable on the gps device (on Mapsource it's fine). With gmaptool I notice the s-f value is 1, normally this is 2. See the attachment for more headers. My mkgmap args file is as follows: family-name=OFM_DBNL family-id=4931 product-id=1 overview-mapname=mapset draw-priority=20 tdbfile latin1 code-page=1252 show-profiles=1 net route index gmapsupp The last mkgmap version that didn't have this issue was r2328 What is going wrong here?
Another observation: Including a typ file seems the reason for a corrupt (?) address index. If I don't include a typ file, I can generate a gmapsupp from img's with a working index.
Hi OK I've an idea what it might be, since a typ file does not have a sort order. But then I thought I had dealt with that case, do you put it before the img files or after? I should be able to look at it tomorrow Steve Minko <ligfietser@online.nl> wrote:
Another observation:
Including a typ file seems the reason for a corrupt (?) address index. If I don't include a typ file, I can generate a gmapsupp from img's with a working index. _______________________________________________
OK I've an idea what it might be, since a typ file does not have a sort order. But then I thought I had dealt with that case, do you put it before the img files or after?
I should be able to look at it tomorrow
Steve
Thanks Steve, Ah, yes I had put the typ file before *.img in the args file, see http://www.openfietsmap.nl/downloads/osm_combi This did work until mkgmap r2328. If I put it at the end after *.img then it is fine again. Would be great if it could be changed, if not it's ok, I'll adapt my scripts now I know what was going wrong here.
Hi
Ah, yes I had put the typ file before *.img in the args file, see http://www.openfietsmap.nl/downloads/osm_combi
OK, that's fine, there is no need to change your script I was just asking to make sure that I understood what was happening in your case. This would work in 2328 because I fixed a bug (in 2334 I think) where "no sort order" was being changed into "code page 1252 sort order". So in r2328 it would work with the TYP file first, *if* you were using latin1/code-page=1252. With another code page, you might not have been so lucky. It should be easy to fix. ..Steve
Hi Minko
When I'm trying to combine two img tiles from different maps mkgmap gives this warning: input file ...img has a different sort order
The attached patch should now fix this. As an aside, I also noticed that if you put the TYP file first, then any following .osm files start with number 63240002, rather than the expected 63240001. ..Steve
Thanks Steve, Ubfortunately I'm not familiar with patches so I can't test it.
The attached patch should now fix this.
As an aside, I also noticed that if you put the TYP file first, then any following .osm files start with number 63240002, rather than the expected 63240001.
On 24/12/12 08:50, Minko wrote:
Thanks Steve, Ubfortunately I'm not familiar with patches so I can't test it.
I've uploaded the jar: URL: http://files.mkgmap.org.uk/download/80/mkgmap.jar ..Steve
Thanks Steve, works as expected now! Merry X-mas to you and everyone on the list, Minko
I've uploaded the jar:
URL: http://files.mkgmap.org.uk/download/80/mkgmap.jar
..Steve
participants (2)
-
Minko -
Steve Ratcliffe