On Saturday, 29 May 2021 5:07:44 AM AEST Gabriel Roldan wrote: > If that's all the meta info to store, anything not in the tile file itself > would be overkill.
> On Thu, 27 May 2021 at 07:47, Andrea Aime <[email protected]> > > wrote: > > Hi all,, > > while reviewing the OGC API Tiles spec, found these bits about returning > > HTTP headers, > > telling the client that a given portion of the tile cache might be fully > > empty, or completely solid, > > from that point on: > > > > > > https://github.com/opengeospatial/ogcapi-tiles/blob/master/core/standard/r > > ecommendations/tileset/REC_tc-deepfullempty.adoc > > > > If we had to implement this (it's just a recommendation) then we'd need to > > store meta-information around > > the tile, something the BlobStore interface and TileObject have no room > > for right now. I'd see it as something that could be useful when we're generating from vectors. So instead of keeping it associated with the Tile, you'd cache it to the side (somewhere) and use it on both the server side to save work and pass it down to the client side if everyone does the extension. Brad _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
