Opened 13 years ago
Closed 13 years ago
#3548 closed bug (fixed)
CRS defaults not sticking
| Reported by: | jctull | Owned by: | nobody |
|---|---|---|---|
| Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
| Component: | Projection Support | Version: | Trunk |
| Keywords: | default crs | Cc: | |
| Must Fix for Release: | Yes | Platform: | OS X |
| Platform Version: | Awaiting user input: | no |
Description
When I set the default CRS, the OTF default project CRS, or the CRS in the project properties, it does not stick. For me, I am trying to use epsg 26911, but it keeps reverting to epsg 2153 for each of those options.
Change History (4)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
It would be nice if the epsg code would be respected. Seeing a deprecated crs selected is confusing.
comment:4 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I believe it's due to r15361. The crs definitions are now considered the same, so qgis takes the first one:
+proj=utm +zone=11 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs +proj=utm +zone=11 +ellps=GRS80 +datum=NAD83 +units=m +no_defs