Changes to require name defined in the style file
Hi All Trouble been a bit slow to update or more likely just plain with my styles but I think that somewhere along the line the automatic use of the name changed. I find I now need to add & name=*{name '${name}'} to any point of interest to display the name. In the past I think I only needed name=* No great problem as I can re-work my style sheet but for my own sanity check did this extra vigour in defining the style creep in? Cheers Brett
Hi Brett, please look at http://www.mkgmap.org.uk/news/2013/12/22/more-flexibility-in-style-files-sty... Doesn't that answer your questions? Gerd From: brussell237@live.com.au To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 20:16:23 +1100 Subject: [mkgmap-dev] Changes to require name defined in the style file Hi All Trouble been a bit slow to update or more likely just plain with my styles but I think that somewhere along the line the automatic use of the name changed. I find I now need to add & name=*{name '${name}'} to any point of interest to display the name. In the past I think I only needed name=* No great problem as I can re-work my style sheet but for my own sanity check did this extra vigour in defining the style creep in? Cheers Brett _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd The perfect answer! I understand the improved logic of the changes, and yes it makes sense, but a side effect is some work is now required editing the style sheet. No great hassle as at least I was not going mad. Cheers Brett From: gpetermann_muenchen@hotmail.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 10:21:17 +0100 Subject: Re: [mkgmap-dev] Changes to require name defined in the style file Hi Brett, please look at http://www.mkgmap.org.uk/news/2013/12/22/more-flexibility-in-style-files-sty... Doesn't that answer your questions? Gerd From: brussell237@live.com.au To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 20:16:23 +1100 Subject: [mkgmap-dev] Changes to require name defined in the style file Hi All Trouble been a bit slow to update or more likely just plain with my styles but I think that somewhere along the line the automatic use of the name changed. I find I now need to add & name=*{name '${name}'} to any point of interest to display the name. In the past I think I only needed name=* No great problem as I can re-work my style sheet but for my own sanity check did this extra vigour in defining the style creep in? Cheers Brett _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Brett, you are not the 1st and probably not the last to be trapped. I thought about a check that warns the user but I found nothing that works always. Any ideas out there? How can mkgmap detect that the user has to modify the style to get a usable result? Gerd From: brussell237@live.com.au To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 20:26:49 +1100 Subject: Re: [mkgmap-dev] Changes to require name defined in the style file Hi Gerd The perfect answer! I understand the improved logic of the changes, and yes it makes sense, but a side effect is some work is now required editing the style sheet. No great hassle as at least I was not going mad. Cheers Brett From: gpetermann_muenchen@hotmail.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 10:21:17 +0100 Subject: Re: [mkgmap-dev] Changes to require name defined in the style file Hi Brett, please look at http://www.mkgmap.org.uk/news/2013/12/22/more-flexibility-in-style-files-sty... Doesn't that answer your questions? Gerd From: brussell237@live.com.au To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 20:16:23 +1100 Subject: [mkgmap-dev] Changes to require name defined in the style file Hi All Trouble been a bit slow to update or more likely just plain with my styles but I think that somewhere along the line the automatic use of the name changed. I find I now need to add & name=*{name '${name}'} to any point of interest to display the name. In the past I think I only needed name=* No great problem as I can re-work my style sheet but for my own sanity check did this extra vigour in defining the style creep in? Cheers Brett _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi The style sheets are rather a black art to me. To get a name on a waterfall do I need to use natural=waterfall {name '${name}'} [0x6508 resolution 20] or natural=waterfall name=* {name '${name}'} [0x6508 resolution 20] Neither appear to be working? I have upgraded to R3132. As for the generic question on warning users on major style sheet changes. The idea sounds great but implementation not so much. By that I can not figure out a sensible way to do it. Warnings after a while get ignored so prefer warnings than means why something did not work rather than suggestions of improvements. While it was great that mkgmap had a lot of inbuilt corrective and often guessed what the user wanted the downside was the style sheets became rather mysterious with hard to figure out the logic for newbies. At least with the current approach they are less "magical" but does mean some update work as people tend to be weeded to "their" style and typ sheets. We are gradually developing a mkgmap community but it forms into three broad groups. Mad mappers, map cutters using mkgmap, and people that simply want an img. The map cutters are the rarest group and we short of reverse engineer solutions or "steal" them from each other. Cheers Brett From: gpetermann_muenchen@hotmail.comTo: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 10:34:33 +0100 Subject: Re: [mkgmap-dev] Changes to require name defined in the style file Hi Brett, you are not the 1st and probably not the last to be trapped. I thought about a check that warns the user but I found nothing that works always. Any ideas out there? How can mkgmap detect that the user has to modify the style to get a usable result? Gerd From: brussell237@live.com.au To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 20:26:49 +1100 Subject: Re: [mkgmap-dev] Changes to require name defined in the style file Hi Gerd The perfect answer! I understand the improved logic of the changes, and yes it makes sense, but a side effect is some work is now required editing the style sheet. No great hassle as at least I was not going mad. Cheers Brett From: gpetermann_muenchen@hotmail.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 10:21:17 +0100 Subject: Re: [mkgmap-dev] Changes to require name defined in the style file Hi Brett, please look at http://www.mkgmap.org.uk/news/2013/12/22/more-flexibility-in-style-files-sty... Doesn't that answer your questions? Gerd From: brussell237@live.com.au To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 28 Mar 2014 20:16:23 +1100 Subject: [mkgmap-dev] Changes to require name defined in the style file Hi All Trouble been a bit slow to update or more likely just plain with my styles but I think that somewhere along the line the automatic use of the name changed. I find I now need to add & name=*{name '${name}'} to any point of interest to display the name. In the past I think I only needed name=* No great problem as I can re-work my style sheet but for my own sanity check did this extra vigour in defining the style creep in? Cheers Brett _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Brett, To make your style compatible you only need to add a <finalize> section at the end of your style files. Polygons example: <finalize> # The finalizer section is executed for each element when a rule with an element type matches include 'inc/compat_polygons'; Same for compat_lines and compat_points In the /inc subfolder you must put these 3 files.
Hi Minko Thanks for the advice. Now in the process of updating my style. Never to sure if I should start again with the default and modify it. It is a pity that the standard style and typ sheets did not mirror the OSM web view but I believe that some Garmins do not take kindly to some typ files so can understand the default been a safe starting point. Also just about every location has particular needs so not much more can be done with default styles as often users' need conflict. Strange as it might appear in Europe but gravel roads that can be impassible by normal cars are classed as National Highways in Australia. Still have not worked out the best way to render gravel roads but still keep their road level rating. Duplicating all the road lines for gravel will likely mean running out of Garmin hex codes for line type. Also OSM surface rules are rather weird. Bit like the hiking classifications that are very word long, but at least they are a standard. Tempted by the technic used by some for bridges to render gravel roads. O'well, thanks to all the developers and testers. I get a few nice thankyous for the img that I produce but frankly this group does most of the work. Thanks again. Cheers Brett Russell PO Box 94 Launceston Tas. 7250 Australia 0419 374 971
On 28 Mar 2014, at 9:23 pm, "Minko" <ligfietser@online.nl> wrote:
Brett, To make your style compatible you only need to add a <finalize> section at the end of your style files. Polygons example:
<finalize> # The finalizer section is executed for each element when a rule with an element type matches include 'inc/compat_polygons';
Same for compat_lines and compat_points In the /inc subfolder you must put these 3 files.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Brett, Maybe you cna have a look at the Lambertus generic new style maps. Recently I have put a dashed overlay line next to the highways to indicate the surface is unpaved. highway ~ '.*(trunk|primary|secondary|tertiary|unclassified|residential|minor|road).*' & mkgmap:unpaved=1 { add mkgmap:road-speed = '-1' } [0x10002 resolution 21 continue with_actions] highway ~ '.*(byway|living_street|service|cycleway).*' & mkgmap:unpaved=1 [0x10002 resolution 23 continue with_actions] The styles you can find here: http://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fst...
Strange as it might appear in Europe but gravel roads that can be impassible by normal cars are classed as National Highways in Australia. Still have not worked out the best way to render gravel roads but still keep their road level rating. Duplicating all the road lines for gravel will likely mean running out of Garmin hex codes for line type. Also OSM surface rules are rather weird. Bit like the hiking classifications that are very word long, but at least they are a standard. Tempted by the technic used by some for bridges to render gravel roads.
Hi Looks like a brilliant and timely solution. Finally buckled and today brought a 4wd. Now more mapping to do! Thanks once again, I will put this in my style sheet. Cheers Brett Brett Russell 237 Oldaker Street Devonport Tas 7310 Phone: (03) 6424 8033 Mobile: 0419 374 971
On 29 Mar 2014, at 7:44 pm, "Minko" <ligfietser@online.nl> wrote:
Hi Brett, Maybe you cna have a look at the Lambertus generic new style maps. Recently I have put a dashed overlay line next to the highways to indicate the surface is unpaved.
highway ~ '.*(trunk|primary|secondary|tertiary|unclassified|residential|minor|road).*' & mkgmap:unpaved=1 { add mkgmap:road-speed = '-1' } [0x10002 resolution 21 continue with_actions] highway ~ '.*(byway|living_street|service|cycleway).*' & mkgmap:unpaved=1 [0x10002 resolution 23 continue with_actions]
The styles you can find here: http://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fst...
Strange as it might appear in Europe but gravel roads that can be impassible by normal cars are classed as National Highways in Australia. Still have not worked out the best way to render gravel roads but still keep their road level rating. Duplicating all the road lines for gravel will likely mean running out of Garmin hex codes for line type. Also OSM surface rules are rather weird. Bit like the hiking classifications that are very word long, but at least they are a standard. Tempted by the technic used by some for bridges to render gravel roads.
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 28/03/14 09:34, Gerd Petermann wrote:
Any ideas out there? How can mkgmap detect that the user has to modify the style to get a usable result?
The version number (in the version file) should be used to detect changes. In this case all you can do is print a message asking them to update their style based on the blog post and then update the version number. Perhaps its a bit late this time, since most people have already made the changes but certainly for the future. Ideally the number could be used for backward compatibility too, but at least a message should be required. ..Steve
participants (4)
-
Brett Russell -
Gerd Petermann -
Minko -
Steve Ratcliffe