- mkgmap-dev - The mkgmap lists

Commit: r1075: Pipeline and more contours in default style.
by svn commit 03 Jul '09

03 Jul '09

Version 1075 was commited by steve on 2009-07-03 11:57:05 +0100 (Fri, 03 Jul 2009) Pipeline and more contours in default style. -Ondrej Novy

1 0

Commit: r1074: Sends a message to the console from an action block.
by svn commit 02 Jul '09

02 Jul '09

Version 1074 was commited by steve on 2009-07-02 19:53:23 +0100 (Thu, 02 Jul 2009) Sends a message to the console from an action block. Useful to see what is happening when creating complex rules. - Richard Fairhurst

1 0

Questions related to practical usage of MKGMAP
by Garvan 02 Jul '09

02 Jul '09

Hi. I have a few questions related to MKGMAP that I could not find answers to in the archives. My data source is mostly OpenStreetmap, but I used gpsmapedit for editing and adding my own traces, so I am using mp format files with the compiler. I am open to other suggestions on managing data, but I need strong editing capabilities. Q1. I have about sixty roads where I get the severe warning: SEVERE (RouteArc): Way ~212 contains an arc whose length is too big to be encoded so the road will not be routable As the warning gives no line number, I am at a loss to find the problem. Does anybody know how I might locate these 60 roads? I tried sorting the roads by number of points, but did not seem to find a match. Perhaps if I calculated the length of each road segment, and sorted by length? Q2. In encoding sea polygons, I must split the polygons up so that they have less than 256 points (I did this in gpsmapedit). When zooming in and out, sometimes polygons show white lines in between, where the shape has been optimized. It there a way to avoid this, or a better way to split up large polygons? Is there a utility to help with this problem? I would only need to do it once, so it does not matter if it is a convoluted route to what I want. Q3. I would like to use road numbers as labels. In gpsmapedit you use the a code like this ~[0X06]117 in the label for the road, but this did not work in MKGMAP. Is there some other way to display road numbers? Thanks for any help and suggestions. Garvan

11 16

Option "preserve-element-order"
by Thilo Hannemann 02 Jul '09

02 Jul '09

Has anybody had success controlling the drawing order with the "-- preserve-element-order" option? The drawing order is random for me, with or without this option. Would be nice to get it working, though, especially for overlays. Regards Thilo

5 10

Commit: r1072: Undo recent change that (potentially) could create a short arc.
by svn commit 01 Jul '09

01 Jul '09

Version 1072 was commited by markb on 2009-07-01 23:48:13 +0100 (Wed, 01 Jul 2009) Undo recent change that (potentially) could create a short arc. It would be extremely unlikely to happen but why introduce new bugs when we have sufficient already?

1 0

Commit: r1071: Don't upper case in the generic layer.
by svn commit 01 Jul '09

01 Jul '09

Version 1071 was commited by steve on 2009-07-01 23:00:02 +0100 (Wed, 01 Jul 2009) Don't upper case in the generic layer. The requirement for labels to be in upper case is a feature of the img format and so is done there (or not if you have the --lower-case flag set). The lower case flag will now have an effect.

1 0

Commit: r1070: Remove "OSM" from message as id could be a PM RoadID.
by svn commit 01 Jul '09

01 Jul '09

Version 1070 was commited by markb on 2009-07-01 15:48:23 +0100 (Wed, 01 Jul 2009) Remove "OSM" from message as id could be a PM RoadID.

1 0

Commit: r1069: Increased MAX_ARC_LENGTH as RouteArc scales arc length down.
by svn commit 01 Jul '09

01 Jul '09

Version 1069 was commited by markb on 2009-07-01 15:33:24 +0100 (Wed, 01 Jul 2009) Increased MAX_ARC_LENGTH as RouteArc scales arc length down. RouteArc appears to work in units of 16 feet rather than metres so we can increase the limit here to 75Km without RouteArc barfing.

1 0

Commit: r1068: Now outputs OSM id of way that has arc too long to encode.
by svn commit 01 Jul '09

01 Jul '09

Version 1068 was commited by markb on 2009-07-01 15:33:21 +0100 (Wed, 01 Jul 2009) Now outputs OSM id of way that has arc too long to encode.

1 0

Re: [mkgmap-dev] Option "preserve-element-order"
by Marco Certelli 01 Jul '09

01 Jul '09

--- Mer 1/7/09, Tomas Straupis <tomasstraupis(a)gmail.com> ha scritto: > 2009/7/1 Felix Hartmann <extremecarver(a)googlemail.com>: > > Drawing order on GPS: > > 1. Polygons (doesn't matter which layer nor map-id,) > --> polygons themselves > > by draw order in typfile. > > How exactly can I control that (where/what is that > typfile)? > In exact, I want to have lakes on top of forests. > Moreover: do you know what is the default GPS drawing order for polygons when a TYP file is not present? At least for the "standard" Garmin polygon types. Marco.

2 1