-
Notifications
You must be signed in to change notification settings - Fork 5
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
Make band filtering more consistent #29
Comments
soxofaan
added a commit
that referenced
this issue
Nov 5, 2019
In GeotrellisTimeSeriesImageCollection:
|
jdries
added a commit
that referenced
this issue
Jun 23, 2020
Also cleaned up layercatalog a bit. The idea is now that the pyramidFactories are responsible for applying the band filter directly. |
jdries
added a commit
that referenced
this issue
Jun 24, 2020
great, thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implementation of band filtering and handling is confusing at the moment
in
GeoPySparkLayerCatalog.load_collection
:s3_jp2_pyramid
,file_pyramid
, and some others do handle band filtering immediately, whileaccumulo_pyramid
ands3_pyramid
do notimage_collection.band_filter(band_indices)
, which will probably fail for the cases where band filtering already happenedin
GeotrellisTimeSeriesImageCollection
:_band_index
which only considers the first band of the list, this is probably a temp hack that has to be eliminatedband_filter
does a special case for source type "file", but that is probably not correct anymore (now that that there are multiple source types that handle band filtering up front)The text was updated successfully, but these errors were encountered: