Hi Gerd A few more things I've discovered.
GPSMapEdit will show bands of emptyness for a thin, correct, slice when you zoom out but with the view zoom level locked at a higher resolution than it expects. This confused some of my previous findings. Changing some sizes changes the behaviour and I sometimes get the holes at level 1 but level 2 is OK. 3 of the edges of the hole correspond to cut-lines to get at the cluster of 'islands', but the 4th corresponds to the subdivision max -size splitting, so it looks like the problem might be related to MapBuilder/MapSplitter/MapArea logic. With option --x-no-mergeshapes (and current trunk) it appears that cutting to this island group happens twice from the left, with 1 line continuing to the right and twice from the top, with 1 line continuing to the bottom. Ticker On Sun, 2021-04-25 at 13:50 +0100, Ticker Berkin wrote: > Hi Gerd > > More more testing with standard style / options etc. As well as - > -order > -by, I had some level params that confused. > > With GPSMapEdit at Zoom level 2, there is a wide cut from the LHS > forest triangle to the holes around 54.9953,-58.2209. It seems to be > the total height of the holes. > > Similar shows in MapSource, but it much more difficult to find. > Resolution needs to be <= 7mi before forest kicks-in. I didn't > investigate how far left the blank area went. > > Looking more closely on Basecamp, the blank area is a rectangle > approx > 54.975,-58.302 to 55.0178,-58.6247, ie it doesn't go to the edge of > the > forest triangle. Also it only shows when detail-level is set to > "highest" > > Ticker > > On Sun, 2021-04-25 at 11:03 +0100, Ticker Berkin wrote: > > Hi Gerd > > > > Just tried this with latest trunk and my standard environment > > (mainly > > --order-by-decreasing-area > > and get very inconsistent results. > > > > On GPSMapEdit seems reasonable - shows forest triangle and, within, > > a > > small area with a number of holes. > > > > MapSource shows a white square, no forest colour and I can't move > > the > > map around, also it doesn't seem to zoom out enough. First time I > > looked I saw 2 white squares. > > > > Basecamp shows the forest triangle, but I can't find the > > islands/holes > > > > I've had problems before with MapSource or Basecamp caches, so I'll > > delete these. Also try with simple options etc > > > > Ticker > > > > > > On Sun, 2021-04-25 at 07:31 +0000, Gerd Petermann wrote: > > > Hi Experts, > > > > > > while working on the faster-mp branch I experimented with the > > > monster > > > relation r9488835. I added tag landuse=forest to it so that it is > > > actually rendered and found huge (wrong) empty rectangles in the > > > forest. > > > The original file is very complex but the same problem also > > > occurs > > > with a simplified file, see > > > http://files.mkgmap.org.uk/download/505/bad-map-split.osm.pbf > > > Just use e.g. > > > java -jar mkgmap.jar --gmapi bad-map-split.osm.pbf > > > Problem: Basecamp and Mapsource don't show this map, GpsMapEdit > > > shows > > > a large white rectangle near 54.97743 -58.30292 > > > > > > I assume that we hit some unknown limit , possibly in > > > LinePreparer > > > or > > > MapSplitter. > > > I've also tried some older versions, so far they all show the > > > problem. > > > Any idea where to look? > > > > > > RgnDisplay shows this data for the problemat area: > > > --------- Level 0, Subdiv 279 ----------------------------------- > > > -- > > > -- > > > ----------- > > > | | | final at 265f, (end > > > 25e2) > > > | | | polygon start 2634 > > > to > > > 265f > > > 00002634 | 000000 | 4b | Polygon 1 > > > | | | Type 0x4b > > > 00002635 | 000001 | 00 00 00 | Label offset: > > > 0x000000 > > > () > > > 00002638 | 000004 | d0 3b | Long delta 15312 > > > 0000263a | 000006 | 2a 3a | Lat delta 14890 > > > | | | Start point > > > 55.24913, > > > -61.91139 2574796/-2885280 > > > 0000263c | 000008 | 0c | Bitstream length 12 > > > 0000263d | 000009 | bb | Base bb > > > 0000263e | 00000a | 06 43 04 00 00 00 4c d1 | Bitstream (len: 12, > > > 0xc) > > > 00002646 | 000012 | 41 ef 00 00 | > > > | | | xsame false, xneg > > > false > > > | | | ysame true, yneg > > > true > > > | | | xbase 16, ybase 15 > > > | | | Coord 55.24913, > > > -62.56851 2574796/-2915904 [-30624,+0] > > > | | | Coord 54.61014, > > > -62.56851 2545017/-2915904 [+0,-29779] > > > | | | Coord 54.61014, > > > -61.91139 2545017/-2885280 [+30624,+0] > > > | | | 0 bits left, 0 > > > | | | > > > 0000264a | 000016 | 50 | Polygon 2 > > > | | | Type 0x50 > > > 0000264b | 000017 | 00 00 00 | Label offset: > > > 0x000000 > > > () > > > 0000264e | 00001a | d0 3b | Long delta 15312 > > > 00002650 | 00001c | b4 08 | Lat delta 2228 > > > | | | Start point > > > 54.97743, > > > -61.91139 2562134/-2885280 > > > 00002652 | 00001e | 0b | Bitstream length 11 > > > 00002653 | 00001f | 9b | Base 9b > > > 00002654 | 000020 | f2 8d 04 40 a7 fe d0 4b | Bitstream (len: 11, > > > 0xb) > > > 0000265c | 000028 | e7 00 00 | > > > | | | xsame false, xneg > > > false > > > | | | ysame true, yneg > > > false > > > | | | xbase 16, ybase 11 > > > | | | Coord 54.97743, > > > -62.51706 2562134/-2913506 [-28226,+0] > > > | | | Coord 55.01732, > > > -62.54665 2563993/-2914885 [-1379,+1859] > > > | | | Coord 55.01732, > > > -61.91139 2563993/-2885280 [+29605,+0] > > > | | | 4 bits left, 0 > > > | | | > > > > > > > > > Gerd > > > _______________________________________________ > > > mkgmap-dev mailing list > > > mkgmap-dev@lists.mkgmap.org.uk > > > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > _______________________________________________ > > mkgmap-dev mailing list > > mkgmap-dev@lists.mkgmap.org.uk > > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
