<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
(Warning: long and difficult subject matter ahead! :-) )<br>
<br>
I love to work with JOSM, but I have two problems with JOSM.<br>
<br>
- When you start drawing a way somewhere in a node, JOSM always assumes
you want to continue some way already present. <br>
This is very annoying and unproductive, because this is nearly always
not what you wanted or intended.<br>
<br>
- When you split a way, the old id (and by consequence its history) are
always in the first part, and the second part gets a new id.<br>
This way the history and id can be left by the smallest part. It should
always assigned to the biggest part.<br>
<br>
Togheter this combination defeats totally the wiki nature of OSM by
disguising the history of one road to some totally unrelated road in
the neighbourhood, also making changes to roads the user never intended
to edit.<br>
An example is in changeset <br>
<a class="moz-txt-link-freetext" href="http://www.openstreetmap.org/browse/changeset/7203063">http://www.openstreetmap.org/browse/changeset/7203063</a><br>
First there was the Verstrekenstraat.<br>
<a class="moz-txt-link-freetext" href="http://www.openstreetmap.org/browse/way/98440181">http://www.openstreetmap.org/browse/way/98440181</a><br>
When the user TAA tried to add a track, <br>
<a class="moz-txt-link-freetext" href="http://www.openstreetmap.org/browse/way/82861117">http://www.openstreetmap.org/browse/way/82861117</a><br>
from this crossing<br>
<a class="moz-txt-link-freetext" href="http://www.openstreetmap.org/browse/node/298362740">http://www.openstreetmap.org/browse/node/298362740</a><br>
JOSM maked this as a continuation of the Verstrekenstraat<br>
It was then splitted and adapted to track by the user who didn't want
this long Verstrekenstraat.<br>
But as this road had the node, where the drawing took place, as
starting node, the track end became the new starting node of the
resulting way and got after the split the id of the Verstrekenstraat.<br>
After the split, (because the user wanted to add a track and not make a
long Verstrekenstraat), JOSM moved the existing id (and history) to the
new drawn track and maked a new road out of the already existing
Verstrekenstraat by giving it a 0 id. In the history of the track , you
see the original way of the Verstrekenstraat.<br>
<a class="moz-txt-link-freetext" href="http://www.openstreetmap.org/browse/way/82861117/history">http://www.openstreetmap.org/browse/way/82861117/history</a><br>
<br>
An example of a node to test this unwanted behaviour is:
<a class="ext-link"
href="http://www.openstreetmap.org/browse/node/803205990"><span
class="icon"> </span>http://www.openstreetmap.org/browse/node/803205990</a>
Suppose you want to add a track into the wood as a dead end.
You select the node and then clicks the way drawing tool.
Do a click in the wood (direction SE) and then escape to end drawing
the segment and then you end up with an extended path of Voetweg 48.
<br>
Oh no, I wanted to add a track! Why is it not a blank road?
<br>
Oh, never mind, we split the result at the starting node and change
properties of the new added part, which has now inherited the id and
history of Voetweg 48. And on top of that the original Voetweg 48 will
get id 0 and be presented from now on in the database as a new way
created by you, while you even had no intention to modify it in the
first place!!
<br>
BTW, also relations are inherited, making tails on it after the split.<br>
I find this behaviour totally undesiable!<br>
<br>
Another example to what mess this can lead is the Jachtdreef in
Jezus-Eik (it still needs correction)<br>
<a class="ext-link"
href="http://www.openstreetmap.org/browse/way/51768961/history">http://www.openstreetmap.org/browse/way/51768961/history</a>
<br>
<a class="ext-link"
href="http://www.openstreetmap.org/browse/way/108859153/history"><span
class="icon"></span>http://www.openstreetmap.org/browse/way/108859153/history</a><br>
<a class="ext-link"
href="http://www.openstreetmap.org/browse/way/97836493/history">http://www.openstreetmap.org/browse/way/97836493/history</a><br>
<br>
Conclusion:<br>
- JOSM should only make continuations of ways on request by the user,
eg by selecting them together with the ending node to draw from.<br>
- For the sake of history, JOSM should give the existing id to the
largest part of the road of a split and not defaulting to the first
part.<br>
<br>
As stopgap for the second point, I try to do a reverse of the road
before and after the split, when I notice that the first part is very
small..<br>
<br>
What do you think?<br>
<br>
I opened a ticket for this, at JOSM, but it seems a 'feature' and not a
bug and the developer won't fix.<br>
<a class="moz-txt-link-freetext" href="http://josm.openstreetmap.de/ticket/6567">http://josm.openstreetmap.de/ticket/6567</a><br>
Comments invited!<br>
<br>
Regards,<br>
Gerard.<br>
</body>
</html>