WARNING: input files have differing sort orders
Hi all, what does this warning mean ? WARNING: input files have differing sort orders Regards Klaus PS: All images are compiled with mkgmap r2309 and the option "--latin1". java -Xmx6000M -jar /home/kto/Freizeitkarte-Entwicklung/tools/mkgmap/mkgmap.jar --max-jobs=3 --license-file=license.txt --index --gmapsupp --product-id=1 --family-id=5819 --family-name="Freizeitkarte_Nordrhein-Westfalen 12.6" --series-name="Freizeitkarte_Nordrhein-Westfalen 12.6" --description="Freizeitkarte_Nordrhein-Westfalen 12.6" --overview-mapnumber=58190000 --product-version=1206 5819*.img 5819.TYP Time started: Fri Jun 29 14:13:25 UTC 2012 WARNING: input files have differing sort orders Time finished: Fri Jun 29 14:13:40 UTC 2012 -- View this message in context: http://gis.19327.n5.nabble.com/WARNING-input-files-have-differing-sort-order... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi It's a bug that occurs when you have type file. I don't think that the type file has a sort order field (though I must check since I'd not considered that untilled just now). I guess that it would be good if the file name could be printed when this happens. I'll post a patch later ..Steve toc-rox <easyclasspage@googlemail.com> wrote:
Hi all,
what does this warning mean ?
WARNING: input files have differing sort orders
Steve If you mean a sort order field for TYP files then non NT TYP files as far as I know do not come with such a field. Nick -- View this message in context: http://gis.19327.n5.nabble.com/WARNING-input-files-have-differing-sort-order... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi
It's a bug that occurs when you have type file. I don't think that the type file has a sort order field (though I must check since I'd not considered that untilled just now).
I guess that it would be good if the file name could be printed when this happens.
I'll post a patch later
Patch attached which fixes this and will properly warn if the TYP file has the wrong code page. ..Steve
I get this warning too. From the previous posts it is not clear to me what the effect of this warning on is the functionality of the generated maps. Is it harmful or can it be ignored? On 4-7-2012 17:21, Steve Ratcliffe wrote:
Hi
It's a bug that occurs when you have type file. I don't think that the type file has a sort order field (though I must check since I'd not considered that untilled just now).
I guess that it would be good if the file name could be printed when this happens.
I'll post a patch later
Patch attached which fixes this and will properly warn if the TYP file has the wrong code page.
..Steve
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 12/07/12 09:41, Lambertus wrote:
I get this warning too. From the previous posts it is not clear to me what the effect of this warning on is the functionality of the generated maps. Is it harmful or can it be ignored?
The warning caused when a typ file was supplied was a false warning and can be ignored as Hermann already replied. That patch has now been committed, so you shouldn't see it for that reason with the latest version. An index can only have one code-page and sorting order, so the error is supposed to warn you if you attempt to combine tiles that were created with different code-page options. ..Steve
On 17/08/12 22:53, Hermann Peifer wrote:
On 2012-07-16 20:09, Steve Ratcliffe wrote:
That patch has now been committed, so you shouldn't see it for that reason with the latest version.
I am still getting the sort order warning, with mkgmap-r2314. Am I missing something?
Strangely I just discovered earlier today that a patch that I thought had been committed, was not. And that was the patch! Sorry about that, I will do it now. ..Steve
On 2012-08-17 19:29, Steve Ratcliffe wrote:
On 17/08/12 22:53, Hermann Peifer wrote:
On 2012-07-16 20:09, Steve Ratcliffe wrote:
That patch has now been committed, so you shouldn't see it for that reason with the latest version.
I am still getting the sort order warning, with mkgmap-r2314. Am I missing something?
Strangely I just discovered earlier today that a patch that I thought had been committed, was not. And that was the patch!
Sorry about that, I will do it now.
Thanks for the fix in r2315. Works fine now. Hermann
Please, does this warning mean that Mkgmap exits or produces a corrupt image? Has anyone been able to test this patch ? On 4-7-2012 17:21, Steve Ratcliffe wrote:
Hi
It's a bug that occurs when you have type file. I don't think that the type file has a sort order field (though I must check since I'd not considered that untilled just now).
I guess that it would be good if the file name could be printed when this happens.
I'll post a patch later
Patch attached which fixes this and will properly warn if the TYP file has the wrong code page.
..Steve
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 2012-07-16 18:48, Lambertus wrote:
Please, does this warning mean that Mkgmap exits or produces a corrupt image?
No. It is just a warning, which appears since revision >= 2306. The images are fine, as far as I can tell. My minimalistic TYP file for hiding road-name-pois is: cat my.txt [_point] Type=0x640a String=0x00,HiddenRoadNamePOI Xpm="1 1 1 1" ". c none" "." [end]
participants (5)
-
Hermann Peifer -
Lambertus -
n Willink -
Steve Ratcliffe -
toc-rox