OpenStreetMap
JOSM+Terracer Now Almost Unusable for Relation Creation
Posted by alexkemp on 6 June 2016 in English. Last updated on 7 June 2016.- March 2016: I begin using JOSM + Terracer
- March 2016: my first bug-report
Leaving “keep outline way” NOT selected + associatedStreet relation IS selected causes an exception when ‘OK’ is pressed
(the developers have more important matters to attend to than Terracer) - April 2016 - May 2016: (after each JOSM update, another bug-report)
Leaving “keep outline way” NOT selected + associatedStreet relation IS selected causes an exception when ‘OK’ is pressed
(each time, the developers have more important matters to attend to than Terracer) - 5 June 2016: Debian Jessie Updates to 8.5
(Debian updates 4 June; I update the following day) - 5 June 2016: JOSM Updates to 10327
- 5 June 2016: JOSM Plugins Update to 32158
- 5 June 2016: the ‘normal’ bug-report, with an extra twist
Leaving “keep outline way” NOT selected causes an exception when ‘OK’ is pressed.
Leaving “keep outline way” IS selected causes an exception when ‘OK’ is pressed
(essentially, terracer is almost unusable if relation is also selected )
It is important now to NOT select “keep outline way” within the Terracer dialog, as otherwise the original house is left beneath the terrace and, for some reason, it is now almost impossible to separate the two. In addition, previously the associatedStreet relation was correctly created for all houses. Now, many houses do not have it created (although the odd one does).
I find the combo of Building Tools + Terracer to be the best method for entering any house (detached, semi-detached or actual terrace) onto the map using JOSM, and the simplest to do so + create an associatedStreet relation at the same time. Now, each & every house causes a software exception.
Oh, spit.
Tuesday 7 June: After more testing, I realise that it is the fact that ‘add to associatedStreet relation’ is selected that is causing the software exception to be thrown (if not selected, no exception). As I understand it, Terracer may have had it’s version changed to match all the other Plugins, but nothing has changed within it’s coding. If accurate, that means that it is something in the interaction between JOSM & Terracer that is causing the problem.
Discussion
Comment from EdLoach on 6 June 2016 at 14:54
I’ve been using the terracer tool with latest stable release today. What do I have to do to reproduce your error? I’m about to try looking at the keep outline way option, which I always have set not to do so.
Comment from Hjart on 6 June 2016 at 17:25
Since JOSM is an open source project, entirely run by volunteers, one solution could be to find a developer near you, who could be convinced (possibly by promising a beer or two) to look into it. Hammering the existing overworked volunteers, obviously doesn’t work.
Comment from alexkemp on 6 June 2016 at 18:42
@Hjart:
“Hammering”? Am I not allowed to mention the fact if JOSM throws an exception when I use it? What strange use of language.
Comment from alexkemp on 6 June 2016 at 19:23
Hi EdLoach
This is classic use of Terracer for myself, and which results in JOSM throwing an exception when ‘OK’ is clicked:—
(I have used Terracer to produce both detached, semi-detached + actual terraces of houses successfully in the past; all of those produce software-exceptions now)
My setup is Linux Debian 8.5; Linux 3.16.0-4-amd64
(correction:— Debian updated 4 June, but I updated my system on 5 June)