logo separator

[mkgmap-dev] mkgmap-dev Digest, Vol 143, Issue 10

From Joris Bo jorisbo at hotmail.com on Thu Jun 4 17:21:53 BST 2020

Hello Dave

I understand your difficulties, i have gone through them as well.
But in the mean while I also find out that it is just not that easy unless you make it a very personal execution.

I tried to translate your comments into a introduction of ‘the mkgmap command line options manual’ which appears if you use -help or if you look at the website.

For now I’m sure It is still not all true, but I like to ask if people think it’s a nice idea to start this manual with this introduction.
If so… Then I’ll try to enhance it in the same direction and then some unix guy could give his comment and so make it better.

Attached what I have in mind. If to be improved I suggest max another page not a full book…

Kind regards

Van: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> Namens Dave Swarthout
Verzonden: donderdag 4 juni 2020 17:05
Aan: Development list for mkgmap <mkgmap-dev at lists.mkgmap.org.uk>
Onderwerp: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 143, Issue 10

Pitney wrote:
"The issue with options and order (of precedence?) still confuses me after using mkgmap for years."

I reckon that was my point in opening this topic all along. I think I've got it now and it makes sense but the documentation could still be made clearer IMO. For example:

Invoking the mkgmap java program involves supplying a list of parameters or commands that allow the user to control the operation of the program and the output generated by it.

These parameters must be preceded by a double dash (two hyphens with no spaces between them) which are immediately followed by a command string. Each such parameter must be terminated with a comma with no space before or after it. (example: java -jar mkgmap.jar --parm1,--parm2,--parm3)

All input file specifications (filename.ext) must follow the last option in the invocation string. You may use a full path for that filespec as long as it is enclosed in quotes. (Windows/Dos example: "C:\Users\username\Downloads\Maps\MyState.osm")

Any type file specification (filename.typ) containing custom bitmaps for Garmin lines, polygons and points must be the last file specification in the list of input files.


Thanks also to Gerd for the latest releases which addressed the spurious space issue and improved the program's error reporting. I'm sure these will go a long way toward smoother operations for those of us who are only casual users of mkgmap.


On Thu, Jun 4, 2020 at 9:12 PM Pitney <mappitney at gmail.com<mailto:mappitney at gmail.com>> wrote:
The issue with options and order (of precedence?) still confuses me after using mkgmap for years. My solution is to not use option files and to hard code all file references. Not good scripting practice but it works.
I think this is a case of where examples are worth a thousand words. I understand in theory option and file order but do not know how to implement it in practice. Examples (in a separate file?) and how to work out which files they will effect may reduce confusion.
I only have a tablet in quarantine so I apologize for any formatting issues.

On June 4, 2020, at 2:11 AM, mkgmap-dev-request at lists.mkgmap.org.uk<mailto:mkgmap-dev-request at lists.mkgmap.org.uk> wrote:

Send mkgmap-dev mailing list submissions to
        mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
        mkgmap-dev-request at lists.mkgmap.org.uk<mailto:mkgmap-dev-request at lists.mkgmap.org.uk>

You can reach the person managing the list at
        mkgmap-dev-owner at lists.mkgmap.org.uk<mailto:mkgmap-dev-owner at lists.mkgmap.org.uk>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of mkgmap-dev digest..."
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>

Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20200604/9563f52e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: suggestion for command manual.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 21610 bytes
Desc: suggestion for command manual.docx
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20200604/9563f52e/attachment-0001.docx>

More information about the mkgmap-dev mailing list