November 2008 - mkgmap-dev - The mkgmap lists

Commit: r728: Add copy to MapElement and implement in subclasses.
by svn commit 29 Nov '08

29 Nov '08

Version 728 was commited by steve on 2008-11-29 14:22:00 +0000 (Sat, 29 Nov 2008) Add copy to MapElement and implement in subclasses. Use wherever copies are being made. (Robert Vollmert)

1 0

Re: Commit: r721: Reversing change to the date routines in this file as I suspect they may be causing the
by Felix Hartmann 28 Nov '08

28 Nov '08

Thanks that fixed it (r723 is working in any case) Now my maps work again in Mapsource. There was however a way to get the broken maps working in Mapsource. 1. set --gmapsupp.img 2. Use gmaptool and "split files for mapsource" the --gmapsupp.img with it and install it to Mapsource. This however strangely only worked for gmapsupp.img. Not for 63240001.img. So the gmapsupp.img was not (as) broken. mkgmap-dev-request(a)lists.mkgmap.org.uk wrote: > Version 721 was commited by steve on 2008-11-27 19:43:04 +0000 (Thu, 27 Nov 2008) > > Reversing change to the date routines in this file as I suspect they may be causing the > recently observed breakage. > > I remember from the beginning that things dont work if the year field has certain values. > >

2 1

bug in LineClipper (branches/nod)
by Robert Vollmert 28 Nov '08

28 Nov '08

Hi, there seems to be something wrong in LineClipper.clip -- it seems to create a bunch of zero-node roads, which then cause a crash in RoadDef.writeNod2 due to a null RoadDef.node. Since my attempts to understand LineClipper.clip failed, I reimplemented it somewhat more explicitly, patch attached. I won't be offended if you prefer to fix your algorithm; the patch is quite ugly and I'm not really sure it works outside my samples. The resulting maps appear to have some segments missing. Do you think this might be caused by clipping? Cheers Robert

2 7

Commit: r723: Table A size can be larger than 128.
by svn commit 28 Nov '08

28 Nov '08

Version 723 was commited by steve on 2008-11-28 00:05:49 +0000 (Fri, 28 Nov 2008) Table A size can be larger than 128. - Robert Vollmert

1 0

Mkgmap .img generation bug
by Felix Hartmann 27 Nov '08

27 Nov '08

There seems to be a but that appeared very recently (I assume about rev 714/715) in the .img generated by mkgmap. It's not possible to integrate them into Mapsource any more (Mapsource will crash on selecting). I will try to find out why and approx at what rev. this bug was introduced. Currently it's only possible to use --gmapsupp.img and then use gmaptool "Split files for Mapsource". to get the maps working in Mapsource. I haven't tested wheter .img generated by mkgmap without --gmapsupp.img work on Garmin Units themselve. It may also have to do something with the new --style-file Felix

2 1

Commit: r721: Reversing change to the date routines in this file as I suspect they may be causing the
by svn commit 27 Nov '08

27 Nov '08

Version 721 was commited by steve on 2008-11-27 19:43:04 +0000 (Thu, 27 Nov 2008) Reversing change to the date routines in this file as I suspect they may be causing the recently observed breakage. I remember from the beginning that things dont work if the year field has certain values.

1 0

routing
by Robert Vollmert 25 Nov '08

25 Nov '08

Hello Steve, all, slowly coming back from an OSM break (sorry), I had a look today at how far mkgmap and routing has come. Great work! So those mysterious TRE header bytes are just computed from the map id? An obscurity feature? I compiled branches/nod and tried creating an img with: $ java -jar mkgmap.jar --route --gmapsupp schoeneberg.osm Correct? After modifying imgfmt.app.net.RoadDef.writeNod2 to return if node==null (that's the routing node), the map compiles. It loads fine on my Etrex Vista HCx, but routing doesn't seem to work. If I try to route, it routes me along the base map (unfortunately, there's a road in the base map near here). I've traced the issue with the null routing node back to mkgmap.general.RoadNetwork.addRoad: in the cases where RoadDef.setNode isn't called, the coordList had length 0. This doesn't happen all the time, though. There's quite a few roads where coordList is non-empty and setNode does get called. Any suggestions on where to investigate further? Are these empty roads to be expected? (I've got the corresponding osm sources, but they're too big to post to the list; let me know if I should send them somewhere.) Cheers Robert

2 3

generating *.tdb from *.img
by Gour 23 Nov '08

23 Nov '08

Hi! Thank you very much for providing mkgmap! Although I do not like (in general) Java software, mkgmap works and it is much better than being forced to use Windoze apps on Linux via Wine etc. I'd like to use QlandkarteGT which requires *.tdb file and I know how to create it when using *.osm files with the --tdbfile option. Now, I stumbled upon few sites which provide pre-made Garmin maps by using OSM data and provide maps either as combined/compressed gmapsupp.img file (which old version of Qlandmkarte would import) or as list of *.img map files (e.g. http://www.osm4you.com/ site) Now, my question is if it's possible to use mkgmap and create *.tdb file out of gmapsupp.img file and/or list of *.img file so that the above mentioned maps could be loaded into QlandkarteGT? Sincerely, Gour -- Gour | Zagreb, Croatia | GPG key: C6E7162D ----------------------------------------------------------------

3 4

Commit: r720: Relations can now be used for style rules. I would imaging that the main use here
by svn commit 23 Nov '08

23 Nov '08

Version 720 was commited by steve on 2008-11-23 19:03:53 +0000 (Sun, 23 Nov 2008) Relations can now be used for style rules. I would imaging that the main use here would be for routes. This will need action rules to be of any use.

1 0

Commit: r719: All polygons were being dropped. This was because every element that was clipped
by svn commit 23 Nov '08

23 Nov '08

Version 719 was commited by steve on 2008-11-23 18:59:30 +0000 (Sun, 23 Nov 2008) All polygons were being dropped. This was because every element that was clipped did not get its max-res copied. It affected all polygons because there was no check to see if a polygon needed clipping first. Gives about a 10% speed improvement, soon to be nullified by the next patch...

1 0