Skip to content
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

Closed
qgib opened this issue May 21, 2015 · 9 comments
Closed

Export Spatialite point layer to CSV fails on Geometry AS_XY #20892

qgib opened this issue May 21, 2015 · 9 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@qgib
Copy link
Contributor

qgib commented May 21, 2015

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


@qgib
Copy link
Contributor Author

qgib commented May 21, 2015

Author Name: Saber Razmjooei (@saberraz)


Confirmed also in master but not in 2.6.1.

It is a regression bug and marked as blocker.


  • priority_id was changed from Low to Severe/Regression
  • operating_system was changed from OSGeo4W to
  • os_version was changed from Windows 7 Prof. x64 to

@qgib
Copy link
Contributor Author

qgib commented May 21, 2015

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was configured as Future Release - High Priority

@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2015

Author Name: Jürgen Fischer (@jef-n)


Is that spatialite layer multipoint?


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2015

Author Name: Saber Razmjooei (@saberraz)


It is MULTIPOINT, indeed.

@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2015

Author Name: Jochen Huber (@huber-j)


Yes, it is MULTIPOINT. Tested with POINT, and it works okay.

@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2015

Author Name: Jürgen Fischer (@jef-n)


Jochen Huber wrote:

Yes, it is MULTIPOINT. Tested with POINT, and it works okay.

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.


  • status_id was changed from Feedback to Closed
  • resolution was changed from to duplicate

@qgib
Copy link
Contributor Author

qgib commented Jun 1, 2015

Author Name: Saber Razmjooei (@saberraz)


I think it is a problem with QSpatialite plugin. The ones converted to Spatialite through ogr2ogr are fine.

@qgib
Copy link
Contributor Author

qgib commented Jun 2, 2015

Author Name: Jochen Huber (@huber-j)


Yes, QSpatialite seems to always (often unnecessarily) generate MULTIPOINT feature sets when importing from QGIS layers.
An error message would be helpful in any case (e.g. "Option AS_XY not supported for MULTIPOINT datasets").
I even think it would be possible to export MULTIPOINT data with AS_XY:
Write one line for every POINT, using the same attributes for every MULTIPOINT part
Add a column "MULTIPART ID" with distinct values für distinct features and shared values for all parts of a MULTIPOINT.

@qgib
Copy link
Contributor Author

qgib commented Jun 2, 2015

Author Name: Saber Razmjooei (@saberraz)


You can always log another ticket as a feature request.
romain974/qspatialite#32

@qgib qgib added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 25, 2019
@qgib qgib added this to the Future Release - High Priority milestone May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

1 participant