search

mapbox / tippecanoe

Build vector tilesets from large collections of GeoJSON features.
BSD 2-Clause "Simplified" License
2.71k stars 430 forks source link

Input format with faster parsing #68

Closed e-n-f closed 8 years ago

e-n-f commented 9 years ago

@morganherlocker would like a simple CSV input format like the datamaps one that is faster to parse than GeoJSON. @aaronlidman, I think you said you'd like this too.

aaronlidman commented 9 years ago

Is this just for geometry or will this also include a way of passing properties?

Before investing in this, do you have an idea of how much gain we would expect by not needing to parse JSON?

e-n-f commented 9 years ago

@aaronlidman I was thinking just "key"="value" at the end of the line. The more serious limitation is no good precedent for a syntax for polygons.

Datamaps input parsing is about 10x the speed of tippecanoe's, and the only real difference is GeoJSON vs just blasting through comma-separated pairs.

There's got to be something that is reasonably fast, easy to generate, and reasonably standardized, but I don't know what it is. GeoJSON is standard but slow to parse and hard to generate because of all the nested objects.

aaronlidman commented 8 years ago

I think parallelized input mitigates this need quite a bit.

@ericfischer - Think we're good to close this?

e-n-f commented 8 years ago

Yeah, probably not worth worrying about this unless to support some other widely-used format like shapefile.