March 2016 - mkgmap-dev - The mkgmap lists

style compiler bug
by Mike Baggaley 09 Mar '16

09 Mar '16

Hi Gerd/Steve, I seem to have come across an anomaly in the style compiler (or I am doing something silly). The following line does not compile: ((highway=* & motorroad=yes) | highway=motorway | highway=motorway_link) & foot!=yes & foot!=designated & foot!=permissive { add mkgmap:foot=no } But this variant compiles: (highway=motorway | highway=motorway_link | (highway=* & motorroad=yes)) & foot!=yes & foot!=designated & foot!=permissive { add mkgmap:foot=no } And so does this one: ((highway=* & motorroad=yes) | highway=motorway | highway=motorway_link) & (foot=yes | foot=designated | foot=permissive) This is the error message: Error in style: Error: (inc/access:6): Invalid rule expression: ((($highway=*&($motorroad='yes'))|(($highway='motorway')|($highway='motorway _link')))&($foot!=yes&($foot!=designated&$foot!=permissive))) Changing the != operators to = allows it to compile, so most likely a mishandling of the ! operator. Any ideas what is wrong? Mike

2 2

Is there a program I can use to see mkgmap tags (mkgmap:) ?
by greg crago 09 Mar '16

09 Mar '16

I can use GPSMapEdit to see contents of my .img file, but I would like to see the mkgmap:(variables) listed on each way and poi. How can I see these tags? Greg

3 2

Should we have a ADVANCED_DEFAULT Style?
by greg crago 09 Mar '16

09 Mar '16

I see many good questions about advanced mapping techniques and I am trying to incorporate these ideas into my maps. I was wondering if we could combine these ideas into a ADVANCED_DEFAULT style? I do not know if everyone wants to keep their own mapping styles secret, but I have added to the default_style and do not mind sharing my own additions. That way new mappers can analyze this code and get up to speed faster and maybe be able to add more ideas to the community. If you do not like a feature, you can always remove that piece of code. My goal is to try to use mkgmap to map maps that look like Garmin City Navigator. So far I have added custom POI symbols for brand specific businesses (fuel, fast food, resturants) Added 1 way arrows Added Bridges over ways Added Bicycle lanes. Greg

4 4

Oneway arrows
by Dave Swarthout 09 Mar '16

09 Mar '16

I would like to see oneway arrows drawn on top of the highway lines the way OSMAnd does it. I tried moving my oneway arrow rules to after the other highway rules were finished processing but they completely disappeared. The lines style rules are below and in my TYP file are defined as blue arrows on a transparent background. # display direction arrows on highways highway=* & (oneway=yes | oneway=1 | oneway=true) [0x10000 resolution 24 continue with_actions] highway=* & oneway=-1 [0x10001 resolution 24 continue with_actions] Thanks, Dave

9 15

Routes being overwritten
by Gary Bamford 08 Mar '16

08 Mar '16

I am producing maps using Mkgmap and Openstreetmap data. the maps I am happy with, lovelly detail the lot. I am using a Garmin Hcx Legend GPS. but I have a problem when I ask the gps to route to a point, it produces the route no problems. but the route disappears on the GPS screen, I can see it appears, but then the roads are being places on top of the route. Any suggestions as to what I have wrong ?

2 4

Commit r3670: Add forkmode=once to build.xml for much faster builds
by svn commit 07 Mar '16

07 Mar '16

Version mkgmap-r3670 was committed by steve on Mon, 07 Mar 2016 Add forkmode=once to build.xml for much faster builds http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3670

2 1

Maintenance Sun 6th March
by Steve Ratcliffe 07 Mar '16

07 Mar '16

Hello The mkgmap server and website will be down from around 4pm GMT on Sunday 6th March so they can be upgraded. This should take less than two hours, probably much less. During the upgrade, mailing list, svn and downloads will not be available. Any mails sent should still arrive afterwards. There will be an announcement on the mailing list just before the downtime and then just afterwards. ..Steve

1 2

problem with splitter and bounding polygon
by Andrzej Popowski 06 Mar '16

06 Mar '16

Hi, I'm trying to compile a map of USA using North America extract form Geofabrik. I use splitter r427 with bounding polygon, something like that: splitter --polygon-file=usa.poly ... north-america-latest.osm.pbf The result is that I get errors in mkgmap: SEVERE (MapFailedException): pbf\29729241.osm.pbf: (thrown in BufferedImgFileWriter.ensureSize()) There is not enough room in a single garmin map for all the input data. The .osm file should be split into smaller pieces first. This error appears for some tiles at the map border. My guess is, that splitter uses only nodes inside bounding poly to compute tiles sizes. When a rectangular tile is placed on a polygon border, estimated node number could be significantly smaller than the full number actually saved in this tile. This could lead to problems as above. I don't have any suggestions for a solution, so I'm going to try to go around it using a simplified poly. I hope, that maybe someone could get an idea how to correct it. -- Best regards, Andrzej

4 12

sorting the values?
by Bernd Weigelt 04 Mar '16

04 Mar '16

Hi In my styles, i try to disable routing for really small ways with this rules highway=* & width ~'.*cm' { delete width } highway=* & width ~'.*m' { set width='${width|part:"m"}'; } highway=* & width ~'.*;.*' { set width='${width|subst:",=>."}'; } highway=* & maxwidth ~'.*cm' { delete maxwidth } highway=* & maxwidth ~'.*m' { set maxwidth='${maxwidth|part:"m"}'; } highway=* & maxwidth ~'.*,.*' { set maxwidth='${maxwidth|subst:",=>."}'; } highway=* & highway!=service & highway!=track & highway!=path & highway!=cycleway & highway!=footway & highway!=pedestrian & (maxwidth<2.0 | width<2.0) { set mkgmap:throughroute=no; } highway=* & (maxwidth<1.0 | width<1.0) { add foot=yes; add access=no; } this seems to work in most cases, but i found some ways like this ways with semicolon separated values https://www.openstreetmap.org/way/235493829 https://www.openstreetmap.org/way/47861325 Is it possible, to sort the values and use only the smallest/greatest value? Bernd

2 2

Anyone verify that Exit info and Destination info still works in mkgmap r3669?
by greg crago 04 Mar '16

04 Mar '16

I seem to have lost the 'Nuvi' looking Exit and Destination strings I use to get on mkgmap with --process-exits & --process-destination options. Here is my compile command: java -ea -Xmx1024M -jar \MKGMAP\mkgmap-r3669\mkgmap-r3669\mkgmap.jar --gmapsupp --description="Metro Area 2016.3.1" --latin1 --index --x-split-name-index --bounds=\MKGMAP\bounds.zip --location-autofill=is_in,nearest --housenumbers --overview-mapname=Plymouth-ov --overview-mapnumber=12390000 --remove-ovm-work-files --style-file=\MKGMAP\openmapchest-style\openmapchest --check-styles --family-id=555 --family-name="Plymouth" --product-id=1 --series-name="Metro Area 2016.3.1" --area-name="My maps" --min-size-polygon --route --drive-on=detect,right --check-roundabouts --check-roundabout-flares --remove-short-arcs --add-pois-to-areas --pois-to-areas-placement="entrance=main;entrance=yes;building=entrance" --generate-sea=extend-sea-sectors,multipolygon,floodblocker,close-gaps=6000 --make-poi-index --make-opposite-cycleways --process-destination --process-exits --tdbfile --poi-address --verbose --input-file=12390005.osm.pbf --input-file=12390006.osm.pbf --input-file=12390007.osm.pbf master_thin.txt And here is the section in the 'lines' file: # start of rules for process-exits and process-destination options # which may add info to a part of these highway=*_link roads: # motorway_link, trunk_link, primary_link, secondary_link, tertiary_link # build destination hint dest_hint=* { delete dest_hint } (highway=motorway_link | highway=trunk_link | highway=primary_link | highway=secondary_link | highway=tertiary_link) & mkgmap:dest_hint=true # { set dest_hint = '${destination:ref|subst: =>} ${destination|subst:;=> |subst:/=> }' | { set dest_hint = '${destination:ref|subst: =>|subst: South=> S|subst: North=> N|subst: East=> E|subst: West=> W} ${destination:street|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy} - ${destination|subst:;=>,|subst:/=>,}' | '${destination:street|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy} - ${destination|subst:;=>,|subst:/=>,}' '${ref|subst: =>|subst: South=> S|subst: North=> N|subst: East=> E|subst: West=> W} - ${destination|subst:;=>,|subst:/=>,}' | '${exit_hint_ref|subst: South=> S|subst: North=> N|subst: East=> E|subst: West=> W} ${exit_hint_name|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy}' | '${exit_to|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy}' | '${destination|subst:;=>,|subst:/=>,}'; } # build exit hint exit_hint=* { delete exit_hint } (highway=motorway_link | highway=trunk_link | highway=primary_link | highway=secondary_link | highway=tertiary_link) & mkgmap:exit_hint=true { set exit_hint = 'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy}' | 'Exit ${ref|subst: South=> S|subst: North=> N|subst: East=> E|subst: West=> W}' | 'Exit ${mkgmap:exit_hint_ref|subst: South=> S|subst: North=> N|subst: East=> E|subst: West=> W} ${mkgmap:exit_hint_exit_to|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy}' | 'Exit ${mkgmap:exit_hint_exit_to|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy}' | 'Exit ${mkgmap:exit_hint_name|subst: Road=> Rd|subst: Street=> St|subst: Avenue=> Ave|subst: Mile=> Mi|subst: Boulevard=> Blvd|subst: Parkway=> Pkwy|subst: Highway=> Hwy}' | 'Exit ${mkgmap:exit_hint_ref|subst: South=> S|subst: North=> N|subst: East=> E|subst: West=> W}'; } # use destination hint and/or exit hint to build name (highway=motorway_link | highway=trunk_link | highway=primary_link | highway=secondary_link | highway=tertiary_link) & (mkgmap:exit_hint=true | mkgmap:dest_hint=true) { name '${exit_hint} ${dest_hint}' | '${dest_hint}' | '${exit_hint}'} # end of rules for process-exits and process-destination options Am I missing something, or did the EXIT and DESTINATION feature stop working? Greg

2 2