-
Notifications
You must be signed in to change notification settings - Fork 380
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
Adding the CVPR Chesapeake dataset #100
Conversation
Ready for review -- just need to upload the new version of the dataset to lila.science and fill in the links. |
I don't love having to add 2 more deps (seems every PR adds at least 1 dep) but these 2 seem unavoidable in the long run anyway. |
pyproj 3.1 doesn't support python 3.6 @adamjstewart - thoughts on dropping 3.6 https://pyproj4.github.io/pyproj/stable/history.html see pyproj4/pyproj#782 for the threading problem that was fixed in 3.1 (I'm imagining we will run into problems if we try to do projections in |
I would prefer not to drop 3.6 just because of a dependency. Numpy also doesn't support 3.6. Can we just install an older version on 3.6? |
sure how do you do that |
I would like to test with older versions of pyproj and shapely. Both of these are almost the latest version available. Having the minimum required version so high makes it difficult for people to install. When I was testing the minimum supported version I basically created a new conda environment with Python 3.6, then pip installed all the deps, then pip installed successively older versions of each package until the tests no longer passed. |
Can you do this if you then? I do not think it is hard for users to install new versions of packages, |
I can once you add unit tests that actually run this code. No minimum version at all is better than setting the latest version to be the minimum version. Many packages aren't necessarily compatible with the latest version of everything. For example, rasterio does not support the latest version of GDAL. If we decided to require the latest version of GDAL, we wouldn't be able to build rasterio at all. |
Generally true, but that's not the case here. There exists a valid set of our required packages that work with pyproj>=3.0 and shapely>=1.7.0 so I do not see what the problem is. In any case, I made a test for the shape warping functionality that we're using from pyproj and shapely, I'll go ahead and test some major versions of the two libraries so that this can be merged. |
If users only installed torchgeo and its dependencies that would be true, but users tend to write their own code and install things like torchgeo into much larger environments where conflicts may be possible. |
Codecov Report
@@ Coverage Diff @@
## main #100 +/- ##
=======================================
Coverage ? 83.65%
=======================================
Files ? 31
Lines ? 1927
Branches ? 0
=======================================
Hits ? 1612
Misses ? 315
Partials ? 0 Continue to review full report at Codecov.
|
torchgeo/datasets/cvpr_chesapeake.py
Outdated
crs = CRS.from_epsg(3857) | ||
res = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are these actually used for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
defining the properties from GeoDataset
Might also need to add deps to |
Just realized we forgot to add this dataset to the docs: 8ab4211 |
Dataset from https://lila.science/datasets/chesapeakelandcover
Some notes:
_check_integrity
behaves differently from other places, see Dataset downloading expected behavior pt. 2 #99__getitem__
we grab the single geotiff that the query intersects with, warp the query geom to the CRS of that file, then return the data corresponding to the warped query.To do:
["naip-new", "lc"]
should return only those layers