New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate pipeline units #906

Merged
merged 2 commits into from Mar 27, 2018

Conversation

Projects
None yet
1 participant
@kbevers
Member

kbevers commented Mar 26, 2018

As suggested here, steps in a pipeline are now checked for compliance.
If the right side units in step n differ from the left side units in
step n+1 the pipeline can't be constructed and an error is raised.

@kbevers kbevers force-pushed the kbevers:validate-pipeline-units branch 2 times, most recently from 8d40497 to a71a27f Mar 26, 2018

kbevers added some commits Mar 26, 2018

Validate that units match between pipeline steps
As suggested in [0], steps in a pipeline are now checked for compliance.
If the right side units in step n differ from the left side units in
step n+1 the pipeline can't be constructed and an error is raised.

[0] https://lists.osgeo.org/pipermail/grass-dev/2018-March/088123.html
Change units of axisswap to 'whatever'
Since units are validated during pipeline setup we need to make sure
that axisswap can be used for more than just projected outputs.

@kbevers kbevers force-pushed the kbevers:validate-pipeline-units branch from a71a27f to bcd647f Mar 27, 2018

@kbevers kbevers merged commit 9874f60 into OSGeo:master Mar 27, 2018

3 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage increased (+0.01%) to 75.769%
Details

@kbevers kbevers added this to the 5.1.0 milestone Mar 27, 2018

@kbevers kbevers deleted the kbevers:validate-pipeline-units branch Jul 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment