Feature request #10251

Processing - Order Model saves values

Added by Antonio Locandro almost 6 years ago. Updated over 5 years ago.

Status:Rejected
Priority:Normal
Assignee:Victor Olaya
Category:Processing/Modeller
Pull Request or Patch supplied:No Resolution:wontfix
Easy fix?:No Copied to github as #:18688

Description

This is how model saves the order of values

PARAMETER:ParameterVector|VECTORLAYER_INPUTROUTEVECTOR|input_route_vector|1|False
167.0,60.0
VALUE:HARDCODEDPARAMVALUE_FIELD_PRECISION_0===2
VALUE:HARDCODEDPARAMVALUE_FIELD_TYPE_0===0
VALUE:HARDCODEDPARAMVALUE_FIELD_LENGTH_0===6
VALUE:HARDCODEDPARAMVALUE_FIELD_NAME_0===calc_dist
ALGORITHM:qgis:addfieldtoattributestable
168.0,160.0

However the algorithm shows this order in screen
Field Name
Field Type
Field Length
Field Precision
Output layer

It would be very useful in order to check models that values where saved in the same order as presented in screen

PARAMETER:ParameterVector|VECTORLAYER_INPUTROUTEVECTOR|input_route_vector|1|False
167.0,60.0
VALUE:HARDCODEDPARAMVALUE_FIELD_NAME_0===calc_dist
VALUE:HARDCODEDPARAMVALUE_FIELD_TYPE_0===0
VALUE:HARDCODEDPARAMVALUE_FIELD_LENGTH_0===6
VALUE:HARDCODEDPARAMVALUE_FIELD_PRECISION_0===2
ALGORITHM:qgis:addfieldtoattributestable
168.0,160.0

order.png - model screenshot (25.6 KB) Antonio Locandro, 2014-05-13 07:38 AM

History

#1 Updated by Antonio Locandro almost 6 years ago

This is another sample

VALUE:HARDCODEDPARAMVALUE_FIELD_TYPE_1===1
VALUE:HARDCODEDPARAMVALUE_FIELD_PRECISION_2===2
VALUE:HARDCODEDPARAMVALUE_FIELD_TYPE_2===1
VALUE:HARDCODEDPARAMVALUE_FIELD_PRECISION_0===2
VALUE:HARDCODEDPARAMVALUE_FIELD_TYPE_0===1
VALUE:HARDCODEDPARAMVALUE_FIELD_NAME_2===diff_dist
VALUE:HARDCODEDPARAMVALUE_FIELD_NAME_0===calc_dist
VALUE:HARDCODEDPARAMVALUE_FIELD_NAME_1===text_dist
VALUE:HARDCODEDPARAMVALUE_FIELD_LENGTH_2===6
VALUE:HARDCODEDPARAMVALUE_FIELD_LENGTH_1===6
VALUE:HARDCODEDPARAMVALUE_FIELD_LENGTH_0===6
VALUE:HARDCODEDPARAMVALUE_FIELD_PRECISION_1===2

A little bit hard to check things since they aren't grouped or in order by layer, this would be easier

VALUE:HARDCODEDPARAMVALUE_FIELD_NAME_0===calc_dist
VALUE:HARDCODEDPARAMVALUE_FIELD_TYPE_0===1
VALUE:HARDCODEDPARAMVALUE_FIELD_LENGTH_0===6
VALUE:HARDCODEDPARAMVALUE_FIELD_PRECISION_0===2
VALUE:HARDCODEDPARAMVALUE_FIELD_NAME_1===text_dist
VALUE:HARDCODEDPARAMVALUE_FIELD_TYPE_1===1
VALUE:HARDCODEDPARAMVALUE_FIELD_LENGTH_1===6
VALUE:HARDCODEDPARAMVALUE_FIELD_PRECISION_1===2
VALUE:HARDCODEDPARAMVALUE_FIELD_NAME_2===diff_dist
VALUE:HARDCODEDPARAMVALUE_FIELD_TYPE_2===1
VALUE:HARDCODEDPARAMVALUE_FIELD_LENGTH_2===6
VALUE:HARDCODEDPARAMVALUE_FIELD_PRECISION_2===2

#2 Updated by Giovanni Manghi almost 6 years ago

  • Category set to 64

#3 Updated by Giovanni Manghi over 5 years ago

  • Category deleted (64)
  • Project changed from 78 to QGIS Application

#4 Updated by Giovanni Manghi over 5 years ago

  • Category set to Processing/Modeller

#5 Updated by Giovanni Manghi over 5 years ago

  • Assignee set to Victor Olaya

#6 Updated by Alexander Bruy over 5 years ago

  • Status changed from Open to Rejected
  • Resolution set to wontfix

This makes no sence, while models itself works as expected

#7 Updated by Antonio Locandro over 5 years ago

Does make sense that it saves in the same order the modeler asks for parameter, especially when debugging when processing fails to work or has bugs, however it seems there is no interest in changing its current behaviour so I will have to live with it

Also available in: Atom PDF