Hi Greg For a long time, with my old eTrex HCx, all I used was: - my style based on mkgmap-default - the option --order-by-decreasing-area - TYP sameOrder.txt which is in the distribution, alongside mapnik.txt Whenever I notice a problem, see a good idea or someone reports difficulties that could be resolved by a style change, I tweak my style, and, every now and again, I submit patches to the default style that brings it closer to my version. Recently I've been having to add a few _lines and _polygons to my TYP because of differences between devices. I've also changed a few type codes that make it incompatible with mkgmap-default & mapnik.txt, but I plan to start a dialog on these as well. Once the styles are compatible again, I'll look at submitting another example typ-file. I've attached my style and typ anyway, feel free to take whatever bits you want. Ticker On Tue, 2020-04-07 at 11:03 -0400, Greg Troxel wrote:
Ticker Berkin <rwb-mkgmap@jagit.co.uk> writes:
For both, apart from the above, I much prefer their default rendering rather than, say, {distribution}/examples/typ-files/mapnik.txt which also slows down the devices to an almost unusable speed.
Is your preferred approach part of mkgmap now? I didn't find it alongside the mapnik typ, and I think it would be useful to share, as an example, or for use. I have been using mkgmap for a very long time and concur that less is better. I did use to use cferrero's typfile and style, which was mostly about adding stoplights and some other things not usually shown. I'd like to see towers/masts as well, survey markers, and various other things that I'm not sure render without typ.
(I admit to being a little distant from what's going on as I mainly use OsmAnd, but I carry my etrex 30 as well, so I have two functioning devices in the woods.)
Thanks, Greg