March 2011 - mkgmap-dev - The mkgmap lists

Commit: r1876: Only apply merge lines at lower resolutions.
by svn commit 02 Mar '11

02 Mar '11

Version 1876 was commited by steve on 2011-03-02 09:42:19 +0000 (Wed, 02 Mar 2011) Only apply merge lines at lower resolutions. merge-lines is as discussed quite problematic, because it happens after the routing notes are placed, and therefore causes some problems. The closer you zoom in, the bigger these problems, while the further you zoom out, the bigger the speed improvement of using this option (at resolution 24 and 23 it makes basically no difference) and the smaller the problems (22 vs 24 means 1/4 of the wrong distance for info popup or jumping map when panning). This only has any affect if you are using the --merge-lines option. - Felix Hartmann

1 0

Re: [mkgmap-dev] dropping place:village, hamlet, suburb in city search
by Martin Boensch 02 Mar '11

02 Mar '11

> Am 19.02.2011 07:08, schrieb maning sambale: > >> The idea is to declutter the city search of these minor places and >> just the actual city/town will be used to index streets and cities. > There would be a disadvantage: > > I assume the assignment of streets to cities works by searching > the nearest place-node. > > This works better if taking the village und suburbs into account > because the density is higher. > > I'm a littlebit amused that nobody seems to fully understand > the location-autofill algorithm. ;-) > > Sould look into the source code but java isn't my mother language... Is there any solution for this problem? I finally build my first map with index option. When I search for streets or crossroads I can choose the Country and the city. I also found the City Dresden,DEU (http://snailrun.de/images/MapSearch/1.jpg) but also all suburbs, located in Dresden (Plauen in Dresden, http://snailrun.de/images/MapSearch/5.jpg) When I try to search for streets in Dresden I only get a few of them. When I search in Plauen, Dresden I find other streets. Thx

1 0

Include the following patches into trunk -- Patch2 - do not merge lines at resolution 24 and 23 if --merge-lines is used
by Felix Hartmann 01 Mar '11

01 Mar '11

merge-lines is as discussed quite problematic, because it happens after the routing notes are placed, and therefore causes some problems. The closer you zoom in, the bigger these problems, while the further you zoom out, the bigger the speed improvement of using this option (at resolution 24 and 23 it makes basically no difference) and the smaller the problems (22 vs 24 means 1/4 of the wrong distance for info popup or jumping map when panning). There was a discussion about this - archive here: http://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg07262.html This patch is working pretty well and makes --merge-lines usable. I have been using it since back then without any probs. So for as long as merge-lines cannot be implemented before creation of the routing nodes (which according to the discussion is really difficult) this tiny patch is great.

2 4

mkgmap r1871 and --index generated maps crashes 62s
by Thorsten Kukuk 01 Mar '11

01 Mar '11

Hi, today I found the following problem: I'm building my gmapsupp.img files with mkgmap and the --index option (exactly with --add-pois-to-areas --make-all-cycleways --link-pois-to-ways --remove-short-arcs --adjust-turn-headings --route --index --net --tdbfile=yes --latin1 --gmapsup --generate-sea=extend-sea-sectors,floodblocker,close-gaps=10000 ...) Normally I have the following areas on my Garmin: - Germany - Austria - USA Searching for citys in all 3 countrys worked fine. Today, when rebuild with mkgmap r1871, I suddenly couldn't find any city in the USA anymore. After some experiences, I found out that I could only find this citys, which are on the CityNavigator Europe map, which I had still on my Card. After removing the Card, search for Citys shows the nearest citys, but pressing the menu button to search for another city let's my Garmin 62s crash. When I tested it about 14 days ago the last time, this all worked fine. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)

2 3

Commit: r1875: Drop small polygons.
by svn commit 01 Mar '11

01 Mar '11

Version 1875 was commited by steve on 2011-03-01 19:47:01 +0000 (Tue, 01 Mar 2011) Drop small polygons. - Johann Gail

1 0

Include the following patches into trunk -- Patch3 - "reduce-point-density-polygon"
by Felix Hartmann 01 Mar '11

01 Mar '11

Now I have been using this patch a long time and , and it really works fine. It applies the DP filter against polygons with a different agressiveness than for lines. This is really useful because strong DP filter against lines looks really bad, while for polygons the visual quality is degraded less. I currently use /--reduce-point-density=4 and -reduce-point-density-polygon=8/ This is perfect for older GPS like etrex to have speed improvements but no drop in visual quality. Also in Mapsource / Qlandkarte GT this works very well. For Oregon or Dakota I would use something like 2.6 (default current behavior) and 5.2 Archived Discussion can be found here: http://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg04260.html Patch by Johan Gail, working very well since then. (well only that it's not yet set in the help file, so I have to use --x in front of the option) I added a part2 -- to add the option to the help file, and allow it to be used without --x on the mkgmap call.

1 0

Include the following patches into trunk -- Patch1 - Drop small Polygons
by Felix Hartmann 01 Mar '11

01 Mar '11

The following patches are in my eyes really worthwhile and should be added to trunk. They all work fine without glitches. 1. Drop small Polygons I am not sure who wrote this patch, but I have been using it longtime and it certainly does improve map performance especially on higher resolutions. It removes all polygons which consist of less than 8 pixels. If you deem that this is too extreme (though 8 pixels is really nothing, and polygons of less than 8 pixel size are barely noticeable anyhow - and only slow down map drawing) the following line could be reduced to maybe 6 or 4 pixels: + private static final int MIN_SIZE_POLYGON = 8;

4 6

Commit: r1867: Translate leisure=track into a line (footway) unless area=yes.
by svn commit 01 Mar '11

01 Mar '11

Version 1867 was commited by marko on 2011-02-28 11:03:17 +0000 (Mon, 28 Feb 2011) Translate leisure=track into a line (footway) unless area=yes.

6 9

Commit: r1874: Add check for empty coastline ways to prevent IndexOutOfBoundsException
by svn commit 01 Mar '11

01 Mar '11

Version 1874 was commited by wanmil on 2011-03-01 17:57:44 +0000 (Tue, 01 Mar 2011) Add check for empty coastline ways to prevent IndexOutOfBoundsException

1 0

R1870 - Can't Search for Places by Name
by Paul 01 Mar '11

01 Mar '11

My very first post on this list entitled 'Garmin "Feature" or bug?' (24/01/09) (http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q1/000281.html) describes a problem which seems to have re-surfaced. I updated to r1870 from a relatively recent version and re-compiled my maps using the same set of options as I have for months only now I can no longer search for place names. The problem is *exactly* as described previously but I can't say definitively that it is since r1870 that this re-occurred. For what it's worth I removed the basemap months ago and have had no problems with searching for cities until now. If I try to search for addresses then the list is just blank, even the auto-generated list of nearby streets which also used to work I generate my maps as below and simply copy/paste onto my 605 java -Xmx2048M -Dlog.config=$abspath/logging.properties -jar mkgmap.jar --style-file=$stylefiles --index --check-roundabout-flares --adjust-turn-headings --remove-short-arcs $driveon --check-roundabouts --add-pois-to-areas --latin1 --gmapsupp --route --max-jobs --code-page=1252 $specifics --family-id=1400 $mapid*.osm $contours/*.osm CF1400.TYP Thanks Paul P.S. Thanks Charlie for the TYP file -- Help map the world - http://wiki.openstreetmap.org/wiki/Main_Page ----------------------------------------------------------------- () ascii ribbon campaign - against html e-mail.

3 2