-
Notifications
You must be signed in to change notification settings - Fork 372
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
GeoDataset with pytorch lightning datamodule not compatible with BoundingBox in sample #1056
Comments
Solution is to subclass from |
Oh, sorry wasn't aware of that. Looking at that should we change bbox and crs to be represented in a compatible datatype instead of deleting it? I think that is still valuable information that people might want to use during their pipeline for visualizations etc |
CRS might be tricky. Bbox might be possible but I would rather wait until someone has a use case for it (probably stitching together prediction patches). It might be as simple as implementing |
I have a use case for it: #1407 Our models (object detection) outputs pixel coordinates relative to the input patch. Then I need to convert them into the full image pixel coords for non-max-suppression. Then I convert them to WGS-84 for delivery to end users. The same workflow would likely apply to segmentation. So I need a way to access the patch-transforms after prediction. |
We can close this. |
Description
I am using a custom
RasterDataset
with aLightningDataModule
. However, pytorch-lightning does not like aBoundingBox
object being returned as part of the sample as it cannot move it todevice
:If I change the code to turn the
BoundingBox
into a list, everything works.Steps to reproduce
Version
0.4.0
The text was updated successfully, but these errors were encountered: