- mkgmap-dev - The mkgmap lists

Commit: r1229: Added an option to create the mdx and mdr files.
by svn commit 24 Sep '09

24 Sep '09

Version 1229 was commited by steve on 2009-09-24 13:16:48 +0100 (Thu, 24 Sep 2009) BRANCH: mdr Added an option to create the mdx and mdr files. Use the --index option. This will create two files, named osmmap.mdx and osmmap_mdr.img by default. The name is controlled by the --overview-mapname option and the default value of that option has been changed to osmmap from 63240000 so the tdbfile and overmap name will also now be osmmap.tdb and osmmap.img by default. You should also give a family-id option as I believe it must be installed under a map family. What's there? The mdx file is complete - it will contain an entry for each map on the command line. You can as normal give .img or .osm files or a mixture of both. The mdr also contains entries for each map, but is otherwise empty. The maximum you will see is that the find button in mapsource should be enabled. Clicking find should just show no entries without crashing. If you used family-id=909 something like the following would be needed to install on windows. Note the IDX and MDR keys and also that they are at the family level (like the typ file) and not at the product level. REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Garmin\MapSource\Families\uk-test] "ID"=hex:8d,03 "IDX"="c:\\maps\\osm\\osmmap.mdx" "MDR"="c:\\maps\\osm\\osmmap_mdr.img" [HKEY_LOCAL_MACHINE\Software\Garmin\MapSource\Families\uk-test\1] "BMAP"="c:\\maps\\osm\\osmmap.img" "LOC"="c:\\maps\\osm\\" "TDB"="c:\\maps\\osm\\osmmap.tdb"

2 1

LBL subfile details
by Anton Todorov 24 Sep '09

24 Sep '09

Hi, Here are some findings that i can not manage to code in java... In mkgmap the text between the header and the first lbl section is hardcoded to the string 'mkgmap'. This section is defined at the end of the header: LBLHDR@0xB0 - 4 byte Text section begin LBLHDR@0xB4 - 4 byte Text section length (INFO_LEN in mkgmap) These values are hardcoded in mkgmap and i do not know how to change that code. It should be converted to something as the other subsections. In all original files the text is 'American'. In the source it is commented as "// Sort descriptor ??? ...". I could speculate that this is kind of dictionary name(like 'American English'). Another finding is (when the texts are coded in 6bits) that the first byte of LBL1 is 0xFF(in Metro Guide) which is decoded as 0x3F == 'End Marker'. In mkgmap it is 0x00 that i think is not correct. All elements that have no name have lbl1 pointer to this end marker so it should be 0xFF. If there are points for the cities and LBL1,2,3,4 are filled in the overview map img, menu Find->Find Places has working City tab in MapSource. Maybe overview img participate in the indexing in some way? Best Regards, Anton Todorov

3 3

address search problem due to required "State" value
by maning sambale 24 Sep '09

24 Sep '09

Several problems with Search by Address in Garmin Mobile XT reported by some of my users. " - unable to search for road names via Address Search option using Where to?" -> "Addresses" -Step 1 0f 5 in Address Search requires entry of "State", no state is listed and no matches found if the "Spell" option is used -unable to proceed with the following Address Search steps because of the said bug" In the Philippines and surely in other countries, we don't have "State". -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

12 30

Commit: r1228: Reduce number of Table A entries.
by svn commit 24 Sep '09

24 Sep '09

Version 1228 was commited by markb on 2009-09-24 11:49:50 +0100 (Thu, 24 Sep 2009) Reduce number of Table A entries. Previously, Table A entries were unique for each combination of start node, end node and RoadDef. But no information from the start and end nodes goes into Table A so we can ignore the start and end nodes and all roads within a given routing centre that use the same RoadDef can now share a Table A entry. This reduces the number of entries required which makes the .img files smaller and, hopefully, also improves the routing because routing centres can now cover a larger area.

1 0

Commit: r1227: Increase limit of node bytes in a route centre to 0x2000.
by svn commit 24 Sep '09

24 Sep '09

Version 1227 was commited by markb on 2009-09-24 11:49:47 +0100 (Thu, 24 Sep 2009) Increase limit of node bytes in a route centre to 0x2000.

1 0

Commit: r1226: Can now read images that have a non-zero XOR byte.
by svn commit 24 Sep '09

24 Sep '09

Version 1226 was commited by markb on 2009-09-24 11:48:09 +0100 (Thu, 24 Sep 2009) Can now read images that have a non-zero XOR byte. If the first byte in the image is non-zero, every byte in the image has to be XORed with it to.

1 0

Commit: r1223: Start a branch for the global index work (mdr).
by svn commit 23 Sep '09

23 Sep '09

Version 1223 was commited by steve on 2009-09-23 22:27:31 +0100 (Wed, 23 Sep 2009) BRANCH: mdr Start a branch for the global index work (mdr). The plan is to quickly create the minimum amount that works, merge it back and then repeat. I am going to read img files to create the index as there is lot of information that is needed in them and it would be useful to create one separately anyway. A similar decision was made wrt the overview map, and so the same code can be used to finally implment a better overview map too.

1 0

Commit: r1215: Added sections for POI and POI type (10 and 11)
by svn commit 23 Sep '09

23 Sep '09

Version 1215 was commited by steve on 2009-09-21 22:45:00 +0100 (Mon, 21 Sep 2009) Added sections for POI and POI type (10 and 11) This enables the Feature tab on the find dialog, but nothing is found. Not that I am particularly suprised as all the numbers are just made up.

4 4

Bug report : closed contour lines are opened
by David 23 Sep '09

23 Sep '09

Hello there, Max_RGN_SIZE and MAX_NUM_LINES increased confidently make possible to build my huge contour lines polish format file. Thank you for this change. I discovered that mkgmap v1180 doesn't close contour lines. I don't know if this bug appears only with polish format files. David <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q3/004064.html>

6 7

[PATCH v1] - Route centre tweaks
by Mark Burton 23 Sep '09

23 Sep '09

Thanks to those who have tried yesterday's table A patch. Seems like it hasn't caused any problems (so far). Today's offering includes the table A tweak but it also increases one of the limits that determine when a route centre needs to be sub-divided. As far as I can tell, the limit was somewhat smaller than it should have been. So with this patch, fewer routing centres should be required (obviously depends on the map data). So please test this patch (it replaces the previous patch) and let me know if their are any issues. You must enable assertions, otherwise if the data structures overflow you won't know until mapsource/gps barfs. Cheers, Mark BTW - if you are not interested in routing over footpaths, changing them to a non-routable type will simplify the routing data further.

5 9