geobuf

> If you have a non-insignificant amount of data points to track this is going to eat just a ton of memory while also being pretty slow to encode/decode. This is a fair critique, however, for any large GeoJSON, the coordinate arrays will dominate the size. I think it's also safe to assume this data will be gzipped at rest and over the wire, which will eliminate most of the "header" metadata size you mention. As you point out, it would be much more efficient to have a binary format, and there are good examples like these, that are ~2-3x smaller in benchmarks: https://flatgeobuf.org/ https://github.com/mapbox/geobuf That said, I think GeoJSON should be compared against other human readable formats like KML, which has a lot of wasted space as well, while being more difficult to read/write.

This looks cool! The GRPC support's what caught my attention, especially as I've found trying to pass GeoJSON objects around GRPC to be a pain. One of the irritating things with Protobufs is the lack of support for nested JSON-style arrays, which GeoJSON LineString and Polygon use. I've seen some https://github.com/mapbox/geobuf but after trying it out for a bit, I felt it wouldn't work well for me. Anyways, I searched the Protobuf files on the repo, but I can't find anything that gives me a guide on what's being done on Tile38. I'll have a deeper look at the source.