Spotted some public functions (those not starting with an underscore) that don't appear to be documented yet at https://tudelftgeodesy.github.io/sarxarray/api_reference/:
Could either manually add entries for these to the docs/api_reference.md file, or to avoid situations like this in the future, use something like autodoc that will ensure public functions in a module are always documented.
Side note: May also want to update these lines in the __init__.py file?
|
from sarxarray import stack |
|
from sarxarray._io import from_binary, from_dataset, read_metadata |
|
from sarxarray.utils import complex_coherence, multi_look |
Not sure which functions you want to allow usage from top-level (e.g. a user calls sarxarray.crop instead of sarxarray.utils.crop), will leave it up to you to decide on the namespace.
Part of JOSS review at openjournals/joss-reviews#10492
Spotted some public functions (those not starting with an underscore) that don't appear to be documented yet at https://tudelftgeodesy.github.io/sarxarray/api_reference/:
read_metadatafunction. Xref Support reading metadata from SNAP corregistration results #82cropfunction, added in 64 Native cropping in radar coordinates #86Could either manually add entries for these to the
docs/api_reference.mdfile, or to avoid situations like this in the future, use something like autodoc that will ensure public functions in a module are always documented.Side note: May also want to update these lines in the
__init__.pyfile?sarxarray/sarxarray/__init__.py
Lines 1 to 3 in 3a11cd0
Not sure which functions you want to allow usage from top-level (e.g. a user calls
sarxarray.cropinstead ofsarxarray.utils.crop), will leave it up to you to decide on the namespace.Part of JOSS review at openjournals/joss-reviews#10492