Using 32 byte hashes as IDs uses an unnecessary amount of space about mbtiles-spec HOT 7 CLOSED

Changing the file format could potentially work without backwards compatibility issues. SQLite3 allows inserting arbitrary data into a column; the column type is merely an affinity, not a strict rule.

from mbtiles-spec.

I rekeyed world-light and got savings of about 83 MB, bringing it from 1219 MB to 1136 MB, and about 7% savings. The resulting file still works in Tilestream. With interactivity, the savings are a lot bigger. Since there are a lot more columns that use a long hash.

from mbtiles-spec.

Also rekeying interactivity, a small sample file I used is now only 80% of the original size (881 to 700 KB). Still works in Tilestream.

from mbtiles-spec.

Declaring id columns as INTEGER PRIMARY KEY further reduces the file size to 78% of the original file size (881 to 688 KB).

from mbtiles-spec.

Does this need to be within mbtiles-spec or are the particulars of TileMill's keying just a TileMill issue?

from mbtiles-spec.

This is a TileMill issue. There's an mbrekey command in node-mbtiles that changes the keys in a file; there's nothing in the spec that mandates keys I believe.

from mbtiles-spec.

All right, moved - https://github.com/mapbox/tilemill/issues/758

from mbtiles-spec.