search

Open-EO / openeo-python-driver

Common parts of a Python driver implementation for OpenEO
Apache License 2.0
11 stars 6 forks source link

Check for common errors in spatial_extent #284

Open EmileSonneveld opened 7 months ago

EmileSonneveld commented 7 months ago

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 commented 6 months ago

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 commented 5 months ago

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

EmileSonneveld commented 1 month ago

The missing CRS code with UTM coordinates was solved in this ticket: https://github.com/Open-EO/openeo-geopyspark-driver/issues/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'}