Dateline crossing dcw polygons and tiles #8318
Merged
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 of proposed changes
See #8266 for background. We kept getting a bad west/east string for the three polygons USA, RU, and FJ that crossed the 180-degree meridian. In combination with tiled remote data sets we ended up with no plot, but always worked well with non-tiled (e.g., 06m and lower resolutions). Ensuring monotonically increasing longitudes from west to east fixed this, and I added a new test just so we stay alert (dcw_180_crossers.sh).
The new test pass:
While master gives empty frames: