-
-
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
Export Spatialite point layer to CSV fails on Geometry AS_XY #20892
Comments
Author Name: Saber Razmjooei (@saberraz) Confirmed also in master but not in 2.6.1. It is a regression bug and marked as blocker.
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Jürgen Fischer (@jef-n) Is that spatialite layer multipoint?
|
Author Name: Saber Razmjooei (@saberraz) It is MULTIPOINT, indeed. |
Author Name: Jochen Huber (@huber-j) Yes, it is MULTIPOINT. Tested with POINT, and it works okay. |
Author Name: Jürgen Fischer (@jef-n) Jochen Huber wrote:
So I guess it's another problem. AS_XY doesn't work for MULTIPOINT. Question is how the multipoint layer was created - maybe related to the two related tickets.
|
Author Name: Saber Razmjooei (@saberraz) I think it is a problem with QSpatialite plugin. The ones converted to Spatialite through ogr2ogr are fine. |
Author Name: Jochen Huber (@huber-j) Yes, QSpatialite seems to always (often unnecessarily) generate MULTIPOINT feature sets when importing from QGIS layers. |
Author Name: Saber Razmjooei (@saberraz) You can always log another ticket as a feature request. |
Author Name: Jochen Huber (@huber-j)
Original Redmine Issue: 12796
Affected QGIS version: 2.8.2
When exporting a Spatialite point layer via "Save as...", geometry is only exported when selecting "AS_WKT". When selecting AS_XY or AS_YX, only the attribute values are exported (see attached files).
When exporting from a Shapefile, the geometry is written correctly with the option AS_XY.
Related issue(s): #18990 (relates), #19856 (duplicates)
Redmine related issue(s): 10584, 11597
The text was updated successfully, but these errors were encountered: