I actually commented on this on CRS the other day. I think adding an export/import tool to the custom CRS tool could help a lot, and the prj wkt format could be used or other formats as seen on spatialreference.org
Personally sqlite seems like a more efficient solution to me within the program, but I agree better access to the information can help some users. We might also consider a form in QGIS with boxes for each of the possible proj parameters rather than having to figure out the syntax (personally I copy past from spatialreference.org) Thanks, Alex On 01/30/2012 01:32 PM, Marco Hugentobler wrote: > Hi Alex > > Isn't it a regression to go from sqlite files to text files? Sqlite > allows to search tables with sql and afaik this is used in several places. > >> while moving and editing flat text files is much easier for ordinal users > > Ordinal users normally don't care about CRS at all. I agree with Andreas > here that it is much more difficult to have knowledge about CRS than > using an sqlite editor (or the commandline prompt). > > Regards, > Marco > > On 30.01.2012 20:58, Alexander Bruy wrote: >> Hi all, >> >> currently QGIS used srs.db to store projection definitions. But with >> this approach >> users can't reorganize CRS definitions as they want (always used >> predefined tree >> with predefined groups). >> >> This can be solved by switching to file-based storage of the CRS >> definitions as in >> latest ArcGIS versions or wxGIS. All CRS definitions are stored as >> files in WKT or >> SPR (preffered) format in subdirectories in some redefined folder and >> user can freely >> create new subdirectories and move files between them to organize >> CRS'es as he/she >> wants. >> >> Opinions, comments? >> >> Thanks > > _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
