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

[Oracle] Digitizing a new curve not working with QGIS 3.28.1 #51263

Closed
2 tasks
Jean-Roc opened this issue Dec 19, 2022 · 1 comment
Closed
2 tasks

[Oracle] Digitizing a new curve not working with QGIS 3.28.1 #51263

Jean-Roc opened this issue Dec 19, 2022 · 1 comment
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality Oracle data provider Regression Something which used to work, but doesn't anymore

Comments

@Jean-Roc
Copy link
Member

What is the bug or the crash?

Hi,

We have a change of behaviour when editing an Oracle layer to add or edit a curve using the digitizing tools, QGIS 3.24 saves a correct 3-nodes arc while 3.28 saves a densified linestring. The base layer and the project are strictly the same.

On this screencap, the upper geometry was created and saved with 3.24.2 and the lower with 3.28.1

curves

Steps to reproduce the issue

  1. Open an Oracle table (geom type multiline)
  2. QGIS 3.24.2
    1. Toggle editing
    2. Add a new line feature and toggle Digitize with Curve
    3. Trace a single curve and save
    4. Toggle the vertex tool and click on the created curve -> it shows a curve with only 3 nodes as intended
  3. QGIS 3.28.1
    1. Toggle editing
    2. Add a new line feature and toggle Digitize with Curve
    3. Trace a single curve and save
    4. Toggle the vertex tool and click on the created curve -> it shows a densified linestring

Versions

Both are the official windows packages

QGIS version 3.24.2-Tisler
QGIS code revision 13c1a02

QGIS version 3.28.1-Firenze
QGIS code revision fde3b8f

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

  • I tried with a new QGIS profile

Additional context

No response

@Jean-Roc Jean-Roc added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Dec 19, 2022
@nicogodet nicogodet added Regression Something which used to work, but doesn't anymore Digitizing Related to feature digitizing map tools or functionality Oracle data provider labels Dec 20, 2022
@troopa81 troopa81 self-assigned this Dec 20, 2022
troopa81 added a commit to troopa81/QGIS that referenced this issue Jan 5, 2023
@troopa81
Copy link
Contributor

troopa81 commented Jan 5, 2023

#51378 will fix new added layer, but for existing projects, you need to change the geometry type with CompoundCurve.

To migrate, with python, you can iterate on your layers and change the dataSource with the following instruction

new_uri=iface.activeLayer().dataProvider().dataSourceUri().replace("type=LineString","type=CompoundCurve")
iface.activeLayer.setDataSource(new_uri, 'test', 'oracle')

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! Digitizing Related to feature digitizing map tools or functionality Oracle data provider Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

3 participants