Due to fast prototyping we were just serializing the RapidJSON object into a string.
I think even though RocksDB gets rid of a lot of the overhead with compression if we want to get serious about file size it makes sense to encode the data better.
Putting a plug here for geobuf (which I believe is the next iteration of osm-binary?); but now that tippecanoe natively supports... we're going to be flying!
Due to fast prototyping we were just serializing the RapidJSON object into a string. I think even though RocksDB gets rid of a lot of the overhead with compression if we want to get serious about file size it makes sense to encode the data better.
Using protozero and a definition like https://github.com/scrosby/OSM-binary/blob/master/src/osmformat.proto we can store the objects and tags much more space efficient.