Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#961 closed enhancement (fixed)

Add a preference to disable display of connections between track points (was: Raw GPS nodes are connected when they shouldn't)

Reported by: dantje Owned by: bvh-osm@…
Priority: minor Milestone:
Component: merkaartor Version:
Keywords: Cc:

Description

When also downloading the raw tracks from the server, it seems as if nodes that don't belong to one track still are connected and are shown as one way.

This leads to many connections that criss-cross the area.

Change History (7)

comment:1 Changed 11 years ago by Shaun McDonald

This is down to the way that the points are downloaded, and the fact that there is no way to be able to tell from the API where one track stops and the next starts.

Is there an option in your app to not draw lines between the points?

comment:2 Changed 11 years ago by dantje

Would it be sensible to assume that those points that are located on the bounding box are endpoints of their respective tracks?

comment:3 Changed 11 years ago by Shaun McDonald

That will reduce the problem, but won't work for tracks that stop or start in the middle of the bbox.

comment:4 Changed 11 years ago by Chris Browet

Summary: Raw GPS nodes are connected when they shouldn'tAdd a preference to disable display of connections between track points (was: Raw GPS nodes are connected when they shouldn't)
Type: defectenhancement

comment:5 Changed 11 years ago by dantje

This preference could be the maximum length that will be drawn: 0m for no connections at all, 100m for connections between node that are closer than 100m.

comment:6 Changed 11 years ago by Chris Browet

Resolution: fixed
Status: newclosed

I implemented the on/off switch of displaying track segments for now. If someone feels dantje solution should be implemented, please reopen.

comment:7 Changed 11 years ago by dantje

I commited a patch (r11030) that uses a fixed threshold of 100m.

Note: See TracTickets for help on using tickets.