[Tile-serving] [osm2pgsql-dev/osm2pgsql] Optimizing geometry storage (Issue #2360)

[mboeringa]

mboeringa left a comment (osm2pgsql-dev/osm2pgsql#2360)

I'd be interested to hear about your test results using ST_QuantizeCoordinates... 

My preliminary testing using ST_QuantizeCoordinates even resulted in a dataset of 14GB ending up at 15GB if I can trust DBeaver's relation size display (woodland data of OpenStreetMap), which is the opposite of what I excepted. A few other datasets gained only a marginal reduction in storage size (maybe 2-3%). Admittedly, my workflow has some more gears going on, but even taking that into account, I have a hard time explaining such result.

Some thorough testing seems warranted though, as it appears your mileage may vary depending on table contents.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/issues/2360#issuecomment-3154050050
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/issues/2360/3154050050 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20250805/2e4e5081/attachment.htm>