Hi all, finally I've merged r2629 into trunk. A brief description of the changes: 1) new or changed options --overview-levels like levels, specifies additional levels that are to be written to the overview map. Counting of the levels should continue. Up to 8 additional levels may be specified, but the lowest usable resolution with MapSource seems to be 11. --remove-ovm-work-files If overview-levels is used, mkgmap creates one additional file with the prefix ovm_ for each map (*.img) file. These files are used to create the overview map. With option --remove-ovm-work-files=true the files are removed after the overview map was created. The default is to keep the files. --polygon-size-limits=limits code Allows to specify different min-size-polygon values for each resolution. Sample: --polygon-size-limits="24:12, 18:10, 16:8, 14:4, 12:2, 11:0" If a resolution is not given, mkgmap uses the value for the next higher one. For the given sample, resolutions 19 to 24 will use value 12, resolution 17 and 18 will use 10, and so on. Value 0 means to skip the size filter. Note that in resolution 24 the filter is not used. 2) Optimizations: - The polygon filter allows larger polygons. - SeaGenerator generates fewer "sea-only" and "land-only" polygons when precomp-sea is used. Both reduce the img size, esp. for maps containing large "sea only" areas. 3) Changes regarding styles: - The support for the out-aged map-features.csv file was removed - Level ranges can now use min-max or max-min - Usage of polygon type 0x4a will be flagged with --check-styles 4) Other changes - A few checks are performed regarding the plausibility of the given options and input files to help beginners. -- View this message in context: http://gis.19327.n5.nabble.com/overview-map-tp5763471.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, congratulations! Great work! A big thanks also to Steve who implemented the basics some time ago! I think it's worthy to add a news to the mkgmap homepage, isn't it? http://www.mkgmap.org.uk/news/ Have fun! WanMil
Hi all,
finally I've merged r2629 into trunk.
A brief description of the changes: 1) new or changed options --overview-levels like levels, specifies additional levels that are to be written to the overview map. Counting of the levels should continue. Up to 8 additional levels may be specified, but the lowest usable resolution with MapSource seems to be 11.
--remove-ovm-work-files If overview-levels is used, mkgmap creates one additional file with the prefix ovm_ for each map (*.img) file. These files are used to create the overview map. With option --remove-ovm-work-files=true the files are removed after the overview map was created. The default is to keep the files.
--polygon-size-limits=limits code Allows to specify different min-size-polygon values for each resolution. Sample: --polygon-size-limits="24:12, 18:10, 16:8, 14:4, 12:2, 11:0" If a resolution is not given, mkgmap uses the value for the next higher one. For the given sample, resolutions 19 to 24 will use value 12, resolution 17 and 18 will use 10, and so on. Value 0 means to skip the size filter. Note that in resolution 24 the filter is not used.
2) Optimizations: - The polygon filter allows larger polygons. - SeaGenerator generates fewer "sea-only" and "land-only" polygons when precomp-sea is used. Both reduce the img size, esp. for maps containing large "sea only" areas.
3) Changes regarding styles: - The support for the out-aged map-features.csv file was removed - Level ranges can now use min-max or max-min - Usage of polygon type 0x4a will be flagged with --check-styles
4) Other changes - A few checks are performed regarding the plausibility of the given options and input files to help beginners.
-- View this message in context: http://gis.19327.n5.nabble.com/overview-map-tp5763471.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
This is great news. The overview map was one of the biggest deficiencies in mkgmap until now. So thanks to Gerd and well done. Also a lot of bugs have been fixed along the way, so I would like to acknowledge that too. I will put up a news item on the website this evening and push out notices to freecode. ..Steve GerdP <gpetermann_muenchen@hotmail.com> wrote:
Hi all,
finally I've merged r2629 into trunk.
A brief description of the changes: 1) new or changed options --overview-levels like levels, specifies additional levels that are to be written to the overview map. Counting of the levels should continue. Up to 8 additional levels may be specified, but the lowest usable resolution with MapSource seems to be 11.
--remove-ovm-work-files If overview-levels is used, mkgmap creates one additional file with the prefix ovm_ for each map (*.img) file. These files are used to create the overview map. With option --remove-ovm-work-files=true the files are removed after the overview map was created. The default is to keep the files.
--polygon-size-limits=limits code Allows to specify different min-size-polygon values for each resolution. Sample: --polygon-size-limits="24:12, 18:10, 16:8, 14:4, 12:2, 11:0" If a resolution is not given, mkgmap uses the value for the next higher
one. For the given sample, resolutions 19 to 24 will use value 12, resolution 17 and 18 will use 10, and so on. Value 0 means to skip the size filter. Note that in resolution 24 the filter is not used.
2) Optimizations: - The polygon filter allows larger polygons. - SeaGenerator generates fewer "sea-only" and "land-only" polygons when
precomp-sea is used. Both reduce the img size, esp. for maps containing large "sea only" areas.
3) Changes regarding styles: - The support for the out-aged map-features.csv file was removed - Level ranges can now use min-max or max-min - Usage of polygon type 0x4a will be flagged with --check-styles
4) Other changes - A few checks are performed regarding the plausibility of the given options and input files to help beginners.
-- View this message in context: http://gis.19327.n5.nabble.com/overview-map-tp5763471.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I'd also like to thank everyone involved in implementing this feature. I have not yet tried the new overview map on a device, but I can confirm that map display is considerably faster in Basecamp on Mac OS X. In addition, the overview map makes the selection of map tiles in MapInstall far far easier (used to transfer the selected map tiles to a GPS device). Excellent work. Cheers. On May 31, 2013, at 4:44 PM, Steve Ratcliffe <steve@parabola.me.uk> wrote:
This is great news. The overview map was one of the biggest deficiencies in mkgmap until now.
So thanks to Gerd and well done.
Also a lot of bugs have been fixed along the way, so I would like to acknowledge that too.
I will put up a news item on the website this evening and push out notices to freecode.
..Steve
GerdP <gpetermann_muenchen@hotmail.com> wrote: Hi all,
finally I've merged r2629 into trunk.
A brief description of the changes: 1) new or changed options --overview-levels like levels, specifies additional levels that are to be written to the overview map. Counting of the levels should continue. Up to 8 additional levels may be specified, but the lowest usable resolution with MapSource seems to be 11.
--remove-ovm-work-files If overview-levels is used, mkgmap creates one additional file with the prefix ovm_ for each map (*.img) file. These files are used to create the overview map. With option --remove-ovm-work-files=true the files are removed after the overview map was created. The default is to keep the files.
--polygon-size-limits=limits code Allows to specify different min-size-polygon values for each resolution. Sample: --polygon-size-limits="24:12, 18:10, 16:8, 14:4, 12 :2, 11:0" If a resolution is not given, mkgmap uses the value for the next higher one. For the given sample, resolutions 19 to 24 will use value 12, resolution 17 and 18 will use 10, and so on. Value 0 means to skip the size filter. Note that in resolution 24 the filter is not used.
2) Optimizations: - The polygon filter allows larger polygons. - SeaGenerator generates fewer "sea-only" and "land-only" polygons when precomp-sea is used. Both reduce the img size, esp. for maps containing large "sea only" areas.
3) Changes regarding styles: - The support for the out-aged map-features.csv file was removed - Level ranges can now use min-max or max-min - Usage of polygon type 0x4a will be flagged with --check-styles
4) Other changes - A few checks are performed regarding the plausibility of the given options and input files to help beginners.
< br />
-- View this message in context: http://gis.19327.n5.nabble.com/overview-map-tp5763471.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
The overview map is only for Basecamp/Mapsource/Qlandkarte GT - so on desktop. On device it get's faster - because the normal map doesn't need to go down to zoomlevel 16 or 14 anymore - and the device BASEMAP can get in earlier (and the Basemap is much faster than rendering several tiles at once). The missing link is now much more that we could create a simple Basemap that is non routable - to replace routable basemaps on newer garmins that interfere with routable mkgmap maps - (because many people now opt to simply drop the garmin basemap because of this)... (that basemap if done well, shouldn't need to be updated more often than every 5 years or so - only basic information needed). On 04.06.2013 00:16, Clinton Gladstone wrote:
I'd also like to thank everyone involved in implementing this feature.
I have not yet tried the new overview map on a device, but I can confirm that map display is considerably faster in Basecamp on Mac OS X. In addition, the overview map makes the selection of map tiles in MapInstall far far easier (used to transfer the selected map tiles to a GPS device).
Excellent work.
Cheers.
On May 31, 2013, at 4:44 PM, Steve Ratcliffe <steve@parabola.me.uk <mailto:steve@parabola.me.uk>> wrote:
This is great news. The overview map was one of the biggest deficiencies in mkgmap until now.
So thanks to Gerd and well done.
Also a lot of bugs have been fixed along the way, so I would like to acknowledge that too.
I will put up a news item on the website this evening and push out notices to freecode.
..Steve
GerdP <gpetermann_muenchen@hotmail.com <mailto:gpetermann_muenchen@hotmail.com>> wrote:
Hi all,
finally I've merged r2629 into trunk.
A brief description of the changes: 1) new or changed options --overview-levels like levels, specifies additional levels that are to be written to the overview map. Counting of the levels should continue. Up to 8 additional levels may be specified, but the lowest usable resolution with MapSource seems to be 11.
--remove-ovm-work-files If overview-levels is used, mkgmap creates one additional file with the prefix ovm_ for each map (*.img) file. These files are used to create the overview map. With option --remove-ovm-work-files=true the files are removed after the overview map was created. The default is to keep the files.
--polygon-size-limits=limits code Allows to specify different min-size-polygon values for each resolution. Sample: --polygon-size-limits="24:12, 18:10, 16:8, 14:4, 12 :2, 11:0" If a resolution is not given, mkgmap uses the value for the next higher one. For the given sample, resolutions 19 to 24 will use value 12, resolution 17 and 18 will use 10, and so on. Value 0 means to skip the size filter. Note that in resolution 24 the filter is not used.
2) Optimizations: - The polygon filter allows larger polygons. - SeaGenerator generates fewer "sea-only" and "land-only" polygons when precomp-sea is used. Both reduce the img size, esp. for maps containing large "sea only" areas.
3) Changes regarding styles: - The support for the out-aged map-features.csv file was removed - Level ranges can now use min-max or max-min - Usage of polygon type 0x4a will be flagged with --check-styles
4) Other changes - A few checks are performed regarding the plausibility of the given options and input files to help beginners.
< br />
-- View this message in context:http://gis.19327.n5.nabble.com/overview-map-tp5763471.html Sent from the Mkgmap Development mailing list archive atNabble.com <http://nabble.com/>. ------------------------------------------------------------------------
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
participants (5)
-
Clinton Gladstone -
Felix Hartmann -
GerdP -
Steve Ratcliffe -
WanMil