Hi Régis,
I agree - it would be good to brainstorm what's missing to have an
FME-like ETL environment.
I see that you are coming to the Madeira dev meeting. Would be a good
opportunity for such discussions and then open the QEP in parallel (or
open it before and work on it).
BTW: refactor fields isn't such a bad name in my opinion. Perhaps we
could introduce aliases for algorithms - so that they could be found
more easily?
Greetings,
Andreas
On 2017-11-23 09:12, Régis Haubourg wrote:
> Hi Andreas,
> I don't have any answer to that particular question, but in many project we
> are working for, it becomes clear that we need to push processing to become
> an ETL, and the field mapping component is clearly a key feature.
> What do you think about opening a QEP and store in there all what's currently
> missing for a clean and easy workflow?
> We clearly will have some funders in 2018.
>
> I see :
>
> # Mapping field alg:
>
> - rename it to something more easy to find. What about "Field matcher" ?
> - automap fields using tolerant expression based on heuristics (unaccent,
> lowercase, soundhex or whatever, field order.. )
> - save and restore config.
> - Auto restore for same table names
> - And, the key for fame, a graphical component for field matching, because
> this is what we all want :)
>
> # database writer :
> - finely control all SQL options: drop table / recreate / truncate / insert /
> update with where clause
> - add rollback option to just try without commiting
> - return all database logs in details
>
> Opinions?
>
> Régis
>
> 2017-11-23 9:01 GMT+01:00 Andreas Neumann <a.neum...@carto.net>:
>
>> Hi,
>>
>> The refactor fields algorithm is potentially very powerful.
>>
>> However, I do miss a way to save and load the configuration (or maybe I just
>> haven't found it). I have layers with many fields and I am adding additional
>> fields with expressions.
>>
>> Every time I run it, I have to do the configuration again and again. Is
>> there a way to save and load the mapping configuration? It would save me a
>> lot of time!
>>
>> Thanks,
>> Andreas
>>
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer [1]
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer [1]
Links:
------
[1] https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
