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

Add parsing of raster symbology #23

Open
bogind opened this issue Dec 4, 2024 · 0 comments
Open

Add parsing of raster symbology #23

bogind opened this issue Dec 4, 2024 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@bogind
Copy link
Contributor

bogind commented Dec 4, 2024

This has been a sore point for a while now, users asking for at least minimal support for raster styling.

As there can be multiple CIM layer types who are considered "raster", it might be better to refactor the current way qlyrxStyler.apply_lyrx_symbols identifies symbology types isn't suited for use with raster layers (including raster image/tile/elevation services) as they do not have a renderer attribute - see CIMRasterLayer Class Members.

TODO:

Globally:

  • Checking each layerDefinition's type attribute should be the first step in applying symbology, to identify unsupported layer types. see list of layer types under the CIMBaseLayer Class
  • low priority - apply LayerElevation for all layer types. Useful for all layer types, but might be more important in rasters, elevation models in particular.
  • Move messaging to styler or other sub-modules, currently reporting success in cases where exceptions are caught or styles are not supported

For Rasters:

There are likely other relevant attributes, but these are a good place to start

@bogind bogind added enhancement New feature or request help wanted Extra attention is needed labels Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant