-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GRASS output is not georeferenced #15227
Comments
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Victor Olaya (@volaya) Should be fixed now
|
Author Name: Giovanni Manghi (@gioman) seems solved to me, please reopen if necessary.
|
Author Name: Giovanni Manghi (@gioman) at the end seems still true, for example with v.buffer as the .prj file is not created. May be other tools are affected.
|
Author Name: Victor Olaya (@volaya) I have just tried v.buffer, and the result has a prj file. One question: does your input data has projection information?? I have noticed that there are problems with GRASS if you use data with no projection, and just using the "Set layer CRS" command in QGIS solves it. Maybe if the layer has no CRS, SEXTANTE should take the project CRS, assuming it has the same one.
|
Author Name: Giovanni Manghi (@gioman) Victor Olaya wrote:
Hi Victor, I have tested with a couple of vectors, with a proper .prj file. Sample attached.
|
Author Name: Giovanni Manghi (@gioman) still true on qgis 2.0.1
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav) More useful info from the mailing list. See thread here:
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Markus Metz (@metzm)
Original Redmine Issue: 5702
Affected QGIS version: 2.4.0
Redmine category:processing/grass
Assignee: Victor Olaya
The GRASS backend uses a temporary location without CRS (xy location). The output is therefore not georeferenced: shapefiles in tempdata have no *.prj file and GeoTIFFs no embedded CRS info. With regard to vector output, the -e flag of v.out.ogr does not have any effect because the location is a xy location. This can be fixed by the user with "Save as..." or "Set layer CRS".
It would be more comfortable if the output would already be georeferenced. This could be done by creating a second temporary location during import, using the CRS of the input data, i.e. [r.in.gdal|v.in.ogr] location=<name_of_new_location>, then switch to this location and proceed as before. The second temporary location will have the CRS of the input data and will use this CRS for export.
The text was updated successfully, but these errors were encountered: