- mkgmap-dev - The mkgmap lists

can't make routing work any more
by Rob 04 Feb '14

04 Feb '14

A couple of weeks ago I downloaded the pennsylvania-latest.osm.pbf OSM dataset and was able to use osmosis to grab a bounding box and then use mkgmap to create a gmapsupp.img file that allowed automotive routing in the selected region. I didn't write down the mkgmap options that I used but they were simple and trivial...that I do remember. It is possible that I used .osm.bz2 XML file instead of the .osm.pbf file but I don't remember for sure. Now I simply cannot reproduce the process using either file. I've created a shell script to try to automate the process and no matter what mkgmap options I used the resulting img file tells me no routable roads in my area when I upload it to the GPS and try to route to a road somewhere. I can create an osm xml file using osmosis that contains the correct bounding box but the final img file loaded into the Oregon 450 GPS seems to not contain any routeable data, no matter what options I use. I'm doing ./make_gmapsupp left=-80.25 top=42.5 bottom=39.25 right=-78.75 as limits to my script. This is the script: -------------------------------------------------------------------------------- #! /bin/sh PATH=$PATH:./bin #bpffile=north-america-latest.osm.pbf pbffile=pennsylvania-latest.osm.pbf tmp=`mktemp` check_exit() { if [ $1 -ne 0 ]; then echo "error code=$1" rm $tmp exit fi } echo "" echo "" echo "processing bounding box..." osmosis --read-pbf file=$pbffile --bounding-box $* --write-xml file=$tmp check_exit $? echo "" echo "" echo "making gmapsupp.img..." java -jar mkgmap.jar \ --input-file=$tmp \ --route \ --index \ --tdbfile \ --housenumbers \ --gmapsupp check_exit $? rm $tmp echo "Done!" -------------------------------------------------------------------- What mkgmap options should I be using to generate routeable data? Also, the family-name and series-name options no longer seem to work. I've tried r2957 and r2998 with equally dismal results.

2 2

mkgmap and marine mode
by toc-rox 03 Feb '14

03 Feb '14

I was informed by an user, that the Freizeitkarte maps are by default in marine mode. Has someone information which bit is set in this case and what the default set by mkgmap is? Cheers Klaus -- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-and-marine-mode-tp5795133.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 2

link-pois-to-ways
by Minko 01 Feb '14

01 Feb '14

I have a question about the link-pois-to-ways option: In the NL's traffic signs are being mapped. http://wiki.openstreetmap.org/wiki/Overzicht_Nederlandse_Verkeersborden#C:_… On this node, http://www.openstreetmap.org/node/2644156384 there is a traffic sign C6 (motorcar=no) in one direction. traffic_sign:backward = NL:C6 Tagging the whole road with oneway=yes is not the correct situation, because it is not a oneway street. Only entering this street by car is not allowed. Does mkgmap support motorcar:backward = no on a node (like barriers)? And how about the direction, does it look to the direction of the way? Does traffic_sign=NL:C6 {set mkgmap:car=no} in the points file work? A workaround is to tag a small part of the way with motorcar:backward = no or this restriction: http://www.openstreetmap.org/relation/3478910 but a routing node would be better.

2 5

Wrong turn heading when using --process-exits
by Jonas Tull 30 Jan '14

30 Jan '14

Hi! I have an issue where a motorway_link which is modified by --process-exits gives the wrong turn heading instruction in my GPS (Nüvi 205). "Turn left at Exit 113" instead of "Turn right at Exit 113". The way is http://www.openstreetmap.org/way/4400960 When looking at the map in QLandkarte it looks like the first two ways created when the _link way is split are almost parallel to the motorway. My guess is that it's somehow related to the relatively long distance between the first and second node in the original _link way. I build my maps with the following (relevant?) arguments: --adjust-turn-headings --route --housenumbers --process-destination --process-exits This issue can also be seen in the maps downloaded from http://garmin.openstreetmap.nl/ /Jonas

4 7

question on new style
by Steve Sgalowski 30 Jan '14

30 Jan '14

with my old style file on my nuvi 1450lmt unit , there is no hospitals comming up now on the poi section i have included amenity = hospital and building = hospital here is the code i use for it amenity=hospital { name '${emergency} ${name} ${name}' | '${emergency}' | '${name}' '${name }' }[0x2000 resolution 24-10] building=hospital [0x2000 resolution 24-10] but i am still not getting any hospitals included in the poi section Stephen

3 3

Commit: r2998: Fixed the build - add setters on restriction relation.
by svn commit 29 Jan '14

29 Jan '14

Version mkgmap-r2998 was committed by steve on Tue, 28 Jan 2014 Fixed the build - add setters on restriction relation.

2 1

Why this error?
by Ataro A 28 Jan '14

28 Jan '14

The first row is number 512. name=* | name!=* { set debug:on=yes } debug:on=yes { echotags "Point not rendered" } <finalize> # The finalizer section is executed for each element when a rule with an element type matches name=* { name '${name}' } What is meaning of the following error? ** Build map with mkgmap Time started: Tue Jan 28 23:37:10 CET 2014 checking style: cycle Error in style: Error: (points:513): Cannot start expression with: # Part of the previous OR expression. could not open style cycle finished check-styles Error in style: Error: (points:513): Cannot start expression with: # Part of the previous OR expression. Could not open style cycle Time finished: Tue Jan 28 23:37:11 CET 2014 Total time taken: 343ms

1 0

places without a name not rendered
by Minko 28 Jan '14

28 Jan '14

On the osm forum there are requests that some place names are not rendered or hardly visible if the name tag is missing: http://forum.openstreetmap.org/viewtopic.php?pid=394440#p394440 In the default style, places without a name are not rendered if it is a city or a town. I would suggest to adapt those lines: place=city & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 18 continue with_actions] place=town & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 19 continue with_actions] replace by: place=city & cityxx!=yes {set cityxx=yes} [0x0700 resolution 18 continue with_actions] place=town & cityxx!=yes {set cityxx=yes} [0x0800 resolution 19 continue with_actions]

3 10

Commit: r2997: House number block numbers incorrect.
by svn commit 28 Jan '14

28 Jan '14

Version mkgmap-r2997 was committed by steve on Tue, 28 Jan 2014 House number block numbers incorrect. Needs the index within the coords with the node-flag set, not the index within all the coords.

1 0

Commit: r2995: Update restriction relations when a way is split in LinkDestinationHook
by svn commit 27 Jan '14

27 Jan '14

Version mkgmap-r2995 was committed by wanmil on Mon, 27 Jan 2014 Update restriction relations when a way is split in LinkDestinationHook When using --process-destination and --process-exits the links are split into multiple parts. The restrictions need to be updated with the new id of the split way if the split part is relevant for the restriction.

1 0