#8251 closed defect (fixed)
User names that have changed
Reported by: | aliponte | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 16.08 |
Component: | Core | Version: | tested |
Keywords: | Cc: | aliponte |
Description
JOSM gets confused, if a user changes his name. Suppose you stored an osm file containing a certain node which was last edited by user "ABC". Some time later you load this file again, but in the meantime this user changed his name to "DEF". If you activate the version protocoll of the node mentioned above, then you'll find user=DEF/ABC. JOSM seems to concatenate the old and new name. Crucial is, what JOSM does when you store this osm file again. You'll find the code user='DEF/ABC' being stored. If you load this file, activate the version protocoll and save this file repeatedly, the user name being stored in the osm file gets longer and longer. Why does JOSM care about the old user name? Why doesn't it just write user='DEF' into its updated osm file version?
As an example I attached a short osm file which is showing what I tried to describe.
Attachments (1)
Change History (6)
by , 12 years ago
Attachment: | gerzap.osm added |
---|
comment:1 by , 12 years ago
comment:2 by , 10 years ago
Another issue with JOSM's handling of users with changed name is when you want to work with the link to the users page at OSM – e.g. from the history window. JOSM gives an URL with https://www.openstreetmap.org/user/Old_name%2FNew_name.
You test the behaviour here here: https://www.openstreetmap.org/node/2117833492
comment:3 by , 10 years ago
The DEF/ABC
originates from org.openstreetmap.josm.data.osm.User#getName
. The question is which username to take for writing the XML file. The names in the User
data structure are unordered.
comment:5 by , 8 years ago
Milestone: | → 16.08 |
---|
Replying to aliponte:
So far it works as intended: JOSM is aware of multiple names for the same user id and concatenates them for display.
That's a bug.