> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Montag, 17. Mai 2021 21:49
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] 4179
>
> yes, but I am not sure which version got the the left right mixed up. I
> think that was the one that en
invisible?
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Montag, 17. Mai 2021 21:49
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] 4179
yes, but I am not sure which version got the the left right mixed up. I think
that was the one tha
Gerd
>
>
> Von: mkgmap-dev mkgmap-dev-boun...@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann <
> extremecar...@gmail.com<mailto:extremecar...@gmail.com>>
> Gesendet: Montag, 17. Mai 2021 19:38
> An: Developmen
list for mkgmap
Betreff: Re: [mkgmap-dev] 4179
Some versions of mkgmap seemed to have created maps where this became a bit
random. So sometimes (but rarely) the reversible mtb and hiking routes ended up
on the same side of the road
On Tue, 18 May 2021 at 02:08, Felix Hartmann
mailto:extremecar
ot be reversed) you
>> have to mark it as such.
>> There is no longer any automatism which tries to guess what you want.
>>
>> Gerd
>>
>>
>> Von: mkgmap-dev im Auftrag von
>> Felix Hartmann
>> Ges
here is no longer any automatism which tries to guess what you want.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Montag, 17. Mai 2021 19:38
> An: Development list for mkgmap
> Betreff: Re: [mk
. Mai 2021 19:38
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] 4179
Oh yeah - what may not happen is the following hypothetical example
1. route=mtb (set line) (can be merged and reversed)
2. highway=x (set road - is not reversed merged - maybe because of oneway tag)
3. route=hiking (set
Oh yeah - what may not happen is the following hypothetical example
1. route=mtb (set line) (can be merged and reversed)
2. highway=x (set road - is not reversed merged - maybe because of oneway
tag)
3. route=hiking (set line - however because the 2. highway was not
reversed, while the 1 route
I meant if there is a line created with continue - and that line is on
the --line-types-with-direction
list, the other copies of that line Or roads should be merged too. And I
think roads should be reversed and merged as much as possible to - also at
resolution 24 if not oneway-1 or on the
Hi Felix,
then what about proposed:
> For line--types-with-direction it would be best to give a resolution
> limit for each type, so if resolution is lower than associated lines
> can be reversed.
Does it means, that you accept wrong direction at lower resolution?
--
Best regards,
Andrzej
ads.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Montag, 17. Mai 2021 18:33
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] 4179
I think Gerd said that now those underlying roads/lines are merged for level 1
and higher. He said to merge them unt
I think Gerd said that now those underlying roads/lines are merged for
level 1 and higher. He said to merge them until someone complains. Merging
as in reversing their direction so longer segments can be merged. All roads
that can be merged without changing direction are merged anyhow.
Hi Felix!
> If the main road is merged but the direction dependant road not - then
> at lower resolutions the DP filter will create a mess
But direction dependent road are merged, aren't they?
> And because I have lots of overview - E.g. oneway arrows, oneway
> streets are loads, there is
The case was that many of those roads are created by continue. If the main
road is merged but the direction dependant road not - then at lower
resolutions the DP filter will create a mess. This is only relevant for 21
or lower I feel. 22-24 it's all right. Most overlays will be right in that
Hi Felix,
why don't make it simple?
Routable roads with oneway=-1 have to be reversed.
Non-routable lines with oneway=-1 have to be reversed if has-direction
is present.
If has-direction is present, road is not reversible for merging at all
layers.
I don't understand your suggestion for
__
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Montag, 17. Mai 2021 08:09
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] 4179
>
> This in referring the the commit message. I think mkgmap in that case
> simply sh
for oneway=-1 reg. left/right? Those lines clearly have a
direction, don't they?
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Montag, 17. Mai 2021 08:09
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] 4179
This in referring
d
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Montag, 17. Mai 2021 04:52
> An: Development list for mkgmap
> Betreff: [mkgmap-dev] 4179
>
> Hi Gerd
>
> oneway tag no longer influences the direction
eversed again.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Montag, 17. Mai 2021 04:52
An: Development list for mkgmap
Betreff: [mkgmap-dev] 4179
Hi Gerd
oneway tag no longer influences the direction flag of non-routable lines. Note
that oneway=-1 still me
Hi Gerd
oneway tag no longer influences the direction flag of non-routable lines.
Note that oneway=-1 still means line is reversed and oneway=yes is set.
I think this is only needed if the linetype is listed
under --line-types-with-direction
If not listed here nor routable oneway=-1 is as
20 matches
Mail list logo
