Changeset browser behaviour change about openstreetmap-website HOT 5 CLOSED

To whoever is going to fix this, please do it by sorting changesets, not by reverting to the old behaviour: it was nearly impossible to highlight a changeset that way.

from openstreetmap-website.

Is there a sort that will actually make every changeset selectable? Even if there is it seems to be that the resulting UI would be incomprehensible...

from openstreetmap-website.

Open this part of map and select "Data view" (or how's it called in English). Now try to select buildings 14 or 29. It won't work. But buildings 12 and 16 are easily selectable. That happens because objects are sorted by date. If they were sorted by size, for example, smaller areas, like buildings, would be selectable.

Now, the problem with changeset view is that there are three types of changesets:

1. Those which cover more than a chosen view area (often partially, so the area is covered in meaningless vertical and horizontal lines). I don't consider such big bboxes worth showing: they just add a useless yellow background.
2. Small changesets. Their position is significant, users should always be able to hover and see which changesets are so small and well-positioned.
3. Rather big changesets: the probability of them being completely covered by small changesets is low enough. And in this case we've got them in a list.

So if to sort changesets solely by bbox area (W*H in the simplest case), it would solve a problem of selecting small changesets and won't affect selectability of bigger ones much.

from openstreetmap-website.

cc @jfirebaugh

from openstreetmap-website.

Fixed by merging #171.

from openstreetmap-website.