[mkgmap-dev] Connected ways rendered as Unconnected ways due to Garmin low resolution
From Gerd Petermann gpetermann_muenchen at hotmail.com on Wed Jan 29 11:18:28 GMT 2020
Hi Eric, it is rather easy to reproduce for me because I can add some debugging code which shows the effect of the rounding to garmin units. You can try yourself: Draw some buildings in JOSM and create copies at other positions. The biggest distortions happen when points are near to the center of 4 nails in my "bed of nails" explanation. I asked for an example because JOSM will not report such a situation. It only complains when a road ends near another one. Try attached sample. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von AnkEric <eric_internet at casema.nl> Gesendet: Mittwoch, 29. Januar 2020 12:06 An: mkgmap-dev at lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Connected ways rendered as Unconnected ways due to Garmin low resolution Hi Gerd, I was very afraid you would ask for an example! I'm 100% sure it's OK on OSM. JOSM validation would protest! Immediately! Examples are very rare AND are always Resolved. If I find one piece of my own Garbage tomorrow I will resolve the same day. The next day I will conclude that it has indeed been solved. By exception: I will wait for OpenFietsMap to see if it has the same issue. In case I do wait, the issue is always confirmed by OpenFietsMap. Also: if I resolve, I will not (no need) Connect or JOIN. My only actions: move the connecting node (and sometimes: delete some nodes). I could have a look at my Changeset Comments. And than... revert my solution? Create Errors deliberately? Lol, please don't tell anyone; -)) Back in memory lane: I now do remember one issue. But also: that was one year ago! The Netherlands, Wassenaar? Roundabout? Can I search my own Changeset Comments? But also: you do not ignore my issue. So next time I do find one, I will NOT resolve and send you the link immediately. Next: I will read your "Distorted-lines". But be prepared for ignore modus: I might not respond anymore because I cannot find an example. Now I understand why it took a few years before I posted this. If it is not reproducible, a solution is almost impossible. / Eric (AnkEric) -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html _______________________________________________ mkgmap-dev mailing list mkgmap-dev at lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: not-connected.osm Type: application/octet-stream Size: 1645 bytes Desc: not-connected.osm URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20200129/3da5561f/attachment-0001.obj>
- Previous message: [mkgmap-dev] Connected ways rendered as Unconnected ways due to Garmin low resolution
- Next message: [mkgmap-dev] Connected ways rendered as Unconnected ways due to Garmin low resolution
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list