Rich Fecher

Currently, there is an assumption from the WMS rendering that each pyramid level fully represents the grid coverage. For large multi-image mosaics, this may not always be the case. We...

JobContextAdapterStore keys, JobContextIndexStore keys, GeoWaveInputKey, and GeoWaveOutputKey, seem like they should have a datastore ID associated with them so that distributed processes that involve multiple datastores do not need to...

Raster configuration panel

2

URL is insufficient for geowave raster configuration. Following PostGIS raster support a separate panel can be created that is more intuitive: [PG Raster sample code](https://github.com/geoserver/geoserver/blob/master/src/community/pgraster/src/main/java/org/geoserver/web/data/store/pgraster/PGRasterCoverageStoreEditPanel.java) [PG Raster documentation](http://docs.geoserver.org/latest/en/user/community/pgraster/pgraster.html)

This became awkward when we indexed 5-dimensional data with multiple lat/lon definitions, but in general can be done more elegantly as it has been leading to some ugly code matching...

This can be thought of much like PostgreSQL's vacuum analyze.