> When generating a GeoPackage via WPS it seems the extent (i.e. minx, miny, > maxx, maxy) for the tile matrix set(s) stored in the gpkg_tile_matrix_set table > of the resulting GeoPackage are set to the bbox supplied in the request as > opposed to the actual extent of the tile matrix set. The result is that when the > requested bbox is smaller (or different) than the tile matrix set extent the tiles > are offset when the GeoPackage is consumed by something like QGIS. This is > because the tile coordinates for tiles within the GeoPackage are in the context > of the original tile matrix set and not the requested bbox. If so (no reason to doubt you, just didn't verify it myself), that would be a bug. Can you file a ticket at https://osgeo-org.atlassian.net/projects/GEOS/issues to ensure that this is not forgotten?
Also, if you haven't already tried it, you might like to upgrade if not on the latest release. There has been a fair amount of work done on GeoPackage recently. Brad ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
