FME

The best features of FME are it's integration capability, ease of use, and geospatial capability. In my own role as a geospatial analyst, there are a few software's that can be used to interrogate and transform spatial datasets - FME has a strong set of tools that allow users to view and manipulate geospatial data alongside non geospatial data as well. This combination makes it a great tool when needing to work with both geospatial and non geospatial data. I can see a lot of opportunity for FME to be used outside of my roles usual tasks due to it being an 'everything tool'. My personal learnings on how to use FME have largely been through practical work on the job rather than training. The tool itself is easy to get into and use and has a great online community and documentation to help its users. It is a tool that can easily be self taught to a certain level being a low code - no code solution to building various solutions. Especially for FME Form which is the desktop version. The standout function to me is FME's ability to integrate - pulling data from one place and loading it to another, connecting to APIs, webhooks etc have been very useful functions. FME Flow makes automation and scheduling of these integrations a very powerful tool - enabling many live processes to run and streamlining workflows. If someone comes to me and says 'can FME do it?' I normally say yes (maybe with a few buts!)

The standard libraries for conversion are good performance wise, the graphical interface is intuitive. For people with a GIS background it is a very good tool.

The availability of support for a huge variety of data sources and formats is outstanding. Whether working with spatial databases, CAD files, raster data, web services, or countless other formats, FME handles them all seamlessly within a single workflow, eliminating the need for multiple specialist tools. Second, the user-friendly interface makes building and managing complex workflows very intuitive. The visual, drag-and-drop workspace allows users of varying technical backgrounds to design sophisticated data transformations without extensive coding knowledge. Third, the availability of advanced automation through FME Flow is a game changer. It allows workflows to be scheduled, triggered, and run on a server environment, enabling true end-to-end automation of geospatial processes at an organisational level.

The FME workbench interface can sometimes not be clear as to why something is failing, or why a field you are filling out is deemed as invalid. Often to tackle error messages and unknowns it is necessary to look at documentation on their site. Which is fine but I imagine tooltips or reminders in the UI would be helpful to improve ease of use. Perhaps the upcoming AI Assist in the newer version of FME will fill this gap. Using FME at a larger organisational level I would say does require someone in the business or a support partner to have a senior level understanding of FME to assist in best practice, debugging and maintenance. Particularly when using FME Flow.

Not a lot of people are familiar with the tool, it's difficult to find people in the market with FME as a skillset, this causes FME to be a liability at times as there's only a few people in the company that are familiar with it. This opposed to writing an ETL pipeline in Java/C# or Python which is much more generic and easier to recruit for.

Licensing costs can be quite high, which may be a barrier for smaller organisations or individual users. Performance can occasionally be slow when processing very large datasets, which can require additional optimisation of workflows. These are relatively minor points in the context of the overall value FME delivers, and non of them have significantly impacted my experience with the software.