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

MSSQL: Add Multipolygon Feature creates wrong geometrytype #19174

Closed
qgib opened this issue Jul 3, 2014 · 9 comments
Closed

MSSQL: Add Multipolygon Feature creates wrong geometrytype #19174

qgib opened this issue Jul 3, 2014 · 9 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers

Comments

@qgib
Copy link
Contributor

qgib commented Jul 3, 2014

Author Name: Jan Lippmann (@j-lippmann)
Original Redmine Issue: 10793
Affected QGIS version: 3.0.0
Redmine category:data_provider/mssql
Assignee: Nyall Dawson


if i digitise a new multipolygonfeature in a MSSQL-Multipolygonlayer (with avoid intersections of new features) and force intersections while digitising,
the geometrytype of the new polygon is "Polygon" and not as expected "Multipolygon".

from this moment all other new added "Multipolygons" are "Polygons"

the problem occurs with the mssql provider and qgis 2.2 and 2.4
there are no problems under postgres provider.(oracle provider not tested)

snapping options and multipolygontable connection are in the screenshot

can anybody reproduce this problem?


@qgib
Copy link
Contributor Author

qgib commented Jul 3, 2014

Author Name: Jan Lippmann (@j-lippmann)


I've added screencast which showing the problem.


  • 7585 was configured as multipolygon_problem.7z

@qgib
Copy link
Contributor Author

qgib commented Jul 3, 2014

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


  • priority_id was changed from High to Normal

@qgib
Copy link
Contributor Author

qgib commented Jun 14, 2015

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


  • category_id was changed from Digitising to Data Provider/MSSQL

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 0
  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Feb 18, 2018

Author Name: Jan Lippmann (@j-lippmann)


this issue is still present in actual master 2.99. please give a feedback, if sample data needed.

@qgib
Copy link
Contributor Author

qgib commented Feb 18, 2018

Author Name: Nyall Dawson (@nyalldawson)


As far as I'm aware no one is working on fixing this bug - if it's critical to you please consider sponsoring a fix or raising discussion on the qgis-dev list.


  • description was changed from if i digitise a new multipolygonfeature in a MSSQL-Multipolygonlayer (with avoid intersections of new features) and force intersections while digitising,
    the geometrytype of the new polygon is "Polygon" and not as expected "Multipolygon".

from this moment all other new added "Multipolygons" are "Polygons"

the problem occurs with the mssql provider and qgis 2.2 and 2.4
there are no problems under postgres provider.(oracle provider not tested)

snapping options and multipolygontable connection are in the screenshot

can anybody reproduce this problem? to if i digitise a new multipolygonfeature in a MSSQL-Multipolygonlayer (with avoid intersections of new features) and force intersections while digitising,
the geometrytype of the new polygon is "Polygon" and not as expected "Multipolygon".

from this moment all other new added "Multipolygons" are "Polygons"

the problem occurs with the mssql provider and qgis 2.2 and 2.4
there are no problems under postgres provider.(oracle provider not tested)

snapping options and multipolygontable connection are in the screenshot

can anybody reproduce this problem?

@qgib
Copy link
Contributor Author

qgib commented Feb 25, 2018

Author Name: Giovanni Manghi (@gioman)


  • subject was changed from MSSQL- Add Multipolygon Feature creates wrong geometrytype to MSSQL: Add Multipolygon Feature creates wrong geometrytype
  • version was changed from 2.4.0 to 3.0.0

@qgib
Copy link
Contributor Author

qgib commented Oct 5, 2018

Author Name: Nyall Dawson (@nyalldawson)


  • status_id was changed from Open to In Progress
  • assigned_to_id was configured as Nyall Dawson

@qgib
Copy link
Contributor Author

qgib commented Oct 5, 2018

Author Name: Nyall Dawson (@nyalldawson)


Applied in changeset 81db005.


  • done_ratio was changed from 0 to 100
  • status_id was changed from In Progress to Closed

@qgib qgib closed this as completed Oct 5, 2018
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers labels May 25, 2019
@qgib qgib added this to the Future Release - High Priority milestone 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! Data Provider Related to specific vector, raster or mesh data providers
Projects
None yet
Development

No branches or pull requests

1 participant