> My information on GeoPackages may be outdated, since the specification has > changed many times since I read it last. > But as far as I remember, the main goal was that a GeoPackage is a > complete/finished collection of data ready for deployment. I'm reasonably familiar with GeoPackage, and don't recall it ever only being considered a "finished" product. The current interop experiment (related tables) is actually about recording extra observations in GeoPackage.
> Even though it may be internally a Database, it should not be treated as > such. > So the word 'append' is inappropriate in this concept. "Citation needed" :-) > If the condition on which the original raster coverage was created no longer > applies, then a new raster coverage must be created that fulfill these new > conditions. That is a narrow and inappropriate view. In any case, I'm happy to build the whole raster, just need a way to do it. > In this case you are extending the bounds of the raster coverage, which may > work when extending in a East/West direction, but not in a North/West > direction (assuming that North/West is 0,0). With mbtiles this would be no > problem since the use a world wide tms numbering for the tiles. You can do this with GeoPackage too, supported by GDAL as one of the tiling schemes (http://www.gdal.org/drv_geopackage_raster.html) > Creating a new raster coverage, with new extent/bounds and sources should be > the idea. This is my main need. I was only looking for how to create a raster coverage with different content at different zoom levels. I will try the gdalwarp solution next, although I did make it work with a simple bash loop and some spatialite SQL commands. Brad _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
