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

tolerate different resolutions between RTM and output raster when `useSAcrs = TRUE` #54

Merged
merged 5 commits into from Sep 14, 2018

Conversation

Projects
None yet
3 participants
@CeresBarros
Contributor

CeresBarros commented Sep 14, 2018

Bugfix when checking resolutions in .projectInputs:

  • when using rasterToMatch and useSAcrs, it can occur that the final resolutions differ due to the different CRS (e.g. when studyArea crs is in degree units and rasterToMatchis in meters)
  • in this case different resolutions should be tolerated
@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Sep 14, 2018

Coverage Status

Coverage increased (+0.006%) to 80.167% when pulling c41beb0 on CeresBarros:development into ba28b75 on PredictiveEcology:development.

coveralls commented Sep 14, 2018

Coverage Status

Coverage increased (+0.006%) to 80.167% when pulling c41beb0 on CeresBarros:development into ba28b75 on PredictiveEcology:development.

@eliotmcintire eliotmcintire merged commit 3f68a90 into PredictiveEcology:development Sep 14, 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.006%) to 80.167%
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment