Hi all,
please help, I just try to make up my mind what mkgmap should do when it finds
overlapping road segments and
one (or both) of the overlaps is a part of a (valid) restriction relation.
This doesn't happen very often, but it is possible.
The attached example contains these two overlappin
For my maps 1) is enough - and warning not even needed. I think it's hard
to find out what the outcome should be.
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,
Hi Felix,
yes, 1) would handle the case in my example.
Just to make sure: I meant turn restrictions, not route relations.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Mittwoch, 4. April 2018 10:48:20
An: Development list for mkgmap
Betr
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).
On 4 April 2018 at 10:54, Gerd Petermann
wrote:
> Hi Felix,
>
> yes, 1) would handle the case in my example.
> Just to make sure: I meant tu
Hi Felix,
well, you started to mention route relations:
"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."
My understanding is that t
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.
Ho
Hi Gerd,
I would ignore them and write a warning/info.
Of course mkgmap could try to handle it, but I don't think it's worth. Better
fix it in the data,which anyway needs to be done.
Henning
On 4 Apr 2018, 17:11, at 17:11, Gerd Petermann
wrote:
>Hi Felix,
>
>well, you started to mention route
Hi Felix,
you may try r4147. I plan to add code to merge different labels of overlapping
ways, I think I can't do much more.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Mittwoch, 4. April 2018 11:44:05
An: Development list for mkgmap
okay that's fine. I think the result will lead to nearly no more actual
problem cases...
On 4 April 2018 at 12:44, Gerd Petermann
wrote:
> Hi Felix,
>
> you may try r4147. I plan to add code to merge different labels of
> overlapping ways, I think I can't do much more.
>
> Gerd
>
> _
Hi Felix,
Maybe we have different ideas what merging of labels means.
With r4149 I've implemented this:
If way w1 has e.g. mkgmap:label:1 = "Main Street" and mkgmap:label:2 = "N 232"
(a ref)
and way w2 has only mkgmap:label:1 = "Main Street" mkgmap adds mkgmap:label:2
from the first way.
Also i
It seems to be more easy to promote OSM Inspector and fix those faults... 😎
Henning
On 4 Apr 2018, 21:55, at 21:55, Gerd Petermann
wrote:
>Hi Felix,
>
>Maybe we have different ideas what merging of labels means.
>With r4149 I've implemented this:
>If way w1 has e.g. mkgmap:label:1 = "Main Street
Hi Henning,
yes, it is quite astonishing that some of these errors exists since years, esp.
in well mapped areas.
I tried to find the source code for OSM Inspector but it seems this is closed
source owned by Geofabrik?
Gerd
Von: mkgmap-dev im Auftrag v
12 matches
Mail list logo
