- mkgmap-dev - The mkgmap lists

Commit: r2541: Documentation: Add description how to preprocess bounds
by svn commit 30 Mar '13

30 Mar '13

Version 2541 was committed by wanmil on Sat, 30 Mar 2013 Documentation: Add description how to preprocess bounds

1 0

Multiple relation names
by Geoff Sherlock 29 Mar '13

29 Mar '13

I’m sure I’ve read on this list that this is possible. For walking maps I would the way name to consist of all possible related names for that way. For instance for the relations named ‘Icknield Way’ and ‘Chiltern Way’, I would like a way that is contained in both relations to be named ‘Icknield Way Chiltern Way’. Currently I am displaying names for relations using the following in the relations style file: type=route { apply { set route_display_name='${name}'; } } Then I changed the names of tracks, bridleways, cycleways and footways in the lines file with: type=route & route_display_name=* { apply { set route_display_name='${route_display_name}' } } (highway=track | highway=bridleway | highway=cycleway | highway=footway) & route_display_name=* {set name='${route_display_name}' continue with_actions} This is working fine except for two points: 1. Where a way shares two relations only one name is shown (presumably the last alphabetically). 2. It seems that when a way is already named the way name is not changed to the name of the relation. So for 1 – is there any way of showing multiple names? And 2 – Why is the name not changed? I would appreciate any help forthcoming. Geoff.

3 12

Strange squares on Garmin GPS device
by Thomas 29 Mar '13

29 Mar '13

Since I have created maps for my Garmin GPS device some days ago something strange happens. The background of the map is loaded with small brownish squares (see attachment) instead of blank/white. I have not changed the style files as well as the TYP file. By the way, the same background drawing happens if no TYP file is used. Was there a change in mkgmap which causes the squares? Does anyone else have this problem? Sincerely, Thomas

5 13

Overview map for Africa
by GerdP 28 Mar '13

28 Mar '13

Hi List, while testing the latest patches I found something strange: I created a map for Africa with default style using java -Xmx6000m -jar mkgmap.jar --max-jobs --nsis --precomp-sea=f:\osm\sea_20130308.zip -c template.args When I open this map in Basecamp I just see white rectangle. I have to zoom in multiple times to see anything. Wouldn't it be better to change the default so that we display at least the boundaries off continents on very low resolutions? Ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Overview-map-for-Africa-tp5754606.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

6 39

Commit: r2540: Fix NPE that occurs if the directory / zipfile given with --precomp-sea doesn't exit
by svn commit 28 Mar '13

28 Mar '13

Version 2540 was committed by gerd on Thu, 28 Mar 2013 Fix NPE that occurs if the directory / zipfile given with --precomp-sea doesn't exit

1 0

Commit: r2539: Initial version of documentation for handling address in Garmin maps
by svn commit 27 Mar '13

27 Mar '13

Version 2539 was committed by wanmil on Wed, 27 Mar 2013 Initial version of documentation for handling address in Garmin maps Yet not complete and a bit unsorted but need to commit it as a first version.

1 0

mkgmap --index --tdbfile with combined contours ???
by prenard 26 Mar '13

26 Mar '13

Hi, I would like to create a map with "combined contours" and "address search" functionality. First, I have created the map without contour using the following command: java -Xmx1200M -jar W:\save-w\softs\OSM_mkgmap\mkgmap.jar ^ --series-name="France Nord + Belg + Lux - V20130318" ^ --product-id=1 ^ --family-id=8000 ^ --family-name="OSM - My map" ^ --gmapsupp ^ --output-dir=..\img ^ --generate-sea=extend-sea-sectors,close-gaps=5000 ^ --remove-short-arcs ^ --route ^ --index ^ --tdbfile ^ --bounds=W:\save-w\softs-conf\OSM\my_maps\France-Nord_Belgique_Luxembourg\V20130308\osm\bounds ^ --location-autofill=is_in,nearest ^ --show-profiles=1 ^ --draw-priority=25 ^ -c ..\osm-pbf\template.args ^ ..\typ\mapnik.typ It is ok: search function is working in Mapsource. Now, I would like to combine this map with "contours layers" using the following commande: java -Xmx1200M -jar W:\save-w\softs\OSM_mkgmap\mkgmap.jar ^ --series-name="France Nord + Belg + Lux - V20130318" ^ --gmapsupp ^ --output-dir=..\img-contours ^ --product-id=1 ^ --family-id=9000 ^ --family-name="SRTM-10" ^ --draw-priority=28 ^ --transparent ^ -c ..\srtm-pbf\template.args ^ --product-id=1 ^ --family-id=8000 ^ --family-name="OSM - My map" ^ --generate-sea=extend-sea-sectors,close-gaps=5000 ^ --draw-priority=25 ^ --remove-short-arcs ^ --show-profiles=1 ^ --route ^ --index ^ --tdbfile ^ --bounds=W:\save-w\softs-conf\OSM\my_maps\France-Nord_Belgique_Luxembourg\V20130308\osm\bounds ^ --location-autofill=is_in,nearest ^ --show-profiles=1 ^ -c ..\osm-pbf\template.args ^ ..\typ\mapnik.typ Map is generated but, this time search is not working in Mapsource... I think that the problem is due to options order... Could you help me ? Patrick -- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-index-tdbfile-with-combined-contours-… Sent from the Mkgmap Development mailing list archive at Nabble.com.

5 6

Default sorting for cp1251
by Valerii Pekarskyi 25 Mar '13

25 Mar '13

Hi, Mainteiners, please accept the patch for changing default sorting for maps created with Windows-1251. https://code.google.com/p/velo100mapper/source/browse/trunk/test/mkgmap-cp1… The main reason of that is to shift Cyrillic letters to the bottom - for not having undefined, not_set_* at the top of the list. As most people who create maps with this charset want to have native language at the top of the list, I see this patch quite useful. Best Regards, Larry0ua

1 0

issues with tile boundaries
by Minko 25 Mar '13

25 Mar '13

Seems that my message doesnt reach the list with attachments, so I try it again: Attachments: https://dl.dropbox.com/u/64716698/OSM/mkgmap/corners.jpg https://dl.dropbox.com/u/64716698/OSM/mkgmap/gap.jpg > I noticed a gap in my maps and artefacts at the outer tile boundaries > when I tried to make a Europe map. > Maybe it is my mistake, because I have drawn a few big rectangular > polygons over Europe and let the splitter calculate those areas. I > then let mkgmap run and combined the img tiles of those sections. When > I look at the total map there are some issues. > > First, there is a big gap at 49.5 longitude (a few 100 meters wide) > between the northern and southern part. It is only visible at the > highest zoomlevels (<200m). When I zoom out, the gap disappears and > routing is possible. If I make a different selection of a fewer tiles > around this latitude, the gap is not there. > > See gap.jpg > > North tile > 10131034: 2306867,4096 to 2344960,22528 > # : 49.499996,0.087891 to 50.317383,0.483398 > > South tile > 10135076: 2301952,4096 to 2306867,40960 > # : 49.394531,0.087891 to 49.499996,0.878906 > > If you look at the Garmin units, 2306867 is not divisible by 2048. > Could this be the reason? > Is it a bug in the splitter or should I use an option to let the > splitter draw areas that exactly fits with 2048 garmin units? > > Second, I noticed in the corners of the map that the background > polygon does not match. > See pic "corners.jpg". > > 10132142: 3266560,1212416 to 3327481,1444704 > # : 70.092773,26.015625 to 71.399996,30.999985 > > Again, the most northern latitude 3327481 is not divisable by 2048 > > I also notice that the map disappears when zooming in at the border > tiles (only at very high zoomlevels, like 100 m or closer). > > I use splitter r297 and mkgmap-r2513, precompiled sea tiles (in > splitter and mkgmap) and a custom background (generate-sea: > land-tag=natural=background), maybe this is also relevant to mention?

5 38

Commit: r2538: align_subdiv_center_v1.patch : Avoid cosmetic problems seen in Mapsource or Basecamp.
by svn commit 25 Mar '13

25 Mar '13

Version 2538 was committed by gerd on Mon, 25 Mar 2013 align_subdiv_center_v1.patch : Avoid cosmetic problems seen in Mapsource or Basecamp. Place sub division centers on a grid calculated with the corresponding resolution to avoid gaps because of rounding.

1 0