Hi Mike, thanks, looks good to me. One problem: --net is no longer obsolete. I've once changed the code so that you can create a map that allows full address search but no routing. It seems I forgot to update the docs.
Please review my changes reg. --net and --route in attached v2 which is for r4103. Please do svn update first. Reg. --polygon-size-limits: This is difficult to describe. The values after pairs of resolution map units, but one has to understand that the values are scaled for resolution. Also the polygons are first scaled to the resolution before this size is calculated Example --polygon-size-limits="24:12, 18:10, 16:8, 11:0" res 24 --> 12 * 2^(24-24) = 12 * 2^0 = 12 * 1 = 12 res 23 --> 12 * 2^(24-23) = 12 * 2^1 = 12 * 2 = 24 res 22 --> 12 * 2^(24-22) = 12 * 2^2 = 12 * 4 = 48 ... res 19 --> 12 * 2^(24-19) = 12 * 2^5 = 12 * 32 = 384 res 18 --> 10 * 2^(24-18) = 10 * 2^6 = 640 res 17 --> 10 * 2^(24-17) = 10 * 2^7 = 1280 res 16 --> 8 * 2^(24-16) = 8 * 2^8 = 2048 res 15 --> 8 * 2^(24-15) = 8 * 2^9 = 4096 ... Maybe you find a nicer description? reg. draw-priority: I've never played with that. My understanding is this: Each map has a draw-priority. When you activate more than one map on your GPS device and they cover the same area this value determines which map is "on top". I think it is used with contour lines in combination with option --transparent. reg. max-jobs: I agree. In splitter the default is to use all processors, mkgmap should do the same. ciao, Gerd ________________________________________ Von: mkgmap-dev <[email protected]> im Auftrag von Mike Baggaley <[email protected]> Gesendet: Samstag, 3. Februar 2018 14:31 An: 'Development list for mkgmap' Betreff: [mkgmap-dev] documentation improvements Hi Gerd, I have attached a further patch for documentation improvements. This clarifies the syntax for several of the options and moves all the deprecated and obsolete options to the end. Please review and commit if happy. In further reading the documentation, I have the following questions that require clarification in the documentation: What are the units for --polygon-size-limits? Can we clarify --draw-priority=25. There is no explanation of what the 25 does. Is this only value that can be provided? What is different if this option is not provided? The operation of the --max-jobs option seems illogical. Why is the default not to use all the CPU cores and hence presumably minimise execution time? Cheers, Mike
documentation-v2.patch
Description: documentation-v2.patch
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
