- mkgmap-dev - The mkgmap lists

Commit: r1573: Fix NullPointerException due to null's being passed instead of
by svn commit 16 Feb '10

16 Feb '10

Version 1573 was commited by steve on 2010-02-16 20:45:23 +0000 (Tue, 16 Feb 2010) Fix NullPointerException due to null's being passed instead of empty sets in new style code.

1 0

no success with --index
by n willink 16 Feb '10

16 Feb '10

Hi I've been trying to create mdx files using --index but to no avail. java -Xmx1024m -jar mkgmap.jar --remove-short-arcs --gmapsupp --family-id=2611 --tdbfile --index --keep-going K:\a_mapsource\mapfeb.osm these are the only files I get: 63240001.img 63240000.img 63240001.tdb Am I missing something? Nick

3 2

[PATCH v4] heed the through_route relation when adjusting turn headings
by Mark Burton 16 Feb '10

16 Feb '10

v4 - in the absence of a through_route relation, don't be fooled into thinking that a side road is the continuing road when it has the same name as the continuing road. -------------------- v3 - bug fixes: now ignores through_route relations if the junction is outside of the tile's bounding box should no longer think that ways that have been split do not start or end at the junction. -------------------- v2 - no longer requires the node to have role "junction" This patch also includes two other changes to the heading adjustment code: When matching arcs, as a last resort, match road class and speed. If at a node, an outgoing arc cannot be matched to an incoming arc by possiblySameRoad(), try to find a single outgoing arc that has the same road class and speed as the incoming arc and use that. and: When adjusting turn headings apply all relevant adjustments. Previously, if a heading needed adjusting because the delta from the outgoing arc was too small, it did not then consider whether the delta from the incoming arc was too small also. Now, it considers both cases and adjusts the heading as appropriate. So please test even if you are not adding any through_route relations and if you see any notable changes (good or bad) please say. -------------------- This new relation (type through_route) specifies which 2 ways are the "through route" at a junction. The relation requires 2 ways (no role required) and a node with role = junction. It should only be used at those junctions where the through route cannot be reliably inferred from the ways' names and/or refs. Here's an example from my local town: | 1 | / | / |/ A | | | | B /| / | / | 2 | The vertical road is the "through route", i.e. you can drive from one end to the other without crossing any white lines. But, from point 1 to point 2 is a B road so ways 1-A, A-B, and B-2 all have some ref, say, B1234. Without the through_route relation, mkgmap assumes (erroneously) that the through route is 1-2 because all of the ways in that route have the ref B1234. By adding 2 through_route relations (one at A and the other at B), mkgmap is informed of the real through route and will take that into account when adjusting the turn headings. The end result is that the quality of the routing directions is improved (we hope). In this example, we need to have 2 relations because the B road joins/leaves the through route at two places. So if you know of any junctions that would benefit from this relation, please add it to the map data and try this patch to see if it improves the routing instructions. Mark

1 0

TYP files : an new tool
by David 16 Feb '10

16 Feb '10

Hello there, I know some of you are looking for a tool which could produce TYP file. I was on the same way since last december. This may help you... http://emerald-island.eu/wikka/MakeTyp Written in C++, the tool is based on this great Perl script from http://ati.land.cz/ and use FreeImage for cool images transformations This is my first release, use it carefully. Cheers, David PS : now, it is your turn, make a graphical editor.

2 1

[PATCH] Enable elevation profile in MapSource
by Ronny Klier 15 Feb '10

15 Feb '10

Hi, there seems to be a way to show elevation profiles for a route without having the DEM subfiles stored in the map. There is a byte in TDB file's header section which can be set to 1. If set MapSource generates the profile from the contour lines. The result is not as good as having the full information from DEM subfiles but better than nothing. Please try this patch, especially with maps without contour lines. Maybe setting this flag has to be bound to existing contour lines. Ronny

6 15

dent in street and bounds problem
by Torsten Leistikow 15 Feb '10

15 Feb '10

Moin, I have attached an OSM-file, where i have to effects with mkgmap-1562: 1. If I convert the OSM-file without any prior editing, the resulting map in mapsource is empty. If I remove the bounds section first, then I get the expected result. I don't know, wether the bounds are set incorrectly by JOSM (I created the OSM file by downloading and saving the data with JOSM), or whether mkgmap has a problem with such small bounds sections. 2. In the attached screen shot you can see the resulting map created by the attached OSM-file. If you zoom in very closely, there is a dent in the secondary road. If I open the OSM-file in JOSM, there is no such dent visible. Is this a data resolution problem of the Garmin format? In JOSM the intersection with the Pirschweg is more north than the intersection with the Bruchweg, in Mapsource it is inverse. Gruss Torsten

3 7

Commit: r1572: Correct and expand documentation of name-tag-list
by svn commit 15 Feb '10

15 Feb '10

Version 1572 was commited by steve on 2010-02-15 16:29:04 +0000 (Mon, 15 Feb 2010) Correct and expand documentation of name-tag-list

1 0

Name sequence
by Chris-Hein Lunkhusen 15 Feb '10

15 Feb '10

Hi, I created a test map of Tokyo and want to use the name:en tag for the names. But I found that changing the name_tag = name:en in the options file is not working. Do I also have to change all references to 'name' in the lines file to 'name:en' ? # Set highway names to include the reference if there is one highway=motorway {name '${ref|highway-symbol:hbox} ${name}' | '${ref|highway-symbol:hbox}' | '${name}' } highway=trunk {name '${ref|highway-symbol:hbox} ${name}' | '${ref|highway-symbol:hbox}' | '${name}' } highway=primary {name '${ref|highway-symbol:box} ${name}' | '${ref|highway-symbol:box}' | '${name}' } highway=secondary {name '${ref|highway-symbol:oval} ${name}' | '${ref|highway-symbol:oval}' | '${name}' } highway=* {name '${ref} ${name}' | '${ref}' | '${name}' } Chris

3 3

{Spam?} multipolygon with outer polygon within inner polygons
by Minko 15 Feb '10

15 Feb '10

Hi, I'm trying to build a map of The Netherlands and got some problems with rendering the administrative borders correctly. Some parts were related to broken relations between tiles, but the major one was caused by a complex relation of enclaves/exclaves of Baarle in the south of the country. I examined this area more closely and narrowed the problem down to this situation, where I cant render the map correctly with mkgmap: A = one big outer ring (the Dutch municipality of Baarle-Nassau), B1, B2 = some islands inside (Belgium territory, role=inner) C= Within some of those islands there are polygons (Dutch, role=outer) It goes wrong with those outer polygons within the inner polygons. Simplification looks like this, where the two vertical border lines are not supposed to be there: http://img63.imageshack.us/img63/1002/bordersnl5.jpg The relation can be found at http://betaplace.emaitie.de/webapps.rel onId=47798 There are no gaps or faults within the relation as far as I can see. I put this question and a few examples of my map also on the forum at http://forum.openstreetmap.org/viewtopic.php?pid=59370 Thanks, Minko

6 6

Confusing results when uploading.
by Dave F. 15 Feb '10

15 Feb '10

Hi When using this command line: java -Xmx512M -ea -jar mkgmap.jar --transparent --style-file="c:\dwgs\Programs\GPS All\Garmin Profile" --family-id=42 M000002.TYP 63272002.gz it creates a 63272002.img using my customized styles & when uploaded appears as I would expect. But when I use the same file to be included in the gmapsupp file in this command the 63272002.img displays as if it was created using the built in style of mkgmap: java -Xmx512M -ea -jar mkgmap.jar --remove-short-arcs --gmapsupp "Contours.img" "63272002.img" --generate-sea:polygons --transparent --style-file="c:\dwgs\Programs\GPS All\Garmin Profile" --family-id=42 M000002.TYP MyTown.osm move "C:\dwgs\Programs\GPS All\mkgmap\gmapsupp.img" "L:\Garmin" Any ideas as to why this is? Cheers Dave F.

3 3