- mkgmap-dev - The mkgmap lists

Commit r3859: Implement new option --ignore-fixme-values to ignore tags with values that contain the fixme pattern. If one uses the option he can disable the corresponding rules
by svn commit 21 Mar '17

21 Mar '17

Version mkgmap-r3859 was committed by gerd on Tue, 21 Mar 2017 Implement new option --ignore-fixme-values to ignore tags with values that contain the fixme pattern. If one uses the option he can disable the corresponding rules in inc/name. --ignore-fixme-values Tells mkgmap to ignore all tags for which the value matches the pattern "(?i)fix[ _]?+me". http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3859

1 0

Commit r3858: refactoring: method idVal(String) is only used for XML reader
by svn commit 21 Mar '17

21 Mar '17

Version mkgmap-r3858 was committed by gerd on Tue, 21 Mar 2017 refactoring: method idVal(String) is only used for XML reader http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3858

1 0

fixme rules
by Andrzej Popowski 21 Mar '17

21 Mar '17

Hi, there are some rules in include/name, designed to remove "fixme" value from tags. Unfortunately they are executed too late for many cases, for example for highway "name" and "ref". I propose to add a file include/fixme to default style and include it at the beginning of points, lines and polygon files. This file could contain fixme rules and other rules, that are useful for all objects. I have found these functions useful: - fixme rules - setting mkgmap:country tag, - correction for multipolygon without area=yes - forcing finalize stage for address I have attached proposed patch to this mail. It duplicate some rules from other includes, which could be removed there, but I haven't done it yet. -- Best regards, Andrzej

6 11

Commit r3857: - refactoring to improve readability of code for high precision
by svn commit 21 Mar '17

21 Mar '17

Version mkgmap-r3857 was committed by gerd on Tue, 21 Mar 2017 - refactoring to improve readability of code for high precision - add TODO for 32 bit high prec based on modified diff_coord_v3.patch http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3857

1 0

if-then-else in style and style options
by Gerd Petermann 18 Mar '17

18 Mar '17

Hi all, I've applied the style-option_v3.patch to the branch, for details see log message: http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3827 I've also tried to fix the known problems with the interpretation of if then statements, so I hope it works now: http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&path=%2F& Just to make this clear: The if statements are translated to "normal" rules, so you cannot do anything with if-then which would not work without, you should also not (yet) exprect run time improvements. The advantage is that you don't have to repeat phrases. A complex sample that shows a possible usage. # Roundabouts if (junction=roundabout) then if (mkgmap:option:single-roundabout=true) then (highway=trunk | highway=trunk_link) [0x0c road_class=4 road_speed=2 resolution 18] (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 19] (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 20] (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 21] else (highway=trunk | highway=trunk_link) [0x0c road_class=4 road_speed=2 resolution 24 continue] (highway=trunk | highway=trunk_link) [0x10801 resolution 18] (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 24 continue] (highway=primary | highway=primary_link) [0x10802 resolution 19] (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 24 continue] (highway=secondary | highway=secondary_link) [0x10803 resolution 20] (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 24 continue] (highway=tertiary | highway=tertiary_link) [0x10804 resolution 21] end # minor roundabouts need no overlay (highway=unclassified | highway=minor ) [0x0c road_class=1 road_speed=1 resolution 21] highway=* [0x0c road_class=0 road_speed=1 resolution 22] end If the corresponding block in the default style lines file is replaced with these rules, you can use option --style-option=single-roundabout to enable the rules which don't add 0x180x lines as overlays for roundabouts. It might be possible to completely remove rules which would never be triggered but that is quite complex, so I leave that for later. Gerd

4 27

Re: [mkgmap-dev] Parallel major roads to cycleways
by David 17 Mar '17

17 Mar '17

Features rules from Openstreetmap.org says : "Cycling infrastructure that is an inherent part of a road - particularly "cycle lanes" which are a part of the road - should usually not be tagged as a separate cycleway, but by adding the cycleway=* tag to an existing highway=*instead." The problem, if there is one, seems to be on the mappers side, not mkgmap styles rules. It should be easy to discard any cycleway along a road with a condition test like (cycleway=* & highway!=*). You can refine it with a test on the road category if needed. Reference : http://wiki.openstreetmap.org/wiki/Tag:highway%3Dcycleway David

2 1

Parallel major roads to cycleways
by Gerd Petermann 17 Mar '17

17 Mar '17

Hi, I just want to share an idea which might be interesting for cycling maps: In Germany and probably also Austria) many major roads have a parallel cycleway close to it, often only separated by a patch of grass or natural=tree_row. Example: A way with bicycle=designated : http://www.openstreetmap.org/way/243499929 runs next to highway=primary B213 http://www.openstreetmap.org/way/328470949 I think nearly no cyclist likes to use those ways -- they are just a bit safer but still lots of cars are running with 100 km/h next to you -- so I think it would be good to have a way to separate them from other ways where no major road is close. A possible way would be this: Simiar to the new ResidentialHook which sets the mkgmap:residential tag we might implement a hook which collects major roads and calculates an area around it (maybe 20m on both sides). Each way (maybe only those with highway=* ) could be checked against those areas in a way that a rule could decide to "dislike" a way which is mostly within such an area when the map is for cyclists. I guess bridges and tunnels (or more generally the layer tag) needs special handling here. Questions: 1) Do you think this would good to have? 2) If yes, what kind of information would be needed in the style? Gerd

5 9

Is any mapper using custom Icons, not displaying labels, but still allows GPS to search by labels?
by greg crago 16 Mar '17

16 Mar '17

I decided to use Custom ICONS for FAST FOOD (for example) So I display a McDonalds POINT, I don't want to show a label, because the symbol conveys the brand name. Yet I want to be able to SEARCH for FAST FOOD and see McDonalds show up in the list. Has anybody done this? I had asked a somewhat similar question and a fellow mapper used a BLANK POINT (0x2a07) for fast food and then overlays unique brand symbols on top of this. But since I am deleting the NAME tag, I don't think the search will work anymore Greg

3 3

Commit r3847: fix rare severe error message "internal error, distance to road too large, ..."
by svn commit 15 Mar '17

15 Mar '17

Version mkgmap-r3847 was committed by gerd on Wed, 15 Mar 2017 fix rare severe error message "internal error, distance to road too large,..." Happens when rather long road segments at certain bearings should be split for house number search but no Garmin point is close enough to prevent zig-zagging. The current algo calculates a wanted split location and tries to find a good Garmin point close to it. It might be better to check if any good Garmin point is an improvement. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3847

3 2

type file and resolutions
by Mike Baggaley 15 Mar '17

15 Mar '17

Hi, does anyone know whether it is possible to use different type files for different resolutions, or to restrict the resolution range of the type file. The problem I am having is that in my map I only use resolutions 24,22,20,18 and 16. Below that I allow the base map to take over. However, in BaseCamp I am getting the base map displayed using my type file (and the whole world uses it, not just the area of my map). If I try the same thing with a commercial map, I can see the base map take over seamlessly at low resolutions. Any suggestions? Thanks, Mike

3 4