<html><head></head><body><div dir="auto">It seems to be more easy to promote OSM Inspector and fix those faults... 😎<br></div>
<div dir="auto">Henning </div>
<div class="gmail_quote" >On 4 Apr 2018, at 21:55, Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="blue">Hi Felix,<br><br>Maybe we have different ideas what merging of labels means.<br>With r4149 I've implemented this:<br>If way w1 has e.g. mkgmap:label:1 = "Main Street" and mkgmap:label:2 = "N 232" (a ref)<br>and way w2 has only mkgmap:label:1 = "Main Street" mkgmap adds mkgmap:label:2 from the first way.<br>Also if w2 has e.g. mkgmap:label:1 = "Main Place" the merged result would be<br>mkgmap:label:1 = "Main Street"<br>mkgmap:label:2 = "N 232"<br>mkgmap:label:3 = "Main Place"<br>I did not yet test if that really works with address search, also there is no method to detect which way is w1 and which is w2.<br>Probably order of appearance.<br><br>Another option would be to somehow concatenate labels, esp. those from ref tags, but I have no idea how to code that<br>as every style might use differents ways to combine refs.<br><br>Gerd<br><br><hr><br>Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecarver@gmail.com><br>Gesendet: Mittwoch, 4. April 2018 12:46:44<br>An: Development list for mkgmap<br>Betreff: Re: [mkgmap-dev] overlapping highways and route restrictions<br><br>okay that's fine. I think the result will lead to nearly no more actual problem cases...<br><br>On 4 April 2018 at 12:44, Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>> wrote:<br>Hi Felix,<br><br>you may try r4147. I plan to add code to merge different labels of overlapping ways, I think I can't do much more.<br><br>Gerd<br><br><hr><br>Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com>><br>Gesendet: Mittwoch, 4. April 2018 11:44:05<br>An: Development list for mkgmap<br>Betreff: Re: [mkgmap-dev] overlapping highways and route restrictions<br><br>Yes I think that could be problematic. I'm not sure how it will end up. I do not create routable lines from the relations file directly, I use the set command and then in the lines file the additional ways are created - so that if one line has 1 or X route relations, there will be no difference. However that assumes they are all added to the same line I guess. So if different routes are copied onto different overlapping ways this principle would go wrong - it won't be a problem if the underlying overlaying ways are moved/merged before the handling of the relations however.<br><br>I have so far seen mostly cases where two overlaying ways were both part of the same route relation - not of different route relations.<br><br>On 4 April 2018 at 11:10, Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com><mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>>> wrote:<br>Hi Felix,<br><br>well, you started to mention route relations:<br>"The case of overlapping ways being part of different route relations on the other hand I've seen quite often - in that case I think it's best to just add all route relations to one way, and remove the other one."<br>My understanding is that the code in mkgmap doesn't have to care about route relations (e.g. type=route, route=bicycle), this is done in the style. With your style those might cause more trouble because you add more routable lines for the members but the current overlap remover will only remove segments with more or less identical attributes.<br>What you suggest requires a completely different approach, right?<br><br>Gerd<br><br><hr><br>Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>>> im Auftrag von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com><mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>>><br>Gesendet: Mittwoch, 4. April 2018 10:58:43<br>An: Development list for mkgmap<br>Betreff: Re: [mkgmap-dev] overlapping highways and route restrictions<br><br>yes I know - but even though both ways you linked have different turn restriction ID - the content of the turn restriction is identical (only straight on).<br><br>On 4 April 2018 at 10:54, Gerd Petermann <gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com><mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>><mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com><mailto:gpetermann_muenchen@hotmail.com<mailto:gpetermann_muenchen@hotmail.com>>>> wrote:<br>Hi Felix,<br><br>yes, 1) would handle the case in my example.<br>Just to make sure: I meant turn restrictions, not route relations.<br><br>Gerd<br><br><hr><br>Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk><mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>>>> im Auftrag von Felix Hartmann <extremecarver@gmail.com<mailto:extremecarver@gmail.com><mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>><mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com><mailto:extremecarver@gmail.com<mailto:extremecarver@gmail.com>>>><br>Gesendet: Mittwoch, 4. April 2018 10:48:20<br>An: Development list for mkgmap<br>Betreff: Re: [mkgmap-dev] overlapping highways and route restrictions<br><br>For my maps 1) is enough - and warning not even needed. I think it's hard to find out what the outcome should be.<br>The case of overlapping ways being part of different route relations on the other hand I've seen quite often - in that case I think it's best to just add all route relations to one way, and remove the other one.<br><br>The example you found here - I think is quite possible to solve - both restriction relations are identical - so one way including the restriction relation can be removed, the route relations copied over. If the restriction is having different rules - then however I don't think we can solve it correctly (well an exception is if we have overlapping ways in OSM which are oneway and opposite to each other - this is a rare case where overlapping ways are not to be removed I guess).<br><br><br><br>On 4 April 2018 at 10:39, Gerd Petermann <GPetermann_muenchen@hotmail.com<mailto:GPetermann_muenchen@hotmail.com><mailto:GPetermann_muenchen@hotmail.com<mailto:GPetermann_muenchen@hotmail.com>><mailto:GPetermann_muenchen@hotmail.com<mailto:GPetermann_muenchen@hotmail.com><mailto:GPetermann_muenchen@hotmail.com<mailto:GPetermann_muenchen@hotmail.com>>><mailto:GPetermann_muenchen@hotmail.com<mailto:GPetermann_muenchen@hotmail.com><mailto:GPetermann_muenchen@hotmail.com<mailto:GPetermann_muenchen@hotmail.com>><mailto:GPetermann_muenchen@hotmail.com<mailto:GPetermann_muenchen@hotmail.com><mailto:GPetermann_muenchen@hotmail.com<mailto:GPetermann_muenchen@hotmail.com>>>>> wrote:<br>Hi all,<br><br>please help, I just try to make up my mind what mkgmap should do when it finds overlapping road segments and<br>one (or both) of the overlaps is a part of a (valid) restriction relation. This doesn't happen very often, but it is possible.<br><br>The attached example contains these two overlapping ways, and both are members of (different) restriction relations:<br><a href="https://www.openstreetmap.org/way/48218016">https://www.openstreetmap.org/way/48218016</a><br><a href="https://www.openstreetmap.org/way/48218008">https://www.openstreetmap.org/way/48218008</a><br><br>(I did not try what the trunk version produces for this mess)<br><br>I see different possibilities:<br>1) ignore route restrictions when removing overlaps, remove those which are invalid after overlapping segments were removed and log a warning<br>2) ignore overlaps when the ways are members of restriction relations<br>3) complex: remove overlaps but try to "repair" the restriction<br><br>I am currently trying to implement 3) but it looks too complicated for such a rare case and in the end we have a clear case of wrong input data here.<br>What do you think?<br><br>Gerd<br><br><br><hr><br>mkgmap-dev mailing list<br>mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>>><br><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br><br><br><br>--<br>Felix Hartman - <a href="http://Openmtbmap.org">Openmtbmap.org</a> & <a href="http://VeloMap.org">VeloMap.org</a><br>Schusterbergweg 32/8<br>6020 Innsbruck<br>Austria - Österreich<br><hr><br>mkgmap-dev mailing list<br>mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>><br><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br><br><br><br>--<br>Felix Hartman - <a href="http://Openmtbmap.org">Openmtbmap.org</a> & <a href="http://VeloMap.org">VeloMap.org</a><br>Schusterbergweg 32/8<br>6020 Innsbruck<br>Austria - Österreich<br><hr><br>mkgmap-dev mailing list<br>mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>><br><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br><br><br><br>--<br>Felix Hartman - <a href="http://Openmtbmap.org">Openmtbmap.org</a> & <a href="http://VeloMap.org">VeloMap.org</a><br>Schusterbergweg 32/8<br>6020 Innsbruck<br>Austria - Österreich<br><hr><br>mkgmap-dev mailing list<br>mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><br><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br><br><br><br>--<br>Felix Hartman - <a href="http://Openmtbmap.org">Openmtbmap.org</a> & <a href="http://VeloMap.org">VeloMap.org</a><br>Schusterbergweg 32/8<br>6020 Innsbruck<br>Austria - Österreich<br><hr><br>mkgmap-dev mailing list<br>mkgmap-dev@lists.mkgmap.org.uk<br><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br><br></pre></blockquote></div></body></html>