You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now pxm has bash scripts, python scripts, external python commands and bash functions to assert various things about raster data. All of these methods have slightly different modes of operation (some raise exceptions, some return a special value, some use exit codes, etc) and are not very easy to test.
I'd like to move all the boolean tests from pxm to subcommands of raster-tester. Basically anytime we need to ask a yes/no question about a raster or set of rasters, this command should be the place to go.
So far we have
compare
isempty
But we could pull in
aligned
crosses-dateline
is_evil
is_lossy
validate
This would also give us an opportunity to define and standardize exactly what a Yes/No response should look like and how the bash scripts should handle them
exit codes
what gets output to stdout/stderr
The text was updated successfully, but these errors were encountered:
whacky idea: what if we made this into a pair of rio scripts: rio isit and rio arethey and used options to specify multiple attributes to test (rather than having subcommands for everything).
So instead of raster-tester isempty blah.tif we would have rio isit --empty blah.tif and we could chain it together with other tests like rio isit --empty --happy --not-crosses-dateline blah.tif
Without thinking too deeply about any of the implications, this seems like an awesome approach. Makes it a little easier to understand just what we're testing for. The syntax is 👌 imo.
Right now pxm has bash scripts, python scripts, external python commands and bash functions to assert various things about raster data. All of these methods have slightly different modes of operation (some raise exceptions, some return a special value, some use exit codes, etc) and are not very easy to test.
I'd like to move all the boolean tests from pxm to subcommands of
raster-tester
. Basically anytime we need to ask a yes/no question about a raster or set of rasters, this command should be the place to go.So far we have
But we could pull in
This would also give us an opportunity to define and standardize exactly what a Yes/No response should look like and how the bash scripts should handle them
The text was updated successfully, but these errors were encountered: