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.

Sign up for GitHub

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

Jump to bottom

Task: take into account GDT_Int8 #50907

Closed
2 tasks
rouault opened this issue Nov 16, 2022 · 0 comments · Fixed by #51586
Closed
2 tasks

Task: take into account GDT_Int8 #50907

rouault opened this issue Nov 16, 2022 · 0 comments · Fixed by #51586
Assignees
@rouault
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Rasters Related to general raster layer handling (not specific data formats)

Comments

@rouault
Copy link
Contributor

rouault commented Nov 16, 2022

What is the bug or the crash?

Now that https://gdal.org/development/rfc/rfc87_signed_int8.html has been implemented in GDAL 3.7.0dev, QGIS GDAL raster interface may need a few changes when testing GDAL raster data type to take into account the new GDT_Int8 value

Steps to reproduce the issue

Versions

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

  • I tried with a new QGIS profile

Additional context

No response
@rouault rouault added Rasters Related to general raster layer handling (not specific data formats) Data Provider Related to specific vector, raster or mesh data providers Bug Either a bug report, or a bug fix. Let's hope for the latter! labels Nov 16, 2022
@rouault rouault self-assigned this Jan 25, 2023
rouault added a commit to rouault/QGIS that referenced this issue Jan 25, 2023
@rouault
[GDAL provider] Minimal support for GDT_Int8 of GDAL 3.7.0
4df384e 
Fixes qgis#50907

GDAL 3.7.0 brings GDT_Int8, which triggers compiler warnings
in QGIS due to those new enumeration values not being handled.

We do a minimal handling of them, by exposing them as QGIS Int16 rasters

A more ambitious fix would be to add proper Int8 support to QGIS.
@rouault rouault mentioned this issue Jan 25, 2023
Merged
rouault added a commit to rouault/QGIS that referenced this issue Jan 25, 2023
@rouault
[GDAL provider] Minimal support for GDT_Int8 of GDAL 3.7.0
70bd0ca 
Fixes qgis#50907

GDAL 3.7.0 brings GDT_Int8, which triggers compiler warnings
in QGIS due to those new enumeration values not being handled.

We do a minimal handling of them, by exposing them as QGIS Int16 rasters

A more ambitious fix would be to add proper Int8 support to QGIS.
nyalldawson pushed a commit that referenced this issue Jan 26, 2023
@rouault @nyalldawson
[GDAL provider] Minimal support for GDT_Int8 of GDAL 3.7.0
6cb82ad 
Fixes #50907

GDAL 3.7.0 brings GDT_Int8, which triggers compiler warnings
in QGIS due to those new enumeration values not being handled.

We do a minimal handling of them, by exposing them as QGIS Int16 rasters

A more ambitious fix would be to add proper Int8 support to QGIS.
qgis-bot pushed a commit that referenced this issue Jan 26, 2023
@rouault @github-actions
[GDAL provider] Minimal support for GDT_Int8 of GDAL 3.7.0
f30b1f0 
Fixes #50907

GDAL 3.7.0 brings GDT_Int8, which triggers compiler warnings
in QGIS due to those new enumeration values not being handled.

We do a minimal handling of them, by exposing them as QGIS Int16 rasters

A more ambitious fix would be to add proper Int8 support to QGIS.
nyalldawson pushed a commit that referenced this issue Jan 27, 2023
@rouault @nyalldawson
[GDAL provider] Minimal support for GDT_Int8 of GDAL 3.7.0
5986a80 
Fixes #50907

GDAL 3.7.0 brings GDT_Int8, which triggers compiler warnings
in QGIS due to those new enumeration values not being handled.

We do a minimal handling of them, by exposing them as QGIS Int16 rasters

A more ambitious fix would be to add proper Int8 support to QGIS.
domi4484 pushed a commit to domi4484/QGIS that referenced this issue Jan 27, 2023
@rouault @domi4484
[GDAL provider] Minimal support for GDT_Int8 of GDAL 3.7.0
68c5a68 
Fixes qgis#50907

GDAL 3.7.0 brings GDT_Int8, which triggers compiler warnings
in QGIS due to those new enumeration values not being handled.

We do a minimal handling of them, by exposing them as QGIS Int16 rasters

A more ambitious fix would be to add proper Int8 support to QGIS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rouault rouault

Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Rasters Related to general raster layer handling (not specific data formats)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[GDAL provider] Minimal support for GDT_Int8 of GDAL 3.7.0 rouault/QGIS
1 participant
@rouault