Bug report #20796

SVM Classification, SupportVectorMachineClassification(OpenCV)-Vector Field

Added by gabriele nolè over 1 year ago. Updated over 1 year ago.

Status:Closed
Priority:Normal
Assignee:Alexander Bruy
Category:Processing/SAGA
Affected QGIS version:3.4.2 Regression?:No
Operating System: Easy fix?:Yes
Pull Request or Patch supplied:Yes Resolution:fixed/implemented
Crashes QGIS or corrupts data:No Copied to github as #:28616

Description

Some saga algorithms (processing menu) do not allow you to choose a vector field. The tools mentioned above have this problem. The solution should be simple enough. I believe that the solution can be something like that...see attached pdf
(example change SVMClassification.txt)
  • before
    QgsProcessingParameterFeatureSource|ROI|Training Areas|-1|None|False
    QgsProcessingParameterSource|ROI_ID|Class Identifier|5|None|False
  • after
    ...............
    QgsProcessingParameterFeatureSource|ROI|Training Areas|-1|None|False
    QgsProcessingParameterField|ROI_ID|Class Identifier|None|ROI|3|False|True
    ...................

SVMClassification_saga.pdf (135 KB) gabriele nolè, 2018-12-13 11:04 AM

Associated revisions

Revision c6540a62
Added by Alexander Bruy over 1 year ago

[processing] fix description files for SVM SAGA algs (fix #20796)

Revision e0a8de47
Added by Alexander Bruy over 1 year ago

[processing] fix description files for SVM SAGA algs (fix #20796)

(cherry picked from commit c6540a627691caa2e49c21029df245e930aeacd6)

History

#1 Updated by Alexander Bruy over 1 year ago

  • Assignee set to Alexander Bruy
  • Status changed from Open to In Progress

#2 Updated by Alexander Bruy over 1 year ago

  • Pull Request or Patch supplied changed from No to Yes

#3 Updated by Alexander Bruy over 1 year ago

  • % Done changed from 0 to 100
  • Status changed from In Progress to Closed

#4 Updated by Alexander Bruy over 1 year ago

  • Resolution set to fixed/implemented

Also available in: Atom PDF