Re: [mkgmap-dev] EU map too big?
Hi Minko, that' s good news :-) When you reach the limit again you may have to remove some details from the overview map, e.g. use level 19/20 instead of 18 or remove the background type 0x10100. I only see one potential improvement in the program: Many bytes are used to store sea / coastline polygons. If we ever manage to find a better algo to simplify them for the low Garmin resolutions we may be able to store better info with fewer bytes. The current combination of filters tends to produce self-intersecting ugly looking triangles which often contain spikes, which means they have redundant bytes. @Mike Baggaley: I think your pointInPolygon-v0.patch showed a completely new approach to simplify polygons using the Java Graphics2D.fillPolygon() method. Maybe this could be used as a new filter for shapes in MapBuilder. It seems to do exactly what we want. Gerd Date: Thu, 14 May 2015 11:17:20 +0200 From: ligfiet...@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] EU map too big? Hi Gerd, Probably something went wrong the first time. I now managed to produce a full map with all the tiles and mkgmap-r3595. Thanks again for the quick fixes! ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] EU map too big?
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, which imposes a hard limit of 4 GB. Large sub-files, those with more than 240 blocks of data, are spanned across multiple FAT blocks with each sub-file part numbered in a 32-bit integer at offset 0x10. File size is only present in the first of these (part 0x). 65535 * 256 ~ 16BG, so I assume that this is the reason. I see files which use a different blocksize, so maybe this limit makes no more sense. @Steve: Can you have a look at this, please? The img file as a whole can be very large by using a large block size as the quoted passage states. This is how we create the global index and the gmapsupp files. (We may not however automatically adjust the block size for regular tiles, but that could be fixed if it became a problem.) The bigger issue is the limits on the individual files (RGN etc) within the .img file. For example the subdivision pointers from TRE into RGN are 3 byte quantities and so this means that the max possible offset into RGN for the start of a subdivision is around 16M. It is possible that there are flags that allows you to extend this, but I don't know of any, nor have I seen any files that break this limit. ..Steve ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Routing parameters
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 subst filters
following that is, for a newbie, quite challenging.
On Fri, May 15, 2015 at 12:17 PM, GerdP gpetermann_muenc...@hotmail.com
wrote:
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 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 assuming that whatever one puts in the exit_to=* tag gets displayed
and
spoken by the Garmin assistant. Does mkgmap ever use the destination=*
tag, and if so under what circumstances?
I found this rule in the lines style sheet, but I do not understand it
well
enough to help me answer my question
(highway=motorway_link | highway=trunk_link) mkgmap:exit_hint=true
mkgmap:dest_hint=true
{ name '${destination:ref|subst: =} ${destination|subst:;= |subst:/=
}' |
'${ref|subst: =} ${destination|subst:;= |subst:/= }' |
'${destination|subst:;= |subst:/= }' |
'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' |
highway=road
'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_exit_to}' |
'Exit ${mkgmap:exit_hint_exit_to}' |
'Exit ${mkgmap:exit_hint_name}' |
'Exit ${mkgmap:exit_hint_ref}'
}
As always, thanks in advance to any help you can provide.
Dave
--
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
--
View this message in context:
http://gis.19327.n5.nabble.com/Routing-parameters-tp5844762p5844766.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
--
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] License and copyright text defects
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 copyright text Second line of the copyright text, including accentuated characters : éàß Third and last line of the copyright text For each run, I run mkgmap v3539, create a .gmap map with jmc_cli, install it on Basecamp thanks to MapManager. I then install it on my Oregon 600 via MapInstall. First run : --license-file=license.txt and --copyright-file=copyright.txt JaVaWa GMTK displays : My license text Second line of license Third and last line, blabla êß BEGINNING OF THE COPYRIGHT TEXT SECOND LINE OF THE COPYRIGHT TEXT, INCLUDING ACCENTUATED CHARACTERS : ÉÀSS THIRD AND LAST LINE OF THE COPYRIGHT TEXT Basecamp displays : BEGINNING OF THE COPYRIGHT TEXT My license text Second line of license Third and last line, blabla êß SECOND LINE OF THE COPYRIGHT TEXT, INCLUDING ACCENTUATED CHARACTERS : ÉÀSS THIRD AND LAST LINE OF THE COPYRIGHT TEXT Oregon 600 displays on the Info page of the map : ©SECOND LINE OF THE COPYRIGHT TEXT, INCLUDING ACCENTUATED CHARACTERS : ÉÀSS ©THIRD AND LAST LINE OF THE COPYRIGHT TEXT The first line of the copyright file is displayed before the license block on Basecamp and it is missing on the GPS device. Second run : --license-file=license.txt and --copyright-file=copyright.txt but copyright.txt content is : Only one line JaVaWa GMTK displays : My license text Second line of license Third and last line, blabla êß PROGRAM LICENCED UNDER GPL V2 ONLY ONE LINE Basecamp displays : My license text Second line of license Third and last line, blabla êß ONLY ONE LINE PROGRAM LICENCED UNDER GPL V2 Oregon 600 displays on the Info page of the map : ©ONLY ONE LINE Note how the lines of the copyright block are switched between GMTK and Basecamp. Independently of the exposed results above, I have a few questions and remarks : - Despite providing a lower case copyright text, the result text is in upper case. Is it done by mkgmap ? Is it a Garmin format limitation ? - In the default license/copyright text, one can read Program released under the GPL and PROGRAM LICENCED UNDER GPL V2. I assume it's the mkgmap license, instead I'd expect here the license of the produced Garmin map. Documentation remarks : --copyright-message=note Specify a copyright message for files that do not contain one. What files are we talking about ? The OSM data files ? By the way, we could add here that --copyright-message is ignored if --copyright-file is also provided. --copyright-file=file Specify copyright messages from a file. Note that the first copyright message is not displayed on a device, but is shown in BaseCamp. The copyright file must include at least two lines. Based on my tests, one can specify a one-line copyright file, mkgmap adds the line PROGRAM LICENCED UNDER GPL V2, the last sentence is not true anymore. --license-file : I don't understand All entries of all maps will be merged in the overview map.. What are all maps ? Is the overview map used to store the overview levels or the gmapsupp.img file ? Cheers, Paco___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Routing parameters
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 assuming that whatever one puts in the exit_to=* tag gets displayed and
spoken by the Garmin assistant. Does mkgmap ever use the destination=*
tag, and if so under what circumstances?
I found this rule in the lines style sheet, but I do not understand it well
enough to help me answer my question
(highway=motorway_link | highway=trunk_link) mkgmap:exit_hint=true
mkgmap:dest_hint=true
{ name '${destination:ref|subst: =} ${destination|subst:;= |subst:/=
}' |
'${ref|subst: =} ${destination|subst:;= |subst:/= }' |
'${destination|subst:;= |subst:/= }' |
'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' |
highway=road
'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_exit_to}' |
'Exit ${mkgmap:exit_hint_exit_to}' |
'Exit ${mkgmap:exit_hint_name}' |
'Exit ${mkgmap:exit_hint_ref}'
}
As always, thanks in advance to any help you can provide.
Dave
--
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] License and copyright text defects
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 above, I have a few questions and remarks : - Despite providing a lower case copyright text, the result text is in upper case. Is it done by mkgmap ? Is it a Garmin format limitation ? It's done by the Software/Device displaying this. - In the default license/copyright text, one can read Program released under the GPL and PROGRAM LICENCED UNDER GPL V2. I assume it's the mkgmap license, instead I'd expect here the license of the produced Garmin map. The default license cannot show the license of your map, the mkgmap devlopers don't know them. Thorsten -- Thorsten Kukuk, Senior Architect SLES Common Code Base SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Routing parameters
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 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 assuming that whatever one puts in the exit_to=* tag gets displayed
and
spoken by the Garmin assistant. Does mkgmap ever use the destination=*
tag, and if so under what circumstances?
I found this rule in the lines style sheet, but I do not understand it
well
enough to help me answer my question
(highway=motorway_link | highway=trunk_link) mkgmap:exit_hint=true
mkgmap:dest_hint=true
{ name '${destination:ref|subst: =} ${destination|subst:;= |subst:/=
}' |
'${ref|subst: =} ${destination|subst:;= |subst:/= }' |
'${destination|subst:;= |subst:/= }' |
'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' |
highway=road
'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_exit_to}' |
'Exit ${mkgmap:exit_hint_exit_to}' |
'Exit ${mkgmap:exit_hint_name}' |
'Exit ${mkgmap:exit_hint_ref}'
}
As always, thanks in advance to any help you can provide.
Dave
--
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
--
View this message in context:
http://gis.19327.n5.nabble.com/Routing-parameters-tp5844762p5844766.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Routing parameters
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 daveswarth...@gmail.com:
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 assuming that whatever one puts in the exit_to=* tag gets displayed
and spoken by the Garmin assistant. Does mkgmap ever use the
destination=* tag, and if so under what circumstances?
I found this rule in the lines style sheet, but I do not understand it
well enough to help me answer my question
(highway=motorway_link | highway=trunk_link) mkgmap:exit_hint=true
mkgmap:dest_hint=true
{ name '${destination:ref|subst: =} ${destination|subst:;= |subst:/=
}' |
'${ref|subst: =} ${destination|subst:;= |subst:/= }' |
'${destination|subst:;= |subst:/= }' |
'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_name}' |
highway=road
'Exit ${mkgmap:exit_hint_ref} ${mkgmap:exit_hint_exit_to}' |
'Exit ${mkgmap:exit_hint_exit_to}' |
'Exit ${mkgmap:exit_hint_name}' |
'Exit ${mkgmap:exit_hint_ref}'
}
As always, thanks in advance to any help you can provide.
Dave
--
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
