Open
Description
What is the bug or the crash?
Adding a custom, user-defined CRS with a WKT definition results in the CRS being added twice.
Steps to reproduce the issue
- Open the Settings menu and select Customs Projections.
- Click the Green Plus icon to add a new CRS
- Enter a name, e.g. Albers South Africa
- Set Format to WKT
- Paste the following WKT text into the Parameters box:
- PROJCS["Albers_Equal_Area_Conic_South_Africa",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137,298.257223563]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Albers"],PARAMETER["False_Easting",0],PARAMETER["False_Northing",0],PARAMETER["central_meridian",24],PARAMETER["Standard_Parallel_1",-18],PARAMETER["Standard_Parallel_2",-32],PARAMETER["latitude_of_origin",0],UNIT["Meter",1]]
- Click the Ok button
- Open the Project menu and select Properties at the CRS tab
- Look in the User-defined section and the newly added CRS appears twice
Versions
<style type="text/css"> p, li { white-space: pre-wrap; } </style>QGIS version | 3.36.1-Maidenhead | QGIS code revision | 3e58945 |
---|---|---|---|
Qt version | 5.15.3 | ||
Python version | 3.9.18 | ||
GDAL/OGR version | 3.8.4 | ||
PROJ version | 9.3.1 | ||
EPSG Registry database version | v10.098 (2023-11-24) | ||
GEOS version | 3.12.1-CAPI-1.18.1 | ||
SQLite version | 3.41.1 | ||
PDAL version | 2.6.0 | ||
PostgreSQL client version | 16.2 | ||
SpatiaLite version | 5.1.0 | ||
QWT version | 6.1.6 | ||
QScintilla2 version | 2.13.4 | ||
OS version | Windows 10 Version 2009 | ||
Active Python plugins | |||
quick_map_services | 0.19.34 | ||
SpreadsheetLayers | 2.1.2 | ||
db_manager | 0.1.20 | ||
grassprovider | 2.12.99 | ||
MetaSearch | 0.3.6 | ||
processing | 2.12.99 |
Active Python plugins
quick_map_services
0.19.34
SpreadsheetLayers
2.1.2
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
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