- mkgmap-dev - The mkgmap lists

transparent overlays breaks address-index on GPS
by Gert Münzel 05 Mar '10

05 Mar '10

Hi, Is there anyone else who has tried to use a transparent overlay on an mkgmap builded map which is containing address-index, eg. openmtbmap.org maps?. Everytime i tried it, the index no more works on the gps. Instead using the same overlay with an original garmin map which contains a address-index, this index stays alive on the GPS.? Any ideas? cheers Gert

2 2

Commit: r1594: The patch closes all ways having both endpoints on the same side outside the bounding box. In this case it is not necessary to check if closing the way intersects the way itself.
by svn commit 04 Mar '10

04 Mar '10

Version 1594 was commited by steve on 2010-03-04 23:40:41 +0000 (Thu, 04 Mar 2010) The patch closes all ways having both endpoints on the same side outside the bounding box. In this case it is not necessary to check if closing the way intersects the way itself. This fixes most (but not all) of the outstanding tile splitter problems. - Bugfix: if a polygon was splitted by the bounding box into different distinct polygons only the first of it was taken. Now all distinct polygons are processed. (thanks to Torsten Leistikow) - WanMil

1 0

[PATCH v1] MP: Close ways with both endpoints outside the bounding box
by WanMil 04 Mar '10

04 Mar '10

The patch closes all ways having both endpoints on the same side outside the bounding box. In this case it is not necessary to check if closing the way intersects the way itself. This fixes most (but not all) of the outstanding tile splitter problems. WanMil

4 13

splitter and multipolygon
by Matteo Gottardi 04 Mar '10

04 Mar '10

Hi all, when the splitter split a multipolygon composed by more than one outer member (example: http://www.openstreetmap.org/browse/way/51237752 ), the result is incorrect. Is there any way to fix them? -- * Matteo Gottardi | matgott(a)tin.it * ICQ UIN 20381372 * Linux - the choice of a GNU generation * GPG Fingerprint: * B9EE 108F 52C8 D50C B667 B1F2 AB56 8A01 BA3D 36A1

2 3

[PATCH v1] - when removing short arcs, don't zap looped ways whose ends almost touch
by Mark Burton 04 Mar '10

04 Mar '10

The short arc removal code was removing (non-short) arcs when their ends were close enough to be considered the same point. Now it just leaves them be. Please test this patch if possible because I have reworked the short arc removal code (and some badness could have crept in). You will probably find some (loopy) ways appearing in your maps that were not there before because they were being trashed. Garvan, can you try this patch or shall I send you a mkgmap.jar? Mark

4 6

Bounds problem with streets
by Tim 04 Mar '10

04 Mar '10

Hello, i have attached a screenshot of my Oregon to explain the problem. As you can see, the streets are not "connected" correct. I have made the map with a self made typ file and an extracted OSM file. Is there a special attribute i must set, when i compile the IMG file, or how can i solve the problem? Greetz, Tim

3 2

Inconsistent Structure in Address index
by Felix Hartmann 04 Mar '10

04 Mar '10

JuergenD, has integrated a new function to correct mkgmap address information on mkgmap created maps. He said that all Garmin maps have a clearly defined tree structure from top (country) down to municipalities. He integrated a function to maptk to correct this data on mkgmap created maps (but written out to mp). Maybe if the tree structure would be filled up (well if some data is wrong because it is missing, it will be wrong) completly without holes, transferring address index could work. All maps need to have no holes on City -> Region ->Country. It is supposedly easily seen with MapEdit. Maptk will now fill up these holes with dummies. is location-autofill=2 good enough? Else maybe one should look at the corrections maptk does on mp file. Here is his explanation in German: /Die Adresseinträge haben eine Baumstruktur. An der Wurzel das Land ( Country ), Äste sind die Regionen ( z.b. Bundesland, Region ) und die Blätter sind die Orte ( Citiy ). Die Verweise gehen in der IMG-Datei per Index von City -> Region -> Country. Das kann man sehr gut bei MapEdit sehen. Bei OSM ist diese Kette meist nicht vollständig definiert. Dazu kommt, dass die Definitionen selten durchgängig sind. Mal ist Region ein Bundesland, mal eine Stadt ( City ist dann eine Vorort) u.s.w. Manchmal sind auch die Zuordnungen schlicht falsch. MapTk füllt jetzt die unterbrochene Kette mit Dummies auf. In der IMG-Datei steht nichts falsches, es ist nur unvollständig./ Source: http://www.naviboard.de/vb/showpost.php?p=342685&postcount=20

2 1

Garmin colour palette
by Daniela Duerbeck 04 Mar '10

04 Mar '10

Hi! I am not sure whether this is the correct ML for this posting, but I think it is not completely wrong. I saw that the colour palette used in the online Typ file editor has too few and some wrong colours, almost for my Garmin Etrex Legend HCx. So I extracted the colour palette of a Garmin waypoint icon and built a webpage that shows the correct colours (at least for my L:egend, I don't know whether it is the same for other Garmins with 265 colours, but I think so): http://www.deltadelta.de/garmin_colours/ You can also download all the pages for offline use: http://www.deltadelta.de/garmin_colours/garmin_colours.zip When you click on one colour you get a page completely coloured in this colour with the hex representation for better cutting and pasting it into the editor. And also because a colour can better be judged when a big area is coloured. (A wall painted looks always different from the small sample in the shop ...) Perhaps someone will find it useful. Dani

4 3

MapTk typ problem
by Mark Burton 03 Mar '10

03 Mar '10

Hi Felix, You will be interested to learn that the problem I mentioned recently regarding my polylines not taking the style from the MapTk generated style file is due to a bug in MapTk - I contacted the author about it and he got back to me today saying "it's a bug, I'm working on it." Cheers, Mark

2 1

MapTk Updated + Nuvi POI code question
by Mark Burton 03 Mar '10

03 Mar '10

Those people using MapTk will be interested to know that a new version has just been released (2.7.2) - among other things, it fixes the problems with multiple lines/POIs that have extended types. Also, does anyone know if any of the extended type POI codes do not show a little dot in the middle of the icon on the Nuvi? Why do Garmin do that? Are they assholes? Mark

2 1