Index on UID

[SlowMo24]

Problem
For OSMContributionView each version of an entity has to be checked for the filters. For a global query this results in mean nr of Versions (1.7) * entites contributions being fed to the filter.

Desired solution
An index per GridCell (might be better then per OSH-Entity) possibly in form of a bitmap to exclude whole grid-cells based on a set of user-ids.

Alternative
?

Additional context
User-specific queries might get more common in future.

[SlowMo24]

this should be made flexible. There should be some kind of index class that I can attach to my View. This class will speed up my computation and reduce resource usage by setting necessary filters. Thereby custom filters (e.g for single research projects requesting these) could be implemented on different attributes like certain tags etc.

[SlowMo24]

any update on this? @rtroilo you worked on something like this, right? element-id filters etc. are other use-cases

[SlowMo24]

Any update on this?
What does the removal as candidate for a feature mean (what's actually the difference to an enhancement?)?
Is this obsolete due to #274 ?

[SlowMo24]

related: #380

[SlowMo24]

To continue the brainstorming:

Apart from an index a filter leveraging the OSM changeset db could enhance user-base queries by providing the exact time-range and area of the users edits. The time-range could for example be aggregated to e.g. monthly time intervals the user was active. The area on the other hand may only be relevant if the changeset area is sufficiently small. The question is, if there are changes that can happen outside the changeset area (e.g. via Relations) and if this process would force the creation of geometries for changes. For hardcore users a query to the changeset db might also take considerable time.