Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Spatial extent is truncated for OPERA-S1 scenes over the antimeridian #1847

Open
asjohnston-asf opened this issue Jan 31, 2024 · 1 comment

Comments

@asjohnston-asf
Copy link
Member

OPERA-S1 scenes over the antimeridian have their outlines truncated when rendered on the Vertex map. I see similar behavior for both RTC and CSLC scenes:

Screenshot from 2024-01-30 12-54-01

The browse images reflect covering the entire S1 SLC burst, but are squished to fit inside the truncated outline:

Screenshot from 2024-01-30 12-54-16

The full spatial extent of these scenes appears to be a multi-polygon in CMR; Vertex appears to only be rendering one of the two polygons.

For OPERA_L2_CSLC-S1_T001-000681-IW2_20231030T183212Z_20240123T023117Z_S1A_VV_v1.0 highlighted in the screenshot, the CMR metadata has this multipolygon, of which only the first polygon is rendered.

{
  "Geometry": {
    "GPolygons": [
      {
        "Boundary": {
          "Points": [
            {
              "Latitude": 65.64483,
              "Longitude": -180
            },
            {
              "Latitude": 65.59529,
              "Longitude": -179.44616
            },
            {
              "Latitude": 65.75857,
              "Longitude": -179.35751
            },
            {
              "Latitude": 65.81571,
              "Longitude": -180
            },
            {
              "Latitude": 65.64483,
              "Longitude": -180
            }
          ]
        }
      },
      {
        "Boundary": {
          "Points": [
            {
              "Latitude": 65.81571,
              "Longitude": 180
            },
            {
              "Latitude": 65.92396,
              "Longitude": 178.67998
            },
            {
              "Latitude": 65.75983,
              "Longitude": 178.60693
            },
            {
              "Latitude": 65.64483,
              "Longitude": 180
            },
            {
              "Latitude": 65.81571,
              "Longitude": 180
            }
          ]
        }
      }
    ]
  }
}
@asjohnston-asf
Copy link
Member Author

Looks like this issue only impacts rendering, not searching. I did a point search on the east side of the antimeridian and this granule still appears in the results as expected, despite rendering entirely on the west side.

Screenshot from 2024-01-30 15-14-46

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant