You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Lets discuss indexing. Previous discussion: #27 (comment)
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:
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.
The text was updated successfully, but these errors were encountered: