Processing Algorithms for import/export/validate #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current implementation
This PR introduces process algorithms for data import / export / validate with ili2pg and ili2gpkg:
They contain all the settings provided by the Model Baker Plugin:
Path through
The input parameters concerning the database connection are passed through as output parameters, means you can easily connect these algorithms in the graphical modeler:
Situation with the input parameter
While we have at the moment just a plain list of input parameters, this is not that comfy to use when starting the algorithms directly. As well it would make sense to have an option to read the connection parameters (like we do it in model baker) from a layer. But not only. It should be optional to enter manually, read from layer or use an existing db connection (defined in the data source manager).
An option would be to create two more algorithms:
But even nicer would be an almighty input parameter:
(Source: https://excalidraw.com/#json=vzYp9UoP3hOo3p19Iz7-e,He6nXlycWuRxn3h42DXUeQ )
But:
Desicion
We decided against having this almighty input parameter, because it's very inflexible in the modeler. We would loose all the flexibility in getting the connection parameters. This is why in the end another "meta-algorithm" is part of the solution. Parsing connection params from layer (like mentioned above):
With this, such models can be built:
processingexample.zip
Choosing an input layer, deciding according to provider what algorithm should be run and pass the parsed connection settings.
To Do