Projection issue: freezes when reprojecting a csv file

[qgib]

Author Name: dr - (dr -)
Original Redmine Issue: 2337
Affected QGIS version: master
Redmine category:projection_support
Assignee: Magnus Homann

---

1. Open attached csv file with delimited text plugin;

2. Set on the fly CRS transformation and set WGS84 /UTM zone 43N CRS (Projected);

3. Click on layer name and choose Zoom to layer extent;

4. Open any shapefile in lon/lat wgs84 projection;

At result QGIS freezes.

---

• 54-22.csv (dr -)

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

If the points you are importing are in the WGS84 /UTM zone system, then you need to configure the vector crs accordingly in the vector properties -> general tab. Alternatively save the imported csv as shapefile (right button in the legend -> save as shapefile) and qgis will ask you the crs of the vector.

In my case (Ubuntu linux, qgis 1.4), with OTFR enabled, the imported csv defined with the wrong crs and other layers, I'm not experiencing freezes, but I cannot see anything in the canvas.

But that is not the worst part:

define the correct crs (WGS84 /UTM zone 43N CRS) for the imported csv, enable otfr and define as project crs WGS84 /UTM zone 43N CRS. Add a wgs84 layer (example: http://thematicmapping.org/downloads/TM_WORLD_BORDERS-0.3.zip ), it will show fine.

Zoom out, at some point qgis crashes:

Fatal: ASSERT: "std::abs( r_d ) > SMALL_NUM && std::abs( r_n ) > SMALL_NUM" in file /home/gio/qgis/qgis_unstable/src/core/qgsclipper.h, line 270
Aborted

[qgib]

Author Name: Maxim Dubinin (@simgislab)

---

freezes for me too

that was the point probably, yes, trying to project already projected vector is bad, but is it possible to indicate it with more obvious error message and not just freeze QGIS on trying to continue working with it like nothing happened?

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Replying to [comment:2 gislab]:

freezes for me too

that was the point probably, yes, trying to project already projected vector is bad, but is it possible to indicate it with more obvious error message and not just freeze QGIS on trying to continue working with it like nothing happened?

When importing csv files it would be enough to have the plugin ask for the CRS(?).

[qgib]

Author Name: Maxim Dubinin (@simgislab)

---

Replying to [comment:3 lutra]:

When importing csv files it would be enough to have the plugin ask for the CRS(?).
I think this would be a good solution.

[qgib]

Author Name: Anne Ghisla (Anne Ghisla)

---

Replying to [comment:4 gislab]:

Replying to [comment:3 lutra]:

When importing csv files it would be enough to have the plugin ask for the CRS(?).
I think this would be a good solution.

With QGIS Trunk r 15304, and Options > CRS > Prompt for CRS, then in Project properties I set projection as WGS84 /UTM zone 43N and OFTR enabled, everything goes fine (load wgs84 layers and zoom out).

If I set as QGIS default Options > CRS > Global default CRS, I load the csv layer and see it with wrong coordinates, then I set Project properties as above. I zoom to layer extent and get a popup window titled "qgis " and with text "Could not draw 54-22 because" and an empty space. In the shell I read:

failed with error: latitude or longitude exceeded limits

Debug: /home/anne/src/qgis/src/core/qgscoordinatetransform.cpp: 490: (transformCoords) throwing exception

Debug: /home/anne/src/qgis/src/core/qgscoordinatetransform.cpp: 304: (transformInPlace) rethrowing exception

Debug: /home/anne/src/qgis/src/core/qgsvectorlayer.cpp: 1107: (draw) Failed to transform a point while drawing a feature of type _. Rendering stopped. forward transform of

(10316.6, 23900.4)

This is almost OK, it's not a freeze and the user can safely remove the faulty layer and fix CRS settings. However the error message does not show up in the popup window.

Anne

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• fixed_version_id was changed from Version 1.7.0 to Version 1.7.4

[qgib]

Author Name: Paolo Cavallini (@pcav)

---

• fixed_version_id was changed from Version 1.7.4 to Version 1.8.0
• crashes_corrupts_data was configured as 0
• version was configured as master

[qgib]

Author Name: Paolo Cavallini (@pcav)

---

• fixed_version_id was changed from Version 1.8.0 to Version 2.0.0

[qgib]

Author Name: Magnus Homann (@homann)

---

• assigned_to_id was changed from nobody to Magnus Homann
• pull_request_patch_supplied was configured as 0

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

This does not happens any more on master.

---

• resolution was changed from to fixed
• status_id was changed from Open to Closed