aggregate_spatial: Clarified that the output geometries are unchang…

[m-mohr]

aggregate_spatial: Clarified that the output geometries are unchanged compared to the input geometries.

Closes #499

[clausmichele]

Is is implicit that the implementation should accept data and geometries with different projections?

[m-mohr]

@clausmichele Yeah, currently it is. Shall we make this explicit?

[clausmichele]

Yes @m-mohr, I think it would be better to mention it explicitly.

[m-mohr]

I guess we'd need to mention this in the data parameter, maybe like this?

A raster data cube with at least two spatial dimensions.\n\nThe data cube implicitly gets restricted to the bounds of the geometries as if filter_spatial() would have been used with the same values for the corresponding parameters immediately before this process. If the CRS of the raster data cube doesn't match the CRS of the geometries, the raster data will be reprojected to the CRS of the geometries.

[clausmichele]

I guess we'd need to mention this in the data parameter, maybe like this?

A raster data cube with at least two spatial dimensions.\n\nThe data cube implicitly gets restricted to the bounds of the geometries as if filter_spatial() would have been used with the same values for the corresponding parameters immediately before this process. If the CRS of the raster data cube doesn't match the CRS of the geometries, the raster data will be reprojected to the CRS of the geometries.

Perfect thanks.

[m-mohr]

Thanks, updated.