You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: dantje [Submitted to the original trac issue database at 10.59am, Saturday, 7th June 2008]
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.
The text was updated successfully, but these errors were encountered:
Author: shaunmcdonald131[at]gmail.com [Added to the original trac issue at 3.01pm, Sunday, 8th June 2008]
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?
Author: dantje [Added to the original trac issue at 11.41am, Saturday, 26th July 2008]
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.
Reporter: dantje
[Submitted to the original trac issue database at 10.59am, Saturday, 7th June 2008]
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.
The text was updated successfully, but these errors were encountered: