<div dir="ltr"><div>Those were my suggestions based on my rather limited experience. I knew there are options for the java environment that require a single hyphen (ex: -Xmx4000m -jar), and then there is the configuration file parameter (which I forgot) but I ignored those for the sake of simplicity. <br></div><div><br></div><div>I think given what you just said, the need for a comprehensive help guide is essential. Otherwise these sorts of questions and the amount of time it takes to sort out the answers will only increase as the program grows more complicated.</div><div><br></div><div>Also, if your 3rd point is true it only adds more confusion to the debate "
3) The typ file can appear anywhere but it is a good idea to place it at the end"<br></div><div><br></div><div>How can it be "a good idea" to place the filespec for the TYP file at the end if it is also true that it "can appear anywhere"? The two assertions appear to be in conflict in my reading of that statement<br></div><div><br></div><div>Dave<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 4, 2020 at 10:34 PM Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com">gpetermann_muenchen@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Dave,<br>
<br>
sorry, but your suggestion would be very wrong, esp. this one:<br>
"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)"<br>
<br>
1) For historic reasons, some parameters require only one dash, e.g. -c or -n.<br>
2) Only some parameters expect a comma separated option list, and since r4517 a "dangling" comma in those lists should provoke an error message.<br>
3) The typ file can appear anywhere but it is a good idea to place it at the end<br>
<br>
The option handling is very difficult to understand, esp. as mkgmap offers so many different ways to do it. There is no way to document it in a few short sentences.<br>
<br>
Gerd<br>
<br>
________________________________________<br>
Von: mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>> im Auftrag von Dave Swarthout <<a href="mailto:daveswarthout@gmail.com" target="_blank">daveswarthout@gmail.com</a>><br>
Gesendet: Donnerstag, 4. Juni 2020 17:05<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 143, Issue 10<br>
<br>
Pitney wrote:<br>
"The issue with options and order (of precedence?) still confuses me after using mkgmap for years."<br>
<br>
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:<br>
<br>
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.<br>
<br>
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)<br>
<br>
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")<br>
<br>
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.<br>
<br>
Etc.<br>
<br>
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.<br>
<br>
Dave<br>
<br>
On Thu, Jun 4, 2020 at 9:12 PM Pitney <<a href="mailto:mappitney@gmail.com" target="_blank">mappitney@gmail.com</a><mailto:<a href="mailto:mappitney@gmail.com" target="_blank">mappitney@gmail.com</a>>> wrote:<br>
Hello<br>
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.<br>
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.<br>
I only have a tablet in quarantine so I apologize for any formatting issues.<br>
Pitney<br>
<br>
On June 4, 2020, at 2:11 AM, <a href="mailto:mkgmap-dev-request@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-request@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev-request@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-request@lists.mkgmap.org.uk</a>> wrote:<br>
<br>
Send mkgmap-dev mailing list submissions to<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:mkgmap-dev-request@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-request@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev-request@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-request@lists.mkgmap.org.uk</a>><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:mkgmap-dev-owner@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-owner@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev-owner@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-owner@lists.mkgmap.org.uk</a>><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of mkgmap-dev digest..."<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
<br>
<br>
--<br>
Dave Swarthout<br>
Homer, Alaska<br>
Chiang Mai, Thailand<br>
Travel Blog at <a href="http://dswarthout.blogspot.com" rel="noreferrer" target="_blank">http://dswarthout.blogspot.com</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Dave Swarthout<br>Homer, Alaska<br>Chiang Mai, Thailand<br>Travel Blog at <a href="http://dswarthout.blogspot.com" target="_blank">http://dswarthout.blogspot.com</a></div></div>