rasterio VS Fiona

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

Your issue is that you're using the default (old) binding to GDAL, based on Fiona [0].

You need to use pyogrio [1], its vectorized counterpart, instead. Make sure you use `engine="pyogrio"` when calling `to_file` [2]. Fiona does a loop in Python, while pyogrio is exclusively compiled. So pyogrio is usually about 10-15x faster than fiona. Soon, in pyogrio version 0.8, it will be another ~2-4x faster than pyogrio is now [3].

[0]: https://github.com/Toblerity/Fiona

[1]: https://github.com/geopandas/pyogrio

[2]: https://geopandas.org/en/stable/docs/reference/api/geopandas...

[3]: https://github.com/geopandas/pyogrio/pull/346

As has been said the definition of a GIS dev is far from written in stone, but to chime in from a personal standpoint: most of what I do is data wrangling/analysis with shapely/geopandas for vectors (or pygeos / fiona for performance when data volumes get large, but seeing as Shapely 2.0 just got released one can likely skip this part) + rasterio for rasters as well as parallelising these tasks for performance if needed (ray is great for that) and then performing machine learning learning against the data (mostly with sklearn and torch).

TypeError 10 refers to (https://github.com/Toblerity/Fiona/blob/master/fiona/_geometry.pyx):