Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Generating insane file sizes #634
I have a geojson that is 43MB, but I'm needing to get to at least zoom level 20, and so obviously the file it creates is just massive.
What would be the best option to get this smaller? I'm not super concerned about the sharpness of the polygon, I just need a reasonable small filesize.
Lowering the detail or changing the simplification (both?)?
Also is there a way to convert my geojson file so I can do parallel processing on it? It can take 2+ days to create the file on my server.
Zoom level 20 is extremely deep. Each of those tiles, even if it is entirely covered by a polygon, still has to spell out the gzip header, the square geometry, and whatever attributes your feature has. Nothing you do with detail or simplification is going to change this very much.
So my main suggestion is to use
If you can't change that, the best you're going to be able to do is to lower the detail and the buffer size so there is as little geometry as possible in each tile. But it's only going to make a tiny difference.
If you want to be able to parse the GeoJSON file in parallel with
The tiling stage of Tippecanoe will always use as many CPUs as are available, no matter how the GeoJSON was formatted.
Maybe that's what I'm doing wrong. I'm using leaflet to display everything, but after a certain zoom level it just disappears. If that's the case I should be able to configure something on that then?