Changes between Initial Version and Version 1 of Ticket #20966


Ignore:
Timestamp:
2021-06-05T07:33:33+02:00 (4 years ago)
Author:
nkamapper
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #20966 – Description

    initial v1  
    1 ReplaceGeometry is refusing to merge two ways if one or more node is tagged on the existing way but not on the new way. This is often inconvenient when importing a set of new highways, because the start and end of ways often do not match. To get around the problem, the existing way must be partitioned into smaller pieces, which is meant to ensure that all tagged nodes are taken care of, but which is a very inefficient procedure during a big import.
     1ReplaceGeometry is refusing to merge two ways if one or more node is tagged on the existing way but not on the new way. This is often inconvenient when importing a set of new highways, because the start and end of ways often do not match. To get around the problem, the existing way must be partitioned into smaller pieces, which is meant to ensure that all tagged nodes are taken care of, but this is a very inefficient procedure during a big import. Often, the existing way is just deleted.
    22
    33It would be good to have a utilsplugin2 parameter which allows two ways to be merged even if there are tagged nodes. A warning could still be displayed so that the tagged nodes could be identified.