titiler VS rasterio

There's a lot to like about GDAL+Rasterio, although I've found having all HTTP requests go through GDAL's C API does result in some limitations on concurrency and multithreading. GDAL's configuration being based entirely on env vars also has its downsides: https://github.com/developmentseed/titiler/issues/186

TiMVT and TiFeatures, along with TiTiler for raster services, complete a trio of python-FastAPI services. The current roadmap includes merging TiFeatures & TiMVT, the vector-based services, into a single project to reduce code redundancy.

COGs are great, but from my experience micro services like titiler don't support complex styling logic. Is there a possibility to create a serverless WMS service with complex styling requirements?

Consider something like titiler if you want to serve the pile of geotiffs out to the web.

We were able to host 10gb six band rasters as well as 2cm RGB split into 100m tiles on S3 using COGS, mosaic.json and the TiTiler project which is powered by AWS lambda functions

TiTiler is a dynamic tile server built on FastAPI and Rasterio/GDAL. Its main features include support for Cloud Optimized GeoTIFF(COG), multiple projection methods, various output formats (JPEG, JP2, PNG, WEBP, GTIFF, NumpyTile), WMTS, and virtual mosaic. It also provides Lambda and ECS deployment environments using AWS CDK.

You're missing transform headers etc, you can write it out with GDAL but rasterio is generally easier to use than the Python GDAL bindings, here's an example.

Out of curiosity, what's stopping you from keeping the data in GTiff and just sampling from them with coordinates? Lots of free software lets you do that easily (e.g. QGIS, rasterio if you use Python etc). Am I not seeing something here?

> X. People will not read the docs.

> Docs are almost useless. Nobody reads them.

> They'll read a one page quick start, and then they want to just start digging in writing code.

> Keep the intros very minimal and very focused on getting things working.

I, for one, read the docs. May fortune smile on those who put effort into https://rasterio.readthedocs.io/

They are terse, but enough breadcrumbs to fumble my way to a working input for gdal_proximity.py

Possibly I'm not a representative sample, but one of my mantras at the office is "If you ain't doc'in', you ain't rockin'."

(Though we are only doing ransom note wiki pages, not library documentation.)

If the package doesn't have shiny Sphynx docs, at least afford us a few cryptic utterances in the source code.

Looks like rio (Rasterio CLI) also uses gdal libraries. https://github.com/rasterio/rasterio/blob/master/rasterio/rio/clip.py