December 2017 - mkgmap-dev - The mkgmap lists

mkgmap:set_unconnected_type differentiate between connected on both sides or on one side only
by Felix Hartmann 14 Nov '19

14 Nov '19

Would it be possible to have the mkgmap:set_unconnected_type=... differentiate between conncected on both sides for lines and only connected on one side? For example I would like to delete all service=driveway shorther than 100m length if they are connected only on one side to another routable line - if they are in between I would like to keep them. (in some countries - e.g. Switzerland and France) often highway=service&service=driveway leads not only to a house but also connects e.g. to a highway=track or highway=path. -- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich

5 44

Commit r3842: Improve ResidentialHook / BoundaryQuadTree: suppress misleading warnings about overlapping admin_level=11 boundaries
by svn commit 09 Apr '18

09 Apr '18

Version mkgmap-r3842 was committed by gerd on Sat, 11 Mar 2017 Improve ResidentialHook / BoundaryQuadTree: suppress misleading warnings about overlapping admin_level=11 boundaries http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3842

8 15

DEM file and the block-size option
by Gerd Petermann 14 Jan '18

14 Jan '18

Hi all, the current default block-size is 512. This is used for most *.img files and gives a maximum file size of 65534*512 ~ 32MB. For large DEM files you might need a --block-size=1024 or even 2048. If I got that right you may run into the next problem when using this option as the mdr file will be also created with this value, and if no value is given it uses 16384 (which means the mdr file can grow close to 1GB) This disadvantage of a larger block-size is that your img files are typically a bit larger. @Steve: If I got that right we should be able to calculate the optimal block-size as we do know the number of bytes that we will write to the img-file before anything is actually written to the disk. Wouldn't that be much better? Gerd

5 15

mkgmap r4025 implements --x-dem-poly option
by Gerd Petermann 06 Jan '18

06 Jan '18

Hi all, see http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4025 this is useful if you create a map for a country extract like nepal (nepal-latest.osm.pbf) Here is a screenshot of a map created with the option --x-dem-poly=nepal.poly http://files.mkgmap.org.uk/download/378/nepal-with-poly.jpg The screenshot also shows some wrong reliefs, and I think I used files without many holes :-( So, next step is to find out what goes wrong with DEM in low resolutions. This might take longer, I hope Frank has an idea. It seems to be a good idea to use a rather high res for the overview map for now. For the screenshot I used --x-overview-dem-dist=276160, with --x-overview-dem-dist=88000 the problems are gone and DEM file is still only ~300KB. Gerd P.S. See also http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&path=%2F&rev=40… I've moved some messages into the logger, so there will be less noise from mkgmap.

5 18

DEM and "holes"
by Frank Stinner 01 Jan '18

01 Jan '18

Unfortunately we have no chance for a good shading if the HGT's have so much "holes" (no data values) like nepal. I have made this picture with QGIS. The blue areas are "no data". I don't know, what makes mapsource with this. Frank --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

3 5

mkgmap r4023 supports zipped hgt files
by Gerd Petermann 28 Dec '17

28 Dec '17

See http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4023 for details. Maybe I'll change the code again so that it doesn't extract the hgt file for each zoom level. Might be a bit faster. Gerd

1 0

mkgmap r4022 ready
by Gerd Petermann 28 Dec '17

28 Dec '17

Hi all, see the log message http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4022 for details about the changes. I've also experimented with code to read a *.poly file and use that to define an area for which mkgmap should not calculate DEM data but was not happy with the results so far. Maybe I'll try again. Henning has pointed me to an error: It seems that mkgmap (and probably also BuildDEMFile) somtimes create invalid DEM data for areas where the hgt files contain large holes, esp. when resolution is low (high dem-dist value). See e.g. http://files.mkgmap.org.uk/download/377/holes.jpg I try to find out more now. Gerd

5 7

Error BeNeLul
by Arndt Röhrig 26 Dec '17

26 Dec '17

4 9

dem not showing
by nwillink 24 Dec '17

24 Dec '17

Hi Gerd I've come across an issue with mkgmap-dem-tdb-r4013 It involves N51E000.hgt but perhaps any xxxE000.hgt It seems to create an empty dem - I came across the problem after splitting the UK - even with max nodes 800,000 I used this pbf : http://files.mkgmap.org.uk/download/376/maidstone.pbf Interestingly , Frank's program creates the correct DEM. r Nick -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

2 1

r4015 in dem-tdb branch implements --x-overview-dem-dist
by Gerd Petermann 24 Dec '17

24 Dec '17

Hi, okay, so we now have three new (still undocumented options) to enable hillshading and calculation of elevation data in routes. Here is a summary of the new options: --x-dem=path_to_dir[,path_to_other_dir,...] gives one or more directories containing *.hgt files. --x-dem-dists=n1,n2,n3,... Sample from a Garmin Demo map: --x-dem-dists="5520, 16560, 44176, 88368" should contain one number for each level in case you want to use the DEM data in a gmapsupp, the values give the number of DEM units between two points. A DEM unit is 360° / 2 ^32. The higher the numbers the smaller the DEM file. Useful values for level 0 start at 1600 if you have 1'' hgt data and a small area, for large areas consider to use 8000 or more. If this option is missing mkgmap will calculate one DEM level based on the resolution of the hgt files. --x-overview-dem-dist=n Use this option to add DEM also to the overview map. The value again gives the distance between two DEM points. It the option is not given or the value is 0 the creation of DEM data for the overview map is disabled. This might be needed for large areas and for overview img files which are already close to 16MB . Useful are probably values > 100000, e.g. 256000 Expect to see "There is not enough room in a single garmin map for all the input data. The .osm file should be split into smaller pieces first." when experimenting with these options. The additional amount of bytes for the DEM files depend on the above options, and the relief of the area. Mountains require much more space compared to flat areas like the netherlands. If you have contour lines in your overview map try without. I'll try to add code to splitter so that it creates smaller tiles for areas with many mountains. I don't know yet how to store that info. Gerd

4 3