mike-000

> This fixes a regression that's prevented us upgrading to the latest openlayers version. Recent tile source changes regressed the ability to fetch image tiles without requiring cors requests. Technically...

The result of `overlay` would be affected by the rendering order of the features. Whatever operation is used it is unlikely to give meaningful results if 3 or more features...

That approach should work https://stackblitz.com/edit/js-isqbdhz6?file=package.json,index.html,index.js You should give your offset projections unique codes otherwise the transform lookups will not work correctly. `source.getView()` will return the projection set in the source,...

If it is not working as expected for some files I suspect those GeoTIFFs are not in EPSG:4326. To handle that case you would need to preload the GeoTIFF to...

If the GeoTIFF does not have a projection OpenLayers will use the view projection (if the view is set by `source.getView()` it would default to EPSG:3857).

You can check for `error` state in the change event ``` source.on('change', (e) => { if (source.getState() === 'error') { const error = source.getError(); // handle error } }); ```

Yes, without the matrix the debug tiles would still appear, just not in the same place as the GeoTIFF. The code setting tile (texture) sizes to integer values is still...

I think a better way would be for TileDebug to take a `source` option. `projection`, `tileGrid`, `wrapX`, `zDirection` and `transformMatrix` could be obtained from that without exposing any additional getters...

> Yes, that would make for a nice API. And it could also work when the source is not yet ready, by waiting until the source is ready before the...

Yes, feature styles might go eventually (KML could be a problem) but currently there are places where flat styles can be used (layers, Draw and Modify interactions) while they cannot...