- mkgmap-dev - The mkgmap lists

[PATCH v4] - Code around highway shield crap when sorting labels
by Mark Burton 21 Mar '10

21 Mar '10

v4 - found the motorways (and a load of other roads too!) -------- v3 - now works harder to clean up road names for use in MDR file - not sure if this will have a beneficial effect but it could possibly fix the issue recently reported by Felix. Motorways are still not showing up. ------- v2 - remove more duplicate labels that only differ in letter case - remove leading spaces from labels even if they start with a Garmin code. Still something wrong with motorway names because on the UK map, only the M74 appears in the mapsource road names - all other motorways are missing - very odd. ------- This patch codes around the problems introduced by highway shields with regard to the sorted roads: 1 - the sort order should now be much improved 2 - no duplicate symbols (shield version + non-shield version) It also includes a fix to the label reading code so that labels with a highway shield prefix are read in correctly when generating the MDR file. For me, in mapsource, road search for roads with highway shields now works apart from motorways which don't seem to searchable - perhaps that's deliberate on Garmin's part? All feedback appreciated. Mark

3 11

Disable multipolygon processing
by Charlie Ferrero 20 Mar '10

20 Mar '10

Hi, Is there a way of disabling the multipolygon processing completely? I generate a routing layer that has no areas nor does it care about relations, so it would be nice if I could disable multipolygon processing to make things quicker. -- Charlie

3 2

Address search and "State"-question on Garmin Oregons
by Daniela Duerbeck 20 Mar '10

20 Mar '10

Hi! Today I bought a Garmin Oregon because of the great features. Now I encountered the (I think) well known state-prompt-issue in the address search. But I find many questions concerning this issue but few answers. Is there already a wiki page? TIA, Dani

2 1

turn restriction relations supported?
by maning sambale 20 Mar '10

20 Mar '10

Hi, Is this supported in mkgmap? http://wiki.openstreetmap.org/wiki/Relation:restriction What should be added in the relations style file? -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

4 6

Mapsource 6.16 - does not send mkgmap created maps with --index to GPS
by Felix Hartmann 20 Mar '10

20 Mar '10

Hi, I'm not sure how many of you are already working with the 6.16 beta. It seems that there is much stricter checking for correct address index, meaning mkgmap created maps where the mdr/mdx is registered cannot be sent to GPS with 6.16. Or is someone able to send maps with address index registered (if not registered, maps transfer okay) to GPS with 6.16.02??

1 0

Missing island names
by Marko Mäkelä 19 Mar '10

19 Mar '10

Now that the waters are displaying fine, with names, I am facing another problem: The names of islands are missing when using the default style. I do not see them even in the gmapsupp.img file. Here are two examples that I tried. The first one is very sparsely mapped, and the second one is very detailed: http://www.openstreetmap.org/browse/way/42942687 name=Karjamätäs, place=islet (role=inner in a multipolygon that has waterway=riverbank in role=outer) http://www.openstreetmap.org/browse/way/36911729 name=Seurasaari, place=island, natural=coastline (in the Baltic sea) There is a place=island in the points file but no place=island or place=islet in the polygons file. Would that help? What should the area name be set to? If a natural=coastline is converted to a sea multipolygon by the generate-sea code, should the natural=coastline island also be converted to a land multipolygon in role=outer and any areas on the island in role=inner, so that there would be no drawing conflict with areas on the island? Best regards, Marko

2 2

understanding mkgmap logs
by maning sambale 19 Mar '10

19 Mar '10

Hi, Thanks to charlie I activated logging in my map compilation and it sure helps in fixing routing issues! I already found and fixed a few oneways coming from nowhere Several reports I don't understand: 2010/03/18 20:31:26 WARNING (StyledConverter): philippines.osm: Motorway exit null (http://www.openstreetmap.org/?mlat=7.07588&mlon=125.62656&zoom=17) has no motorway! (either make the exit share a node with the motorway or specify the motorway ref with a exit:road_ref tag) 2010/03/18 20:31:26 WARNING (StyledConverter): philippines.osm: Motorway exit closed subdivision gate (http://www.openstreetmap.org/?mlat=14.13477&mlon=120.97857&zoom=17) has no motorway! (either make the exit share a node with the motorway or specify the motorway ref with a exit:road_ref tag) In my style I assigned barrier=gate as a highway exit: barrier=gate [0x2001 resolution 24] Full log is here: http://dl.dropbox.com/u/607635/osm-ph_gps_maps/latest/mkgmap.log.0.txt -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 2

[PATCH v1] Multipolygon: Allow nested inner polygons
by WanMil 19 Mar '10

19 Mar '10

I have found that some multipolygons use nested inner polygons. Example: * A forest (outer) with a lake (inner) that has an island (inner) which is not a forest. (example: http://www.openstreetmap.org/browse/relation/331402) By definition of the multipolygon relation (http://wiki.openstreetmap.org/wiki/Relation:multipolygon) one has to create two mps. But I see that it is a nice simplification lots of mappers are using. Attached patch handles this situation. The inner and outer roles are now used as follows: * the outmost polygon must have role=outer (or role=<empty>) * all outmost polygons with role=inner are not used (a warning is issued) * all inside polygons with role=inner use their own tagging * all inside polygons with role=outer use the mp tagging if available or their own tagging if the mp is not tagged * all inside polygons with role=<empty> are categorized automatically as outer/inner depending on the nest level * all inside polygons with role=outer without a direct ambient inner polygon are dropped with a warning message (outer in outer polygon) Most of the renderers do not support inner in inner polygons but I think it is a very reasonable extension of the multipolygon handling. This patch also improves the error messages. I haven't seen any more "are not processed due to an unknown reason" messages and I look forward that the community will also not be able to generate any more ... ;-) WanMil

7 23

[PATCH v3] - Code around highway shield crap when sorting labels
by Mark Burton 18 Mar '10

18 Mar '10

v3 - now works harder to clean up road names for use in MDR file - not sure if this will have a beneficial effect but it could possibly fix the issue recently reported by Felix. Motorways are still not showing up. ------- v2 - remove more duplicate labels that only differ in letter case - remove leading spaces from labels even if they start with a Garmin code. Still something wrong with motorway names because on the UK map, only the M74 appears in the mapsource road names - all other motorways are missing - very odd. ------- This patch codes around the problems introduced by highway shields with regard to the sorted roads: 1 - the sort order should now be much improved 2 - no duplicate symbols (shield version + non-shield version) It also includes a fix to the label reading code so that labels with a highway shield prefix are read in correctly when generating the MDR file. For me, in mapsource, road search for roads with highway shields now works apart from motorways which don't seem to searchable - perhaps that's deliberate on Garmin's part? All feedback appreciated. Mark

2 2

Broken Routes based on mkgmap map due to "functional characters" inside name
by Felix Hartmann 18 Mar '10

18 Mar '10

Hi, I just got this comment yesterday via my homepage. Seemingly mkgmap in some circumstances puts ENQ - functional characters into the name of streets (when adding the name from a route relation). This causesMapsource not being able to reopen a saved route, nor the route working correctly on GPS. The functional are not displayed inside the tooltip, but visible when opening a (.gdb) route inside a text editor). My style-files are accessible here (Web-SVN or SVN): http://openmtbmap.origo.ethz.ch/wiki/development See the original comment I got in German below: Comment: Hallo, ich schon wieder!! Bei mir ist folgendes Problem aufgetreten: Ich habe Routen mit Mapsource auf der NRW- (openmtbmap – nordrhein-westfalen.7z.zip)oder Holland-Karte (openmtbmap – Netherlands)erstellt, konnte die jedoch teilweise nicht vom PC auf's Nüvi übertragen. Dank netter Menschen im Garmin-Forum stellte sich als Ursache heraus, dass bei den problematischen Routen an einer oder an mehreren Stellen in der Datei (als GPX mit MS gespeichert (lassen sich aber mit MS nicht wieder ööffnen) und mit einem Editor betrachtet) ENQ - Steuerzeichens enthalten waren. Die entsprechenden Zeilen sehen so aus; Nrw Nrw Radverkehrsnetz Nrw, Kreis Borken Lcn Cw Nrw Nrw Radverkehrsnetz Nrw, Kreis Borken Lcn Cw oder Rom Rom Via Romana Rcn Trk Rom Rom Via Romana Rcn Trk Das markante ist also, dass das erste Wort des Textes mit diesem ENQ - Steuerzeichen wiederholt wird. Da das doch die Infos aus den Karten sind, frage ich mich, ob die Daten evtl. so aus den Karten kommen. Die Abspeicherung der Route als GPX und die Öffnung mit dem Editor können nicht die Ursache sein, da auch das Nüvi 550 solche Routen nicht mal als Datei (geschweige denn als Route verareitet) annimmt. Wenn ich diese ENQ's entferne und die Datei mit MS öffne, dann ist wieder alles ok und das Nüvi nimmt sie an.

3 2