- mkgmap-dev - The mkgmap lists

Commit: r1432: Add mkgmap: prefix to carpool tag.
by svn commit 10 Dec '09

10 Dec '09

Version 1432 was commited by markb on 2009-12-10 17:31:43 +0000 (Thu, 10 Dec 2009) Add mkgmap: prefix to carpool tag. This makes it consistent with mkgmap:unpaved and mkgmap:ferry. The toll tag is now the odd-one-out but as toll=yes is often found on highways, it's probably OK not prefixing it.

1 0

Commit: r1431: Reduce the resolution of link ways and motorway exits and adjust speeds.
by svn commit 10 Dec '09

10 Dec '09

Version 1431 was commited by marko on 2009-12-10 17:17:59 +0000 (Thu, 10 Dec 2009) Reduce the resolution of link ways and motorway exits and adjust speeds. Based on a patch submitted by Felix Hartmann.

1 0

Commit: r1430: When linking POIs to ways, replace node in exits list (if required).
by svn commit 10 Dec '09

10 Dec '09

Version 1430 was commited by markb on 2009-12-10 15:18:39 +0000 (Thu, 10 Dec 2009) When linking POIs to ways, replace node in exits list (if required). The bug fix in r1404 broke motorway exits because when the Node was replaced, it didn't replace the reference to the original node in the exits list. It does now.

1 0

Address search in mapsource fails to find some streets
by Mark Burton 09 Dec '09

09 Dec '09

Just playing around with mapsource using the street search feature and noticed that some streets don't show up in the search. For example, in the GB map, I can select "Well Street" from the select street dialog but when I ask it to find that street, it says nothing found. Other streets in the same locality are found OK. It's weird that it knows about the street enough to put it in the dialog but then can't actually find any streets with that name. Is this a known issue? Mark

1 0

Commit: r1428: Fix a typo in the default style: cycle_barier should be cycle_barrier.
by svn commit 09 Dec '09

09 Dec '09

Version 1428 was commited by marko on 2009-12-09 21:32:31 +0000 (Wed, 09 Dec 2009) Fix a typo in the default style: cycle_barier should be cycle_barrier.

1 0

Commit: r1427: Set mkgmap:unpaved=1 in more cases.
by svn commit 09 Dec '09

09 Dec '09

Version 1427 was commited by marko on 2009-12-09 21:25:11 +0000 (Wed, 09 Dec 2009) Set mkgmap:unpaved=1 in more cases. Based on the suggestions of Felix Hartmann.

1 0

Support for advanced multipolygons?
by Nop 09 Dec '09

09 Dec '09

Hi! Are there any plans to support advanced multipolygons in mkgmap? As this type of polygons is supported by both mapnik and osmarender, they are used more frequently. Mkgmap seems to ignore this type completely and more and more larger forests disappear off the Garmin maps, like this area near Vienna: http://www.openstreetmap.org/?lat=48.2539&lon=16.2463&zoom=13&layers=B000FTF bye Nop

4 5

Ist there a node limit ot a way?
by Nop 09 Dec '09

09 Dec '09

Hi! The OSM API has a limit of 2000 nodes to a way since v0.6. In the XML format itself there is no restrictions, if data comes not from the API but from another source like a SHP file import, there might be a larger number of nodes per way. Does mkgmap have a limit on how many nodes per way it can process? Or would it be able to handle larger shapefiles? bye Nop

1 0

[PATCH v1] grok unpavedness
by Mark Burton 09 Dec '09

09 Dec '09

Bloody typical, you wait around for ages hoping for a new routing capability to be added to mkgmap and then two come along on the same day. I've been trying to discover how unpavedness is encoded for at least 6 months. Every now and again, I return to think about it some more. Check and re-check the same old data structures. Very frustrating, no progress. Damn those cunning bastards at Garmin.... However, a month or two ago, I discovered that Table C contains more than just turn restrictions. I still don't know many of it's little secrets but, today, having exhausted all other possibilities, I finally twigged that Table C contains the key to understanding "unpavedness". Gotcha! The attached patch allows you to add either unpaved=yes/true/1 or paved=no/false/0 to a way and then it will be ignored for routing purposes when the GPS has been told to avoid unpaved roads. Not sure if those are the best tags to use - any thoughts? BTW - the unpaved road line type 0x0a has nothing to do with unpavedness, it's just a routable way that gets drawn as a dashed line (default rendering). Feedback, etc. Mark

10 30

Suggestions
by Peter & Suzie 09 Dec '09

09 Dec '09

1. The first suggestion I have is to output the warning messages in html format so that when the url for a problem is logged, the file can be opened in a browser and just click on the link to problem. I played with this and it seems to work, maybe an extra option could be added to output this format so the default is how it is now? 2. This may be able to be done already but I could not see how, currently I use my own style files to create the output I desire but every time a new feature is added the the default ones I need to get that and add to all my style sets or reapply my changes to the default ones. It would be good to have the ability to create a set of overide style files that only contain things that are to be changed from the default style you are using and some type of marker so some default ones can be deleted. Are they worth me looking at?

4 4