New processing manage fields algorithm

[Arnaud Morvan]

We want to create a new processing algorithm for manage table fields.

This new algorithm would have :
one standard input layer vector parameter
one standard output layer vector parameter

a specific fields mapping parameter composed, in columns
source field name (optionnal)
destination field name
destination type, length, precision
expression (default to the source field name)
the mapping would be initialized, when possible, with the input
layer fields.

In the dialog :
the first tab would present the normal input/output parameters and
a button to go to the next tab
the supplementary fields tab would contains the fields mapping

The final goal is to supply a user friendly interface to manage table
fields :
rename fields
change field types
add new fields based on expression
change fields order
and save the result as a new file, temporary file or memory layer

What do you think about this ? Any remarks ?

Arnaud

[Victor Olaya]

That's definitely a nice idea. I guess this was what you started working on
at the Hackfest but i wasn't of much help since i wasn't understanding the
idea completely... :-(

Here are some suggestions:

- There are some algorithms that have a custom UI and that you can take as
example. The vector calculator is probably one of them
- You will need to create a custom UI for the modeler as well, in case you
want to appear with a nicer dialog than the default one. Processing
supports that, but there is no algorithm currently using it. I can take
care of that once you have the basic UI finished
- Sounds like it would be a nice algorithm to have for editing a layer.
That is, to modify it instead of generating a new one. You can do that by
not having a visible output layer in the UI, and just returning the input
layer source path instead as output value.

Let me know if you have questions.

Regards

Post by Arnaud Morvan
We want to create a new processing algorithm for manage table fields.
one standard input layer vector parameter
one standard output layer vector parameter
a specific fields mapping parameter composed, in columns
source field name (optionnal)
destination field name
destination type, length, precision
expression (default to the source field name)
the mapping would be initialized, when possible, with the input layer
fields.
the first tab would present the normal input/output parameters and a
button to go to the next tab
the supplementary fields tab would contains the fields mapping
The final goal is to supply a user friendly interface to manage table
rename fields
change field types
add new fields based on expression
change fields order
and save the result as a new file, temporary file or memory layer
What do you think about this ? Any remarks ?
Arnaud
_______________________________________________
Qgis-developer mailing list
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Régis Haubourg]

hi, vert nice idea.I would miss a tool to import a destination schema like in
ETL tools (and why later not a graphical mapping tool like tmap component in
talend).
cheers , régis



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/New-processing-manage-fields-algorithm-tp5168441p5168510.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.