- mkgmap-dev - The mkgmap lists

roundabouts3.patch
by Gerd Petermann 10 Jan '17

10 Jan '17

Hi Mike, please review https://www.openstreetmap.org/way/456114715 in the attached pbf file. The trunk version complains about this and I think that's good, the patched version doesn't. Gerd

2 1

Installer not working
by Stéphane MARTIN 09 Jan '17

09 Jan '17

Hi, I am unable to obtain a proper installer for Windows. All the processes work fine until I open BaseCamp (v. 4.6.2) An error occur: "Problem with installation of Mayotte-OSM-default. Reinstall Mayotte-OSM-default and re-run BaseCamp." MapConverter does not want to run. Maps are made with a Linux station. makensis is from repository: $ makensis -VERSION $ v2.50-1 mkgmap-r3741 - Files - Style: http://tuxdomain.darktech.org/osm-garmin/view.php?file=Mayotte/default.zip Scripts: https//tuxdomain.darktech.org/osm-garmin/view.php?file=Mayotte/work_Mayotte.zip I did not see a message to help. A suggestion ? Steph

4 16

copyright and check roundabouts improvements
by Mike Baggaley 09 Jan '17

09 Jan '17

HI Gerd, have you made any progress on testing the two patches on copyright reader improvements and checking roundabouts that I posted before Christmas (attached)? Cheers, Mike

3 6

Commit r3745: in the lines file add area=yes for highways with mkgmap:mp_created=true
by svn commit 09 Jan '17

09 Jan '17

Version mkgmap-r3745 was committed by gerd on Mon, 09 Jan 2017 in the lines file add area=yes for highways with mkgmap:mp_created=true - Andrzej Popowski http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3745

1 0

Commit r3744: in the polygons file treat highways with mkgmap:mp_created=true like those with area=yes
by svn commit 09 Jan '17

09 Jan '17

Version mkgmap-r3744 was committed by gerd on Mon, 09 Jan 2017 in the polygons file treat highways with mkgmap:mp_created=true like those with area=yes - lig fietser http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3744

1 0

multipolygon highway areas (like pedestrian)
by lig fietser 08 Jan '17

08 Jan '17

Hi, I have noticed mkgmap does not recognize multipolygon pedestrian areas that are tagged without area=yes as polygons. Example: http://overpass-turbo.eu/s/l6k Area=yes is I think not needed if it is a mulitpoygon, so I want to add this in my style (or maybe mkgmap should automatically recognize this) but how? I cant figure this out. I have tried to add this rule in the relation style file: type=multipolygon & highway=* { apply { set area=yes } } But this does not work, pedestrian highways are still rendered as line and not as area. Also a rule like highway=* & (type=multipolygon|area=yes) in my polygon style does not work. Any ideas?

2 5

Map background is wrong color
by Jakob Mühldorfer 08 Jan '17

08 Jan '17

Hi, I noticed something odd. This might not be related to mkgmap, but I hope you have some idea. Using the OpenTopoMap typ file: https://github.com/der-stefan/OpenTopoMap/blob/master/garmin/style/typ/Open… The draworder starts with: > [_drawOrder] > Type=0x4b,0 > ;background The Polygon 0x4b is also defined to be white: > [_polygon] > Type=0x4b > Xpm="0 0 1 0" > "a c #ffffff" > [end] and to make things even worse: in screenshots the background is plain white: https://i.imgur.com/MGr3hlw.png But on the device, it is definitely yellow. Even more yellow than this image might illustrate: https://i.imgur.com/QDSz7Mc.jpg Display energy saving mode is also turned off And the display is not at fault, the text box on top is perfect white Did I use some setting in mkgmap wrong (transparency or such)? Or does Garmin screw it up Thanks Jakob

1 0

Estrange detours
by Carlos Dávila 07 Jan '17

07 Jan '17

Current default style produces some estrange detours for a test route in a couple of places in my home town (blue circles 1 and 2 in attached screenshot). I've tracked the issue down and behavior has been changing with mkgmap versions, as detailed in the following chart, being current situation worst for this particular case: MapSource 6.16.3 BaseCamp 4.2.5 mkgmap version Car Truck Car Truck 1 2 1 2 1 2 1 2 <3081 OK OK OK OK OK OK OK OK 3088-3108 Suboptimal route OK Loop OK Loop OK Loop >=3111 Suboptimal route Bad Loop OK Loop OK Loop Main changes were introduced with r3081 (merge from the high-prec-coord branch) and r3111 (merge from NOD127 branch). Perhaps those changes need a review. All test were done with the following command, only changing mkgmap jar file: java -Xmx600m -ea -jar mkgmap.jar --bounds=bounds.zip --route --latin1 --code-page=1252 --family-name="Test" --family-id=190 --product-id=1 --series-name="Test-default" --overview-mapname=55190000 --mapname=55190000 --index --add-pois-to-areas --link-pois-to-ways --location-autofill=is_in,nearest --style=default typ/EUR-190.TYP /home/carlos/tmp/test1.osm Files for test: http://alternativaslibres.org/files/detours.zip Note that first street after point 1 is tagged hgv=no, otherwise trucks would probably take the same suboptimal route than cars since r3081.

3 19

Re: [mkgmap-dev] How to label maps generated by mkgmap -r3742
by rheinskipper1000 07 Jan '17

07 Jan '17

Thanks for asking. I have exactly the same problem. -------- Ursprüngliche Nachricht --------Von: greg crago <gregcrago(a)gmail.com> Datum: 07.01.17 00:53 (GMT+01:00) An: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> Betreff: [mkgmap-dev] How to label maps generated by mkgmap -r3742 I am trying to label different maps for each state and the map name seems to be comming from cities15000.zip Here is my splitter command: java -Xmx1024m -Xms1024m -ea -jar \MKGMAP\splitter-r560\splitter-r560\splitter.jar --max-nodes=700000 --handle-element-version=keep --mapid="12380000" --geonames-file=\MKGMAP\cities15000.zip --description=OH-greg --max-areas="255" --no-trim --status-freq="600" ohio-latest.osm.pbf pause Here is my mkgamp command: java -ea -Xmx1024M -jar \MKGMAP\mkgmap-r3742\mkgmap-r3742\mkgmap.jar --gmapsupp --mapname=Ohio --description="OH_1-5THIN_BC" --latin1 --index --x-split-name-index --bounds=\MKGMAP\bounds.zip --location-autofill=bounds,is_in,nearest --housenumbers --overview-mapname=OH-ov --overview-mapnumber=12380000 --remove-ovm-work-files --style-file=\MKGMAP\BaseCamp-style\openmapchest --check-styles --family-id=665 --family-name="Ohio" --product-id=3 --series-name="OH_1-5THIN_BC" --area-name="My_maps" --min-size-polygon --route --drive-on=detect,right --check-roundabouts --check-roundabout-flares --remove-short-arcs --add-pois-to-areas --add-pois-to-lines --pois-to-areas-placement="entrance=main;entrance=yes;building=entrance" --generate-sea=extend-sea-sectors,multipolygon,floodblocker,close-gaps=6000 --make-poi-index --process-destination --process-exits --tdbfile --poi-address --verbose -c template.args master_thin.txt pause I have used 'description' 'mapname' ' family name' 'series-name' I still cannot seem to get my maps to be labeled correctly. In BaseCamp v4.6.2 the map is labeled "US-Mansfield" and on my Garmin Montana 600 it is also labeled "US-Mansfield" Greg

1 0

Maximum map size
by Jakob Mühldorfer 06 Jan '17

06 Jan '17

Hi, Could you please tell me the maximum map size. I know it is around the 4GB mark, but no idea what the exact size limit is. Currently the gmapsupp file is 3951493120Bytes, how much larger can it get before it is broken? Thanks Jakob

3 3