[COG] Media type

[Pedro Goncalves]

I would suggest the usage of the profile link relation
image/tiff; profile=<URI-reference>

the value to be defined (for example it could be https://www.cogeo.org/ )

Further reading at
https://tools.ietf.org/html/rfc6906#section-3.1
and check also
https://ruben.verborgh.org/articles/fine-grained-content-negotiation/

FYI this is already being used by GML 
https://www.iana.org/assignments/media-types/application/gml+xml


> On 25 Jul 2019, at 04:34, Chris Holmes <cholmes at planet.com> wrote:
> 
> I'm +1 on cloud-optimized=true over cog
> 
> And I do think we should formalize it into a spec, starting with the gdal details as the base.
> 
> I started a repo ages ago https://github.com/cogeotiff/cog-spec but never got anywhere past porting the GDAL page over, as I got overtaken by other tasks :(
> 
> But doing it in its own repo had mostly been since OGC hadn't established an actual geotiff spec / repo, so I'd say it probably makes sense to make an extension for COG of some sort that builds on https://github.com/opengeospatial/geotiff/ and hopefully is even in the same repo.
> 
> On Wed, Jul 24, 2019 at 1:56 PM Even Rouault <even.rouault at spatialys.com> wrote:
> > Sidebar: I feel like "cloud-optimized geotiff" is pretty vague about the
> > implementation and "cog" even more so. If this sub type were to be
> > formalized, I'd hope we could come up with something more technically clear
> > and less buzzy like "http optimized" or "direct access".
> 
> https://gdal.org/drivers/raster/cog.html#file-format-details
> could serve as a base for this.
> 
> -- 
> Spatialys - Geospatial professional services
> http://www.spatialys.com
> _______________________________________________
> COG mailing list
> COG at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/cog
> _______________________________________________
> COG mailing list
> COG at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/cog