The use cases for FME are mainly integration to the GE Smallworld product. GE Smallworld is a GE product, and we are using it to integrate with other third-party products into GE Smallworld and ADMS systems. The feature regarding automation capacity for scheduling data processing tasks is mainly used by one of our customers, Vodacom, and they are doing the automated exchange. That is very useful for them. It's only one of my customers that's using it. That's their business requirement to do real-time data exchange.
Senior Solution Architect at a consultancy with 201-500 employees
Real User
Top 10
May 5, 2025
FME is used to transfer GIS data from either on-premise into the cloud or between the primary servers and disaster recovery. We use it in various different ways.
I use two versions currently. The latest version that's just come out and the 2022 versions. Currently, I'm using the solution to pull APC data using the data collection. I've got to transform the data massively to make it usable, so I use FME for huge amounts of transformation and to put it into ArcGIS Enterprise. FME is a ZTL as well, specifically the "L" bit. I also use FME for a lot of analysis where we want it quick and efficient on big datasets that ArcGIS Pro is unrealistic to do on. I also use FME, where if somebody sends me a spreadsheet where, for example, we would need to get everything in capital letters, it's quicker for me to capitalize everything in FME Workbench than it is in Excel. I can use FME for just about everything, from logging processes to looking at file structures, what's changed in file structures, what people are doing, or what they've updated. It's not just need-to-know. It's a massive piece of software that's also coded in Python. What FME can't do, I then write in Python. I can make FME pull in ArcPy, which means that for every single thing that ArcGIS Pro can do, I can make FME. It's much bigger than the box.
Primary use cases include: creating automatic data flow processes, enabling users to self-serve their data needs, and handling real-time events. It is a fault-tolerant, scalable multi-tier solution, so it has backup facilities. One can use a multi-server setup with a database. We can download data, start processes, update databases, send messages, tweets, push notifications, and almost everything in a few clicks. With spatial data, it has almost no competitors.
Expert Data at a government with 1,001-5,000 employees
Real User
Jan 27, 2021
We use FME to do some ad hoc analysis, especially facial analysis, but they use it as well to do some generic processing for data quality controls. These are the main use purposes. It's in a governmental context and the most important data sets or addresses link to other information. Also authentication on partials.
FME is a powerful tool designed for efficient geospatial data handling, supporting over 400 file formats and integrating with diverse systems. Its intuitive interface facilitates seamless automation of workflows, making it ideal for sectors that manage large spatial data volumes.With FME, businesses automate data flows and manage GIS data transfers while integrating with tools like GE Smallworld. It empowers users with self-service capabilities for data processing and real-time event...
The use cases for FME are mainly integration to the GE Smallworld product. GE Smallworld is a GE product, and we are using it to integrate with other third-party products into GE Smallworld and ADMS systems. The feature regarding automation capacity for scheduling data processing tasks is mainly used by one of our customers, Vodacom, and they are doing the automated exchange. That is very useful for them. It's only one of my customers that's using it. That's their business requirement to do real-time data exchange.
FME is used to transfer GIS data from either on-premise into the cloud or between the primary servers and disaster recovery. We use it in various different ways.
I use two versions currently. The latest version that's just come out and the 2022 versions. Currently, I'm using the solution to pull APC data using the data collection. I've got to transform the data massively to make it usable, so I use FME for huge amounts of transformation and to put it into ArcGIS Enterprise. FME is a ZTL as well, specifically the "L" bit. I also use FME for a lot of analysis where we want it quick and efficient on big datasets that ArcGIS Pro is unrealistic to do on. I also use FME, where if somebody sends me a spreadsheet where, for example, we would need to get everything in capital letters, it's quicker for me to capitalize everything in FME Workbench than it is in Excel. I can use FME for just about everything, from logging processes to looking at file structures, what's changed in file structures, what people are doing, or what they've updated. It's not just need-to-know. It's a massive piece of software that's also coded in Python. What FME can't do, I then write in Python. I can make FME pull in ArcPy, which means that for every single thing that ArcGIS Pro can do, I can make FME. It's much bigger than the box.
Primary use cases include: creating automatic data flow processes, enabling users to self-serve their data needs, and handling real-time events. It is a fault-tolerant, scalable multi-tier solution, so it has backup facilities. One can use a multi-server setup with a database. We can download data, start processes, update databases, send messages, tweets, push notifications, and almost everything in a few clicks. With spatial data, it has almost no competitors.
We use FME to manage network infrastructure for Smallworld Database.
We use FME in geographical data analysis where a lot of sources or processes are involved.
We use FME to do some ad hoc analysis, especially facial analysis, but they use it as well to do some generic processing for data quality controls. These are the main use purposes. It's in a governmental context and the most important data sets or addresses link to other information. Also authentication on partials.