Bug report #3996
wrong extents in shapefile.
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||windows||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||worksforme|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||13985|
I opened a shapefile, selected some features, translated them, then saved my file. I then discovered that the bounds saved in the shapefile were wrong.
When I later opened the file (with wrong bounds) in an older version of qgis(1.4.0), and exported it in another file the bound were recomputed and the new file had correct bounds.
The wrong shapefile in joined files is named "multi_bati_final", and the one with correctly recomputed bounds "multi_bati_final_with_correct_bounds".
#1 Updated by Paolo Cavallini almost 12 years ago
- Category set to Vectors
- Pull Request or Patch supplied set to No
#2 Updated by Giovanni Manghi over 11 years ago
- Target version set to Version 1.7.4
#3 Updated by Paolo Cavallini about 11 years ago
- Crashes QGIS or corrupts data set to No
- Affected QGIS version set to master
- Target version changed from Version 1.7.4 to Version 1.8.0
#4 Updated by Paolo Cavallini almost 11 years ago
- Target version changed from Version 1.8.0 to Version 2.0.0
#5 Updated by Jürgen Fischer almost 9 years ago
- Target version changed from Version 2.0.0 to Future Release - Lower Priority
#6 Updated by Médéric RIBREUX over 7 years ago
- Status changed from Open to Feedback
what did you mean by bounds (extent of the layer ?) and translated (reprojected ?) ?
Could you still reproduce this bug on a recent version of QGIS ? If it is the case, can you supply at least three layers (in order to easily reproduce the bug):
- the original one (not translated/reprojected).
- the bad translated one.
- the layer that should have been produced by QGIS.
#7 Updated by Giovanni Manghi over 7 years ago
- Status changed from Feedback to Closed
- Resolution set to worksforme
if there was an issue this seems long gone, reopen if necessary.