Add a flag to allow for Geoid-height on NaN points in DEM generation#88
Add a flag to allow for Geoid-height on NaN points in DEM generation#88reinieroost wants to merge 1 commit intosenbox-org:masterfrom
Conversation
|
Link to desktop PR: senbox-org/snap-desktop#40 |
|
Thanks for this PR. That's great. User contribution is always welcome. Thanks |
| @Parameter(description = "The elevation band name.", defaultValue = "elevation", label = "Elevation Band Name") | ||
| private String elevationBandName = "elevation"; | ||
|
|
||
| @Parameter(description = "Fill nodata values by geod values", defaultValue = "false", label = "Fill Nodata with Geod") |
There was a problem hiding this comment.
Minor note: there's a typo in 'geoid'.
|
The snap-desktop pull request has already been merged but not this one on snap-engine. Therefore, AddElevationUI currently breaks because the fillWithGeod parameter doesn't exist in AddElevationOp. Also there are spelling errors for fillWithGeod. |
|
@jun--lu Why have you reverted the PR snap-desktop#40 by this senbox-org/snap-desktop#41? Why not simply applying this PR and fix the typo? |
|
Hi Marco, By accident I merged the pull request under snap/desktop on AddElevationUI to master and I did not know that there is anther pull request under snap/engine on AddElevationOp until Luis pointed out. I've tried to merge AddElevationOp to master, then I realised that you want to make this change after V6.0 release (your email on Set. 24 ). Therefore, I reversed the merge. Jun |
|
Jun, if this PR is tested and does not break existing processing chains I’m fine with the merge of it. |
|
Hi Marco, |
|
|
This allows to avoid NaN values at places where the DEM is NaN, by using Geoid heights instead. This is very favorable for coastal regions. It is a switch that does not affect the default.
I will also update the UI (snap-desktop), see pull-request.