> I think it is correct to not merge them, but maybe we should ignore
> oneway=* for non-routable lines?
>
> Gerd
>
>
>
> Von: Gerd Petermann
> Gesendet: Freitag, 14. Mai 2021 09:59
> An: Development list for mkgmap
> Betreff
I just noticed the version I uploaded from 4709 was not identical to the
one I once created with I think 4709. However I do not know what I had done
for that time. I cannot identify which mkgmap version I used for creating
the smaller and better routing version - or what changes I had done (the
sty
Hi all,
reading the discussion, I think it would be good to separate 2 cases:
- routable roads with one-way attribute,
- all lines which have direction.
As for routing, I would assume, that all problems are resolved
automatically and correctly by mkgmap. Routing is only valid at level 0.
On lo
n
Gesendet: Freitag, 14. Mai 2021 09:42
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
I think it is enough with a simple list. As for why it changed for me is Imho
because those lines are mostly created with continue or continue with action
and it's really hard to se
von Felix
Hartmann
Gesendet: Freitag, 14. Mai 2021 13:33
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Maybe the second route is now with shorter distance instead of shorter time.
It's bicycle with either shorter time or distance and no avoidances at all. And
I us
Hartmann
Gesendet: Freitag, 14. Mai 2021 13:33
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Maybe the second route is now with shorter distance instead of shorter time.
It's bicycle with either shorter time or distance and no avoidances at all. And
I use the most up to
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Freitag, 14. Mai 2021 13:33
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Maybe the second route is now with shorter distance instead of shorter time.
It's bicycle with either short
an't say for sure which version is installed right now (4009 or 4011),
> but I think the difference should not be that large?
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Freitag, 14. Mai 2021 10:38
&
___
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Freitag, 14. Mai 2021 10:38
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
I never tested Mapsource, only Basecamp. Routing in Basecamp is much more
similar to modern devices.
But I jus
s best. I still feel I will always use other lines can be
> > > > reversed to be merged.
> > > >
> > > > On Fri, 14 May 2021, 15:32 Gerd Petermann <
> > > > gpetermann_muenc...@hotmail.com gpetermann_muenc...@hotmail.com>> wrote:
> > &
Mai 2021 11:02
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Routable one-way roads must have their correct direction preserved and
line-merging needs to know and respect this.
I do not think so. They must have their correct direction for level 0, but not
for level 1 (exc
> > > it
> > > > works best. I still feel I will always use other lines can be
> > > > reversed to be merged.
> > > >
> > > > On Fri, 14 May 2021, 15:32 Gerd Petermann <
> > > > gpetermann_muenc...@hotmail.com> wrote:
> > > &g
mkgmap:has-direction=true and only rely on the new option -
> > -line
> > > > -types-with-direction
> > > >
> > > > Do you see a need to have both?
> > > >
> > > > Gerd
> > > >
> > > >
erd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Freitag, 14. Mai 2021 10:20
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
please explain in more detail. Why would you add a line with a type that has a
direction to be rendered at
von Felix
Hartmann
Gesendet: Donnerstag, 13. Mai 2021 17:52
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Yes I am pretty sure. Because I just recreated the map and it is the same
again. https://openmtbmap.org/mtbaustria_4709.exe vs
https://openmtbmap.org/mtbaustria_4711
the evaluation of the special tag
> > > mkgmap:has-direction=true and only rely on the new option --line
> > > -types-with-direction
> > >
> > > Do you see a need to have both?
> > >
> > > Gerd
> > >
> > >
> >
gt;
> > Gerd
> >
> >
> > Von: mkgmap-dev im Auftrag
> > von Ticker Berkin
> > Gesendet: Freitag, 14. Mai 2021 09:22
> > An: Development list for mkgmap
> > Betreff: Re: [mkgmap-dev] Commit 4710
> >
et: Freitag, 14. Mai 2021 09:42
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
I think it is enough with a simple list. As for why it changed for me is Imho
because those lines are mostly created with continue or continue with action
and it's really hard to see what hap
eed to have both?
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Ticker Berkin
> Gesendet: Freitag, 14. Mai 2021 09:22
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Commit 4710
>
> Hi Gerd and others
>
> I'll test
: Freitag, 14. Mai 2021 09:22
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Hi Gerd and others
I'll test setting of 0x40 flag for extended and the range of standard
types on various devices over the weekend.
Is there any real need for the force/allow-reverse-merge op
the code which tries to propagate the direction flag to
> underlying roads for now. Let's see first how often this is really
> needed.
>
> Gerd
>
>
>
> ____________
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Donnerstag, 13. Mai 2021 23:36
> An: Development lis
roads for now. Let's see first how often this is really needed.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Donnerstag, 13. Mai 2021 23:36
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Hi
Various tho
Hi
Various thoughts:
The 0x40 polyLine direction flag probably has no effect on modern
Garmin devices. As Gerd says, GPSMapEdit puts an arrow on lines if it
is set. In my notes from testing all line types, I found some cases
where an eTrex put compass bearings (N/NE/E/...) on some line types
wher
Hi Gerd,
here example of lines, that shouldn't be merged:
https://www.openstreetmap.org/way/481106241
https://www.openstreetmap.org/way/481106244
https://www.openstreetmap.org/way/481106242
I have tested with mkgmap-low-res-opt-r4711 and it works correctly.
Lines are not merged with mkgmap:has-
Hi Andrzej,
yes, sure, the tag mkgmap:has-direction=true was only implemented for that.
Gerd
Von: mkgmap-dev im Auftrag von Andrzej
Popowski
Gesendet: Donnerstag, 13. Mai 2021 19:36
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Commit
Hi Gerd,
it is clear, but I was thinking about something else, about merging
lines with reversed points. If mkgmap performs that kind of merging,
there should be an option to block reversing for a particular object
type. I got impression, that mkgmap:has-direction is a flag, that can be
used.
ftrag von Andrzej
Popowski
Gesendet: Donnerstag, 13. Mai 2021 17:03
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Commit 4710
Hi Gerd,
I don't know particulars about direction flag, that is written into img.
Maybe it gives some kind of protection against drawing a line in revers
di
Hi Gerd,
I don't know particulars about direction flag, that is written into img.
Maybe it gives some kind of protection against drawing a line in revers
direction? Would be nice to test, if it were possible.
Anyway, for me problem is about reversing a line by mkgmap. I think that
attribute,
Mai 2021 14:33
An: Development list for mkgmap
Betreff: AW: [mkgmap-dev] Commit 4710
Hi Felix,
are you sure that you tested the two versions with exactly the same input? (osm
data, style, options)?
If the changes in r4710 or r4711 really cause differences in routing quality
there must be an erro
where routing differs?
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Donnerstag, 13. Mai 2021 14:24
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Yes, 4711 on branch vs best version 4709 on branch. 4709 was best so
rtmann
> Gesendet: Donnerstag, 13. Mai 2021 13:16
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Commit 4710
>
> I just looked it up. It must have been 4709 with best routing for me
> (unlikely but maybe it could have been 4708), while 4711 is a bit worse
> (but
what branch it was made.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Donnerstag, 13. Mai 2021 13:16
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
I just looked it up. It must have been 4709 with best routing f
_
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Donnerstag, 13. Mai 2021 11:28
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Commit 4710
>
> Well I just got to test routing - and the current version is a degradation
>
nk.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Donnerstag, 13. Mai 2021 11:28
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Commit 4710
>
> Well I just got to test routing - and the current v
list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
Well I just got to test routing - and the current version is a degradation vs
the intermediate version from yesterday for my maps. The current version routes
better than before, but worse than the intermediate version.
As for the list - it
ution, the current handling seems too complex.
Gerd
Von: mkgmap-dev im Auftrag von Andrzej
Popowski
Gesendet: Donnerstag, 13. Mai 2021 11:10
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Commit 4710
Hi all,
I didn't know about mkgmap:has
and r4707).
>
> I'm now fixing the detection code, next I'm trying to figure out how to
> configure the details reg. direction handling.
>
> Gerd
>
>
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet:
list for mkgmap
Betreff: AW: [mkgmap-dev] Commit 4710
Hi Felix,
FYI:
I just found out that the current code to detect if the style sets
mkgmap:has-direction=true doesn't work. Seems I didn't test this :(
The change in r4710 changed only the LineMerger in the branch. Even with r4711
Hi all,
I didn't know about mkgmap:has-direction. Good to see there is
possibility to protect direction of the line. Please note, there are
lines, which aren't roads but really have directions. Some example:
- waterway=river, stream, maybe canal, ditch too,
- natural=cliff,
- man_made=embankme
reg. direction handling.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Donnerstag, 13. Mai 2021 09:52
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Commit 4710
I kinda feel by default even oneway=yes should only mean do not cha
more.
>
> The change should not affect routing at all (none of the changes in the
> low-res-opt branch should).
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Donnerstag, 13. Mai 2021 02:59
> An:
-dev im Auftrag von Felix
Hartmann
Gesendet: Donnerstag, 13. Mai 2021 02:59
An: Development list for mkgmap
Betreff: [mkgmap-dev] Commit 4710
fix error in LineMergeFilter reg. lines with direction
The line merger should not merge lines if one has the direction flag set and
the other has not.
fix error in LineMergeFilter reg. lines with direction
The line merger should not merge lines if one has the direction flag set
and the other has not. Problem exists also in trunk.
Hmm fixing this stopped all the nice size optimization. Map size got much
bigger again.
I did not find any place whe
43 matches
Mail list logo
