Skip to main content

QGIS-FME Form Connector Plugin


mygis
Supporter
Forum|alt.badge.img+13
  • Supporter

Hello all,

We have developed a QGIS Plug in to allow QGIS users to select a specific layer in their project, process it in FME then get it back as a temporary layer or a normal layer in QGIS. Trust me, we usually say that the sky is the limit, but really there is no limit in what you can process. The plugin is still marked as experimental and wish to get some feedback through our support channel.
 



You need to use our FME Workspace template (not an fmwt file, just a sample) and try experimenting. The workspace was developed using FME2024.2.0 .

Some would say that QGIS already has a great number of tools which I agree, however FME has a lot more to offer in other areas.

Before downloading the plugin, make sure you allow viewing the experimental plugins in the plugin manager on QGIS:
 


The FME example looks something like this:
 

 

The official plugin page is available here: https://plugins.qgis.org/plugins/qgisfmeformconnector/

I hope this will bring ease in your data transfer and data integration for QGIS users who have FME Form. Good luck and let your imagination go wild.

 

14 replies

hkingsbury
Celebrity
Forum|alt.badge.img+53
  • Celebrity
  • April 16, 2025

@mark2atsafe - Not too late for this weeks Whats up Wednesday?


jkr_wrk
Influencer
Forum|alt.badge.img+29
  • April 17, 2025

I don't seem to get it working. Looks like it ignores the FME executable path:

 


danilo_fme
Evangelist
Forum|alt.badge.img+44
  • Evangelist
  • April 17, 2025

@mygis It is very interesting. Thanks for share.


jkr_wrk
Influencer
Forum|alt.badge.img+29
  • April 17, 2025

Another error I found:

The plugin looks at the header of the FMW file to identify the user parameters.
But if the path to the fmw file contains spaces the path is surrounded by quotes.

"C:\Program Files\FME24825\fme.exe" “C:\FME\QGIS 2024.fmw”

This solves the error:

"C:\Program Files\FME24825\fme.exe" C:\FME\QGIS2024.fmw

Which means you have to open the workbench and save it as another file without spaces in the name. Because the header is not updated when just renaming the file.

 

These paths are both extracted from the file header:

And not used for the command:

Which would be the right choice for the fmw filename, because the user could be renaming without opening.

In my case the environment variable also has c:/program files/FME21821 as a path so just calling fme.exe would use FME 2021 to run the workbench. So reading the header to figure out what the path to FME is would be best.

 

 

 

 

 


mygis
Supporter
Forum|alt.badge.img+13
  • Author
  • Supporter
  • April 17, 2025

Thanks ​@jkr_wrk , it is fixed. If you are in a hurry I can pass you the new script to update the plug in. We will make the update by tomorrow it will take 24-48 hours to reflect in the repository. This is still in the experimental stage, although the paths table error was deigned to work the way you mentioned.

Thanks again for participating in this experiment and giving us your feedback.

Lyes.

 


jkr_wrk
Influencer
Forum|alt.badge.img+29
  • April 17, 2025

No problem, looks promising.

Was it also intended to be able to overwrite both paths after selecting the workbench or only the fme.exe location?

 

 

 


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • April 17, 2025
hkingsbury wrote:

@mark2atsafe - Not too late for this weeks Whats up Wednesday?

Too late to spot it! But I’ll definitely add it to an upcoming issue. Thanks for tagging me.


mygis
Supporter
Forum|alt.badge.img+13
  • Author
  • Supporter
  • April 18, 2025

Hi ​@mark2atsafe I have sent you a personal message here, I guess the best way is to tag you instead. Let me settle these issues first before you decide to post anything as this is only the tip of the iceberg.

Thanks.

Lyes


mygis
Supporter
Forum|alt.badge.img+13
  • Author
  • Supporter
  • April 21, 2025

Hi ​@jkr_wrk and all,

 

We are now at version 1.0.0 and it has been approved super fast by the QGIS Plugin team. Here are the main changes:

1.0.0
- Fixed filename with spaces error.
- Fixed changing fme.exe path selection.
- The plugin no longer reads the fme.exe and workspace location from the workspace header.
- Users must set the fme.exe path and save it in an ini file to be able to run the translation.
- Added synchronized layer selection widget.
- Changed state of command line table input area from read only to editable.

 


Lastly, if there are any issues/bugs with this please email us at mygis@gis.my as I do now want to use the FME community website as  a support platform. Thank you for understanding.

 


jkr_wrk
Influencer
Forum|alt.badge.img+29
  • April 22, 2025

Seems to be working now.

One little thing at this moment, the plugin looks for #!   A0_PREVIEW_IMAGE=" as end of the header. This is not part of 2021 fmw files so the header analysis does not stop in time:

Opening and saving in 2022 will solve the issue.

Ending at the first #! after <WORKSPACE would support 2021 files.

 

 

 

 


mygis
Supporter
Forum|alt.badge.img+13
  • Author
  • Supporter
  • April 22, 2025

Thank you for your help on this.  I will put a note on the page. We will only look ahead in terms of file version as we will be releasing our next product soon.  I will keep you posted in a new thread.


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • April 22, 2025
mygis wrote:

Hi ​@mark2atsafe I have sent you a personal message here, I guess the best way is to tag you instead. Let me settle these issues first before you decide to post anything as this is only the tip of the iceberg.

Thanks.

Lyes

 

A message is fine, I was just away for a long weekend. I’ve messaged you back now!


mygis
Supporter
Forum|alt.badge.img+13
  • Author
  • Supporter
  • April 23, 2025

Hi Mark,

The Algorithm is available but still as an experimental plugin. I am still editing this post:

 

 


mygis
Supporter
Forum|alt.badge.img+13
  • Author
  • Supporter
  • April 23, 2025

Just a continuation of our work, we have just launched the QGIS-FME Form Algorithm, more details are available here:

 

 

Hope this will help. It is still experimental.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings