- mkgmap-dev - The mkgmap lists

Commit: r689: Code to create rules from the new style files.
by svn commit 08 Nov '08

08 Nov '08

Version 689 was commited by steve on 2008-11-08 08:46:07 +0000 (Sat, 08 Nov 2008) Code to create rules from the new style files. This version still only uses map-features though.

3 2

3byte .typ file support
by Felix Hartmann 03 Nov '08

03 Nov '08

I found out one missing information about the 3byte .typ files. 3 byte typfiles are addes as v2type=XXXXX instead ov type=xx00 I'll confirm this later, but it looks like that if we use v2type=1160d then garmin handhelds (with typ support) will interprete this line as Digital Elevation Model DEM. This could be the key to not only see contour lines, but also have a DEM. See the following articles in Spanish for more information about it (use google translate if you don't understand Spanish too well): http://gpsando.blogspot.com/2008/10/iii-trasteando-de-nuevo-con-el-garmin.h… http://gpsando.blogspot.com/2008/06/trasteando-con-el-garmin-topo-espaa-v3.… http://gpsando.blogspot.com/2008/09/trasteando-de-nuevo-con-el-garmin-topo.…

3 6

Commit: r688: Split up the reader.osm directory for further development on the style system.
by svn commit 02 Nov '08

02 Nov '08

Version 688 was commited by steve on 2008-11-02 17:20:55 +0000 (Sun, 02 Nov 2008) Split up the reader.osm directory for further development on the style system.

1 0

Commit: r687: Minor changes renaming variables.
by svn commit 02 Nov '08

02 Nov '08

Version 687 was commited by steve on 2008-11-02 15:06:36 +0000 (Sun, 02 Nov 2008) Minor changes renaming variables.

1 0

Commit: r686: Merge in from trunk.
by svn commit 02 Nov '08

02 Nov '08

Version 686 was commited by steve on 2008-11-02 13:51:25 +0000 (Sun, 02 Nov 2008) Merge in from trunk.

1 0

3byte .typ file support
by Felix Hartmann 27 Oct '08

27 Oct '08

Well it's the same for the typfile itself, meaning that in the typfile the definition you have to give is the same for getting it displayed. I'm not sure whether the data structure in the .img is the same too, but it could well be. In any case set 0x00 to 0x0000 otherwise the old definition files won't work. For example old: polyline|highway|motorway|0x01||10 should then be read as new and will be displayed without typfile: polyline|highway|motorway|0x01|0x00|10 polyline|highway|newtype|0x01|0x01|10, will however ONLY show up if you give it a definition in the .typfile. I suppose this could work. Garmin even uses a 5 digit definition like this in the typfile: [Polygon] Type=0x1101d Draworder=4 String=4,CONIFEROUS FOREST or [Polyline] Type=0x10e0c String=4,WATERFALL or [Polyline] Type=0x10f00 String=4,BANK So maybe for Polygons and Polylines their defintion would be accordingly polygon|natural|CONIFEROUS FOREST|0x11|0x01d|16 polyline|highway|WATERFALL|0x10|0xe0c|10 with even 3 digits in the subtype. Maybe also it doesn't matter how long the definition can be, the only important thing would be that it is accordingly attributed in the typfile. For POI both exists, for example: [POI] Type=0x6411 String=4,Tower or [POI] Type=0x11502 String=4,CAVE

1 0

3byte .typ file support
by Felix Hartmann 27 Oct '08

27 Oct '08

Is there any work going on related to 3byte support for Polylines and Polygons. In principle this should be the same as for POIs which are already in the 3byte form. With OSM Composer there is now an easy to use GUI for Mkgmap that greatly enhances the need for more definitions. This is due to the possibility to copy any object and assign new tags to it based on criteria (this has been possible using perl but now it became comparably very easy). I.e. you have a Polyline tagged "Highway=track; Bicycle=yes" then you could automatically retag this to something like "Highway=bicycletrac". Or "Highway=track, track_grade=3" to Highway=track3 and render it in a different color. It's too possible to copy objects. Instead of retagging you could now overlay a color code around the track indicating the trackgrade. You would now have two Polylines one Highway=track and an identical one on top of it with "track_grade=3". (I hope I am doing everything correct here, never posted on a mailinglist).

2 1

Commit: r685: Check for zero.
by svn commit 26 Oct '08

26 Oct '08

Version 685 was commited by steve on 2008-10-26 20:33:06 +0000 (Sun, 26 Oct 2008) Check for zero.

1 0

Commit: r684: Allow the Origin keyword
by svn commit 26 Oct '08

26 Oct '08

Version 684 was commited by steve on 2008-10-26 20:32:45 +0000 (Sun, 26 Oct 2008) Allow the Origin keyword

1 0

Commit: r683: Add the node indicator in the rgn file.
by svn commit 31 Aug '08

31 Aug '08

Version 683 was commited by steve on 2008-08-31 13:31:22 +0100 (Sun, 31 Aug 2008) Add the node indicator in the rgn file. This makes routes on my test map work fairly well. One road segment is not displayed, although routes sometimes work as though it is there.

1 0