Hi Gerd Yes, --order-by-decreasing-area will cause more polygon splitting as it forces polygons to be split with the subdivision splitting. However the code does try to keep the subdivision splitting to appropriate power-of -2 for for the zoom level (as far as I can remember) I've often seen narrow white bands like this, mainly in the sea where they are more obvious. If I remember correctly this was noticeable on BaseCamp and they come and go with zooming, even within the same map -level. Ticker On Sat, 2020-10-10 at 06:09 +0000, Gerd Petermann wrote:
Hi Karl,
I think this might be related to the multipolygon cutting. There is this comment in the code for MultipolygonCutter: // try to find a cut point that is a multiple of 2048 to // avoid that gaps are painted by MapSource and QLandkarteGT // between the cutting lines
In some cases this fails, maybe you see the result. I don't think that we can always find such a good cut point, so there is probably not much we can do about it. @Ticker: Is it possible that option --order-by-decreasing-area produces more of these cases?
Besides that it is unlikely that this has an effect on routing.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von 7770 <7770@foskan.eu> Gesendet: Freitag, 9. Oktober 2020 16:49 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Disconnected map sections, types in TYP -files.
Hi. Both actually, i can follow such lines for many kilometers. In the past i was also able to find similar cases on www.opentopomap.org, which for sure has routing problems over longer distances.
Here is one such place which i was able to locate just now: https://www.opentopomap.org/#map=15/58.92148/18.28258 If i recall correctly, this show (or showed) a white line on a GPS.
Kind regards, Karl
On fredag 9 oktober 2020 kl. 15:41:35 CEST Gerd Petermann wrote:
Hi Karl,
okay, looked at 217.bmp. It doesn't seem to be related to tile boundaries. I think someone else reported similar problems, only visible on the device. I've never seen them on my Oregon. Do the gaps disappear when you zoom in or out?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von 7770 <7770@foskan.eu> Gesendet: Freitag, 9. Oktober 2020 15:34 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Disconnected map sections, types in TYP -files.
Hi Gerd, screenshot and log uploaded. Kind regards, Karl
On fredag 9 oktober 2020 kl. 14:43:30 CEST Gerd Petermann wrote:
Hi Karl,
please upload a screenshot and the splitter.log to http://files.mkgmap.org.uk/
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von 7700 <7770@foskan.eu> Gesendet: Freitag, 9. Oktober 2020 14:40 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Disconnected map sections, types in TYP -files.
Hi, unfortunately --no-trim has not helped, i can still observe such gaps.
The splitter command: java -Xmx1200m -jar ../mkgmap/splitter-r597/splitter.jar \ --output-dir=norden/splitted/ \ --mapid=77700001 \ --max-nodes=1500000 \ --no-trim \ norden/norden.o5m > norden/splitted/splitter.log
Kind regards Karl
On fredag 9 oktober 2020 kl. 11:51:24 CEST Gerd Petermann wrote:
Hi Karl,
reg. the gaps betweet tiles: This sounds like you use splitter with --no-trim=false. Try without it.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von 7700 <7770@foskan.eu> Gesendet: Freitag, 9. Oktober 2020 11:37 An: Development list for mkgmap Betreff: [mkgmap-dev] Disconnected map sections, types in TYP -files.
Hi. Still on my learning path, and thanks for good documents, which have helped a lot.
Now i have one observation and a few questions.
1. i observe that in the map created (mkgmap 4585) i can see disconnected map sections, they usually show up as a thin white line in the map, often easier to see over water or darker areas. The gap sometimes makes the routing calculations fail if the gap is in the routing direction and big enough. I have observed these gaps not inly in the maps have made, but also at opentopomap, but not with garmin.opensteetmap.nl (to mention some examples). Pictures can be provided if wanted. Is there a proper way to eliminate these gaps when generating the maps?
2. When working with TYP files, i have read: If a polygon type is not listed in this section, then it will not be displayed at all.
Is this valid? If it is, then it means i really have to add every single item which may be generated and which is on the map, otherwise i risk loosing information without even knowing, say if i want to change very small portions from how the device displays something.
I have found that there some information sets that cover a lot of types that garmin devices can show, but is it possible to extract a list from mkgmap, for example extracting the default set? Is the example mapnik.txt file complete or just an example?
If i didn't make errors, it seems there is a difference between generating gmapsupp with no TYP and this example TYP.
3. From which type number can i define my own type to avoid collission with existing types? I am thinking of adding handling for aerialways.
4. Related to the polygon amenity=parking and displaying of a picture. on maps such as from garmin.openstreetmap.nl, the polygon for amenity=parking displays the same parking symbol (garmin default, round with red P and black border) as for a point amenity=parking. I tried generating the individual tiles with the style present from mkgmap using --style-file=path/styles/, in which i see a mapping in the polygons file: amenity=parking | parking=surface [0x05 resolution 22]
But even with this, the parking polygons do not show any picture/symbol. What else is needed?
Kind regards Karl
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev