
Hi, from time to time I face the problem, that POI or addresses are not findable in mapsource or on the GARMIN device. But if you look at the map, they are there. With other styles, or making "small" changes to the style by disabling a random POI, suddenly they are there. But sometimes then other POI or addresses are missing. Is there a tool which dissembles a map and prints relevant informations about the index? I would like to compare the cases, where an index entry is not found and where it is found, and what the difference is. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

Hi ThorstenI've noticed that pois are only searchable in mapsource if they appear in the mdr.img file.The categories are directly linked to the occurence of a poi type in the mdr subfile.This may not be what you are looking for but I'm examining the mdr structure myself and have written a small binary tool to extract the pois ( not addresses); it only reads NT and non NT mdr.img files. http://www.pinns.co.uk/osm/bits/mdr_pois.zip <http://www.pinns.co.uk/osm/bits/mdr_pois.zip> Interestingly,a) TOPOs only seem to include pois with 1400+ rangeb) There is another byte attached to each indexed poi - mkgmap seems to set it to 0 - No idea what it does but I have seen values 1-16 elsewhere.Nick -- View this message in context: http://gis.19327.n5.nabble.com/Tool-to-dump-index-tp5877646p5878725.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (2)
-
nwillink
-
Thorsten Kukuk