Faster hit detection with tens of thousands of polygon features.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- performance
Research direction
Start by tracing the hit detection instructions, executor, RTree, and loadFeature() paths mentioned in the issue. Determine whether a bounded-area hit test or an existing example can address the slowdown, and define done as a documented or implemented approach that avoids processing distant polygon features.
Written by the indexing model from the issue text.
Description
When I have many polygon features on the map, and all of those are shown, (you can imagine all cities in the US are shown in the view). my pointer hover action can be slow. I see that there are optimization techniques applied, to create an executor and features kept in RTree etc. but in the situation it still requires to have a list of all features in "hit detection instructions", when it seems to me that only features overlaps, or contained, within say 50 pixels from the pointer location. (I can give up features that are not fully contained.) Maybe there is a custom way to do this on my end, such as indeed do the loadFeature() for a smaller area each time and run hit test? Is there an existing example like this?
- Dominant language
- JavaScript
- Stars
- 12.6k
- Forks
- 3.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 21
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openlayers/openlayers
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
openlayers/openlayers#17145 ·
-
feature request
Difficulty 1/5 Under an hour Newbie friendliness 70/100
openlayers/openlayers#16410 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 68/100
openlayers/openlayers#16042 ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 45/100
openlayers/openlayers#17630 · 7 comments ·
-
Openfreemap 3D Openfeature request
Difficulty 5/5 Over a week Newbie friendliness 25/100
openlayers/openlayers#17590 · 14 comments ·
All issues in openlayers/openlayers
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100