I'm trying to enhance an old import which created single houses as two building=yes ways:
I'm trying to convert both ways to building:part=yes, and draw a new path around them to hold the building=yes. Using JOSM here what I can do:
It works well but It's way to long to cover the whole city :P Is there a better/faster/less error prone way? asked 01 Apr '19, 22:15 mdk |
Instead of individually merging the nodes, you can use JOSM's validator. It shows error messages for duplicate building nodes, and can automatically fix them. When you select the heading in the JOSM validator panel (where it describes the kind of error) rather than one of the individual errors listed below it, clicking the Fix button will merge them all at once. That's quite nice already when used for a single building's nodes, but it can really save time if you do it only once at the end of your editing session. However, you must make sure that you do not "fix" anything except the building outlines you've just added! Luckily, the validator runs only on the currently selected elements when clicking the Validation button. To select only the ways you've created or re-tagged in the current session, you can open JOSM's search (Ctrl-F) and enter the search string Additional ideas:
answered 02 Apr '19, 16:57 Tordanik |
Maybe "Follow Line" is nicer? It still won't be great, but you start a line with it by clicking 2 existing nodes in order and then each time you press "F" it adds the next node, pausing for instruction on shared nodes. So you can create the outer way with ~3 clicks (2 to start it and 1 to continue it) and 2 presses of "F". No cut and paste, no merging, etc. answered 02 Apr '19, 03:35 maxerickson That's right, it's a bit better (it avoid merging which takes time).
(02 Apr '19, 08:40)
mdk
|
Side note: If you know that a particular use of
wall=no
describes a roof (rather than e.g. a balcony or shed), consider usingbuilding:part=roof
for it. Becausewall=no
has been used for so many different things in the import, it's hard to make use of.