Skip to content

Confusing daterange and bbox filter methods on ImageCollection classes #67

Closed

Description

@soxofaan

Base class ImageCollection (in openeo.imagecollection)

  • defines date_range_filter(self, start_date,end_date)
    • not implemented (just pass)
    • flagged in docblock as deprecated (use filter_daterange instead)
  • defines filter_daterange(self, extent)
    • implemented basically by calling date_range_filter()

Child classes (ImageCollectionClient in openeo.rest and GeotrellisTimeSeriesImageCollection in GeoPyspark driver):

  • override date_range_filter(self, start_date,end_date) with actual implementation
  • no def of filter_daterange(self, extent)

Same pattern for bbox_filter and filter_bbox

So the deprecated methods are implemented and the new non-deprecated calls forward to deprecated implementations? Shouldn't it be the other way around?

Activity

  1. self-assigned this
    on Jul 18, 2019
  2. added 12 commits that reference this issue on Jul 19, 2019
  3. added 3 commits that reference this issue on Aug 5, 2019
  4. added 3 commits that reference this issue on Aug 26, 2019
  5. soxofaan commented on Sep 4, 2019

    @soxofaan
    MemberAuthor

    issue resolved by #69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions