SWOT Raster files with wrong Spatial Extents

[cordmaur]

I'm using earthaccess to search for raster tiles around an AOI in the Amazon Basin, however, it is returning Granules located in Russia.
With further investigation, I noticed the spatial extents are incorrectly set to -180, -90, 180, 90 (example below), causing these wrong tiles to be retrieved.

{'TemporalExtent': {'RangeDateTime': {'EndingDateTime': '2025-05-02T22:25:31.272Z',
   'BeginningDateTime': '2025-05-02T22:25:10.139Z'}},
 'GranuleUR': 'SWOT_L2_HR_Raster_100m_UTM01W_N_x_x_x_032_138_018F_20250502T222510_20250502T222531_PIC2_01',
 'AdditionalAttributes': [{'Values': ['034L',
    '035L',
    '036L',
    '037L',
    '034R',
    '035R',
    '036R',
    '037R'],
   'Name': 'TILE'}],
 'MeasuredParameters': [{'QAStats': {'QAPercentMissingData': 0,
    'QAPercentOutOfBoundsData': 0},
   'ParameterName': 'N/A'}],
 'SpatialExtent': {'HorizontalSpatialDomain': {'Geometry': {'BoundingRectangles': [{'WestBoundingCoordinate': -180,
      'SouthBoundingCoordinate': -90,
      'EastBoundingCoordinate': 180,
      'NorthBoundingCoordinate': 90}]},

If we look at these specific tiles (Pass 138 - 034, 035, 036, etc... ), we can notice the discrepancy:

[celiaou-podaac]

Unfortunately, we currently rely on a manual fix for this intermittent spatial extent error. This issue arises from when the incoming data files have certain geometries that our ingest software cannot translate into to a valid CMR coverage. I will run the fix for this soon when I get a chance and comment again here upon completion.