Yes, as you can see above, I understand the intent of those two options.
But if someone could further explain what's happening in the rule, I would
be most appreciative.
I'm guessing the first part assigns a name or ref if one appears in the
tagging but understanding the logic of the series of "s
On Fri, May 15, Paco Tyson wrote:
> This is the license and copyright text :
Your format is wrong. A newline defines a new license, not
a new line. GARMIN Software and devices will sort the different
licenses and remove duplicates before displaying them.
> Independently of the exposed results a
Hi all,
I started customizing the copyright/license text for my map. I found some
strange results that I want to share with you.
This is the license and copyright text :
license.txt :
My license text
Second line of license
Third and last line, blabla êß
copyright.txt :
Beginning of the copyri
Hi Dave,
please check the documentation for --process-destination and
--process-exits:
http://www.mkgmap.org.uk/doc/options
If I got this right, these option mark exits so that Garmin knows where
they are where they lead.
Gerd
Dave Swarthout wrote
> I am curious to know how mkgmap handles the
Hi Dave,
I'm curious about this too and hope the specialist could explain this to us.
Alexandre
2015-05-15 14:45 GMT-03:00 Dave Swarthout :
> I am curious to know how mkgmap handles the display of and text to speech
> aspects of motorway junctions. It's hard to test for this without actually
>
I am curious to know how mkgmap handles the display of and text to speech
aspects of motorway junctions. It's hard to test for this without actually
creating a route and then driving it to see and hear what the Garmin is
doing with the data or to discover where it gets the information from.
I'm as
Hi
"This definition implies that an IMG file can never have more than 65,535
blocks, but
the use of large block sizes (2048, 4096, etc…) allow the IMG file to hold
several gigabytes of
data. The only practical limit on IMG file size seems to be the use of
32-bit integers for file
offsets, whic
Hi Minko,
I don't know much about the reason for this 16MB limit. I found this in
imgformat-1.0.pdf:
"This definition implies that an IMG file can never have more than 65,535
blocks, but
the use of large block sizes (2048, 4096, etc…) allow the IMG file to hold
several gigabytes of
data. The only
Thanks Gerd,
I have now updated and uploaded the Europe map in case you'll make another bike
trip ;-)
http://www.openfietsmap.nl/downloads/europe
BTW Is 16 Mb still the limit for the overview map?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.
Hi ,
this message is produced in a routine which doesn't know the
file name (and I found no easy way to change that), so
the only good improvement that I found is to print a stack trace
when it doesn't happen while processing a single OSM input file.
(mkgmap r3596).
@Steve: Maybe we can throw a
Version mkgmap-r3596 was committed by gerd on Fri, 15 May 2015
print a stack trace if a MapFailedException is produced in one of the combiners
(index, overview map, nsis etc)
This should help to overcome the confusion created by the hint
"There is not enough room in a single garmin map for all
11 matches
Mail list logo
