Yirgacheffe is an attempt to wrap gdal datasets such that you can do computational work on them without having to worry about common tasks:
The motivation for Yirgacheffe layers is to make working with gdal data slightly easier - it just hides some common operations, such as incremental loading to save memory, or letting you align layers to generate either the intersection result or the union result.
For example, say we had three layers that overlapped and we wanted to know the
from yirgacheffe.layer import Layer, UniformAreaLayer
elevation_layer = RasterLayer.layer_from_file('elecation.tiff')
area_layer = UniformAreaLayer('area.tiff')
validity_layer = RasterLayer.layer_from_file('validity.tiff')
# Work out the common subsection of all these and apply it to the layers
intersection = RasterLayer.find_intersection([elecation_layer, area_layer, validity_layer])
elevation_layer.set_window_for_intersection(intersection)
area_layer.set_window_for_intersection(intersection)
validity_layer.set_window_for_intersection(intersection)
# Create a layer that is just the size of the intersection to store the results
result = RasterLayer.empty_raster_layer(
intersection,
area_layer.pixel_scale,
area_layer.datatype,
"result.tif",
area_layer.projection
)
# Work out the area where the data is valid and over 3000ft
def is_munro(data):
return numpy.where(data > 3000.0, 0.0, 1.0)
calc = validity_layer * area_layer * elevation_layer.numpy_apply(is_munro)
calc.save(result)
result.close()If you want the union then you can simply swap do:
intersection = RasterLayer.find_union(elecation_layer, area_layer, validity_layer)
elevation_layer.set_window_for_union(intersection)
area_layer.set_window_for_union(intersection)
validity_layer.set_window_for_union(intersection)If you want to work on the data in a layer directly you can call read_array, as you would with gdal. The data you access will be relative to the specified window - that is, if you've called either set_window_for_intersection or set_window_for_union then read_array will be relative to that and Yirgacheffe will clip or expand the data with zero values as necessary.
If you have set either the intersection window or union window on a layer and you wish to undo that restriction, then you can simply call reset_window() on the layer.
Layers also work with Python's with statement, which helps prevent you forgetting to close a layer, which is important both for ensuring results are written to disk when you want, and that memory used by layers is freed (Yirgacheffe doesn't cache data in memory, but it uses GDAL which does).
So for example you can turn the above example to:
with RasterLayer.empty_raster_layer(
intersection,
area_layer.pixel_scale,
area_layer.datatype,
"result.tif",
area_layer.projection
) as result:
# Work out the area where the data is valid and over 3000ft
def is_munro(data):
return numpy.where(data > 3000.0, 0.0, 1.0)
calc = validity_layer * area_layer * elevation_layer.numpy_apply(is_munro)And you no longer need to explicitly call result.close() to ensure the result is written to disk.
Yirgacheffe is work in progress, so things planned but not supported currently:
This is your basic GDAL raster layer, which you load from a geotiff.
with RasterLayer.layer_from_file('test1.tif') as layer:
data = layer.read_array(0, 0, 10, 10)
...You can also create empty layers ready for you to store results, either by taking the dimensions from an existing layer. In both these cases you can either provide a filename to which the data will be written, or if you do not provide a filename then the layer will only exist in memory - this will be more efficient if the layer is being used for intermediary results.
with RasterLayer.empty_raster_layer_like(layer1, "results.tiff") as result:
...Or you can specify the geographic area directly:
with RasterLayer.empty_raster_layer(
Area(left=-10.0, top=10.0, right=-5.0, bottom=5.0),
PixelScale(0.005,-0.005),
gdal.GDT_Float64,
"results.tiff"
) as result:
...You can also create a new layer that is a scaled version of an existing layer:
with RasterLayer.layer_from_file('test1.tif') as source:
scaled = RasterLayer.scaled_raster_from_raster(source, PixelScale(0.0001, -0.0001), 'scaled.tif')This layer will load vector data and rasterize it on demand as part of a calculation - because it only rasterizes the data when needed, it is memory efficient.
Because it will be rasterized you need to specify the pixel scale and map projection to be used when rasterising the data, and the common way to do that is by using one of your other layers.
with VectorLayer.layer_from_file('range.gpkg', 'id_no == 42', layer1.pixel_scale, layer1.projection) as layer:
...This class was formerly called DynamicVectorRangeLayer, a name now deprecated.
In certain calculations you find you have a layer where all the rows of data are the same - notably geotiffs that contain the area of a given pixel do this due to how conventional map projections work. It's hugely inefficient to load the full map into memory, so whilst you could just load them as Layer types, we recommend you do:
with UniformAreaLayer('area.tiff') as layer:
....Note that loading this data can still be very slow, due to how image compression works. So if you plan to use area.tiff more than once, we recommend use save an optimised version - this will do the slow uncompression once and then save a minimal file to speed up future processing:
if not os.path.exists('yirgacheffe_area.tiff'):
UniformAreaLayer.generate_narrow_area_projection('area.tiff', 'yirgacheffe_area.tiff')
area_layer = UniformAreaLayer('yirgacheffe_area.tiff')This is there to simplify code when you have some optional layers. Rather than littering your code with checks, you can just use a constant layer, which can be included in calculations and will just return an fixed value as if it wasn't there. Useful with 0.0 or 1.0 for sum or multiplication null layers.
try:
area_layer = UniformAreaLayer('myarea.tiff')
except FileDoesNotExist:
area_layer = ConstantLayer(0.0)If you have H3 installed, you can generate a mask layer based on an H3 cell identifier, where pixels inside the cell will have a value of 1, and those outside will have a value of 0.
Becuase it will be rasterized you need to specify the pixel scale and map projection to be used when rasterising the data, and the common way to do that is by using one of your other layers.
hex_cell_layer = H3CellLayer('88972eac11fffff', layer1.pixel_scale, layer1.projection)You can combine several layers into one virtual layer to save you worrying about how to merge them if you don't want to manually add the layers together. Useful when you have tile sets for example. Any area not covered by a layer in the group will return zeros.
tile1 = RasterLayer.layer_from_file('tile_N10_E10.tif')
tile2 = RasterLayer.layer_from_file('tile_N20_E10.tif')
all_tiles = GroupLayer([tile1, tile2])If you provide tiles that overlap then they will be rendered in reverse one, so in the above example if tile1 and tile2 overlap, then in that region you'd get the data from tile1.
To save you specifying each layer, there is a convenience method to let you just load a set of TIFs by filename:
with GroupLayer.layer_from_files(['tile_N10_E10.tif', 'tile_N20_E10.tif']) as all_tiles:
...Or you can just specify a directory and it'll find the tifs in there (you can also add your own custom file filter too):
with GroupLayer.layer_from_directory('.') as all_tiles:
...This is a specialisation of GroupLayer, which you can use if your layers are all the same size and form a grid, as is often the case with map tiles. In this case the rendering code can be optimised and this class is significantly faster that GroupLayer.
tile1 = RasterLayer.layer_from_file('tile_N10_E10.tif')
tile2 = RasterLayer.layer_from_file('tile_N20_E10.tif')
all_tiles = TiledGroupLayer([tile1, tile2])Notes:
Once you have two layers, you can perform numerical analysis on them similar to how numpy works:
Pixel-wise addition, subtraction, multiplication or division, either between arrays, or with constants:
with RasterLayer.layer_from_file('test1.tif') as layer1:
with RasterLayer.layer_from_file('test2.tif') as layer2:
with RasterLayer.empty_raster_layer_like(layer1, 'result.tif') as result:
calc = layer1 + layer2
calc.save(result)or
with RasterLayer.layer_from_file('test1.tif') as layer1:
with RasterLayer.empty_raster_layer_like(layer1, 'result.tif') as result:
calc = layer1 * 42.0
calc.save(result)Pixel-wise raising to a constant power:
with RasterLayer.layer_from_file('test1.tif') as layer1:
with RasterLayer.empty_raster_layer_like(layer1, 'result.tif') as result:
calc = layer1 ** 0.65
calc.save(result)You can specify a function that takes either data from one layer or from two layers, and returns the processed data. There's two version of this: one that lets you specify a numpy function that'll be applied to the layer data as an array, or one that is more shader like that lets you do pixel wise processing.
Firstly the numpy version looks like this:
def is_over_ten(input_array):
return numpy.where(input_array > 10.0, 0.0, 1.0)
layer1 = RasterLayer.layer_from_file('test1.tif')
result = RasterLayer.empty_raster_layer_like(layer1, 'result.tif')
calc = layer1.numpy_apply(is_over_ten)
calc.save(result)or
def simple_add(first_array, second_array):
return first_array + second_array
layer1 = RasterLayer.layer_from_file('test1.tif')
layer2 = RasterLayer.layer_from_file('test2.tif')
result = RasterLayer.empty_raster_layer_like(layer1, 'result.tif')
calc = layer1.numpy_apply(simple_add, layer2)
calc.save(result)If you want to do something specific on the pixel level, then you can also do that, again either on a unary or binary form.
def is_over_ten(input_pixel):
return 1.0 if input_pixel > 10 else 0.0
layer1 = RasterLayer.layer_from_file('test1.tif')
result = RasterLayer.empty_raster_layer_like(layer1, 'result.tif')
calc = layer1.shader_apply(is_over_ten)
calc.save(result)Note that in general numpy_apply is considerably faster than shader_apply.
There are two ways to store the result of a computation. In all the above examples we use the save call, to which you pass a gdal dataset band, into which the results will be written. You can optionally pass a callback to save which will be called for each chunk of data processed and give you the amount of progress made so far as a number between 0.0 and 1.0:
def print_progress(p)
print(f"We have made {p * 100} percent progress")
...
calc.save(result, callback=print_progress)The alternative is to call sum which will give you a total:
with (
RasterLayer.layer_from_file(...) as area_layer,
VectorLayer(...) as mask_layer
):
intersection = RasterLayer.find_intersection([area_layer, mask_layer])
area_layer.set_intersection_window(intersection)
mask_layer.set_intersection_window(intersection)
calc = area_layer * mask_layer
total_area = calc.sum()Similar to sum, you can also call min and max on a layer or calculation.
The following features are considered experimental - they have test cases to show them working in limited circumstances, but they've not yet been tested on a wide range of use cases. We hope that you will try them out and let us know how they work out.
The RescaledRasterLayer will take a GeoTIFF and do on demand rescaling in memory to get the layer to match other layers you're working on.
with RasterLayer.layer_from_file("high_density_file.tif") as high_density:
with RescaledRasterLayer.layer_from_file("low_density_file.tif", high_density.pixel_scale) as matched_density:
# Normally this next line would fail with two RasterLayers as they ahve a different pixel density
intersection = RasterLayer.find_intersection([high_density, matched_density])
high_density.set_intersection_window(intersection)
matched_density.set_intersection_window(intersection)
calc = high_density * matched_density
total = calc.sum()
There is a parallel version of save that can use multiple CPU cores at once to speed up work, that is added as an experimental feature for testing in our wider codebase, which will run concurrently the save over many threads.
calc.parallel_save(result)By default it will use as many CPU cores as are available, but if you want to limit that you can pass an extra argument to constrain that:
calc.parallel_save(result, parallelism=4)Because of the number of tricks that Python plays under the hood this feature needs a bunch of testing to let us remove the experimental flag, but in order to get that testing we need to put it out there! Hopefully in the next release we can remove the experimental warning.
Thanks to discussion and feedback from the 4C team, particularly Alison Eyres, Patrick Ferris, Amelia Holcomb, and Anil Madhavapeddy.
Inspired by the work of Daniele Baisero in his AoH library.