Repository navigation
Fix antimeridian burst crossing - #222
Merged
Merged
Conversation
arcisad
approved these changes
Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
For some Sentinel-1 scenes, the CDSE scene footprint doesn’t show the antimeridian crossing, but the individual burst geometries do. This adds a second check that merges the burst geometries and tests them for a crossing, so these scenes are correctly flagged as antimeridian scenes.
Example scenes
For flagged scenes, the DEM buffer is increased from 38.4km (1200 pixels @ 32m) to 57.6km (1800 pixels @ 32m) so the DEM fully covers the scene area. A very slight difference in dem resampling has changed values for antarctic scenes that cross the anti-meridian but not in any meaningful way. Gold tiles over the AM will be regenerated after release.
Type of change
General Checklist
isce3_rtc checklist (if this PR touches the isce3_rtc product)
Tests
pixi run test-isce3-rtc. More on testing is provided in the testing section of isce3_rtc.mdpixi run test-isce3-rtc-full-docker-workflow-runpasses)Product Versioning (Product Data has Changed)
If product data changes (for example, a bugfix in the ISCE3 software changes pixel locations),
product_versionshould be bumped in S1_RTC_IW.yaml and S1_RTC_STATIC_IW.yaml. E.g.product_versionis bumped from1.0.0to1.0.1. This will be reflected in the output product filenames and metadata created by the pipeline.