February 2019 - mkgmap-dev - The mkgmap lists

documentation improvement patch
by Mike Baggaley 30 Jan '20

30 Jan '20

Hi Gerd, I have attached a patch to improve the documentation of the command line. I did it some time ago and had forgotten about it, but the discussion on whether to change default options prompted me to come back to it. The change is purely to the documentation, no code changes. Please review and if it meets with your approval, commit. Thanks, Mike

6 28

New branch for default typ file
by Gerd Petermann 21 Dec '19

21 Dec '19

Hi all, I've created a new branch now with changes proposed by Joris. I hope this helps bringing this forward. Attached is a document from Joris. Gerd

11 52

mkgmap:set_unconnected_type differentiate between connected on both sides or on one side only
by Felix Hartmann 14 Nov '19

14 Nov '19

Would it be possible to have the mkgmap:set_unconnected_type=... differentiate between conncected on both sides for lines and only connected on one side? For example I would like to delete all service=driveway shorther than 100m length if they are connected only on one side to another routable line - if they are in between I would like to keep them. (in some countries - e.g. Switzerland and France) often highway=service&service=driveway leads not only to a house but also connects e.g. to a highway=track or highway=path. -- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich

5 44

Sample basic mkgmap config file
by Gerd Petermann 13 Nov '19

13 Nov '19

Hi all, here is my proposal for a file which should be good for every new user. I plan to add it to the examples directory in the distributed zip. Please suggest improvements if you miss something really important. I started to write a HOWTO but got stuck because it is so difficult to handle the differences between Windows/Linux/Mac and the usage of relative or absolute paths. I've recently learned that new users might not even know how to copy a file into a hidden directory like C:\ProgramData. I know that some of you distribute packages containing styles and scripts but I think they all work either only on Windows or on Linux or they require further packages like pearl. Correct me if I'm wrong. No idea how to continue here :( Gerd

4 16

default style improvements
by Ticker Berkin 01 Mar '19

01 Mar '19

Hi I'd like to make quite a few changes and improvements to the default style. Some of these should be non-contentious: The first change I propose is to make the layout consistent and clearer and I've attached a patch to do this for the points/lines/polygons files. The only change here is white-space (blanks, tabs, new-lines), no other characters have been changed. I've used: $ java ... uk.me.parabola.mkgmap.osmstyle.StyleImpl pathTo/default to check there are no semantic changes, but this program fails to dump the <finalize> section, so I've checked these very carefully via other methods. Next changes I am thinking of are: Simple layout where character changes are involved Provide more information on unnamed objects where a good garmin mapping hasn't been found, eg, after all the shop=known ... lines there is a mop-up: shop=* & shop!=no & shop!=none [0x2e0c resolution 24] changing this to: shop=* & shop!=no & shop!=none {add name='${shop|subst:"_=> "}'} [0x2e0c resolution 24] will name unnamed shops with the value of the shop tag. There are about 15 sections that benefit from this. Add more commonly used tag-values, eg: tourism=bed_and_breakfast [0x2b02 resolution 24] and other mop-ups I think these sort of changes should be applied to the trunk After this, the changes I'm thinking of will require more discussion. Regards Ticker

10 76

Update of typ with correct codepage and special chars
by Joris Bo 28 Feb '19

28 Feb '19

Hello, Thx for all the help and tips. When using utf-8 and codepage 65001 together it works from txt tot typ and back to .txt But it's easy to mess up if you (accidently) re-save from a typ-editor in the wrong txt format, so be careful. Tested from .txt to .typ with mkgmap.jar * In the previous version I made a mistake when restoring a backup column of the German translations after messing up, This should now be the work of Ralf * The Portuguese translations are updated thx to Alexandre * Thx to Steph for the French translations ! * Hopefully fixed the codepage issues Feel free to feedback New languages can be added using the xls Kind regards Joris

4 6

mkgmap experimental options --x..
by dave pitney 23 Feb '19

23 Feb '19

Hello - Is there a listing of mkgmap experimental options? I know these are not listed in the docs (nor should they be) but I may find one that is helpful. Also it should be stated that support for these may not be available. Thanks, -- pitney ----------------- end of message ------------------------

2 1

splitter option? (or new request)
by dave pitney 23 Feb '19

23 Feb '19

Hello - Is there is an option to not compress pbf output files when using splitter? I use the split files as input to mkgmap. Osmium has an option "pbf_compression=none" which is placed in the json file as an option. This increases file size (appx double) but allows faster file reading/writing. Given the low cost of storage and the (relatively) high cost of processing/time this may be a useful splitter option. I am current using r591. Thank you, -- pitney ----------------- end of message ------------------------

2 1

A minor, documentation only change request
by Randolph J. Herber 22 Feb '19

22 Feb '19

This request may cause changes in many places; but, no changes to mkgmap behavior. It took me close to five years to learn what really was meant by: " but the lowest usable resolution with MapSource seems to be 11." in --overview-levels. I suggest a change to " but the lowest usable resolution (coarsest scale, smallest scale number) with MapSource seems to be 11." I had interpreted that the numbers to the right of the colon had to be 11 or smaller numerically. Randolph J. Herber

2 1

posting test
by dave pitney 22 Feb '19

22 Feb '19

testing if pitney can post -- pitney ----------------- end of message ------------------------

2 1