May 2010 - mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] Really Serious bug when not using --route
by Felix Hartmann 25 May '10

25 May '10

On 25.05.2010 11:53, Alexander Atanasov wrote: > Hi Felix, > > On Tue, May 25, 2010 at 2:02 AM, Felix Hartmann > <extremecarver(a)googlemail.com> wrote: > > >> Just got to test it. Good try but ain't work. Still crashing >> Mapsource/Basecamp. Only solution I think is to make --route default and >> compulsory for the moment. Else people will create maps that havoc other >> maps without realising. >> > Do you have a working image without routing, and if so can you send it > to me/give a link/? > I'll try to find the flag. It must be in the TRE header. > Created with mkgmap, not possible. I'm not sure about cgpsmapper but it could be well possible that it is broken too. As for working .img (it's inside the .img files and not the tdb), you could probably analyse any non routable tile produced with MPC, like most/older Garmin Topo maps.

1 0

Trouble with huge multipolygons
by aighes 24 May '10

24 May '10

Hello! I've trouble with some multipolygons in norway. Screenshot of the Problem you'll find http://www.aighes.de/data/mp.png here (1mb). These 3 destroyed multipolygons have each more then 2000 nodes. Is this a mkgmap Problem, that should be solved, or is it better, to split the multipolygons into several parts. Mapnik renders the area correct. cu, aighes -- View this message in context: http://gis.638310.n2.nabble.com/Trouble-with-huge-multipolygons-tp5090118p5… Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 2

Multipolygons not displayed
by Carlos Dávila 23 May '10

23 May '10

I've noticed that some mp which outer polygon is formed by several untagged ways (e.g. [1] [2] [3]) do not appear in my maps (neither with default or custom style), only inner polygons are displayed. If I add relations style file lines like these: highway=pedestrian & area=yes {apply {add highway=pedestrian; add area=yes; add name='${name}' } } landuse=village_green {apply {add landuse=village_green} } leisure=garden {apply {add leisure=garden} } leisure=park {apply {add leisure=park; add name='${name}'} } then outer polygons are shown in the map, but inner ones disappear. Probably I missed something about mp, but don't know how to get these multipolygons correctly rendered. [1] http://www.openstreetmap.org/browse/relation/537150 [2] http://www.openstreetmap.org/browse/relation/417896 [3] http://www.openstreetmap.org/browse/relation/406299

1 0

seamarks and style file
by frmas 23 May '10

23 May '10

Hello, Do I have the right to write in my style points file something like that : seamark:buoy_lateral:colour=green [0x1604 resolution 20] seamark:buoy_lateral:colour=red [0x1605 resolution 20] The nodes in the osm file are like those ones : <node id='-10342' action='modify' timestamp='2010-05-22T11:29:17Z' visible='true' lat='46.957287947016' lon='-2.322523554923099'> <tag k='seamark:buoy_lateral:category' v='port' /> <tag k='seamark:buoy_lateral:colour' v='red' /> <tag k='seamark:buoy_lateral:shape' v='pillar' /> <tag k='seamark:light' v='yes' /> <tag k='seamark:light:colour' v='red' /> <tag k='seamark:topmark:colour' v='red' /> <tag k='seamark:topmark:shape' v='cylinder' /> <tag k='seamark:type' v='buoy_lateral' /> </node> <node id='-10340' action='modify' timestamp='2010-05-22T11:29:17Z' visible='true' lat='46.96333741944368' lon='-2.3130953826729668'> <tag k='seamark:buoy_lateral:category' v='starboard' /> <tag k='seamark:buoy_lateral:colour' v='green' /> <tag k='seamark:buoy_lateral:shape' v='pillar' /> <tag k='seamark:topmark:colour' v='green' /> <tag k='seamark:topmark:shape' v='cone, point up' /> <tag k='seamark:type' v='buoy_lateral' /> </node> Thank you. Francois --

2 2

Suggestion for multipolygon version of --generate-sea
by Charlie Ferrero 22 May '10

22 May '10

Hi list, One of the good things about the non-multipolygon version of --generate-sea (--generate-sea=no-mp) is that it generates a land polygon, which for those of us who cannot change the default Garmin yellow colour of the background is very useful. As far as I can tell, the multipolygon version of --generate-sea does not create this land polygon, which is a bit of a drawback. Is there any chance the multipolygon code could be extended to add a land polygon creation option just like the no-mp approach does? Or perhaps it's already there and I just don't know how to apply it? Thanks, -- Charlie

2 1

Fedora packaging for mkgmap
by Bruce Cowan 21 May '10

21 May '10

I'm currently working on packaging mkgmap for Fedora[0]. I'm using revision 1647, as it was the most up-to-date when I was doing the packaging. I'd welcome any recommendations or advice on which revision to choose for the initial packaging, or any other comments. [0] https://bugzilla.redhat.com/show_bug.cgi?id=592645 -- Bruce Cowan <bruce(a)bcowan.me.uk>

2 1

Re: [mkgmap-dev] [PATCH] Routable pedestrian areas
by Minko 20 May '10

20 May '10

Well, I compiled the map with version 1620, and on my map the outlines of those pedestrian areas are rendered as footway, and are routable (dotted lines). The polygon is rendered grey. See a screenshot of my map at http://img249.imageshack.us/img249/993/dam.jpg The osm data of this square: http://www.openstreetmap.org/browse/way/34132635 IF those are connected to other roads, you can make a good routing already without a patch. In my style file the continue statement makes sure the pedestrian roads are rendered (as footway) as well as the area. Minko Marko Mäkelä wrote An educated guess: you cannot translate the same way to both a polygon (area) and a line, or can you now that the style branch has been merged to trunk? I would prefer to see this in the style file. The fewer hard-coded tweaks in the mkgmap core, the better. Is there now a way to implement the oneway-cycleway duplication in the style file? If there is, could the current code be removed from the core?

8 9

Transliteration of persian and arabic script
by Claudius Henrichs 18 May '10

18 May '10

Currently if the name-tag is written in persian or arabic script on a garmin device it ends up transliterated into latin script. I am not sure if garmin is doing this internally or mkgmap. Can any developer clear this up? I am asking because this transliteration contains some error as it seems some persian characters (at least one, the "alef") are not mapped to latin ones so they end up as question marks Some examples: source: پمپ بنزین نامجو current: pmp bnzyn n?mjw correct: pmp bnzyn namjw source: میدان سعدآباد current: myd?n s'dab?d correct: mydan s'dabad source: مجتمع پزشکی ثامن الائمه current: mjtm` pzshkhy th?mn ?l?y'Mh correct: mjtm` pzshkhy thamn alay'Mh I've found script/make-transliteration-table.pl and as far as I understand the mapping error seems in Perl's Text::Unidecode module then. Maybe the script's author, Ævar, can take a look :) Thanks in advance, Claudius

5 6

Exception from Format6Encoder
by Ronny Klier 18 May '10

18 May '10

Hi, using current Geofabrik extracts for Germany I run in an ArrayIndexOutOfBoundsException: at uk.me.parabola.imgfmt.app.labelenc.Format6Encoder.put6(Format6Encoder.java:136) at uk.me.parabola.imgfmt.app.labelenc.Format6Encoder.encodeText(Format6Encoder.java:90) at uk.me.parabola.imgfmt.app.Label.write(Label.java:117) at uk.me.parabola.imgfmt.app.lbl.LBLFile.newLabel(LBLFile.java:125) at uk.me.parabola.mkgmap.build.MapBuilder.processPOIs(MapBuilder.java:461) at uk.me.parabola.mkgmap.build.MapBuilder.makeMap(MapBuilder.java:193) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:96) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:61) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:189) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:1) The string to encode is "½" (1/2 as single character). This is used as housenumber in Wuerzburg: http://www.openstreetmap.org/?lat=49.801248&lon=9.927579&zoom=18 To solve this I increased the byte buffer provided in encodeText by 1. But I'm not sure if this is the right solution. Ronny

2 1

[PATCH v2] Advanced restrictions
by Nakor 16 May '10

16 May '10

Hello, So my post from a couple weeks ago was correct. You can have turn restrictions with via ways. Attached is a patch that does that and also implements the "More restriction exceptions <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2010q2/008330.html>" I posted yesterday. I'd like to warn that this was a quite complex thing and I did not fully understand the relation structure in mkgmap so it may break other thinks. I needs to be reviewed by s.o. who knows how restriction relation works in mkgmap. It has limitations as well: * If the via ways gets split for routing (like in http://www.openstreetmap.org/browse/relation/275622 where via way http://www.openstreetmap.org/browse/way/41694496 gets split at http://www.openstreetmap.org/browse/node/62547613 because of an incoming ramp), the relation creation fails * I did not try with more than one via way but it probably just fails as well Those again would need to be looked at by s.o. with better knowledge of how routing and restrictions works. Thanks, N.

4 11