Combining multiple bounding boxes: intersect instead of arbitrairy one

[soxofaan]

support question raised by @manugv which has this use case (condensed):
load_collection(bbox1) .... filter_spatial(bbox2)

bounding box of result is bbox2, while Open-EO/openeo-processes#201 clarified that it should be intersection

related part of logic:

openeo-python-driver/openeo_driver/dry_run.py

Lines 485 to 488 in 8974d65

	# Take first item (to reproduce original behavior)
	# TODO: take temporal/spatial/categorical intersection instead?
	# see https://github.com/Open-EO/openeo-processes/issues/201
	constraints[op] = args[0]

[jdries]

Fixing this may impact use cases that wish to somehow define the desired output bounding box in some way.

[soxofaan]

I think we should at least logging for some time to get a better view of what is happening here in reality and what the impact of changing it might be. Later we can then see if it makes sense to make this an opt-in fix or opt-out fix, or something like that

[manugv]

I was wrong so deleted my old comment. I finally found the filter_spatial behavior and the attached image shows it perfectly.

1. If the filter_spatial bbox1 is bigger than the load_collection bbox then bbox1 is considered (see image below). This should not happen as the intersection should give nan/no data values in the regions outside load_collection bbox
2. The filter_spatial bbox1 is smaller than the load_collection bbox then the intersection gives nan/no data values in the regions outside filter_spatial bbox1 as seen in the image below.

Image Description

1. Blue outline is bbox1 given as an input to filter_spatial. The output of filter_spatial is the bbox1 + red regions. Red region is nan values as they are outside bbox (As expected). Yellow region is where there is data (not as expected) but should have been nans
2. Green in background is my actual load_collection bbox.