pbf
S2 geometry
| pbf | S2 geometry | |
|---|---|---|
| 4 | 4 | |
| 763 | 1,639 | |
| 0.9% | 0.7% | |
| 0.0 | 2.0 | |
| over 1 year ago | 10 months ago | |
| JavaScript | Go | |
| BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pbf
-
Parquet-WASM: Rust-based WebAssembly bindings to read and write Parquet data
it's been about 3 years, but in Grafana at the time we were using something like ArrowJS + Arrow Flight + protobuf.js and then render the datasets into dashboards on Canvas, especially for streaming at ~20hz.
when i benchmarked the fastest lib to simply convert the protobuf decode (https://github.com/mapbox/pbf), it was 5x slower than native JSON parsing in browsers for dataframe-like structures (e.g. a few dozen 2k-long arrays of floats).
-
Outperform Protobuf.js with fixed-size encoding
does it beat https://github.com/mapbox/pbf ?
-
Protobuf-ES: The Protocol Buffers TypeScript/JavaScript runtime we all deserve
at least in the frontend (without WASM), it depends.
i tested https://github.com/mapbox/pbf and while it was faster for deep/complex structs vs an unoptimized/repetative JSON blob, it was slower at shallow structs and flat arrays of stuff. if you spend a bit of time encode stuff as flat arrays to avoid mem alloc, JSON parsing wins by a lot since it goes through highly optimized C or assembly, while decoding protobuf in the JIT does not.
-
A standalone protobuf to typescript(for deno) code generator
The runtime is taken from mapbox/pbf (with basic type definitions)
S2 geometry
-
I wrote a package to compute the distance between two geographic latitude, longitude coordinates
I could be mistaken, but https://github.com/golang/geo does it already...
-
Get Coordinates Within Maps Bound Box
s2 a geo library from google can do exactly that, and has an implementation in Go. https://github.com/golang/geo
- Looking for a library to perform boolean operations on polygons
-
Protocol buffers database, a Key-Value database on the wire
There's a Java port and bindings for Python. The go port has been a work in progress for a while and the claimed to be at about 40% done. There's a rust port but it is based off of the go port and thus not complete either.
What are some alternatives?
protobuf - Protocol Buffers for JavaScript (& TypeScript).
h3 - Hexagonal hierarchical geospatial indexing system
sia - Sia - Binary serialisation and deserialisation
S2 geojson - Draw a polygon on the map or paste a geoJSON and explore how the s2.RegionCoverer covers it with S2 cells depending on the min and max levels
mbtileserver - Basic Go server for mbtiles
h3-go - Go bindings for H3, a hierarchical hexagonal geospatial indexing system
deno-pbf - Deno pbf port of https://github.com/mapbox/pbf
osm - General purpose library for reading, writing and working with OpenStreetMap data
osm - Open Service Mesh (OSM) is a lightweight, extensible, cloud native service mesh that allows users to uniformly manage, secure, and get out-of-the-box observability features for highly dynamic microservice environments.
fast-encoding - Fast, cross-platform, small and easy-to-use base64 and hex encoding.
simplefeatures - Simple Features is a pure Go Implementation of the OpenGIS Simple Feature Access Specification