https://issues.qgis.org/https://issues.qgis.org/favicon.ico2011-03-06T08:27:19ZQGIS Issue TrackingQGIS Application - Bug report #3548: CRS defaults not stickinghttps://issues.qgis.org/issues/3548?journal_id=242492011-03-06T08:27:19ZBorys Jurgiel
<ul></ul><p>I believe it's due to <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/839824406553a5952e440389cb4c572a8fac066c" title="be less restrictive on interpreting CRSes git-svn-id: http://svn.osgeo.org/qgis/trunk@15361 c881...">83982440</a> (SVN r15362). The crs definitions are now considered the same, so qgis takes the first one:</p>
<p>+proj=utm +zone=11 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs<br />+proj=utm +zone=11 +ellps=GRS80 +datum=NAD83 +units=m +no_defs</p> QGIS Application - Bug report #3548: CRS defaults not stickinghttps://issues.qgis.org/issues/3548?journal_id=242502011-03-06T08:37:22ZJohn Tull
<ul></ul><p>It would be nice if the epsg code would be respected. Seeing a deprecated crs selected is confusing.</p> QGIS Application - Bug report #3548: CRS defaults not stickinghttps://issues.qgis.org/issues/3548?journal_id=242512011-03-15T04:33:21ZBorys Jurgiel
<ul></ul><p>It should be ok now</p> QGIS Application - Bug report #3548: CRS defaults not stickinghttps://issues.qgis.org/issues/3548?journal_id=242522011-03-15T04:33:41ZBorys Jurgiel
<ul><li><strong>Resolution</strong> set to <i>fixed</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>