[houzi]

This is sorely missed in the GIS world: A well written and simple tool that isn't over engineered trying to cover all sorts of fringe use cases. Very clean code and good design at first glance.

I get why rasterio is preferred, its API is less annoying, but I'm not sure putting a leaking abstraction over gdal helps much. It just creates an aluring veneer over gdal, without really solving the main problems of gdal, being its monolithic monstrosity of hardly portable yet highly necessary GIS tool functionality.

Doesn't matter too much with gdal's warts, as this server should be deployed with ansible or in a container anyways, so portability is handled in a somewhat sane manner.

Thanks for open sourcing this!

[SahAssar]

Isn't this built on rasterio? I haven't used terracotta or rasterio, but your comment sounded like you compared them.

[dionhaefner]

I think the point was that Terracotta might be better off using GDAL directly instead of via rasterio.

Maybe, but I think mapbox is doing a great job with rasterio, and so far we didn’t run into any unsolvable problems (although we got close sometimes). I think for the ease of installation alone rasterio is a blessing.

[houzi]

Yes. I'm having a hard time finding a good selling point for rasterio.

> I think for the ease of installation alone rasterio is a blessing.

How does rasterio simplify installation, when you still have to deal with gdal's C extension dependencies?

[dionhaefner]

Rasterio wheels ship with GDAL binaries. No C compiler needed.

[houzi]

Yes. Sorry for the ambiguous comment.

Whenever I see a GIS application, I'm always curious to see how they solve the gdal problem.

The best is always no GDAL, but that gets pretty hard to do quite quickly as GDAL contains some really great algorithms for dealing with non-trivial raster processing.

[mistrial9]

yes, GDAL :-)