#7405 closed defect (fixed)
TIGER tags changed unnecessarily with Combine Way and Replace Geometry
Reported by: | rickmastfan67 | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: | joshdoe |
Description
I've just started noticing this while cleaning up some Tiger imported ways here in the USA. Sometimes when nodes that aren't needed in the beginning of the way are moved to a different place in the way to keep them, one of the tags on the way gets changed without warning. The tag in question is "tiger:tlid".
I've created a test file that shows this in action (will be attached below). Hopefully, nobody edits this way till you can test this it because it requires the History of the way not to be altered after I created the file.
Here's the ways to use the file to duplicate this problem (once you open the file):
- Select the blank way and the "Hamilton Rd" way that parallels it.
- Once you have both selected, do the "Replace Geometry" action.
- Once that has been completed, pull up the history (Ctrl+H - hopefully no shortcut conflict on your end) on "Hamilton Rd".
Once you've done that, notice on the history window that the "tiger:tlid" tag has been changed without any warning.
Have no idea why in the first place it's getting changed. This is only happening when a node gets moved later in the line. If all the nodes stay in the same place, the "tiger:tlid" tag doesn't get changed at all when using the "Replace Geometry".
Attachments (1)
Change History (6)
by , 13 years ago
Attachment: | ticket7405.osm added |
---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Cc: | added |
---|
comment:3 by , 13 years ago
Component: | Plugin utilsplugin2 → Core |
---|---|
Priority: | normal → minor |
Summary: | Replace Geometry changing some tags without warning → TIGER tags changed unnecessarily with Combine Way and Replace Geometry |
I believe this to actually be a problem in core, specifically TigerUtils.combineTags. Note the same issue occurs if you combine a new untagged way with this same road. The tlid values are the same, the order is just changed. The order is changed because a Set is used, which doesn't guarantee an order, but guarantees there won't be any duplicates (which is why a Set is used in the first place). I believe a simple fix would be to only combine tags if there's more than one value.
Thankfully this problem isn't serious, it just adds to the noise of a changeset. It's worth fixing however.
Whoops, forgot the build info: