Hi there,
That's good new, especially given the new policy of SAFE software on
licence costs.
On my view, here is the wishlist :
- as stated before, be aware of the datasource structure in a model, with
the ability to refresh it, or read it from a config ressources (file,
database etc..)
- have t
Hi all,
We are currently evaluating work to improve QGIS processing to a closer
experience to FME.
There is already some information here from Nyall.
Our memories are a bit loose, is there any other work done on requirements
or a wishlist?
Is there any work already started so we don't hijack?
Th
On Tue, 7 Apr 2020 at 17:35, Andreas Neumann wrote:
>
> Hi Nyall,
>
> Thank you for sharing this interesting document.
>
> I have questions and remarks:
>
> 1. One fundamental difference between FME and QGIS modeler, as far as I
> understand it, is the fact that FME data sources are much more tigh
Hi Nyall,
Thank you for sharing this interesting document.
I have questions and remarks:
1. One fundamental difference between FME and QGIS modeler, as far as I
understand it, is the fact that FME data sources are much more tightly
coupled with the model than in QGIS modeler. This has the adv
Great job, Nyall!
Ready for a next round of crowdfunding?
Cheers.
Il 07/04/20 03:27, Nyall Dawson ha scritto:
> Hi list,
>
> Just wanted to give a heads up on a document I've recently completed,
> which maps existing FME functionality across to the equivalent QGIS
> Processing or Expression equiv
Hi list,
Just wanted to give a heads up on a document I've recently completed,
which maps existing FME functionality across to the equivalent QGIS
Processing or Expression equivalent:
https://github.com/nyalldawson/qgis-processing-hitlist/blob/master/fme.md
Since FME transformers are both algori
