- mkgmap-dev - The mkgmap lists

Commit: r3334: Translate public_transport=platform in the default point style.
by svn commit 31 Aug '14

31 Aug '14

Version mkgmap-r3334 was committed by marko on Sun, 31 Aug 2014 Translate public_transport=platform in the default point style. Contributed by Carlos Dávila.

1 0

Routing Algorithm of Garmin
by Bernhard Hiller 26 Aug '14

26 Aug '14

When selecting "Minimize Distance", the result conforms with the expectations: the shortest route is selected by the Garmin Oregon 600. But with "Minimize Time", things are different. It is not at all the route with the shortest time. By setting a "Via Point", I can have it calculating my preferred route, which is calculated with a shorter time. I.e. despite the title of my selection, the device did not minimize time. Example: Travel from Bayreuth to Erlangen. The Oregon calculates a long route via motorways, 98.4 km, at 67 minutes. With a Via Point west of Ebermannstadt, the distance is shortened to 64.9 km, but also the time is now 60 minutes only. The longer distance might be appropriate - but I find the longer time strange. It is 7 minutes / 10% longer by time! Travelling along my preferred route, the device has to recalculate several times, with some more such results. E.g. from Obernsees, it prefers 86.4 km at 56 minutes over a route of 51.8 km at 46 minutes - 10 minutes or 20% longer! From east of Ebermannstadt, it prefers 39.8 km at 30 minutes over 29 km at 26 minutes. All the preferred routes use long sections of motorways, and reduce the sections on roads with low road_class attribute(road_class=2; lower values are not present in my preferred route). What are your experiences? How much is the "penalty" for low road_class values? Are still other factors important?

3 3

line-break in address-field
by Wolfgang Hammel 18 Aug '14

18 Aug '14

Hi, I'd like to have -- for example -- for all fuel stations both, the phone and fax numbers to be included in the phone field of the address-information. Therefore I included the following rule in the points file: amenity=fuel & fax=* {set mkgmap:phone = 'phone: ${mkgmap:phone} fax: ${fax}' | 'fax: ${fax}'} So phone and fax numbers are separated by a space character. However it would help for a better readabilty to have phone and fax number separated by a newline. So I tried the following rule amenity=fuel & fax=* {set mkgmap:phone = 'phone: ${mkgmap:phone}\nfax: ${fax}' | 'fax: ${fax}'} But to no avail. "\n" is display as it is and is not interpreted as an escape sequence. So I played aroud with different approaches, for example the unicode newline 0x0085. amenity=fuel & fax=* {set mkgmap:phone = 'phone: ${mkgmap:phone}\u0085fax: ${fax}' | 'fax: ${fax}'} This also didn't work. So the questions I have are: Are the garmin devices (Oregon 550 in my case) able to display address-info with linebreaks in one field on two diffeent lines? And if so: Is it possible to have a newline or line break included in a string assignment in an action block? Thanks. Wolfgang

2 1

link ways to pois
by Felix Hartmann 13 Aug '14

13 Aug '14

Now I just noticed in some cities people used noexit=yes in abundance for ways like highway=service & access=private, or footway=sidewalk plus access=private. Now as I decided to render noexit=yes - but not the above sidewalk or access=private highway=service, I get quite a few "floating" points shown in the map. Would there be way to reference the underlying line into the points file - basically the opposite of link-pois-to-ways.. In that case one could have: noexit=yes & ( mkgmap:lines:highway!=service & mkgamp:lines:access!=private ) to not show them... This is not really a big thing, and I don't know many other cases where such an option would be useful. So I don't expect it to be implemented. More just like a note - if it's easy to implement it would be nice.... (another approach would be to define in the lines file to remove any points of the line under condition X- but I think that would be a bit more complicated). -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

1 0

barrier=lift_gate
by GerdP 11 Aug '14

11 Aug '14

Hi all, I noticed that the default style is a bit strange regrading barriers: The barrier at node http://www.openstreetmap.org/node/1597509392#map=19/52.21425/8.81559 has an influence on routing (with --link-pois-to-ways), but it is not displayed in the map. The reason is that we use barrier=* when we evaluate the effect on routing, but we display only specific barriers: barrier=bollard | barrier=bus_trap | barrier=gate [0x660f resolution 24] barrier=block | barrier=cycle_barrier | barrier=stile | barrier=kissing_gate [0x660f resolution 24] I think we should display all barriers which have an effect on routing, but I am not sure what to change in the style. Any suggestions? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/barrier-lift-gate-tp5814057.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 3

route runs
by Steve Sgalowski 11 Aug '14

11 Aug '14

with long distance driveing the latest patch is ok however , when your driveing is under 100 km it re sets the display any ideas

1 0

Commit: r3333: merge branch rhumbline to fix issues with very long lines which are
by svn commit 08 Aug '14

08 Aug '14

Version mkgmap-r3333 was committed by gerd on Fri, 08 Aug 2014 merge branch rhumbline to fix issues with very long lines which are great circle paths like the "Great Britain National Grid". Since Garmin assumes that all line segments are rhumb lines, we have to make sure that we don't remove too many points from GC lines. The advantage is that this reduces the number of needed complex bearing calculation a little bit.

2 1

New Bug with recent changes? - Did not find CoordPOI node at...
by Felix Hartmann 08 Aug '14

08 Aug '14

happens on todays France from Geofabrik... Any more details needed? SEVERE (StyledConverter): e:\openmtbmap\maps\63910060.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=47.205967&mlon=-1.570172&zoom=17 in ways [WAY: 104287722 ft(47.20554828643799/-1.5673112869262695) [mkgmap:street=ft,wayin omtb22=yes,mkgmap:label:1=ft,cggmap:access=yes,mkgmap:country=FRA,bicycle=yes,mkgmap:way-poi-node-ids=[1257928748],mkgmap:admin_level2=FRA,mkgmap:bicycle=yes,highway=footway,mkgmap:admin_level8=Nantes,mkgmap:city=P¶le de proximitÚ Nantes-Loire,mkgmap :admin_level4=Pays de la Loire,mkgmap:set_unconnected_type=none,mkgmap:admin_level7=Nantes,mkgmap:admin_level6=Loire-Atlantique,mkgmap:admin_level9=P¶le de proximitÚ Nantes-Loire,mkgmap:region=Loire-Atlantique,mkgmap:admin_level3=France mÚtropolitain e,name4XQ=ft], WAY: 110017340 null(47.206106185913086/-1.5698432922363281) [man_made=pier,mkgmap:city=P¶le de proximitÚ Nantes-Loire,mkgmap:admin_level8=Nantes,mkgmap:way-has-pois=true,mkgmap:admin_level4=Pays de la Loire,mkgmap:set_unconnected_type= none,mkgmap:admin_level7=Nantes,mkgmap:admin_level6=Loire-Atlantique,mkgmap:admin_level9=P¶le de proximitÚ Nantes-Loire,mkgmap:taxi=no,mkgmap:admin_level3=France mÚtropolitaine,mkgmap:country=FRA,mkgmap:region=Loire-Atlantique,mkgmap:way-poi-node-ids =[1257928748],mkgmap:admin_level2=FRA]] SEVERE (StyledConverter): e:\openmtbmap\maps\63910060.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=47.206350&mlon=-1.569255&zoom=17 in ways [WAY: 110017341 null(47.20621347427368/-1.5695858001708984) [man_made=pier,mkgmap :city=P¶le de proximitÚ Nantes-Loire,mkgmap:admin_level8=Nantes,mkgmap:way-has-pois=true,mkgmap:admin_level4=Pays de la Loire,mkgmap:set_unconnected_type=none,mkgmap:admin_level7=Nantes,mkgmap:admin_level6=Loire-Atlantique,mkgmap:admin_level9=P¶le de proximitÚ Nantes-Loire,mkgmap:taxi=no,mkgmap:admin_level3=France mÚtropolitaine,mkgmap:country=FRA,mkgmap:region=Loire-Atlantique,mkgmap:way-poi-node-ids=[1257928765],mkgmap:admin_level2=FRA], WAY: 286691905 Quai Fernand-Crouan ft(47.206363677978516 /-1.5692424774169922) [mkgmap:label:2=Quai Fernand-Crouan,mkgmap:street=Quai Fernand-Crouan ft,mkgmap:label:1=Quai Fernand-Crouan ft,name=Quai Fernand-Crouan,mkgmap:country=FRA,mkgmap:way-poi-node-ids=[1257928765],mkgmap:admin_level2=FRA,mkgmap:city= P¶le de proximitÚ Nantes-Loire,highway=footway,mkgmap:admin_level8=Nantes,mkgmap:way-has-pois=true,mkgmap:admin_level4=Pays de la Loire,mkgmap:set_unconnected_type=none,mkgmap:admin_level6=Loire-Atlantique,mkgmap:admin_level9=P¶le de proximitÚ Nantes -Loire,mkgmap:admin_level7=Nantes,mkgmap:admin_level3=France mÚtropolitaine,mkgmap:taxi=no,name4XQ=Quai Fernand-Crouan ft,mkgmap:region=Loire-Atlantique]] SEVERE (StyledConverter): e:\openmtbmap\maps\63910063.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=47.993891&mlon=-1.784319&zoom=17 in ways [WAY: 55131584 ser(47.995147705078125/-1.7864370346069336) [service=alley,mkgmap: street=ser,mkgmap:label:1=ser,mkgmap:country=FRA,mkgmap:way-poi-node-ids=[693309916],mkgmap:admin_level2=FRA,highway=service,mkgmap:admin_level8=Guichen,mkgmap:way-has-pois=true,mkgmap:admin_level4=Bretagne,mkgmap:set_unconnected_type=0x1001e,mkgmap: admin_level7=Redon,mkgmap:admin_level6=Ille-et-Vilaine,mkgmap:city=Guichen,mkgmap:region=Ille-et-Vilaine,mkgmap:admin_level3=France mÚtropolitaine,name4XQ=ser]] SEVERE (StyledConverter): e:\openmtbmap\maps\63910072.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=49.474819&mlon=0.170093&zoom=17 in ways [WAY: 49696353 ChaussÚe Amiral Bonnivet(49.474825859069824/0.17009496688842773) [m kgmap:street=ChaussÚe Amiral Bonnivet,mkgmap:label:1=ChaussÚe Amiral Bonnivet,name=ChaussÚe Amiral Bonnivet,mkgmap:country=FRA,mkgmap:way-poi-node-ids=[2800717714][2467792640],mkgmap:admin_level2=FRA,highway=tertiary,mkgmap:admin_level8=Le Havre,sour ce=Bing;cadastre-dgi-fr source : Direction GÚnÚrale des Imp¶ts - Cadastre. Mise Ó jour : 2014,mkgmap:way-has-pois=true,mkgmap:admin_level4=Haute-Normandie,mkgmap:admin_level7=Le Havre,mkgmap:admin_level6=Seine-Maritime,mkgmap:city=Le Havre,mkgmap:reg ion=Seine-Maritime,mkgmap:admin_level3=France mÚtropolitaine]] SEVERE (StyledConverter): e:\openmtbmap\maps\63910078.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=48.189085&mlon=1.096232&zoom=17 in ways [WAY: 28554035 ser(48.189167976379395/1.0947060585021973) [mkgmap:street=ser,mkgma p:label:1=ser,mkgmap:country=FRA,mkgmap:way-poi-node-ids=[762717048],mkgmap:admin_level2=FRA,highway=service,mkgmap:admin_level8=Unverre,mkgmap:way-has-pois=true,mkgmap:admin_level4=Centre,mkgmap:set_unconnected_type=0x1001e,mkgmap:admin_level7=ChÔte audun,mkgmap:admin_level6=Eure-et-Loir,mkgmap:city=Unverre,mkgmap:region=Eure-et-Loir,mkgmap:admin_level3=France mÚtropolitaine,name4XQ=ser]] SEVERE (StyledConverter): e:\openmtbmap\maps\63910124.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=48.297523&mlon=4.040753&zoom=17 in ways [WAY: 128124052 CW(48.29742193222046/4.0404582023620605) [mkgmap:street=CW,mkgmap: label:1=CW,mkgmap:country=FRA,mkgmap:way-poi-node-ids=[2522778481][2390067305][2522778496][1416547331],mkgmap:admin_level2=FRA,highway=cycleway,mkgmap:admin_level8=Sainte-Savine,source=Bing,mkgmap:way-has-pois=true,mkgmap:admin_level4=Champagne-Arden ne,mkgmap:admin_level7=Troyes,mkgmap:admin_level6=Aube,mkgmap:set_unconnected_type=none,mkgmap:city=Sainte-Savine,mkgmap:admin_level3=France mÚtropolitaine,mkgmap:region=Aube,name4XQ=CW]] SEVERE (StyledConverter): e:\openmtbmap\maps\63910141.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=48.877990&mlon=2.284495&zoom=17 in ways [WAY: 246082955 ft(48.87798070907593/2.2844910621643066) [mkgmap:street=ft,mkgmap: label:1=ft,mkgmap:country=FRA,mkgmap:way-poi-node-ids=[2531630824],mkgmap:admin_level2=FRA,mkgmap:city=17e Arrondissement,highway=footway,mkgmap:admin_level8=Paris,mkgmap:way-has-pois=true,mkgmap:admin_level4=╬le-de-France,mkgmap:admin_level10=Quarti er des Ternes,mkgmap:admin_level7=Paris,mkgmap:admin_level6=Paris,mkgmap:admin_level9=17e Arrondissement,mkgmap:set_unconnected_type=none,mkgmap:admin_level3=France mÚtropolitaine,mkgmap:taxi=no,name4XQ=ft,mkgmap:region=Paris]] SEVERE (StyledConverter): e:\openmtbmap\maps\63910194.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=43.953274&mlon=4.807230&zoom=17 in ways [WAY: 138250306 pth(43.9532732963562/4.807226657867432) [mkgmap:street=pth,mkgmap: label:1=pth,mkgmap:country=FRA,mkgmap:way-poi-node-ids=[1515587726],mkgmap:admin_level2=FRA,highway=path,mkgmap:admin_level8=Avignon,mkgmap:way-has-pois=true,mkgmap:admin_level4=Provence-Alpes-C¶te d'Azur,mkgmap:taxi=no,mkgmap:admin_level7=Avignon,mk gmap:admin_level6=Vaucluse,mkgmap:set_unconnected_type=none,mkgmap:city=Avignon,mkgmap:admin_level3=France mÚtropolitaine,mkgmap:region=Vaucluse,name4XQ=pth]] SEVERE (StyledConverter): e:\openmtbmap\maps\63910199.osm.pbf: Did not find CoordPOI node at http://www.openstreetmap.org/?mlat=46.568444&mlon=3.330532&zoom=17 in ways [WAY: 200960122 ser(46.568427085876465/3.3304667472839355) [mkgmap:street=ser,mkgm ap:label:1=ser,mkgmap:country=FRA,mkgmap:way-poi-node-ids=[2109153389],mkgmap:admin_level2=FRA,highway=service,mkgmap:admin_level8=Moulins,source=Orthophotographie CRAIG/TopoGEODIS 2009,mkgmap:way-has-pois=true,mkgmap:admin_level4=Auvergne,mkgmap:adm in_level7=Moulins,mkgmap:admin_level6=Allier,mkgmap:set_unconnected_type=0x1001e,mkgmap:city=Moulins,mkgmap:admin_level3=France mÚtropolitaine,mkgmap:region=Allier,name4XQ=ser]] -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

3 4

Commit: r3332: fix error "Did not find CoordPOI node at ..." introduced with r3330
by svn commit 08 Aug '14

08 Aug '14

Version mkgmap-r3332 was committed by gerd on Fri, 08 Aug 2014 fix error "Did not find CoordPOI node at ..." introduced with r3330 Todo: Prefer to move barrier nodes away from a junction instead of merging with the junction node.

1 0

Commit: r3331: fix minor issue with closed ways that are not connected to other roads
by svn commit 07 Aug '14

07 Aug '14

Version mkgmap-r3331 was committed by gerd on Thu, 07 Aug 2014 fix minor issue with closed ways that are not connected to other roads simplify code: use Coord.decHighwayCount() instead of creating a copy of Coord. This has a small (positive) side effect if the node is also used in other ways.

1 0