Uploaded image for project: 'GeoTools'
  1. GEOT-5833

Image mosaic won't respond to requests outside of the coverage bbox it cached in memory

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 17.3, 18.0
    • Component/s: imagemosaic plugin
    • Labels:
      None

      Description

      This is an issue, as mosaics granules can be harvested in a number of ways that do not update said bounding box.
      Examples:

      • A cluster in which only one node is doing harvesting via the GeoServer REST API or similar tool (it may get an up to date bbox, but the others won't)
      • The index being managed by some external process directly, without going thought the mosaic code machinery at all

      Re-computing the full mosaic bbox at every request is not possible for performance reasons (a time based mosaic can contain millions of items, only some store can do quick bbox aggregation, and we need a precise bbox anyways), as an alternative, compute the area actually covered by granules within the request parameters (bbox, filter, elevation, max granules and the like) making the cost of bbox calculation proportional, and way smaller, than building then actual mosaic response itself.

        Attachments

          Activity

            People

            • Assignee:
              aaime Andrea Aime
              Reporter:
              aaime Andrea Aime
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: