Kipling

@Zeitsperre cool! For the docblocs so far, I've just been using the Google standard (I do this via vscodes autoDocstring) extension. So let's do google.

http://docs.opengeospatial.org/is/19-008r4/19-008r4.html

GeoTiff codes https://step.esa.int/docs/v4.0/apidoc/engine/org/esa/snap/core/util/geotiff/GeoTIFFCodes.html

@Stan92 Go through this tutorial that I made and see if it helps: https://github.com/KipCrossing/Micro-Camera

I'm just going to drop this here: https://kipcrossing.github.io/2021-01-03-noGDAL/

No worries @harry093 . **noGDAL** is just a philosophy and there are many packages that fit the bill, but I assume you are talking about the [geotiff](https://github.com/Open-Source-Agriculture/geotiff) python package that...

Thanks for picking that up. If you've already debugged, please open a PR and I'll merge asap! Thanks!

> Please refer to our package, it provide an alternative solution for making geotiff tags. https://github.com/UTokyo-FieldPhenomics-Lab/EasyIDP/blob/ff687a6d3e27a0155d137019a15ba8461ce2222e/easyidp/geotiff.py#L351 > > But it only suitable for cutting a region from given geotiff (only...

Sooooo... I just got a solution from ChatGTP: ```python import xarray as xr import tifffile import tifftools # Load the data and create a tifffile object data = xr.open_dataset('data.nc') tiff...

Looks like this might be a major problem with chatGTP. That is; when the solution is not obvious, it will make up a solution based on features that don't exist.