-
Notifications
You must be signed in to change notification settings - Fork 47
Open
Labels
enhancementFeature improvement or requestFeature improvement or request
Description
While editing the documentation (and slightly the workflows) in #852, I noted some things we can improve:
- The
topoworkflow expects areference_elevsubsection betweeninputsandpath_to_elev, which is unexpected (and not really documented) because the workflow works on a single elevation input. We can probably remove, except if we intend to add support for multiple elevation data in the future? - Having
to_vcrsas input intopo/accuracyseems unnecessary: Thesampling_gridargument already specifies which grid/CRS should be used when comparing both (reference or to-be-aligned). The vertical CRS being part of the CRS, it's transformed automatically during that step, so it never needs to be transformed during input reading withto_vcrs. The user should only be able to set or override the vertical CRS of the input data (set_vcrs). - The
accuracyworkflow detailed description has two sub-tabs forreference/tba_elevwithin the tabinputs, but the description are exactly the same word-for-word for each. We could simplify by having those as a single page to avoid sub-tabs.
Some thoughts of global parameters that could be useful for users to access:
- The
resamplingduring reprojection, or during point-grid interpolation (bilinear, cubic, etc). We could use the global GeoUtils parameters for this. - The
nodata_propagationbehaviour during reprojection/interpolation.
Metadata
Metadata
Assignees
Labels
enhancementFeature improvement or requestFeature improvement or request