Skip to content
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

Upgrade to GeoTrellis 3.0 #5231

Closed
notthatbreezy opened this issue Oct 24, 2019 · 1 comment · Fixed by #5393
Closed

Upgrade to GeoTrellis 3.0 #5231

notthatbreezy opened this issue Oct 24, 2019 · 1 comment · Fixed by #5393
Assignees
Labels
maintenance Things we need to do that aren't bugs or new features, but keep us sane and help the app

Comments

@notthatbreezy
Copy link
Contributor

Problem description

There is a new GeoTrellis release that changes some library functionality, moves things that were in contrib to core, and should allow us to hopefully remove any dependency on spark(!!).

The goal of this upgrade should be to use new functionality makes sense, but hold off on larger architectural changes for their own issues (e.g. probably shouldn't switch to using RasterSourceF at this point) but I think it should include the removal of our custom BacksplashRasterSource for the default GeoTiffRasterSource that allows passing in an optional GeoTiff (which we can do with our GeoTiffInfo change).

Expected Behavior or Output

Upgraded GeoTrellis in RF

@notthatbreezy notthatbreezy added the maintenance Things we need to do that aren't bugs or new features, but keep us sane and help the app label Oct 24, 2019
@jcahail jcahail modified the milestone: RF Sprint 12/12 - 01/02 Dec 13, 2019
@jisantuc
Copy link
Contributor

jisantuc commented Apr 8, 2020

As we stay behind on GT before Cats 2.0, it gets harder and harder to use typelevel ecosystem libs, since the versions we're stuck on are behind the versions that are documented (specifically with STTP). As we use the RF API and artifacts to support client work, that makes it harder and harder over time efficiently to re-use our own code. We should do this soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Things we need to do that aren't bugs or new features, but keep us sane and help the app
Development

Successfully merging a pull request may close this issue.

3 participants