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: julio.costa[at]openstreetmap.cl [Submitted to the original trac issue database at 10.36am, Wednesday, 9th March 2011]
When you press the "GPS data" button in Potlatch 2 you only get a few "pieces" (literally just a few parts of the whole trace) of the traces that you know are in that area, but when you press the G key in Potlatch 1 you get all the traces right.
The text was updated successfully, but these errors were encountered:
Author: StellanL [Added to the original trac issue at 6.20pm, Friday, 22nd April 2011]
Replying to [ticket:3572 julio.costa@]:
When you press the "GPS data" button in Potlatch 2 you only get a few "pieces" (literally just a few parts of the whole trace) of the traces that you know are in that area, but when you press the G key in Potlatch 1 you get all the traces right.
P2 seems to
Only draw those segments of a track that both start and end within the window.
Draw connecting lines between the end points of all tracks drawn.
This leads to many artifacts near the edges, especially on a road with many traces made at high speed, like a freeway.
Hopefully simple solutions:
Use a larger window when selecting "visible" segments.
Move, instead of draw, when switching between different tracks.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reporter: julio.costa[at]openstreetmap.cl
[Submitted to the original trac issue database at 10.36am, Wednesday, 9th March 2011]
When you press the "GPS data" button in Potlatch 2 you only get a few "pieces" (literally just a few parts of the whole trace) of the traces that you know are in that area, but when you press the G key in Potlatch 1 you get all the traces right.
The text was updated successfully, but these errors were encountered: