gdal VS godot_voxel

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.

Don't do this, CSG is unoptimized. Use this.

Take a look at https://github.com/Zylann/godot_voxel, which would be a great starting point that you could build game mechanics on top of.

https://github.com/Zylann/godot_voxel https://voxel-tools.readthedocs.io/en/latest/

Currently all our major C++ based number crunching is in the GDAL. We haven't had to make in-house GDExtensions or Modules, yet. But we do also use Godot Voxel. Both are good examples of where you'd want more native speed.

I originally ported Qodot to an engine module that required people to compile their own engine (like godot-voxel) but users were turned away at this first roadblock.

I really wanted to use it but sadly it might be hard to export projects done with it cuz it's not a gdextension yet https://github.com/Zylann/godot_voxel/issues/333 still possible but i think you gotta compile something.

If you aren't adverse to doing a custom editor build you could add https://github.com/Zylann/godot_voxel

To give some practical examples. At my day job we use GDAL (a C++ geospatial data processing library) and Zylann's Godot Voxel (a C++ engine Module) https://github.com/Zylann/godot_voxel

The master branch of this one will also build as a GDExtension for Windows. This one is successfully building regularly, but structured different than the rest of the GDExtensions I've seen. I haven't played with this project too much yet, but it's an insanely powerful module/extension: https://github.com/Zylann/godot_voxel