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

ZipDatasets don't have an index therefore you can't sample properly #135

Closed
calebrob6 opened this issue Sep 14, 2021 · 0 comments · Fixed by #144
Closed

ZipDatasets don't have an index therefore you can't sample properly #135

calebrob6 opened this issue Sep 14, 2021 · 0 comments · Fixed by #144
Milestone

Comments

@calebrob6
Copy link
Member

calebrob6 commented Sep 14, 2021

All of our samplers take an index that we use to find places that we'd like to sample from. When we create a ZipDataset there isn't a single index that we can use to sample from. When the component datasets of the ZipDatasets don't overlap spatially this is a problem. For example, this happens when I want to combine several splits from the ChesapeakeCVPR dataset into a larger dataset to train with.

This is a specific instance of some of the stuff in #86.

@adamjstewart adamjstewart reopened this Nov 20, 2021
@adamjstewart adamjstewart added this to the 0.2.0 milestone Nov 20, 2021
@adamjstewart adamjstewart added utilities Utilities for working with geospatial data and removed utilities Utilities for working with geospatial data labels Jan 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants