Check for common errors in spatial_extent

[EmileSonneveld]

Users often type errors in spatial extent. This often gives errors, but sometimes very obscure ones.

For example:
'spatial_extent': {'west': [0], 'south': 60.11, 'east': 25.24, 'north': 60.35, 'crs': 'EPSG:4326'},
'spatial_extent': [1,2,3,4],

The following already gives an error:
"spatial_extent": {"east": 4, "north": 51.22, "south": 51.215, "west": 5}, -> geotrellis.vector.ExtentRangeError: Invalid Extent: xmin must be less than xmax (xmin=5.07, xmax=4.08)

Maybe we can also catch UTM coordinates while no CRS is specified.

[EmileSonneveld]

User example that could be caught by this:

        "spatial_extent": {
          "west": 4329317.717132108,
          "east": 4330615.2810456185,
          "north": 3005295.0854642093,
          "south": 3003997.791438847
        },

j-240516d78c86445aa82203c98bcbab49

[soxofaan]

Also make sure this is included in the /validation code path

[EmileSonneveld]

The missing CRS code with UTM coordinates was solved in this ticket: Open-EO/openeo-geopyspark-driver#815

When doing checks on the extent, this error is raised:
collection_id 'SENTINEL2_L2A': Unsupported spatial extent: {'west': 4329317.717132108, 'south': 3003997.791438847, 'east': 4330615.2810456185, 'north': 3005295.0854642093, 'crs': 'EPSG:4326'}

[EmileSonneveld]

'spatial_extent': [1,2,3,4], now gives:
openeo.rest.OpenEoClientException: Invalid geometry argument: [1, 2, 3, 4]
Was fixed in: Open-EO/openeo-python-client#678

[soxofaan]

'spatial_extent': [1,2,3,4] now gives: openeo.rest.OpenEoClientException: Invalid geometry argument: [1, 2, 3, 4]. Was fixed in: Open-EO/openeo-python-client#678

Open-EO/openeo-python-client#678 only addresses the issue if the user uses load_collection from python client at that point. I think it still makes sense to do this kind of input checking at driver level regardless of used client

[EmileSonneveld]

Then we can keep this ticket open for the moment.
I was just clearing out some old tickets