Conversation
|
Are there news about this process? It would be important for the ClouDInSAR project. |
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| val cols = originalCols / window._1 | ||
| val rows = originalRows / window._2 | ||
| val newLayout = LayoutDefinition( | ||
| RasterExtent(metadata.extent, CellSize(metadata.cellSize.width*window._1, metadata.cellSize.height*window._2)), | ||
| cols, | ||
| rows |
There was a problem hiding this comment.
runUserCodeSpatialWindowReduce builds the new LayoutDefinition with a RasterExtent whose column/row counts are just the coarsened tile dimensions, so LayoutDefinition computes layoutCols/layoutRows as 1×1 even when the input cube spans many tiles. The RDD keys are left unchanged, so the metadata no longer matches: downstream mapTransform/retiling/writing will treat every key as covering the full extent or mark keys as out of bounds. Any cube with more than one tile will therefore get incorrect spatial extents after a spatial window reduce.
Useful? React with 👍 / 👎.
…ate_spatial_window
3 participants
No description provided.