- mkgmap-dev - The mkgmap lists

WG: Mapping smoothness and surface to maxspeed
by Gerd Petermann 24 Oct '16

24 Oct '16

Von: Gerd Petermann<mailto:GPetermann_muenchen@hotmail.com> Gesendet: Montag, 24. Oktober 2016 18:54 An: Jakob Mühldorfer<mailto:mail@jmuehldorfer.de> Betreff: AW: [mkgmap-dev] Mapping smoothness and surface to maxspeed Hi Jakob, the maxspeed value is not stored in the img file, but the default style contains inc/roadspeed which sets mkgmap:road-speed-max accordingly. This value is stored in the img file and AFAIK it is also used for bicycle routing. Gerd Von: Jakob Mühldorfer<mailto:mail@jmuehldorfer.de> Gesendet: Sonntag, 23. Oktober 2016 19:05 An: mkgmap-dev(a)lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> Betreff: [mkgmap-dev] Mapping smoothness and surface to maxspeed Hi, question about the Etrex 20x routing: Would it work to model smoothness and surface values for bike routing as maxspeed? For example apply maxspeed=5 to a smoothness=bad way, so the on-device-routing has a lower preference for this way Or does the routing for bikes not look at maxspeed in Etrex devices? Thanks for feedback Jakob _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

3 2

Confusing "Turn right" instruction
by Jakob Mühldorfer 24 Oct '16

24 Oct '16

Hi, yesterday I ran into a confusing "turn right" instruction https://i.imgur.com/u4mfpmQ.jpg This might be a problem with the data, as the data in OSM does have quite an angle to merge two oneway lanes, where in reality you go straigt: https://www.openstreetmap.org/relation/5698558 The only hints that this is not a right turn is the relation above, and the turn:lanes on the previous road part. https://www.openstreetmap.org/way/239362184 Is there any "hack" you can apply to handle such situation, or is it too complicated to deal with and just an unfortunate situation where the representation of streets in OSM is not perfect. Best Jakob

2 2

Commit r3699: Improve map generated with command like
by svn commit 24 Oct '16

24 Oct '16

Version mkgmap-r3699 was committed by gerd on Mon, 24 Oct 2016 Improve map generated with command like java -jar mkgmap.jar --gmapsupp test-map:all-elements The wanted effect is to be able to see the Garmin device classification of the point/line/area type/subType by just hovering the cursor over it; if the item has a name (el.setName()) this is shown instead. For named items it is still possible to see the classification by clicking on it (in the top bar of the item information display), but getting to the next item can take a lot of operations. patch by Ticker Berkin http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3699

1 0

Mapping smoothness and surface to maxspeed
by Jakob Mühldorfer 23 Oct '16

23 Oct '16

Hi, question about the Etrex 20x routing: Would it work to model smoothness and surface values for bike routing as maxspeed? For example apply maxspeed=5 to a smoothness=bad way, so the on-device-routing has a lower preference for this way Or does the routing for bikes not look at maxspeed in Etrex devices? Thanks for feedback Jakob

1 0

Naming natural=peak with ref=*
by Stéphane MARTIN 22 Oct '16

22 Oct '16

Hi, I have a problem naming a "natural=peak" when the node has also a "ref=*". e.g.: <node id="669975855" version="2" timestamp="2011-10-30T18:15:24Z" uid="191786" user="bulzor14" changeset="9696614" lat="44.0979812" lon="6.1389134"> <tag k="description" v="Borne SGA - Point vu en place en 1981"/> <tag k="ele" v="1140.02"/> <tag k="man_made" v="survey_point"/> <tag k="name" v="Pic d'Oise"/> <tag k="natural" v="peak"/> <tag k="note" v="Ne pas déplacer ce point, cf. - Do not move this node, see - http://wiki.openstreetmap.org/wiki/WikiProject_France/Repères_Géodésiques#P…"/> <tag k="ref" v="0404701 - A"/> <tag k="source" v="©IGN 2010 dans le cadre de la cartographie réglementaire"/> <tag k="url" v="http://ancien-geodesie.ign.fr/fiche_point.asp?num_site=0404701&no_ptg=0…"/> </node> The problem is that the "ref" appears before the peak's name, even if deleted in the points file. My points file says: natural=peak & ref=* {delete ref} natural=peak {name '${name} (${ele} m)' | '${name}'} [0x6616 resolution 22] N.B.: "man_made=survey_point" is not set in the points file. The result is, e.g. "0404701 - a Pic D'Oise" and not "Pic D'Oise 1140.02 M". Any ideas ? Best regards. Steph

2 2

scripts/download/mkdoc
by Mike Baggaley 22 Oct '16

22 Oct '16

Just updating my source to the latest version and notice that scripts/download/mkdoc has the following two lines in: DOC=~steve/www/web/mkgmap/content/doc WEB_DOC_PDF=~steve/www/mkgmap.org.uk/docroot/doc/pdf Should ~steve be in the released code? The previous version just had ~. Cheers, Mike

1 0

AllElements patch
by Ticker Berkin 22 Oct '16

22 Oct '16

Hi I have a patch for mkgmap/reader/test/AllElements.java It shows items (areas, lines, points) with and without a name, so you can easily see the Garmin name/classification for the item and with and without a background, so you can see the relative draw priority and possible (semi)transparency of the area. Can this be applied to the main development line? Regards Ticker Berkin

2 2

Commit r3698: Another 'bracket' clarification, in typ-compiler
by svn commit 20 Oct '16

20 Oct '16

Version mkgmap-r3698 was committed by steve on Thu, 20 Oct 2016 Another 'bracket' clarification, in typ-compiler http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3698

1 0

Commit r3697: Clarify usage of 'brackets' in documentation.
by svn commit 20 Oct '16

20 Oct '16

Version mkgmap-r3697 was committed by steve on Thu, 20 Oct 2016 Clarify usage of 'brackets' in documentation. Also a fix to the mkdoc script that should result in the website documentation being updated. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3697

1 0

Commit r3696: Fix documentation error.
by svn commit 17 Oct '16

17 Oct '16

Version mkgmap-r3696 was committed by steve on Sun, 16 Oct 2016 Fix documentation error. - Carlos Dávila http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3696

4 4