Commit: r1283: Merged the MDR code back to trunk
Version 1283 was commited by steve on 2009-10-16 15:21:25 +0100 (Fri, 16 Oct 2009) Merged the MDR code back to trunk One change to compare labels ignoring case was required to produce identical img files. Plus unrelated test failure from when the size of the NOD section was reduced fixed. Note that the default overview-mapname is now osmmap rather than 63240000. The --index option creates a global index file, named by default osmmap_mdr.img along with an osmmap.mdx file. Although this should not have affected any existing feature, it is a rather large change so please be on the lookout for any problems.
When I create a map with the --index option, and install in MapSource using MapsetToolkit v1.62, and then check the registry entries using the "Check Registry" option in MapsetToolkit, it reports an Status Error/Warning stating "FID not matches with MDX file", and gives the FID as -2181 when the Family ID is should be 5547. I do not see anything in the registry or map source that might fix this. Is this an error in mkgmap, in my compile or installation procedures? Thanks Garvan svn commit wrote:
Version 1283 was commited by steve on 2009-10-16 15:21:25 +0100 (Fri, 16 Oct 2009)
Merged the MDR code back to trunk
One change to compare labels ignoring case was required to produce identical img files. Plus unrelated test failure from when the size of the NOD section was reduced fixed.
Note that the default overview-mapname is now osmmap rather than 63240000.
The --index option creates a global index file, named by default osmmap_mdr.img along with an osmmap.mdx file.
Although this should not have affected any existing feature, it is a rather large change so please be on the lookout for any problems. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 17/10/09 09:23, Garvan & maew wrote:
When I create a map with the --index option, and install in MapSource using MapsetToolkit v1.62, and then check the registry entries using the "Check Registry" option in MapsetToolkit, it reports an Status Error/Warning stating "FID not matches with MDX file", and gives the FID as -2181 when the Family ID is should be 5547.
I suspect that is an error in mapsettoolkit. All maps, including non-mkgmap ones, seem to give a similar error. I'm pretty sure that if it were wrong, then the maps would not load. ..Steve
participants (3)
-
Garvan & maew -
Steve Ratcliffe -
svn commit