# Donloading EWKB format is larger than GeoJSON?

I'm trying to find the most efficient way to download boundaries and thought it would naturally be EWKB, since this stores each geometry coordinate as binary floats, whereas GeoJSON stores everything as text with one byte per numeric digit. However, when trying this out, it turns out the EWKB downloads are almost twice as large as the GeoJSON downloads, so I'm thinking something must be wrong with the way the EWKB is generated. Here's an example of downloading all boundaries for Afghanistan:

GeoJSON (1.79MB)

EWKB (3.28MB)

https://osm-boundaries.com/Download/Submit?apiKey=

<apikey>&db=osm20210712&osmIds=-303427&recursive&format=EWKB&srid=4326&landOnly

MagnusThe GeoJSON is limited to 9 decimals while the EWKB (and EWKT) format uses whatever is in the database, which can be a lot more. For example the first coordinate in this polygon is 61.5622549375 29.6585979362252 (10 decimals in longitude).

PS! Edited your post and removed your token.