Frank Stinner wrote
Sorry, but i have no success
Just I use mkgmap 2379 with the default-style. My Optionfile is:
family-name=TEST series-name=TEST description=TEST bounds=\Gps\Data\bounds_20121019.zip country-name=Deutschland country-abbr=DEU region-name=Deutschland region-abbr=DEU name-tag-list=name:de,int_name,name:en,name index route net tdbfile nsis area-name=Germany road-name-pois=0x2f15 draw-priority=20 reduce-point-density=2.6 reduce-point-density-polygon=1.2 merge-lines remove-short-arcs latin1 levels=0:24,1:23,2:22,3:21,4:20,5:19,6:17 max-jobs
I think, the Registry is ok:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Garmin\Mapsource\Families\FAMILY_6324] "ID"=hex:B4,18 "IDX"="j:\\Gps\\Projekte\\DB-Test\\org_mkgmap\\osmmap.mdx" "MDR"="j:\\Gps\\Projekte\\DB-Test\\org_mkgmap\\osmmap_mdr.mdx" [HKEY_LOCAL_MACHINE\SOFTWARE\Garmin\Mapsource\Families\FAMILY_6324\1] "Loc"="j:\\Gps\\Projekte\\DB-Test\\org_mkgmap\\" "Bmap"="j:\\Gps\\Projekte\\DB-Test\\org_mkgmap\\osmmap.img" "Tdb"="j:\\Gps\\Projekte\\DB-Test\\org_mkgmap\\osmmap.tdb"
Maybe the order of the options is important???
I don't think the order is important, but maybe one of the options causes trouble. For example, merge-lines is documented to cause routing-errors. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Option-index-but-no-Find-Place-in-Mapsource-t... Sent from the Mkgmap Development mailing list archive at Nabble.com.