Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PB-1053: cog ignore alpha channel #1102

Draft
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

sommerfe
Copy link
Contributor

No description provided.

pakb and others added 4 commits October 15, 2024 09:36
Instead of having a big chunk of code that does the heavy lifting (loosely copied or similar in places like the load-kml and load-gpx plugin, plus the drag and drop handler) I gathered all this logic in one place, giving it the necessary options/config to handle all situation and be written only once.

There is now only one way of dealing with a KML/KMZ/GPX file from external/local source, the dedicated parser.

List of other things done while working on this :
 - changing updateLayer action to receive a layer ID instead of an index (was never used because of the hassle to get this index). I replaced uses of updateLayers when it was used for a single layer.
 - move all extent utils in... extentUtils.js
 - FileInput can now receive params for i18n placeholders in the error message
 - Fixing a missing rename with the local file disclaimer, it was not the correct tooltip shown for local files because of that
 - Adding a zoom to extent button in the layer list, if the layer provides an extent (meaning KML/GPX and soon COG)
renaming the layer type from GeoTIFF (which we shouldn't support much, too big of a risk of users loading very large files and crashing the app because of lack of memory) and clarifying that we support COG (Cloud Optimized GeoTIFF)

Adding a dedicated parser for COG files

improvements made during this work package :
 - read the no data value from the COG metadata (instead of arbitrarily setting it to zero)
 - re-load COG extent if the layer was added at startup through a URL param
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants