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" <[email protected]> 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 > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
