Is it possible to translate tile requests from a mapping engine wanting Google Map style tiles into tile requests from a geopackage file? If not, where can I find information about how to create a mapping engine that handles the dizzying array of options provided by geopackage (as in, something that would help with understanding how to use srid, min_x, pixel_x_size, tile_width, matrix_width, zoom_level, and screen coords to determine which tiles at which rotation displayed where)
I have used MBTiles in the past to supply tiles to a mapping engine that requested tiles in Google Map style. This worked well as MBTiles uses the same projection and uses TMS for the tiling scheme. This meant I only needed to modify the y value of each request to translate from TMS to Google Maps style.
Two of the problems that I am having trouble figuring out how to overcome in regards to translating google maps tile requests to a specific tile in geopackage is how to handle the potential difference in projection, and how to handle the difference in origin. (By difference in origin I mean Google maps starts 0,0 at the top left corner of the world (because it assumes the whole world has data), whereas geopackage starts at the top left of the data (which might be the whole world but likely will not be))
If it makes any difference I am trying to do this in C++ using Qt and QtLocation.