GeoServer 2.10.0 does not work with raster GeoPackages conforming to the OGC GeoPackage Encoding Standard - Requirement 45 for the tile matrix. OGC GeoPackage tile matrices have their tile origin at the upper left. GeoPackages with an origin at the upper left are not rendered correctly in GeoServer.
This issue was fixed by cloning the GeoTools 16.0 GeoPackage Module (gt_geopkg) to the WorldWind GeoPackage Module (worldwind_gt_geopkg) and modifying the following classes:
GeoPackageReader: changed the tile set origin from the bottom left to the top left; also added support for a default coverage name for better integration into GeoServer;
GeoPackageFormat: changed the name from "GeoPackage (mosaic)" to "GeoPackage (tiles)" to distinguish between coverages from the original GeoPackage module.
GeoServer 2.10.0 does not work with raster GeoPackages conforming to the OGC GeoPackage Encoding Standard - Requirement 45 for the tile matrix. OGC GeoPackage tile matrices have their tile origin at the upper left. GeoPackages with an origin at the upper left are not rendered correctly in GeoServer.
It appears the GeoTools' GeoPackage implementation--used by the GeoServer Community GeoPackage Extension--expects a tile origin at the lower left (possibly using an OSGeo TMS specification).