[gdal-dev] Introducing the cogger and godal projects

[thomas bonfort]

There is no c++ version, although there are no specific go constructs
that would prevent a port to c++ if you really wanted to.
It could also be possible to export a C function from the go code,
exposed as a shared library, that would only work on local files
and who's signature would be something like:

int rewrite(char *outputfilename, char *intpufilename);

--
thomas

On Tue, Jun 8, 2021 at 10:32 AM Javier Jimenez Shaw <j1 at jimenezshaw.com> wrote:
>
> Thanks Thomas!
> I see this is in Go. Is there a C++ version of it? Or how easy is to use it from C++ code?
> Thanks.
> .___ ._ ..._ .. . ._.  .___ .. __ . _. . __..  ... .... ._ .__
> Entre dos pensamientos racionales
> hay infinitos pensamientos irracionales.
>
>
>
> On Fri, 4 Jun 2021 at 18:48, Even Rouault <even.rouault at spatialys.com> wrote:
>>
>> I haven't benchmarked cogger but I'd expect it to be much faster than gdal_translate -of COG (if your input is GeoTIFF and always properly tiled and compressed of course!). gdal_translate -of COG uses generic GDAL API to acquire input data, which implies decompression / recompression. And in particular, if using input GeoTIFF with lossy compressed methods such as JPEG or WebP, cogger will avoid adding any new loss.
>>
>> Le 04/06/2021 à 18:28, thomas bonfort a écrit :
>>
>> I haven't extensively used -of COG (the cogger code actually predates the cog driver) but iirc there are at least some cases where it uses an intermediate file, which would imply that cogger does offer some speedups. I'll let Even confirm...
>> Regards,
>> Thomas
>>
>> Le ven. 4 juin 2021 à 18:14, <Matt.Wilkie at yukon.ca> a écrit :
>>>
>>> Is cogger specifically for the scenario where your converting a large imagery library that already exists, but isn't cloud optimized? i.e. Does it offer any advantages over the one step `gdal_translate -of cog ...` when starting fresh?
>>>
>>> Cheers,
>>>
>>> Matt
>>> Geomatics Analyst | Environment | T 867-667-8133 | Yukon.ca
>>> Hours: 08:30-16:30, Tue-Wed: Office, Thu-Fri: Remote.
>>
>>
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>>
>> --
>> http://www.spatialys.com
>> My software is free, but my time generally not.
>>
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/gdal-dev