- mkgmap-dev - The mkgmap lists

Re: R: [mkgmap-dev] (almost) duplicated node issue
by Marco Certelli 25 May '09

25 May '09

I know about IMG resolution, Mark. That is the reason I think there is a bug. If the Garmin cannot handle such short arcs, mkgmap shall compile the case in a way that does not violate the garmin specs. But I'm not really sure that the problem is exactly this. It might be that mkgmap has a bug in the routing data base compiling. Well I'm not expert, but I guess something goes wrong when the 2 so close nodes collapses in a single node when the garmin encoding is applied. Then 2 nodes in OSM, 1 node in Garmin... and the routing DB gets corrupted. Something like that (but I'm really speculating). Someone should check the code to track the situation. The osm file I've attached (that reproduce the error) is small enough to be tested carefully. Ciao. --- Dom 24/5/09, Mark Burton <markb(a)ordern.com> ha scritto: > Da: Mark Burton <markb(a)ordern.com> > Oggetto: Re: R: [mkgmap-dev] (almost) duplicated node issue > A: mkgmap-dev(a)lists.mkgmap.org.uk > Data: Domenica 24 maggio 2009, 19:04 > > Hi Marco, > > I believe that the distance between nodes must not be less > than some > minimum value (can't remember what it is off the top of my > head). So I > guess what you have found is an arc whose length is too > short to > handled by the garmin software. > > Cheers, > > Mark > > > Well, maybe I've found something strange. > > > > I've attached to this mail a .zip file containing a > small .osm DB (downloaded today) and a screenshot (.png) > > > > If I try to compile the attached .osm file, I get a > map with broken routing data that crashes MapSource (for > example try to get a route from one side to the other of > "Piazza Caprera" in the centre of the map, or try routes in > the lower left corner). This problem is independent by > mkgmap style and mkgmap version (if you download the Italian > map from http://www.team-oid.de/cgi-bin/maps_download/showdir.cgi > compiled about one month ago, you'll get the same routing > problems in this area) > > > > I've discovered an issue that maybe is the cause of > the problem. If you open the attached picture you'll see a > very short segment (less than 1 meter) that you can identify > with the coordinates. It is at the cross between Via Zara > and Corso Trieste (you must zoom a lot). > > > > Well, if you delete this short piece of road, the > routing Data Base is built correctly by mkgmap. Maybe > somthing related to rounding makes this too short segment a > problem during map compiling (the two ends collapses in one > point...). > > > > I don't think I'll be able to go further: I hope that > what I found can help some mkgmap developers to individuate > the issue and a possible solution. > > > > I've not corrected the OSM DB, so you can still > download this area by yourself. > > > > Ciao, Marco. > > > > > > > > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >

5 8

Precision circle
by Nop 25 May '09

25 May '09

Hi! Usually, there is a blue circle showing on my Vista HCx when the position quality is bad. As more satellites are being located, it grows smaller and vanishes when the positioning is good. Recently I have observed that a large circle is showing permanently, even when the positioning is very good (+-3 m). In the GPS forum it was mentioned that the behaviour of the circle depends on the map, so I'm asking the question here, too. Has anybody observed this behaviour? Is there anything during map generation that may influence it? bye Nop

4 7

Precision circle
by Marco Certelli 25 May '09

25 May '09

Just a little bit of info. I made some experiments with a GPS72 with other maps (POI only, not OSM) a couple of years ago. I remember the radius of the circle precision is something like "GPS real-time in-accuracy" + "displayed level map in-accuracy". The map in-accuracy depends on the "garmin" level. If a map shows a level 24 (the most possible "accurate" level), the map precision is 3/4 meters. If the map has only levels up to 23, the precision is 6/8 meters. If the map has a maximum level of 22, precision is 10/15 meters, and so on. Ciao, Marco. P.S. Level 24 means using 24 bits to store coordinates (lat/lon). And so on... --- Lun 25/5/09, Felix Hartmann <extremecarver(a)googlemail.com> ha scritto: > Da: Felix Hartmann <extremecarver(a)googlemail.com> > Oggetto: Re: [mkgmap-dev] Precision circle > A: "Development list for mkgmap" <mkgmap-dev(a)lists.mkgmap.org.uk> > Data: Lunedì 25 maggio 2009, 08:48 > For me on Vista HCx it's working as > well. Once position is accurate, precision circle is very > small. > > Nop wrote: > > > > Hi! > > > > Ralf Kleineisel schrieb: > >> Nop wrote: > >> > >>> The discussion over at the GPS forum points > towards a setting inside the > >>> map, too. It seems mkgmap marks the maps as > terribly inaccurate so the > >>> maximum precision is an inaccuracy of 260m. > >> > >> With my maps generated with mkgmap my eTrex Legend > HCx shows the circle > >> correctly, i.e. it disappears when the GPS > position precision is good enough. > > > > Ok, so we have 2 with the problem, one without. Let's > try to figure out the difference. > > > > Does anybody have any idea where in the map this > setting is stored? > > > > bye > > Nop > > _______________________________________________ > > mkgmap-dev mailing list > > mkgmap-dev(a)lists.mkgmap.org.uk > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >

2 1

"Unpaved Road"
by Marko Mäkelä 25 May '09

25 May '09

Recently, I mapped some disused roads and the like, including this one: http://www.openstreetmap.org/browse/way/34929277/history highway=track motor_vehicle=unknown surface=sand tracktype=grade1 width=2 The map cursor tooltip of the Garmin Edge 705 calls this way "Unpaved Road" in English. I am using the default style of mkgmap -r1040. It remains to be seen if this is related to the "Avoid unpaved roads" routing option, but it sure looks promising. Then again, maybe not. This ought to be line style 0x0a, which highway=track and highway=unsurfaced map to. I will make some experiments later. Marko

1 1

Commit: r1041: Document the --route option.
by svn commit 24 May '09

24 May '09

Version 1041 was commited by elrond on 2009-05-24 21:26:31 +0100 (Sun, 24 May 2009) Document the --route option. According to stever (on irc), it implies --net, so told so too.

1 0

R: [mkgmap-dev] (almost) duplicated node issue
by Marco Certelli 24 May '09

24 May '09

Well, maybe I've found something strange. I've attached to this mail a .zip file containing a small .osm DB (downloaded today) and a screenshot (.png) If I try to compile the attached .osm file, I get a map with broken routing data that crashes MapSource (for example try to get a route from one side to the other of "Piazza Caprera" in the centre of the map, or try routes in the lower left corner). This problem is independent by mkgmap style and mkgmap version (if you download the Italian map from http://www.team-oid.de/cgi-bin/maps_download/showdir.cgi compiled about one month ago, you'll get the same routing problems in this area) I've discovered an issue that maybe is the cause of the problem. If you open the attached picture you'll see a very short segment (less than 1 meter) that you can identify with the coordinates. It is at the cross between Via Zara and Corso Trieste (you must zoom a lot). Well, if you delete this short piece of road, the routing Data Base is built correctly by mkgmap. Maybe somthing related to rounding makes this too short segment a problem during map compiling (the two ends collapses in one point...). I don't think I'll be able to go further: I hope that what I found can help some mkgmap developers to individuate the issue and a possible solution. I've not corrected the OSM DB, so you can still download this area by yourself. Ciao, Marco.

2 1

duplicated node issue
by Marco Certelli 23 May '09

23 May '09

Hi, while I'm experimenting the new "fantastic" --ignore-maxspeeds option, I think I've found a bug. The problem is a (rare) crash of the mapsource routing engine (actually it stops with an error: MPL_CALCROUTE.CPP error 1) when (I think) a duplicated node in the OSM data is encounterd by the route searching function. The problem appears with a map of Italy I compiled with my style and it does not appear using the default style. It appears using both the 1038 and the 1040 mkgmap versions. Well, it might be my style, but I really don't understand the relationship between the style and the error. I've attached the style causing the issue, if you want to make some test. I'm continuing analysis: I'm trying to understand wich style row highlights the problem. Ciao, Marco.

1 0

Commit: r1040: Add support for reversed one way streets specified with oneway=-1.
by svn commit 21 May '09

21 May '09

Version 1040 was commited by markb on 2009-05-21 23:24:43 +0100 (Thu, 21 May 2009) Add support for reversed one way streets specified with oneway=-1.

1 0

Commit: r1039: Add --ignore-maxspeeds option to cause maxspeed tags to be ignored.
by svn commit 21 May '09

21 May '09

Version 1039 was commited by markb on 2009-05-21 23:24:39 +0100 (Thu, 21 May 2009) Add --ignore-maxspeeds option to cause maxspeed tags to be ignored.

1 0

Re: [PATCH v1] Re: [mkgmap-dev] maxspeed tag vs road_speed preset
by Marco Certelli 21 May '09

21 May '09

Hi, I guess "commit" means putting the patch in the mainstream mkgmap. Well if you do that and I can download the new version of mkgmap with the -- ignore-maxspeed switch, I'll test it immediately with my style and I'll send back the results (mainly the changes in routing and ETA). Marco. --- Gio 21/5/09, Mark Burton <markb(a)ordern.com> ha scritto: > Da: Mark Burton <markb(a)ordern.com> > Oggetto: Re: [PATCH v1] Re: [mkgmap-dev] maxspeed tag vs road_speed preset > A: mkgmap-dev(a)lists.mkgmap.org.uk > Data: Giovedì 21 maggio 2009, 21:29 > > > From the various posts on this topic, I get the impression > that there > is much more to this business than just zapping the > maxspeed tags. > > Why don't those people who care about this stuff work out > what is really > required and either come up with a concrete proposal as to > how it > should be done, or even better still, come up with a patch > that does it? > > In the meantime, shall I commit this little option? > > Cheers, > > Mark > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >

2 1