Closed anandthakker closed 9 years ago
Just started working on this and realized that the memory implications might be prohibitive. The problem is that after we "rehydrate" the vector tile data into GeoJSON, all those tiny features we're adding up to get the total population start to add up pretty quick.
Now, because of the way the vector tiles work, we could actually stream this straight to the download, so that we'd only ever have 1 tiny polygon in memory at a time. (That's already how we're processing the data to get the total.) But doing this for the download might be slightly complicated, so I'm wondering: is a valuable enough feature to be worth some extra time, or should we punt on it?
/cc @smit1678 @jflasher
I think that's fine to punt on this until we have more data to export with your shape.
Cool. Could also just do a simpler version that just downloads the drawn polygon with population count (i.e., excluding the smaller internal polygons)
once polygon area is calculated, provide link to download geojson of the result: