yesql VS rasterio

There's a whole family of libraries like that. Yesql is the first I became aware of. The repo has an (incomplete) list of ports to other languages: https://github.com/krisajenkins/yesql#other-languages

> People will not read the docs.

Reminds me of a pull request I made a while ago

https://github.com/krisajenkins/yesql/pull/151/files

The first piece of code on the readme is "not the solution" (lol), and everybody I knew who was trying to use that library was copy-pasting that specific piece of code from the readme.

If you're not familiar with lisps in general, it might be hard to grok the differences between lisp-macros (as used in Clojure) and "normal" macros you see in other languages.

But, if you are familiar already, and just wanna see examples of neat macros that makes the API nicer than what a function could provide, here are a few:

- https://github.com/clojure/core.async/blob/master/examples/w...

- https://github.com/weavejester/compojure

- https://github.com/ptaoussanis/timbre

- https://github.com/krisajenkins/yesql

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