August 2014 - mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] mkgmap build greater than 3113 routes through barriers with access=no
by Paulo Carvalho 06 Aug '14

06 Aug '14

Well, it can be dafaulted to on, but sometimes one may want to not translate node properties to ways. For example: a map may have barriers and one may want to have such as POIs in an alert file for Garmin POI Loader instead of them interfering with routing. It all depends on map purpose. 2014-08-06 8:44 GMT-03:00 Greg Troxel <gdt(a)ir.bbn.com>: > > Paulo Carvalho <paulo.r.m.carvalho(a)gmail.com> writes: > > > Just checking: did you remember to use the --link-pois-to-ways option > in > > your compile command? Also, did you place the barrier node apart from > the > > way or did you format a way node as a barrier? (the latter is > preferable, I > > think.) > > As I understand it, the semantics of OSM are that a barrier node in a > way does control access. So it's a bug if mkgmap by default does not > produce a map that respects that. Essentially, I'm arguing that > --link-pois-to-ways should default to on, following the principle that > there is a correct garmin representation of OSM semantics and that this > correct representation should be the default. >

2 1

mkgmap build greater than 3113 routes through barriers with access=no
by Paulo Carvalho 06 Aug '14

06 Aug '14

Hi, Just checking: did you remember to use the --link-pois-to-ways option in your compile command? Also, did you place the barrier node apart from the way or did you format a way node as a barrier? (the latter is preferable, I think.) cheers, Paulo 2014-08-06 7:01 GMT-03:00 <mkgmap-dev-request(a)lists.mkgmap.org.uk>: > Send mkgmap-dev mailing list submissions to > mkgmap-dev(a)lists.mkgmap.org.uk > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > or, via email, send a message with subject or body 'help' to > mkgmap-dev-request(a)lists.mkgmap.org.uk > > You can reach the person managing the list at > mkgmap-dev-owner(a)lists.mkgmap.org.uk > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mkgmap-dev digest..." > > Today's Topics: > > 1. mkgmap build greater than 3113 routes through barriers with > access=no (Ervin Malicdem) > 2. Re: mkgmap build greater than 3113 routes through barriers > with access=no (Gerd Petermann) > 3. Re: mkgmap build greater than 3113 routes through barriers > with access=no (Gerd Petermann) > 4. Commit: r3326: fix typo in WrongAngleFixer which sometimes > created distorted lines. (svn commit) > 5. Re: mkgmap build greater than 3113 routes through barriers > with access=no (Ervin Malicdem) > 6. Re: mkgmap build greater than 3113 routes through barriers > with access=no (Gerd Petermann) > > > ---------- Mensagem encaminhada ---------- > From: Ervin Malicdem <schadow1(a)gmail.com> > To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Date: Wed, 6 Aug 2014 17:29:38 +0800 > Subject: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > > Just noticed that the mkgmap build greater than 3113 is allowing routing > through barriers with access=no. > > I have not changed the style since then except that I upgraded to a new > mkgmap build and routing through gates with access=no is possible. > > > Ervin M. > *Schadow1 Expeditions* - A Filipino must not be a stranger to his own > motherland. > http://www.s1expeditions.com > > > ---------- Mensagem encaminhada ---------- > From: Gerd Petermann <gpetermann_muenchen(a)hotmail.com> > To: "mkgmap-dev(a)lists.mkgmap.org.uk" <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Date: Wed, 6 Aug 2014 11:38:22 +0200 > Subject: Re: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > Hi Ervin, > > please check: r3112 and r3113 did not change any functionality. > Was that a typo? > > Gerd > > ------------------------------ > Date: Wed, 6 Aug 2014 17:29:38 +0800 > From: schadow1(a)gmail.com > To: mkgmap-dev(a)lists.mkgmap.org.uk > Subject: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > > > Just noticed that the mkgmap build greater than 3113 is allowing routing > through barriers with access=no. > > I have not changed the style since then except that I upgraded to a new > mkgmap build and routing through gates with access=no is possible. > > > Ervin M. > *Schadow1 Expeditions* - A Filipino must not be a stranger to his own > motherland. > http://www.s1expeditions.com > > _______________________________________________ mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > ---------- Mensagem encaminhada ---------- > From: Gerd Petermann <gpetermann_muenchen(a)hotmail.com> > To: "mkgmap-dev(a)lists.mkgmap.org.uk" <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Date: Wed, 6 Aug 2014 11:44:19 +0200 > Subject: Re: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > .. and also 3114 did not change something which could explain that. > > Gerd > > ------------------------------ > Date: Wed, 6 Aug 2014 17:29:38 +0800 > From: schadow1(a)gmail.com > To: mkgmap-dev(a)lists.mkgmap.org.uk > Subject: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > > > Just noticed that the mkgmap build greater than 3113 is allowing routing > through barriers with access=no. > > I have not changed the style since then except that I upgraded to a new > mkgmap build and routing through gates with access=no is possible. > > > Ervin M. > *Schadow1 Expeditions* - A Filipino must not be a stranger to his own > motherland. > http://www.s1expeditions.com > > _______________________________________________ mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > ---------- Mensagem encaminhada ---------- > From: svn commit <svn(a)mkgmap.org.uk> > To: mkgmap-svn(a)lists.mkgmap.org.uk > Cc: > Date: Wed, 6 Aug 2014 10:46:57 +0100 (BST) > Subject: [mkgmap-dev] Commit: r3326: fix typo in WrongAngleFixer which > sometimes created distorted lines. > > Version mkgmap-r3326 was committed by gerd on Wed, 06 Aug 2014 > > fix typo in WrongAngleFixer which sometimes created distorted lines. > > > ---------- Mensagem encaminhada ---------- > From: Ervin Malicdem <schadow1(a)gmail.com> > To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Date: Wed, 6 Aug 2014 17:52:59 +0800 > Subject: Re: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > I apologize, I was trying to find the latest released build of mkgmap > since March 17 2014 as that was the last version of the map that worked. > Just saw that generated that working map with mkgmap 3080. Anything after > that have this issue. > > Ervin M. > *Schadow1 Expeditions* - A Filipino must not be a stranger to his own > motherland. > http://www.s1expeditions.com > > > On Wed, Aug 6, 2014 at 5:44 PM, Gerd Petermann < > gpetermann_muenchen(a)hotmail.com> wrote: > >> .. and also 3114 did not change something which could explain that. >> >> Gerd >> >> ------------------------------ >> Date: Wed, 6 Aug 2014 17:29:38 +0800 >> From: schadow1(a)gmail.com >> To: mkgmap-dev(a)lists.mkgmap.org.uk >> Subject: [mkgmap-dev] mkgmap build greater than 3113 routes through >> barriers with access=no >> >> >> Just noticed that the mkgmap build greater than 3113 is allowing routing >> through barriers with access=no. >> >> I have not changed the style since then except that I upgraded to a new >> mkgmap build and routing through gates with access=no is possible. >> >> >> Ervin M. >> *Schadow1 Expeditions* - A Filipino must not be a stranger to his own >> motherland. >> http://www.s1expeditions.com >> >> _______________________________________________ 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 >> > > > > ---------- Mensagem encaminhada ---------- > From: Gerd Petermann <gpetermann_muenchen(a)hotmail.com> > To: "mkgmap-dev(a)lists.mkgmap.org.uk" <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Date: Wed, 6 Aug 2014 12:01:46 +0200 > Subject: Re: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > Hi Ervin, > > okay, that is more plausible. Please give a few more details: > Do you see that problem also with the default style? > Is it possible that the barrier is on a tile border? > > If you download a small area around that barrier, do you see the > same problem? > What routing options are you using (bike, car, etc) and > what is the OSM id of the barrier? > > If you like, just post a link to your input files and the mkgmap > options so that we can reproduce the problem. > > Gerd > > ------------------------------ > Date: Wed, 6 Aug 2014 17:52:59 +0800 > From: schadow1(a)gmail.com > To: mkgmap-dev(a)lists.mkgmap.org.uk > Subject: Re: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > > I apologize, I was trying to find the latest released build of mkgmap > since March 17 2014 as that was the last version of the map that worked. > Just saw that generated that working map with mkgmap 3080. Anything after > that have this issue. > > Ervin M. > *Schadow1 Expeditions* - A Filipino must not be a stranger to his own > motherland. > http://www.s1expeditions.com > > > On Wed, Aug 6, 2014 at 5:44 PM, Gerd Petermann < > gpetermann_muenchen(a)hotmail.com> wrote: > > .. and also 3114 did not change something which could explain that. > > Gerd > > ------------------------------ > Date: Wed, 6 Aug 2014 17:29:38 +0800 > From: schadow1(a)gmail.com > To: mkgmap-dev(a)lists.mkgmap.org.uk > Subject: [mkgmap-dev] mkgmap build greater than 3113 routes through > barriers with access=no > > > Just noticed that the mkgmap build greater than 3113 is allowing routing > through barriers with access=no. > > I have not changed the style since then except that I upgraded to a new > mkgmap build and routing through gates with access=no is possible. > > > Ervin M. > *Schadow1 Expeditions* - A Filipino must not be a stranger to his own > motherland. > http://www.s1expeditions.com > > _______________________________________________ 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 > > > > _______________________________________________ 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 >

3 2

3229 in branch rhumbline ready for trunk?
by Gerd Petermann 06 Aug '14

06 Aug '14

Hi all, I think r3229 is ready for trunk. It handles Rogers Grid data correctly. Besides that the differences to trunk are small (as expected). The throughput might be a bit better as the rhumb line calculations allow to skip some trig functions. If I here no complains, I'll merge on friday. Gerd

1 0

Commit: r3326: fix typo in WrongAngleFixer which sometimes created distorted lines.
by svn commit 06 Aug '14

06 Aug '14

Version mkgmap-r3326 was committed by gerd on Wed, 06 Aug 2014 fix typo in WrongAngleFixer which sometimes created distorted lines.

1 0

bounds branch
by Jaromír Mikeš 05 Aug '14

05 Aug '14

Hello, what is the state of "bounds" branch? It is still "work in progress"? I personally using this branch for awhile (r3309) and I noticed great improvement in bounds. Great work! best regards mira

2 1

Merging pbf files before splitter/mkgmap fails
by paco.tyson＠free.fr 03 Aug '14

03 Aug '14

Hi all, I need help for a slightly offtopic problem. I've got a (huge) list of addresses in CSV format. I want to add them to the pbf file from geofabrik before running splitter/mkgmap. Those addresses aren't in OSM. I converted the CSV file to an .osm file. The script produces the addresses with a negative osm id. I then use osmconvert : ./osmconvert geofabrik.osm.pbf addresses.osm --out-pbf -o=complete.pbf No error returned. The complete.pbf file is correctly processed by the splitter/mkgmap toolchain. But the map doesn't show the addresses. I tried to look for the problem : - The .osm file seems correct, it opens correctly in JOSM. - Converting the .osm file to .pbf format before merging doesn't help - Something funny : after merging, the .pbf file is slightly smaller than the geofabrik one. osmconvert does a more efficient job at creating pbf files ? I guess that the problem lies in the merging part but I didn't find any inspection tool for the pbf format. Can anybody help ? Paco.

3 5

help needed
by Gerd Petermann 03 Aug '14

03 Aug '14

Hi all, I am still trying to find a better solution for the problem posted by Roger Calvert: http://gis.19327.n5.nabble.com/Incorrect-compilation-of-grid-lines-tp580950… We are using some approximations to speed up calculations, most of them work fine as long as distances are rather short. On the other hand, mkgmap doesn't check if distances are short, so in some cases we have rather large errors. I found two sources for formulas: http://www.movable-type.co.uk/scripts/latlong.html and http://williams.best.vwh.net/avform.htm The latter gives an example to verify the code. I've coded some lines in Java and got similar results as in the "worked example". I've then tried to verify the example in JOSM, esp. the cross-track-error. Unfortunately, when I try to draw a (nearly) perpendicular line from point A to line LAX-JFK, JOSM says the line is ~27.7 km long, while the example calculations are near 13.8 km or about 50% of the JOSM value. What am I getting wrong? Gerd

6 15

new branch rhumbline
by GerdP 03 Aug '14

03 Aug '14

Hi all, I've started a new branch rhumline to implement the changes reg. distance and bearing calculations. With r3322 I've committed a first working version. The differences to trunk are rather small when normal OSM data is processed and Rogers Grid data seems to be working fine. I did not yet check all places where we calculate distances or bearings. I think there are a few places where we have to use the great circle distance, e.g. when searching for the nearest node or in housenumber processing. I'll check these cases later. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/new-branch-rhumbline-tp5813506.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

1 0

Commit: r3320: TYP documentation: minor format, spelling and style changes.
by svn commit 01 Aug '14

01 Aug '14

Version mkgmap-r3320 was committed by steve on Fri, 01 Aug 2014 TYP documentation: minor format, spelling and style changes.

1 0

Curvy routing support: new function?
by Manfred Brenneisen 01 Aug '14

01 Aug '14

Hi all, Garmin offers "curvy roads" preferences for their zümo 390 and 590 devices. https://buy.garmin.com/en-US/US/on-the-road/motorcycles/zumo-390lm/prod1382… I'm thinking about creating motorcycle maps for old 200 series. Might it be useful to integrate a curviness() function so that mkgmap can optimize for curvy roads too? It might also help do determine a better default speed for curvy roads for use with car routing. The curviness() value might be the overall absolute turning angle (in degrees) of a road segment divided by the segment's length. What's your opinion? Cheers Manfred Pseudo code might look like this: function curviness() { oldpoint=points(0) foreach (point of a way segment as newpoint) { d_x=(newpoint.x-oldpoint.x)/360*40000000*COS(newpoint.x*PI()/180) //in meters d_y=(newpoint.y-oldpoint.y)/360*40000000 //in meters length+=sqrt(d_x**2+d_y**2) angle=arctan(d_y/d_x) d_angle=abs(angle-old_angle) sgn_x=sgn(d_x) sgn_y=sgn(d_y) if ((sgn_x*sgn_y*old_sgn_x*old_sgn_y)=-1 && (sgn_x!=old_sgn_x)) d_angle=pi-d_angle // 180 degrees correction, otherwise north-south roads show strange results if (point>1) sum_angle+=d_angle old_angle=angle oldpoint=newpoint old_sgn_x=sgn_x old_sgn_y=sgn_y } return sum_angle/length } // perhaps simple multiplication is faster than 4 times sgn() functions?

5 15