Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Migration Note: Idea originally posted on 2015-10-29
***Note from Migration:***Original Title was: "Reject"port for writers \ changes to error log behavior with rejected features by writers Currently, when features are rejected when writing a file, there is no way to tell until you open the file.For example, if 51 features are passed by a transformer (and are visible in the inspector or other data formats), but 4 cannot be written to a specific writer (rejected), FME will still report"51 features written, Transformation successful"even though in actuality only 47 features are written.I propose that the FME logger and workspace will say"47 features written, 4 rejected by output file, Transformation successful"Alternatively, the addition of a "reject" port for writers can also be a solution.As there is no "reject" port for writers as there is with transformers, there is no way to tell without scrolling in the error log whether all features are written by a specific writer, until you open exported file in FME Data inspector.This behavior is discussed in this thread with an example. https://knowledge.safe.com/questions/69542/missing-points-when-exporting-to-shapefile.html?childToView=69550#comment-69550 Migration Note: Idea originally posted on 2018-05-03
***Note from Migration:***Original Title was: Text size in the JSON \ XML transformers for the XQuery text editor too small on Mac When using any of the XML \ JSON - Templater, Flattener, etc. when entering the query in the text editor, the font is so small it's unreadable on a Mac. It will not allow you to change the text size and none of the zoom options work. Other text editors are ok on the Mac. Migration Note: Idea originally posted on 2019-04-18
When I got a humongous pile of parquet-files I had to find a way to read and filter the data in them. I found this and it works great, https://duckdb.org/docs/guides/import/parquet_import.html.Fast SQL-queries on all files without having to move the data into something else first!Using DBeaver and a DuckDB connection ":memory:" I can do queries like this:select count(distinct Id) FROM "D:\myfiles\**\*.parquet"where startingdate >= '2020-07-27 00:00:00' Perhaps this will be a bonus with the upcoming DuckDB-reader/writer...??? :) Migration Note: Idea originally posted on 2024-02-01
World files like tfws produced by FME are rounded to 10 significant digits when written by the various raster writers even if the original georeferencing is more precise. This is an issue when working with images in Lat-Long when attempting to work with both the original image and the created image because transformers like the RasterBandCombiner or RasterCalculator fail with an error that the x and y spacing doesn't match.Simply writing geotiffs won't work because the tif image is processed in non-geospatial aware software and requires the tfw to preserve the georeferencing information. A common workflow is RasterReader->FMEprocessing->FeatureWriter(tif+tfw)->external processing->FeatureReader-> Further FME processing It would be nice if we could specify the significant digits and/or whether to round them at all on either the writer itself or as a system setting. Migration Note: Idea originally posted on 2024-02-02
I propose creating a file navigation window, akin to QGIS' "Browser," to FME Desktop. This window would enable me to swiftly browse files and decide whether to use them as readers or writers.Moreover, I envision the convenience ofmarking specific paths as favorites or bookmarks for my frequently used locations. This feature aims to enhance the user experience by simplifying the process of locating and incorporating files in FME Desktop. Migration Note: Idea originally posted on 2024-02-02
Migration Note: Idea originally posted on 2016-05-04
Migration Note: Idea originally posted on 2015-11-20
Migration Note: Idea originally posted on 2016-03-27
Migration Note: Idea originally posted on 2015-12-03
Could be useful for readers as well. Migration Note: Idea originally posted on 2018-04-25
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.
