I just traced a kilometer (or less) of features - houses and alignments for a village, using the EDS3377 projection. Doing validation (or upload) will basically hang the process. It always stop early at checking crossing ways. In konsole, I can see that java is using all the allocated memory. I have let the process run but it never finishes, prompting a kill command to stop it. This is unexpected since I have done much bigger edits than this without any problems at all. Here is what I’ve tried:
tried three different josm versions; 17833,17702 & 17428
deleted every layer except the data layer before validate/upload
I’m guessing, a bug in JOSM that’s triggered by something in your data. I’d be sure to save a copy of your layer-that-won’t-upload (if you haven’t already), as I think a JOSM developer might be very interested in it.
Hopefully a JOSM developer is reading this. I know there’s a bug tracker somewhere…
JOSM makes it really easy to report a bug, see Help → Report Bug. Attach the info that you posted here. I assume the projection is a problem for the spatial index that is used in Crossing Ways test.
A workaround in such situations is to disable the test to be able to upload.
Now thinking about it, this is my second edit of the area. It uploaded the first time for edits in an adjacent area using same projection.
Today, I disabled self crossing check and ways crossing check, and sets projection to mercator and upload works this time. Although, honestly, I think it will also upload using different projection as long as I skip the ways crossing check.
I’ll do another edit and try again with non-default projection and without ways crossing check. After that we’ll see if there’s actually a bug somewhere.
)
I know there’s a bug tracker somewhere…