Slow Point Data/is geojson pokey?
I have a map that uses point data sets in .geojson files, about
4,000 points. It seems to load in Tilemill fine, but the export
time (zoom levels 3-13, extent including the lower 48 + AK and HI)
is predicted at 50 hours. I've attached the geojson. Other than the
point file, I'm just using the data that comes with Tilemill and
polygon file that works fine in other maps(just for labels). Any
ideas about what might be causing this problem? Is it that the
point file is projected as WGS84? Is geojson just a bad idea here?
Is it my carto styles?
Thanks!
Matthew
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Tom MacWright on 01 Aug, 2011 02:42 PM
GeoJSON is definitely not a very fast format for data input. It's convenient, but for lots of points, it's going to be slow. The knowledgebase has a bit on optimizing data for TileMill - you'll want to use
ogr2ogrto convert GeoJSON to a shapefile in EPSG:900913 projection.3 Posted by Matthew Loveless on 02 Aug, 2011 12:10 AM
Yeah, I thought I might need to do that. Thanks!
Matthew Loveless closed this discussion on 02 Aug, 2011 12:26 AM.