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

Fixed gdalwarp call (was not matching extent to RTM) #73

Merged
merged 6 commits into from Nov 15, 2018

Conversation

Projects
None yet
2 participants
@tati-micheletti
Copy link
Contributor

tati-micheletti commented Nov 15, 2018

  • It is now comparable to raster::projectRaster
  • added a test to check for RTM crs, res and extent to be the same as output of postProcess() using gdalwarp system call

tati-micheletti and others added some commits Nov 15, 2018

added a test to check for RTM crs, res and extent to be the same as o…
…utput of postProcess() using gdalwarp system call

- which is then comparable to raster::projectRaster

@achubaty achubaty merged commit f2101ba into PredictiveEcology:development Nov 15, 2018

1 check was pending

continuous-integration/travis-ci/pr The Travis CI build is in progress
Details

achubaty added a commit that referenced this pull request Nov 15, 2018

update NEWS
with #71, #73
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment