Opened 11 years ago

Closed 9 years ago

#2176 closed defect (duplicate)

History Page Changeset Filtering

Reported by: pinkduck@… Owned by: Tom Hughes
Priority: minor Milestone:
Component: website Version:
Keywords: changeset bounds history viewport Cc:…


The history page is next to useless at seeing what has changed in my area. It is frequently populated by (big) changesets from places such as Russia and Poland, when I'm looking at a 4km square region in a small English city, thousands of miles away.

It seems as though relations, or the bounds tags, of uploads are being used for hit testing. Relations should be excluded, as these are just aggregation of map data, mostly unchanged. Only changesets featuring edits that affect nodes in the viewport I'm looking at should be returned, nothing more.

Case in point: Area: 0.9877,52.5247 to 1.5775,52.7331 Returns first changeset match as: Not a single changed node in that can be found in my viewport area

Now I appreciate that performing hit testing on node lat/lng values to return an aggregated set of changesets might be rather slow. Perhaps rather than a single bounds including all changed content, the server/client could create one or more bounds regions for associated clusters of nodes? With backdated generation for previous changesets.

I note that JOSM has recently added an option to update edits as individual changesets rather than a group, but it would be best for the server/client to make such aggregation decisions optimally than relying on user knowledge and attentiveness.

Another intermediate possibility would be to add the option of excluding 'big' changesets from the history view, unless say the bounds of a changeset were fully encompased by the viewport.

Change History (3)

comment:1 Changed 10 years ago by NicolasDumoulin

Cc:… added

comment:2 Changed 10 years ago by TheFive

I would like an exclude of 'big' change sets (all defined as big in the history view) as solution too.

comment:3 Changed 9 years ago by Tom Hughes

Resolution: duplicate
Status: newclosed

Duplicate of #1775.

Note: See TracTickets for help on using tickets.