Opened 13 years ago
Closed 13 years ago
#7201 closed defect (fixed)
[Patch] combining ways screws up the order of ref tags
Reported by: | NE2 | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
If you create two ways with ref=US 1;SR 2 and combine them, the ref is changed to SR 2;US 1.
Attachments (1)
Change History (7)
comment:1 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
It's much worse. Now, when merging a node without tags with a node containing several tags (building=yes/source=Bing), the merged node contains all values for each key (building=Bing;yes/source=Bing;yes)
comment:4 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
This is happening again. Combining "US 101; CA 2" and "US 101" results in " CA 2;US 101".
by , 13 years ago
Attachment: | 7201.patch added |
---|
comment:5 by , 13 years ago
Summary: | combining ways screws up the order of ref tags → [Patch] combining ways screws up the order of ref tags |
---|
Patch attached. Retains order of multi-value values (and its spacing if possible).
To be on the safe side, I'd await the end of stabilization phase although I do not expect any problems with the patch.
In [4746/josm]: