Re: [mkgmap-dev] DEM file and the block-size option

Hi, here is attached temporary fix for block-size. List of changes: * Default block size for img set to 1k. This allows for img up to 64MB. User can change this value with option --block-size. * Block size for overview map fixed at 1k. Not changeable by user. * Block size for MDR fixed at 16k.

Re: [mkgmap-dev] what do the 0x4a polygon in the mean?

Hi Andrezj, okay, I'll try again tomorrow. Gerd Von: mkgmap-dev im Auftrag von Andrzej Popowski Gesendet: Freitag, 12. Januar 2018 20:36:03 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re:

[mkgmap-dev] what do the 0x4a polygon in the mean?

Hi experts, today I played with a map that has non-rectangular shape. I tried this: Use the dem-poly option to cut also the 0x4b polygon for each tile, use these 0x4b polygons also in the overview map and also for 0x4a in the overview map. I expected that this would create nicer maps but found

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Henning, looking at your files, I see that small rectangles are forced by overlapping areas. I think restriction for poly are the same as for option --polygon-file, quote from doc: "If the polygon area(s) describe(s) a rectilinear area with no more than 40 vertices, splitter will try to

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

On 13.01.2018 00:43, Andrzej Popowski wrote: > Is it this right-angled shape of polys required? I'm not 100% sure, but somehow I remember Gerd told me it needs to be rectangle shaped. Hening ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Small tiles are mainly caused by not well aligned polygons. I attached you kmz with my splitter result. You can compare them for example in josm. I just have realized the small tiles while testing in beginning of DEM-support. While checking for broken img-files with 0kb I found several others with

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Henning, you are right, using splitter is a valid alternative to my process. Is it this right-angled shape of polys required? And where are created small tiles, around any border or only on overlapping areas? -- Best regards, Andrzej ___

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Andrzej For Africa it can be useful, as areas with drive on left /right are at least roughly horizontal and vertical. Also you don't need overlapping for this use case. In general I also think, as soon as mkgmap can support non-rectangle tiles, it will be better obsolete. Using non-rectangle

Re: [mkgmap-dev] DemDisplay supports now img files with GMP

Hi Gerd Have found some interesting distances Latest Spain , Germany, Austria Holland,Poland  Topos : 5520;16560;44176;88368 Topo Franc V3 and V4 : 6624 only Italy :2752;8472;44176;88368 Sweden:9936;9936;13248;13248;26512 r Nick ___ mkgmap-dev

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Henning, > --polygon-desc-file=filename.osm Thanks for info. That's very interesting. Actually I would like similar processing for mkgmap, since I'm satisfied with standard splitting. But I see a good uses for this feature. I can create polygons for drive on left and drive on right

[mkgmap-dev] DemDisplay supports now img files with GMP

Hi all, thanks to hints from Andrzej DemDisplay is now able to read DEM data from NT map (GMP format). See http://www.mkgmap.org.uk/websvn/revision.php?repname=display=516 New binary: http://www.mkgmap.org.uk/websvn/revision.php?repname=display=516 Usage is the same as before. Winterkarte uses

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Oh, forgotten to mention: --polygon-desc-file=filename.osm you need to use for splitter. Henning ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Something similar is already possible with splitter. You can create an *.osm file with many polygons inside, each with tags name=* and mapid=* (see attachment). splitter will give you tiles with 6234 and per polygon a .args with list of necessary data tiles per map. That args-file you can hand

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Peter, Viefinder-Panoramas files not only contains voids but some serious errors too, like depressions 1km deep. At least they had some years ago. SRTM data version 3 are mostly void free, but I can see some voids for example in Nepal. Currently you need a login to get SRTM data. I think

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Henning, > you should be able to split Europe once and then just let mkgmap > calculate all the country maps based on the boundary polygons I'm doing something similar for my maps. I create a map of a continent, for example Africa and then I execute mkgmap with list of img to create

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Gerd, ok, maybe I was too fast. ;-) I just tried to understand your Bremen example. You have splitted Lower Saxony (Niedersachsen) into 15 tiles. Based on these 15 tiles you want to let mkgmap create a map of Bremen by using a map polygon, which is not following any of the splitted tiles. Lets

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Henning, sorry, can't follow. All I tried to point out was that it is not a good idea to use an option --overview-map-polygon. My understanding is that a bounding polygon has to be used for all tiles that build a map and that the 0x4b polygon of the overview map should be the combination of

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

So your idea was basically: User has splitted a data file covering city A in the upper part and city B in the lower part. Now user wants to ask mkgmap creating a map with that data file for city A only by giving mkgmap a polygon only covering upper part of that data tile. Ok, I haven't thought

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Andrzej Thanks for that Nick On 12/01/2018 12:10, Andrzej Popowski wrote: Hi Nick, DEM in GMP should be the same. The difference is, that in DEM subfile headers starts at 0, but in GMP header is at address contained at offset 0x2D. If you want to analyze DEM then algorithm is something

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Gerd, using poly to clip background could be a way to create irregular maps. There are some caveats. Background doesn't clip map data, they will be still visible. The proper way would be to clip data too. Detailed tiles and overview map have different resolution and usually their edges

Re: [mkgmap-dev] mkgmap r4048 seems to fix problem with hill shading

Hi Andrzej, the change only applies to rectangles completely outside of the polygon. I don't know why those areas cause trouble in other areas. Maybe the old data was somehow corrupting the memory in MapSource. Gerd Von: mkgmap-dev

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Henning, reg. Bremen: I thought the other way around. Say you split and compile Niedersachsen as 15 rectangular tiles. Next you compile Bremen using some of these tiles and an polygon for Bremen that is only used for the overview map. I guess that would look very strange. I also don't know

Re: [mkgmap-dev] mkgmap r4048 seems to fix problem with hill shading

Hi Gerd, great, thanks for quick solution! I haven't looked at code but I think mkgmap builds internal poly from tiles area, when dem-poly is missing. So DEM in overview is still clipped. I haven't noticed artifacts in this case, was it different form irregular poly? -- Best regards,

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Andrzej, thanks for the hint. I'll try to code that in DemDisplay today. Gerd Von: mkgmap-dev im Auftrag von Andrzej Popowski Gesendet: Freitag, 12. Januar 2018 13:10:32 An:

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Gerd, I probably didn't got your issue. So far I understand I gave mkgmap a list of data tiles or already compiled map tiles. based on this mkgmap creates a complete map. At the moment the overview map is rectangle of maxlat,maxlon,minlat,minlon. Based on my suggestion user in future would be

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Nick, DEM in GMP should be the same. The difference is, that in DEM subfile headers starts at 0, but in GMP header is at address contained at offset 0x2D. If you want to analyze DEM then algorithm is something like that: char *subfile int offset; if (typ == DEM) offset = 0 if

Re: [mkgmap-dev] dem-poly and precomp-sea

Hi Gerd, probably all Garmin's map have irregular background. You can look for example at old Winter Activity Map: https://static.garmincdn.com/shared/de/custom/winter2013/_download/winterkarte.zip It is GMP, but DEM data should be the same. -- Best regards, Andrzej

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Henning, I don't think that we should apply a bounding polygon only to the overview map. If you compile tiles for whole Germany and produce a map for Bremen using some of these tiles and an overview map that was created with a proper polygon I would assume that this looks strange when you zoom

Re: [mkgmap-dev] The 0x4b background polygon in the overview map

Hi Gerd, I think this would be best and additionally I would suggest to make the polygon defined by user (as suggested in DEM-poly and precomp-sea thread). As default I would limit overview map to the map tiles. Maybe then we should name the parameter --overview-map-polygon=filename I'm not

[mkgmap-dev] The 0x4b background polygon in the overview map

Hi all, up to now mkgmap always creates a rectangular 0x4b polygon for the overview map. I wonder if I should change that so that the 0x4b polygons of the sub tiles are used. This seems to be the better way if we start using non-rectangular 0x4b polygons? Gerd

[mkgmap-dev] mkgmap r4048 seems to fix problem with hill shading

Hi all, I've changed the code so that when a sub tile (typically 64x64) is completely outside of the polygon (--dem-poly) is still encoded with a bit stream. This is how BuildDEMFile does it and it seems that this solves all problems reported by Andrzej. Before this I simply wrote a header

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Gerd Many thanks so far I've got similar results as you have had ie an old GB TOPO :1648,3312,13248,53024 an old Swiss : 3312,13248,53024,212096 another one : 3312,6624,26512,106048,424192,1696768 I've also been extracting the dem from some GMP files but clearly the structure is quite

Re: [mkgmap-dev] option --show-profiles and DEM

Hi Nick, I've uplodaed display.jar r515: http://files.mkgmap.org.uk/download/388/display.jar See http://www.mkgmap.org.uk/websvn/revision.php?repname=display=515 The previous one also contained an experimental patch in MdrCheck which was not in the svn repo. Gerd

Re: [mkgmap-dev] dem-poly and precomp-sea

Hi Andrzej, yes, and maybe that's also an explanation for the problems with the hill shading. The current implementation in mkgmap fills the values outside of the polygon with "invalid" height. Maybe Garmin only does that for those sub tiles which are completely outside of the polygon. I can