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

Elevation profile PDF export #57880

Closed
2 tasks done
zsiki opened this issue Jun 25, 2024 · 0 comments · Fixed by #58033
Closed
2 tasks done

Elevation profile PDF export #57880

zsiki opened this issue Jun 25, 2024 · 0 comments · Fixed by #58033
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Profile tool

Comments

@zsiki
Copy link
Contributor

zsiki commented Jun 25, 2024

What is the bug or the crash?

Exporting any elevation profile to PDF there is a scaling problem in the created PDF. Only a very small part of the upper left corner of the profile is visible in the exported PDF. Export the profile as image is correct using the same chart ranges as in PDF export.
I suppose it is a scaling problem.

Steps to reproduce the issue

  1. Open an elevation raster/DEM
  2. Open the elevation profile panel
  3. Capture a line on the DEM
  4. Click on Export PDF tool
  5. Accept default chart ranges ans save
  6. Open the exported PDF to see the issue.

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>
QGIS version 3.34.8-Prizren QGIS code revision 9164233
Qt version 5.15.3
Python version 3.10.12
GDAL/OGR version 3.4.1
PROJ version 8.2.1
EPSG Registry database version v10.041 (2021-12-03)
GEOS version 3.10.2-CAPI-1.16.0
SQLite version 3.37.2
PDAL version 2.3.0
PostgreSQL client version 14.12 (Ubuntu 14.12-0ubuntu0.22.04.1)
SpatiaLite version 5.0.1
QWT version 6.1.4
QScintilla2 version 2.11.6
OS version Ubuntu 22.04.4 LTS
       
Active Python plugins
ClipMultipleLayers 3.2.0
quick_map_services 0.19.34
cesium_ion v1.0.2
fuzzy_join 0.1
StreetView 3.2
thematics 0.6
QuickOSM 2.2.3
processing_saga_nextgen 1.0.0
arearatio 0.2
configurable_search 0.5
grassprovider 2.12.99
db_manager 0.1.20
processing 2.12.99
QGIS version 3.34.8-Prizren QGIS code revision [9164233](https://github.com/qgis/QGIS/commit/91642333b10) Qt version 5.15.3 Python version 3.10.12 GDAL/OGR version 3.4.1 PROJ version 8.2.1 EPSG Registry database version v10.041 (2021-12-03) GEOS version 3.10.2-CAPI-1.16.0 SQLite version 3.37.2 PDAL version 2.3.0 PostgreSQL client version 14.12 (Ubuntu 14.12-0ubuntu0.22.04.1) SpatiaLite version 5.0.1 QWT version 6.1.4 QScintilla2 version 2.11.6 OS version Ubuntu 22.04.4 LTS

Active Python plugins
ClipMultipleLayers
3.2.0
quick_map_services
0.19.34
cesium_ion
v1.0.2
fuzzy_join
0.1
StreetView
3.2
thematics
0.6
QuickOSM
2.2.3
processing_saga_nextgen
1.0.0
arearatio
0.2
configurable_search
0.5
grassprovider
2.12.99
db_manager
0.1.20
processing
2.12.99

Supported QGIS version

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

New profile

Additional context

No response

@zsiki zsiki added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Jun 25, 2024
nyalldawson added a commit to nyalldawson/QGIS that referenced this issue Jul 9, 2024
QPdfWriter doesn't return the output resolution as the device
physicalDpiX(?!), so let's hack around this by just setting
the output resolution to match the value reported by
physicalDpiX...

Fixes qgis#57880
nyalldawson added a commit that referenced this issue Jul 18, 2024
QPdfWriter doesn't return the output resolution as the device
physicalDpiX(?!), so let's hack around this by just setting
the output resolution to match the value reported by
physicalDpiX...

Fixes #57880
qgis-bot pushed a commit that referenced this issue Jul 18, 2024
QPdfWriter doesn't return the output resolution as the device
physicalDpiX(?!), so let's hack around this by just setting
the output resolution to match the value reported by
physicalDpiX...

Fixes #57880
nyalldawson added a commit that referenced this issue Jul 31, 2024
QPdfWriter doesn't return the output resolution as the device
physicalDpiX(?!), so let's hack around this by just setting
the output resolution to match the value reported by
physicalDpiX...

Fixes #57880
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Profile tool
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants