[QGIS-trac] Re: [Quantum GIS] #2092: fTools export/add geometry
tool should use source dataset CRS as target dataset CRS
Quantum GIS
qgis at qgis.org
Sun Nov 15 12:17:22 EST 2009
#2092: fTools export/add geometry tool should use source dataset CRS as target
dataset CRS
-----------------------------------------------------+----------------------
Reporter: marisn | Owner: cfarmer
Type: bug | Status: new
Priority: major: does not work as expected | Milestone: Version 1.4.0
Component: Python plugins and bindings | Version: HEAD
Resolution: | Keywords:
Platform_version: | Platform: Gentoo
Must_fix: No | Status_info: 0
-----------------------------------------------------+----------------------
Comment (by marisn):
Replying to [comment:2 cfarmer]:
> Replying to [ticket:2092 marisn]:
>
> All fTools functions should use the input dataset CRS for all output
datasets. However, this means that, for example, shapefiles with no .prj
file will automatically default to the project default CRS (often WGS84).
In other words, the fTools functions ignore any manually specified CRS
info. Is it possible that this is the cause for the misspecified
shapefile? 'On the fly' option should *not* affect any fTools functions...
fTools doesn't use input CRS for output. Target CRS is determined by
settings in "Settings" -> "Options" -> "CRS". By default (?) it will use
WGS84 as target CRS and there is no such option as "input CRS".
I have created more generic enhancement ticket #2093 about project CRS
handling in QGIS might solve also this issue, still if fTools result
generation is not affected by OTFR, there still is a room for bogus
results as described per this bug. Thus input CRS as target CRS is the
safest option.
--
Ticket URL: <https://trac.osgeo.org/qgis/ticket/2092#comment:3>
Quantum GIS <http://qgis.org>
Quantum GIS is an Open Source GIS viewer/editor supporting OGR, PostGIS, and GRASS formats
More information about the QGIS-trac
mailing list