fixed handling of projections not stored in qgis database.

wonder · wonder · commit 1db6c93b9a12 · 2009-03-22T09:38:10.000Z
now the projection string shouldn't be lost. git-svn-id: http://svn.osgeo.org/qgis/trunk/qgis@10398 c8812cc2-4d05-0410-92ff-de0c093fc19c
diff --git a/src/core/qgscoordinatereferencesystem.cpp b/src/core/qgscoordinatereferencesystem.cpp
@@ -430,8 +430,14 @@ bool QgsCoordinateReferenceSystem::createFromProj4( const QString theProj4String
       }
     }
   }
+  
+  // if we failed to look up the projection in database, don't worry. we can still use it :)
+  if (!mIsValidFlag)
+  {
+    setProj4String(theProj4String);
+  }
+
 
-  // NOTE: if its still empty after all the above steps then, the projection string is lost. Is that bad?
   return mIsValidFlag;
 }
 

Original file line number	Diff line number	Diff line change
`@@ -430,8 +430,14 @@ bool QgsCoordinateReferenceSystem::createFromProj4( const QString theProj4String`
`430`	`430`	`}`
`431`	`431`	`}`
`432`	`432`	`}`
	`433`	`+`
	`434`	`+ // if we failed to look up the projection in database, don't worry. we can still use it :)`
	`435`	`+ if (!mIsValidFlag)`
	`436`	`+ {`
	`437`	`+ setProj4String(theProj4String);`
	`438`	`+ }`
	`439`	`+`
`433`	`440`
`434`		`- // NOTE: if its still empty after all the above steps then, the projection string is lost. Is that bad?`
`435`	`441`	`return mIsValidFlag;`
`436`	`442`	`}`
`437`	`443`