- mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] Commit: r868: Implement routing for .osm input files
by stefan＠binaervarianz.de 13 Feb '09

13 Feb '09

Sorry for the quick post some minutes ago. I had to leave for work and was in a hurry. The downloaded OSM data seams big enough to contain the region I asked for with all ways and stuff. mkgmap doesn't display any error messages regarding the files size. I compiled a map about 70% of this size some days ago (with the snapshot version), which came out as just one file after usage of splitter. So I though this map wouldn't need to be chopped in pieces either. Maybe I was wrong? As posted before, if I try to use splitter on the osm file now, it produces an error. I'm running this on a Mac (privious test were on a Win-PC), but that should make any differences, right? I can upload the .osm file to anyone who likes to test it. Even if it is corrupt, maybe someone can find a way to detect this and make mkgmap output a meaningfull error message? (please allow 8-9h until I return from work) If you say my command lines were right, I don't know what else to do other then to download the OSM data again. ----- Ende der weitergeleiteten Nachricht -----

2 1

Re: [mkgmap-dev] [PATCH] make gps report correct exit when routing through roundabouts
by Paul 12 Feb '09

12 Feb '09

For what it's worth.. r877 patched or unpatched completes on todays data r878 patched or unpatched completes on todays data r878 patched had a final file size 0.1MB bigger than unpatched Hopefully it was just a case of routing nodes too close together. Personally I haven't yet seen any issue with roundabouts such as those you described earlier but I'll keep the --frig-roundabouts option enabled Paul P.S. Sorry about the personal email Mark. I didn't realise these weren't going to the list Mark Burton wrote: > Hi Paul, > >> Any of the attached should fail (they do for me) but remember that they >> only fail on the patched version of r877. > > Thanks, I couldn't get them to fail but I have changed the code a little > so, perhaps, the problem has gone away. > > Cheers, > > Mark > >

1 0

Routing over ferrys
by Jan-Ole Spahn 12 Feb '09

12 Feb '09

Is there anything known about routing for cars over ferrys? I mean short ferrys routes over a river or over the Kiel-Channel like in my case. I tried several start an stop points that should cause the ferry to be the shortest and fastest way, but my garmin routes an other (much longer) way over the next bridge. The ferry is tagged with route=ferry, and I tried also with additional key motorcar=yes. Cheers, Jan

2 2

[PATCH] make gps report correct exit when routing through roundabouts
by Mark Burton 12 Feb '09

12 Feb '09

As discussed yesterday, the gps sometimes tells you to leave the roundabout at an earlier exit than it should. I believe that whether this happens or not is influenced by the angle at which roads are attached to the roundabout or something related to the angles between the roundabout segments. For example, a roundabout with 4 points, each point having a road, will probably work OK if the roads "point" pretty much at the centre of the roundabout, like this: | --@-- | But if the roads are more like this: -- -- @ -- -- the gps is likely to get the exit count wrong. The attached patch "frigs" roundabouts by adding an extra point between each pair of adjacent nodes. The extra points are positioned "outside" of the line joining the two nodes. The effect is to make roundabouts "rounder". Unfortunately, it also makes them ugly as the frigging is being done by a dumb computer with little aesthetic capability. However, the good news is that it appears to make the routing instructions specify the correct exit now. YMMV If interested, please try this out and report success/failure. In particular, it would be good to know if it makes roundabouts that previously were OK, bad. The patch is for the current "nod" branch. Cheers, Mark

5 12

mkgmap-869 pinky routing line
by Gert Münzel 11 Feb '09

11 Feb '09

Hi, i have tested r869 with a simple trailtrack. A part of this track(trackpart_26), which caused the problem before now is working. Unfortunately trying the whole track doesn't work. The pinky line is drawn straight between trackpart_140 and trackpart_141 and again ok starting with trackpart_142. Splitting trackpart_141 into 2 pieces solves it. trackpart_141 contains 24 nodes with 711m length. But there were other parts(e.g. 105, 142,143) which are bigger. For me without any knowledge of the garmin img structure its a riddle. As you already mentioned, there must be another reason. But anyway hope my observings are helpful for you guys. I tried to attached the zipped mp-format-file of this track not knowing if its possible in this mailinglist. regards Gert Münzel

3 6

Commit: r877: Fix error in distance calculation for equal coordinates.
by svn commit 11 Feb '09

11 Feb '09

Version 877 was commited by robert on 2009-02-11 10:48:09 +0000 (Wed, 11 Feb 2009) Fix error in distance calculation for equal coordinates. Distance calculation is now cut short for equal nodes. For some coordinates, the calculation could result in NaN. Other cosmetic changes.

1 0

Commit: r876: Patch for ferries and routing.
by svn commit 10 Feb '09

10 Feb '09

Version 876 was commited by steve on 2009-02-10 23:08:13 +0000 (Tue, 10 Feb 2009) Patch for ferries and routing. - Mark Burton

1 0

Commit: r875: highwayType can now be null.
by svn commit 10 Feb '09

10 Feb '09

Version 875 was commited by steve on 2009-02-10 22:54:06 +0000 (Tue, 10 Feb 2009) highwayType can now be null.

1 0

Commit: r874: Make ferries and roundabouts routable.
by svn commit 10 Feb '09

10 Feb '09

Version 874 was commited by steve on 2009-02-10 22:41:33 +0000 (Tue, 10 Feb 2009) Make ferries and roundabouts routable. -Mark Burton

1 0

Commit: r873: Tweeks for speed.
by svn commit 10 Feb '09

10 Feb '09

Version 873 was commited by steve on 2009-02-10 22:39:25 +0000 (Tue, 10 Feb 2009) Tweeks for speed. -Mark Burton

1 0