Open ideas have been reviewed by our Product Management and are open for commenting and voting.
This idea is targeted to custom transformer deployment on FME Server but can be applied more generally to shared resources on FME Server.Currently, custom transformers can be deployed to either a Repository, or to the Resources > Engine > Transformers folder as a shared resource.Transformers deployed as a shared resource are available to all workspaces at runtime, which is very effective for ensuring consistency across an organisation.The issue is that there is no simple way to manage this single resource across a large organisation with multiple development groups and I'm currently working with an organisation that has the "Engine" resource folder locked down so that only administrators can upload data there, to avoid inadvertent uploading of transformers that could potentially impact multiple workspaces.It would be great if alternate shared resource paths could be implemented, either as entirely separate locations, or as sub-folders under the current path. (e.g. Engine > Transformers > [my sub-folder name]). In conjunction with this, sub-folders should allow for separate permissions than those of the main Engine folder.Implementing the above would allow for different development teams to manage their own shared resources without impacting the entire organisation, and without needing to grant blanket permissions to the entire "Engine" folder.
It would be nice if we can choose an ArcGIS webmap to use as the basemap of the GeometryPicker. This would be very nice to use with the Web App.
This is a follow on from my previous idea C658999. The latest version works well and outputs the target compression ratio used for my ECW files but the "Actual Compression Ratio" attribute is not working / does not seem to have been fixed. I am struggling to calculate the ratio myself. I have the correct formula, but I can't combine all of the necessary attributes (particularly file size) to perform the calculation. I can use some transformers to generate the file size but it takes hours if I have geometry attached, but I need the geometry for other things. I also can't subtract the header information to get a more accurate compression value. Can you please update the ECW reader to include / fix the Actual Compression Ratio. Thanks.
Workspace authors are important, but so too are the persons who install and administer FME. This webinar will suggest ways to administer FME and how to optimize your FME Server setup.This idea is a potential webinar to be presented during October-December, 2022.
As more data becomes available in three dimensions, it's possible to create town and city models that are highly detailed and realistic. But how can you integrate all that spatial data? With FME of course, and this webinar will show you how.This idea is a potential webinar to be presented during October-December, 2022.
It would be great to add a reader for SDMX (https://sdmx.org/)Updated title for clarity, old title: Senior GIS Administrator
In this webinar, we'll explore how FME can be used with Microsoft Azure web services, (particularly Data Storage and Data Management services) and cover some of the different transformers and formats that exist to support this.This idea is a potential webinar to be presented during October-December, 2022.
Here we'll look at open data portals (for example, CKAN) and how to use FME to publish data.This idea is a potential webinar to be presented during October-December, 2022.
In this webinar, we'll look at different scenarios and decide which transformers to use. In particular, we'll look at SpatialFilter vs SpatialRelator vs Clipper vs Overlayers.This idea is a potential webinar to be presented during October-December, 2022.
A series of webinars, each about how FME can work with a different database; includes Postgres, SQL Server, Azure, Snowflake, BigQuery, AWS, Aurora, etc.This idea is a potential webinar to be presented during October-December, 2022.
This webinar covers the different Reprojector transformers in FME. Which have specific purposes? How do they differ from each other?This idea is a potential webinar to be presented during October-December, 2022.
How to validate and fix address data using FME, including how to meet standards such as NENA.This idea is a potential webinar to be presented during October-December, 2022.
How to integrate different spatial data sources and deliver it to others in either 2D or 3D Adobe PDF.This idea is a potential webinar to be presented during October-December, 2022.
This webinar will cover the absolute basics of using databases with FME.This idea is a potential webinar to be presented during October-December, 2022.
An in-depth look at the parameters and techniques involved in creating custom coordinate systems.
A look at cloud-native and cloud-optimized formats and how FME can be used to deal with them efficiently.This idea is a potential webinar to be presented during October-December, 2022.
A look at FME Server triggers that handle file-based events, such as adding/deleting a file, modifying a file, directory changes, date changes, and others.This idea is a potential webinar to be presented during October-December, 2022.
Looking at how Mapnik can be integrated and used with FME, including the MapnikRasterizer transformer.This idea is a potential webinar to be presented during October-December, 2022. It is an updated version of a previous webinar.
This webinar will cover the absolute basics of using both raster data and point cloud data within FME.This idea is a potential webinar to be presented during October-December, 2022.
A webinar that explores the use of FME for transportation and transit projects, including DoTs.This idea is a potential webinar to be presented during October-December, 2022.
This webinar is an in-depth look at how to use parameters. It will include best practices on where/when to use them across FME products.This idea is a potential webinar to be presented during October-December, 2022.
A deep dive into coordinate systems in FME. A follow-up to Coordinate Systems 101.This idea is a potential webinar to be presented during October-December, 2022.
***Note from Migration:*** Original Title was: TestFilter Option Which Allows you to Choose to let all Data Test Against all Filters Instead of doing it Stepwise Add an option to the TestFilter, where you can choose to let all data test against all filters instead of doing it step-wise. E.g. If I have a dataset of 10 objects and 3 queries in a TestFilter, I want all 10 objects to test against each of the 3 queries. Normally a few objects would fall out in the first test, a few more in the second, etc. For now I can solve this with a Loop transformer, but it would be nice to have an option in the TestFilter to test all data against all queries.
We can already write into an existing table in h_store format using text type (thanks to Takashi for the tips). It would be great that postgres/gis writer recognise h_store type. Consequently, we would be able to create a new table containing h_store type using FME ( currently, I use SQL instead)
The ProjectWiseWGSConnector List action needs an option to add search filter (e.g. regex on doc name), so it can improve the performance of the list action and narrow down the returned results.
In-depth courses for all FME skill levels.
Explore our extensive collection of how-to guides and tutorials.
Log an issue with us. Our support team is ready to help.
