We currently use geotiff.js as our underlying TIFF reader in the browser. Despite the name, it's really not a Geo-specific TIFF reader at all. It's hard to find a single API it exports that is specific to geospatial (other than parsing GeoTIFF metadata).
This means it's much closer to our async-tiff: geotiff.js is a low-level TIFF reader.
But it's quite useful to have a higher-level abstraction, as we found while creating the Python async-geotiff. For example, geotiff.js doesn't do any special handling of mask IFDs, making it very easy to incorrectly render masks as normal IFDs (#196).
Following the API of async-geotiff, we should create higher-level GeoTIFF API, at least for internal use
We currently use geotiff.js as our underlying TIFF reader in the browser. Despite the name, it's really not a Geo-specific TIFF reader at all. It's hard to find a single API it exports that is specific to geospatial (other than parsing GeoTIFF metadata).
This means it's much closer to our
async-tiff: geotiff.js is a low-level TIFF reader.But it's quite useful to have a higher-level abstraction, as we found while creating the Python
async-geotiff. For example, geotiff.js doesn't do any special handling of mask IFDs, making it very easy to incorrectly render masks as normal IFDs (#196).Following the API of async-geotiff, we should create higher-level GeoTIFF API, at least for internal use