I've made this offer before, but here it is again: my company can host on "
libtiff.info", with DNS already in place and fronted through Cloudflare,
with TLS.
Depending on what's needed on the server, could be running in the next
couple of hours, possibly Anycast to 30 servers globally for speed
FWIW, we definitely use tiffsplit quite a bit.
Kemp Watson
On Wed, Jun 14, 2023 at 9:48 AM Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
> On Wed, 14 Jun 2023, Greg Troxel wrote:
> >
> > I am guessing that pretty much nobody wants to use these any more, and
> > that anything that needs
LibTIFF’s naming is confusing - there really isno such thing as a “directory “.
There are IFDs, and there are SubIFDs. And they are completely different from
each other.
W. Kemp Watson
Objective Pathology Services
Toronto, Canada
http://www.objectivepathology.com
k...@objectivepathology.com
I just found this also... downloaded 4.4.0, and got this oddness:
-- Building tiff version 4.5.0
-- libtiff library version 6.0.0
Should this not be more like:
Building TIFF version 6.0
libtiff library version 4.4.0
It's pretty much exactly backwards!
Also, building on Windows with VS 2022,
Not sure about your particular file, but we extract hundreds of thousands of
YCbCr JPEG images from TIFFs every day...
W. Kemp Watson
Objective Pathology Services
Toronto, Canada
http://www.objectivepathology.com
k...@objectivepathology.com
tel. +1 (647) 783-4431
> On May 21, 2022, at 3:37
This is a bit of an offhand comment without much thought, but perhaps TIFF
group should focus only on describing the physical manifestation of the
pixels, and the more "usage" oriented metadata is best left to other
entities?
That's a pretty rough comment, and I know there's a fair bit of history
So, you can certainly find a place to plug your data. Maybe a question is “just
how standard is standard”? Is this just for Google use, or applicable to GDAL
or GeoTIFF or other environments too?
W. Kemp Watson
Objective Pathology Services
Toronto, Canada
http://www.objectivepathology.com
Again, no deep knowledge:
Do you mean not the start/end of an image export, but of an image acquisition
over time, like a satellite traversal creating a stitched image from individual
fields acquired over minutes or maybe hours?
I would have assumed GeoTIFF would have already considered this;
Hi Simon:
Speaking from close to no knowledge here...
Is it that critical to know both start and end times of an export? Can you
perhaps average them to one value?
Can you assume DateTime is UTC with your particular files and use cases?
Not sure if this is helpful, just posing a simple
It's indeed used in slide imaging fairly commonly, but with
"non-conforming" TIFFtags (33003 and 33005 instead of 34712), and
essentially to Leonard's point... why?
It's a historical artifact from 20-year-old CPUs: the tradeoff here is
essentially a Gaussian pyramid for speed vs a Laplacian
It's pretty straightforward to do it yourself via the "RawTile" calls.
Kemp Watson
On Fri, Apr 1, 2022 at 2:34 PM miguel medalha wrote:
> Hello
>
> Are there any plans to include JPEG2000 compression (OpenJPEG, for
> example)?
>
> Thank you.
>
>
>
Milian, are these images for geomapping or digital pathology? I am guessing
so since you mentioned mipmap subIFDs.
If so, there is a good 20-25 years of experience in how to efficiently
write and read these large files, and the solution has inevitably come down
to tiling the data, and absolutely
12 matches
Mail list logo
