February 2009 - mkgmap-dev - The mkgmap lists

Find by name - experimental patch
by Mark Burton 01 Feb '09

01 Feb '09

Hi Folks, I recently discovered OSM, josm, mkgmap, etc. it's interesting stuff. As part of my contribution to the general effort, I have been working on getting the garmin "find by name" function working with city names contained in maps generated from OSM files. I believe I have the basis of a solution and the attached patch works for me - YMMV. I am posting it here so that it can be tested on more maps and gps types (I am using a etrex vista) and see if it works OK. Note that the patch hard codes the map's country name to GBR (UNITED KINGDOM). Obviously, that will need to be configurable but I haven't yet worked out the best way of achieving that. You must use a non-6 bit character set. I use the --latin1 option. So, if you can, please try the attached patch and see if it works for you. Obviously, if it breaks other stuff, we need to fix that right away. Cheers, Mark

5 19

Wrong_route_calculation / strange straight routing lines on GPS
by Carlos Dávila 01 Feb '09

01 Feb '09

>On Jan 28, 2009, at 23:10, Gert Münzel wrote: >/> making my first steps with mkgmap that, although the routing works />/> fine in Mapsource, i get in trouble on my Gps unit Garmin gmap60csx. />/> Very often i got these strange straight magenta routing lines in />/> between normal routing. />/> Meanwhile i figured out that it seems to be that t has something to />/> do with the length of a polyline. I don't know if it is the count of />/> points/nodes of the polyline or still the lenght or both. />/> But comparing the same mp-file once compiled with mkgmap, once with />/> cgpsmapper i see, that cgpsmapper split these long lines during />/> mkgmap leave them like they are. /> >How did you compare the IMG files? Have you tried decompiling the >broken IMG with test.display.*? Have you tried manually splitting the >polylines in the .mp-file? Does it help? > >My guess is that the problem lies with long polylines (in the .mp- >file) that are split into several polylines (in the IMG) by mkgmap, >which results in a road made up of several polylines. > >But if I understand you correctly, maybe the problem is just with long >polylines in the IMG file? I think there must be something else than length of polylines and number of nodes. I get this error in a route that always starts at a node in a roundabout, no matter how far you fix the destination out of this point or in how many pieces you split the way. In another case, error seems to me to be related with the route crossing boundaries of an area tagged as area=yes, landuse=industrial, place_name=Pol. Ind. Las Capellanías

4 5

[patch] mkgmap-add-eclipse-support
by Ben Konrath 01 Feb '09

01 Feb '09

Hi, I've been studying the mkgmap source for the past couple of days using eclipse and I needed this patch to get it work. Any chance this could be committed? Comments are appreciated. Cheers, Ben

2 3

[PATCH] proof of concept code to generate fake POIS for named ways
by Mark Burton 01 Feb '09

01 Feb '09

Folks, The attached patch adds a --road-name-pois option that will generate a named node for each named way. It currently places the node near the middle of the way. The fake node has a tag place=road_name_POI and will need an entry in the points file like this: place=road_name_POI [0x640a resolution 21] I think the code 0x64a is a good choice because it is shows up as a "geographic point" (well, it does on the etrex). The patch is really just for experimentation and comment but it could grow into something useful. In particular, the manner I have implemented it may not be optimal/approved. It's just what came to mind first. As I don't actually need this functionality myself, perhaps it would be better for a developer that wants this (and has suitable hardware for testing) to take it over. BTW - It currently makes no attempt to merge multiple ways with the same name. Cheers, Mark

1 3

Commit: r859: Ignore points that don't have both lon and lat.
by svn commit 01 Feb '09

01 Feb '09

Version 859 was commited by steve on 2009-02-01 11:15:31 +0000 (Sun, 01 Feb 2009) Ignore points that don't have both lon and lat.

1 0