January 2018 - 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

Re: [mkgmap-dev] DEM-file generation from geo-tiff sources ?
by Frank Stinner 05 May '18

05 May '18

For my opinion your data sources are very interesting. This is a short look to the alps, the tile E40N20 from https://land.copernicus.eu/. There seem's to be a little problem at the near of some coastlines, but we have on the other hand a high resolution of 25m. I belive, a bigger problem is the coordinate reference system. Copernicus data have EPSG:3035, garmin use EPSG:4326. It would be fine, if mkgmap could be read geotiffs and calculate with different coordinate reference systems. This would perhaps collect the interpolation for changing the coordinate reference system and for the garmin map. On the other hand: this is a lot of mathematical stuff. I'm not a java hacker and i don't know, if there are usable geografic librarys for this work. At the moment we have to translate the tiffs from EPSG:3035 to EPSG:4326, then the segmentation in 1°x1° tiffs an at last the conversion to hgt files. This should not be a very great problem with gdal-tools or so, but it is additional work. Frank

5 13

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

Please help with news about new DEM options
by Gerd Petermann 03 Feb '18

03 Feb '18

Hi all, with r4093 I've merged the dem-tdb branch into trunk. I think it would be good to mention this in the "Latest news" on [1] , maybe with one or two screen shots, but I have no idea how to write this "from a users view". Do we need a how-to that describes the sources for hgt files and maybe more about the new options? It would be great if somebody could help with that. Gerd [1] http://www.mkgmap.org.uk/

6 11

Style Manual
by Mike Baggaley 01 Feb '18

01 Feb '18

I notice the style manual has no mention of mkgmap:stylefilter or mkgmap:tagsincomplete in it. I see these in the output of the echotags command when handling a relation. Can they be added to the documentation? Cheers, Mike

3 3

Option --dem-profile seems to cause crash in MapSource
by Gerd Petermann 31 Jan '18

31 Jan '18

Hi all, I've just noticed that MapSource crashed after pressing the "Show Profile..." button for a route. I can reproduce the crash on MapSource, Basecamp just says "The current map does not contain any elevation data on the selected route(s)" This problem disappears when I remove the --dem-poly option, so I think there still is a problem in the encoder :-( The interesting thing is that my route is far away from the polygon boundary. I'll try to find out more ... Gerd

2 3

"RE: Option --dem-profile seems to cause crash in "MapSource
by cdavilam 31 Jan '18

31 Jan '18

1 0

Commit r4094: improve documentation about default for --levels: Mention that the default style overwrites the hard coded default.
by svn commit 30 Jan '18

30 Jan '18

Version mkgmap-r4094 was committed by gerd on Tue, 30 Jan 2018 improve documentation about default for --levels: Mention that the default style overwrites the hard coded default. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4094

1 0

Commit r4093: merge from dem-tdb branch
by svn commit 30 Jan '18

30 Jan '18

Version mkgmap-r4093 was committed by gerd on Tue, 30 Jan 2018 merge from dem-tdb branch This implements new "Hill Shading (DEM) options". It also contains the changes from the auto-block branch which improves the calculation of the block size in img files and corrects some miscalculations in the structure of the MDR index file. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4093

1 0

remove splitter option align-for-dem again or change mkgmap?
by Gerd Petermann 29 Jan '18

29 Jan '18

Hi all, with current code in mkgmap this option is of no use, as mkgmap rounds the dem-dist values (down) to multiples of 16. (9942 -> 9936 , 3314 ->3312) This means that points are always interpolated, no matter where the tile boundaries are. So, I see two possibilites: 1) remove the option from splitter (it is not yet documented anyway) 2) change the code in mkgmap to allow using the exact dem-dist values without rounding I think this works fine with MapSource and Basecamp, but maybe some devices will not be able to handle that, as Garmin maps always use the rounded values. A possible benefit of the exact values is that we may be able to avoid interpolation, at least in some areas of the world. What do you think? Gerd

3 9