rasterio VS gdal

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

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.

GDAL is the real heart, the python aspect is mostly wrappers around that I'm fairly sure. I love python for the record, the only reason I bring it up, is cause python haters accuse it of being slow, but QGIS drops down to C++ when speed is necessary, like most modern packages do.

gdal 0.15 (repo, docs), a set of Rust bindings for the GDAL library, used for access to geo-spatial data formats, is now out!

GDAL (Geospatial Data Abstraction Library) is a the geospatial data processing library. It handles a lot of Raster/Vector analysis and alteration. gdal_contour and gdal_rasterize which would be used to create isolines (contour lines) . There's more complex processing and analyses than that. More common is reprojecting multiple layers, and some that being as Vector files, into different coordiatne systems.

Access: GDAL

As an example we use GDAL heavily through its C# binds. We do all the additional data processing, that isn't done by the C++ GDAL, in C#. The final results are both Data (held in memory or temp exported to a file), and a normalized Raster Texture that we can display on a TextureRect. Most of the C# data processing scripts aren't even Inheriting from any Godot Class.

I think this would be the best way to handle this. GDAL is what you should look into for this project.