Performance characteristics of index init
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 6.5k
- Forks
- 627
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 6
Description
I'm thinking about using H3 as a storage for vector map cells for map rendering. A cell would contain geometry data for a given zoom level.
What are the runtime characteristics of H3 for this scenario?
For an example, consider a web map which needs to calculate which cells it would need to request from a server for the current view. Would it need to initialize an index in order to query for the cells for the current view bbox and given resolution? If so, what is the expected memory footprint of the index?
Or are the cell indices calculated mathematically on demand?
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.
Research direction
No file, test, or entry point is identified. First determine how H3 answers bounding-box cell queries and whether index initialization is involved, then document the expected runtime behavior and memory footprint for the described map-rendering scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- data
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100