Feature request #3918
Consider use of the term "CRS" instead of "Projection" throughout QGIS
|Pull Request or Patch supplied:||Resolution:||fixed|
|Easy fix?:||No||Copied to github as #:||13942|
Recent OGC documents prefer the term "Coordinate Reference System" in situations that previously referred to "Spatial Reference System" or even "Projection".
We should review the usage of the term "Projection" in the cases where CRS is actually a more descriptive term.
The semantic difference between SRS and CRS is contrasted by the following ISO Standards:
- Spatial Referencing by Coordinates ( ISO 19111:2003 ) - e.g. http://loki.cae.drexel.edu/~wbs/ontology/iso-19111.htm
- Spatial Referencing by Geographic Identifier ( ISO 19112:2003 ) - e.g. http://loki.cae.drexel.edu/~wbs/ontology/iso-19112.htm
An SRS could refer to an address-based lookup scheme (as well as a coordinate-based lookup scheme) - therefore what QGIS currently deals with are more accurately called CRSs.
#4 Updated by Maciej Sieczka - almost 12 years ago
Replying to [comment:6 timlinux]:
Given the invasiveness of the changes required and that we are months away from 1.0.0 I'm shifting this over to 2.0.0.
What's invasive about changing several strings in the user interface?
Moreover this is definitely not a "feature request" but a "bug report". Simply, projection!=coordinate system, while QGIS uses the term "projection" in places where actually "coordinate system" should be used.
Projection is only an element of a coordinate system, and only of a projected one. Unprojected CS does not even have a projection.
Bogus terminology makes learning (and teaching) harder.
#5 Updated by Tim Sutton almost 12 years ago
- Status changed from Open to In Progress
My comment was based on the assumption that the original poster was referring to internal references to SRS in source code etc. ("CRS" instead of "Projection" throughout QGIS). I agree in the user interface it should be relatively painless to change and will look at doing so for 1.0.0
Changed the ticket type from bug (nothing is 'broken' by using one term over another here) to enhancement.
Changed severity to minor (nothing is broken although the term's useage may be incorrect it doesnt interfere with the normal functioning of the application).
#6 Updated by Maciej Sieczka - almost 12 years ago
Replying to [comment:8 timlinux]:
Changed the ticket type from bug (nothing is 'broken' by using one term over another here) to
But it is broken. Like if you called an apple a car.
Changed severity to minor (nothing is broken although the term's useage may be incorrect it
doesnt interfere with the normal functioning of the application).
Not "may be" but evidently is.
#7 Updated by Tim Sutton almost 12 years ago
- Status changed from In Progress to Closed
- Resolution set to fixed
I have fixed this with e1368a77 (SVN r8955). Please note its a superficial fix in as much I only changed end user visible aspects of QGIS to use the CRS term. As I mentioned in one of my previous comments above, changing through the whole of QGIS source base every useage (e.g. class name) to CRS is considerable work and I would not like to make such changes this close to 1.0. I'm closing this ticket, and will revisit the programmatic naming conventions as relates to CRS in a future release of QGIS.