Opened 9 years ago
Closed 9 years ago
#13911 closed enhancement (duplicate)
Can't replace geometry
Reported by: | naoliv | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin utilsplugin2 | Version: | |
Keywords: | replace geometry | Cc: |
Description
Open the attached file. Both areas are present in OSM.
I want to replace the right one by the left one (keep the geometry of the right side with the nodes, way and history from the left).
Select the left area, Shift
, click the right area, Ctrl+Shift+G
and see Please select one way that exists in the database and one new way with the correct geometry
It's not the first time that Replace Geometry can't replace one way by the other.
From what I see, there is no problem in the data and Replace Geometry should just replace them.
Or if there is some kind of error or unmet condition, could we have a better and more descriptive message?
JOSM:
URL:http://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2016-11-01 23:23:54 +0100 (Tue, 01 Nov 2016) Build-Date:2016-11-02 02:32:44 Revision:11209 Relative:URL: ^/trunk Identification: JOSM/1.5 (11209 pt_BR) Linux Debian GNU/Linux testing (stretch) Memory Usage: 393 MB / 10206 MB (129 MB allocated, but free) Java version: 1.8.0_111-8u111-b14-2-b14, Oracle Corporation, OpenJDK 64-Bit Server VM Screen: :0.0 1600x900, :0.1 1280x1024 Maximum Screen Size: 1600x1024 Java package: openjdk-8-jre:amd64-8u111-b14-2 Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-9 VM arguments: [-Dawt.useSystemAAFontSettings=on] Dataset consistency test: No problems found Plugins: + Create_grid_of_ways (32699) + FastDraw (32938) + ImportImagePlugin (32699) + OpeningHoursEditor (32699) + PicLayer (32796) + RoadSigns (32796) + SimplifyArea (32796) + apache-commons (32699) + buildings_tools (32944) + conflation (0.3.0) + contourmerge (1030) + download_along (32946) + editgpx (32699) + ejml (32680) + geojson (43) + geotools (33042) + importvec (32699) + indoorhelper (32680) + jts (32699) + log4j (32699) + measurement (32936) + merge-overlap (32699) + opendata (33040) + pbf (32865) + pdfimport (32796) + poly (32699) + reverter (32796) + scripting (30761) + tageditor (33021) + todo (30000) + turnlanes (32796) + turnlanes-tagging (252) + turnrestrictions (32796) + undelete (32699) + utilsplugin2 (32815)
Attachments (1)
Change History (7)
by , 9 years ago
Attachment: | cant-replace.osm added |
---|
comment:1 by , 9 years ago
comment:2 by , 9 years ago
I use it with new objects too.
But shouldn't it always replace, no matter if the object is new or not?
In this example we have 2 duplicated areas. One older, with a wrong perimeter, and one new, with a more correct tracing.
I would like to keep the older way + the new perimeter.
comment:3 by , 9 years ago
I think the problem with two existing ways is that JOSM doesn't know which one you want to keep.
I guess you can still get what you want when you create a copy of the existing way that should be replaced,
delete that way, paste at original position and then use replace geometry.
comment:4 by , 9 years ago
And I always though that the order was important here (first select the one that will be replaced and then select the one that will replace the object) :-/
comment:6 by , 9 years ago
Keywords: | replace geometry added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Type: | defect → enhancement |
Closed as duplicate of #9942.
I've always used "replace geometry" is used like this:
Draw a new line which better describes the wanted geometry. Then replace the existing (bad) way with this new way, so that the
new way has the history of the replaced one.