I don't have enough insight to the file format but this could well be
the case.
Could you explain in a few words, how it works?
The NOD section is like you describe it.
The point about the different levels being linked is in the NET
section. Here is a a single road in NET:
Hello Steve,
I'm the origin writer of the mergeline code. It was a try to improve the
effectiveness of the dp filter. When a nearly straight way consists of
severeal short pieces, dp filter could not do much. If the segments are
combined beforehand, dp filter could work much better and combine
Hi Johann
I'm the origin writer of the mergeline code. It was a try to improve the
I will be very happy if you can set the call of the filter at the
correct place. Feel free to do it, I don't have the time nor a running
IDE at the moment.
OK If I can see a good way to do it, I will.
Yes
Currently the --merge-lines works in all resolutions. However in
resolution 24 and 22 there is not much speed improvement on the GPS, but
it's quite annoying that the information pop up on hoover shows in the
wrong place.
I can vaguely remember seeing a similar effect a year ago. I
Here is a screenshot from Mapsource, where you can see the problem
(pop up is around 900m off - that's out of the screen on the GPS in
most zoom levels):
(the pop up should be right besides the hand symbol)
On 01.11.2010 09:27, Johann Gail wrote:
One more problem, you cannot route onto those broken roads, as the
routing will go to the place the popup is at. That means any
merged-line, cannot be choosen as a destination for autorouting (or
said, you cannot decide where on the road you'll end up).
See
Just for reference. I found the old thread:
http://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg03680.html
So if there is no way to correct it right (merge-lines before routing
layer for resolution 24) - then I would support dropping merge-lines for
resolution 24 and 22 by default
Just for reference. I found the old thread:
http://www.mail-archive.com/mkgmap-dev@lists.mkgmap.org.uk/msg03680.html
Thanks for searching the old thread. It is true, now I can remember too.
The problem was (and I think is) that the routing tables are generated
before the merging. So the
Hi
It currently works at all resolutions. However at 24 and 22 I could not
Well all I can say is that the code is only called for
resolutions less than 24:
if (mergeLines res 24) {
LineMergeFilter merger = new LineMergeFilter();
lines =
On 01.11.2010 23:28, Steve Ratcliffe wrote:
Hi
It currently works at all resolutions. However at 24 and 22 I could not
Well all I can say is that the code is only called for
resolutions less than 24:
if (mergeLines res 24) {
LineMergeFilter merger = new
Which file is this in? If so would changing this to
if (mergeLines res 22) {
LineMergeFilter merger = new LineMergeFilter();
lines = merger.merge(lines);
}
work out for me? Or do I run into problems on further lines? (I do think
Yes that should be
On 02.11.2010 00:28, Steve Ratcliffe wrote:
Which file is this in? If so would changing this to
if (mergeLinesres22) {
LineMergeFilter merger = new LineMergeFilter();
lines = merger.merge(lines);
}
work out for me? Or do I run into problems on
Currently the --merge-lines works in all resolutions. However in
resolution 24 and 22 there is not much speed improvement on the GPS, but
it's quite annoying that the information pop up on hoover shows in the
wrong place. It would be great if one could specify the first resolution
from which
On 31/10/10 07:33, Felix Hartmann wrote:
Currently the --merge-lines works in all resolutions. However in
resolution 24 and 22 there is not much speed improvement on the GPS, but
It works at resolutions less than 24.
So it would be expected that it makes no difference at resolution 24.
it's
14 matches
Mail list logo
