Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Too easy to miss the right node #1153

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments
Closed

Too easy to miss the right node #1153

openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments

Comments

@openstreetmap-trac
Copy link

Reporter: ColinMarquardt
[Submitted to the original trac issue database at 1.53pm, Sunday, 7th September 2008]

On the German mailing list, someone mentioned that it seemed to him that Merkaartor was producing more unconnected ways than other editors.

I can imagine this being the case, since if you have a GPX track loaded, it's very easy to hit a GPX node instead of a node belonging to a drawn way (which would then connect a new way to an existing way).

There are several options how we could improve that: let the GPX track have a much lower snapping distance, i.e. don't let the GPX nodes be as magnetic as a drawn node. Another way could be to color connected nodes of a way differently (possibly only of selected ways if it gets too much visually). The most intrusive way would be an option to have the GPX layer unclickable at all.

There are probably even more possible solutions I don't think of now...

@openstreetmap-trac
Copy link
Author

Author: borisc
[Added to the original trac issue at 8.56am, Wednesday, 10th September 2008]

Replying to [ticket:1153 ColinMarquardt]:

The most intrusive way would be an option to have the GPX layer unclickable at all.

To my opinion, track layers should be uneditable by default, however there should be a switch to make them editable (e.g. right click in the layer dock, or a toggle icon in the layer dock)

@openstreetmap-trac
Copy link
Author

Author: LonelyPixel
[Added to the original trac issue at 3.43pm, Saturday, 3rd January 2009]

What do we need GPX nodes for at all? Is there some use for them to be nodes? Visible and with interaction? To me, the line between those points is totally enough to know.

If you make the track layer unclickable, don't forget the photos that are inserted on that layer. This is another problem right now: You cannot select a photo if there's ~ 20 GPX nodes right at the same place, because you made one point per second and remained there for awhile to get a more precise position, or to take that photo, etc.

@openstreetmap-trac
Copy link
Author

Author: ColinMarquardt
[Added to the original trac issue at 8.19pm, Sunday, 4th January 2009]

I actually like seeing the nodes, because it reminds me of my traveling speed at that point. I go like "Oh, that thick node cluster is where you changed the tire tube, and there is that steep incline following... wait, wasn't there a bench right at the corner? Ok, put it on the map". So these nodes are not completely useless to me.

@openstreetmap-trac
Copy link
Author

Author: ColinMarquardt
[Added to the original trac issue at 9.21pm, Sunday, 4th January 2009]

Replying to [comment:2 LonelyPixel]:

What do we need GPX nodes for at all? Is there some use for them to be nodes? Visible and with interaction? To me, the line between those points is totally enough to know.

If you make the track layer unclickable, don't forget the photos that are inserted on that layer. This is another problem right now: You cannot select a photo if there's ~ 20 GPX nodes right at the same place, because you made one point per second and remained there for awhile to get a more precise position, or to take that photo, etc.

I now see that you have a patch making GPX nodes unclickable - assuming photos are unaffected, great :)

@openstreetmap-trac
Copy link
Author

Author: koying
[Added to the original trac issue at 1.39pm, Monday, 16th February 2009]

Solved by read-only layers, isn'it...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant