Geobuf Index
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
Lets discuss indexing. Previous discussion: https://github.com/mapbox/geobuf/issues/27#issuecomment-67220880
I think the solution I'd like to see here is a separate PBF-based format that would come as a separate file coupled with a Geobuf file that would store:
- serialized R-Tree (rbush) with leafs pointing to feature offsets in the geobuf pbf
- a map of feature ids to feature offsets for fast single-feature seeking
The R-tree serialization should avoid embedded messages because they are hard to decode lazily. I'd imagine one possible solution to be nodes stored as a flat set of messages, with references to children implemented as offset pointers.
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
Start with the previous discussion linked in the issue and inspect how Geobuf currently encodes feature data. Define the separate PBF-based index format, including lazy R-tree serialization and feature-id offsets, then validate that it supports spatial and single-feature seeking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data, performance, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100