pbf
mbtileserver
Our great sponsors
| pbf | mbtileserver | |
|---|---|---|
| 4 | 4 | |
| 763 | 599 | |
| 0.9% | 3.2% | |
| 0.0 | 5.9 | |
| over 1 year ago | 3 months ago | |
| JavaScript | Go | |
| BSD 3-clause "New" or "Revised" License | ISC License |
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)
mbtileserver
-
Offline map loading
So far I've tried building MBTiles with Maperitive using the OSM layer. Then hosting these MBTile files on an MBTileServer (https://github.com/consbio/mbtileserver) as slippy maps. Cesium can then read in and access these tiles pretty quickly and more or less it does the job.
-
Which tile server should I use? Terracotta or Geoserver or is there a better one?
https://github.com/consbio/mbtileserver We heavily use this tile server works awesome
- Why do I need geoserver?
-
Alternative to SQLite to store tiles for web visualisation
I like this tile server https://github.com/consbio/mbtileserver
What are some alternatives?
protobuf - Protocol Buffers for JavaScript (& TypeScript).
pbf - OpenStreetMap PBF golang parser
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
deno-pbf - Deno pbf port of https://github.com/mapbox/pbf
S2 geometry - S2 geometry library in Go
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.
sequentially-generate-planet-mbtiles - Generate vector tiles for the entire planet on relatively low spec hardware.
fast-encoding - Fast, cross-platform, small and easy-to-use base64 and hex encoding.
osm - General purpose library for reading, writing and working with OpenStreetMap data
img-encode - Encode an image to sound and view it as a spectrogram - turn your images into music
godal - golang wrapper for github.com/OSGEO/gdal