Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
When inspecting features, particularly identifying point geometries, I find myself wanting to visualise the Identifier attribute for alot of points, sometimes along lines and centre of polygons. Obviously desktop GIS have this functionality…. but I’m asking to build on the Mark location option which already has a Label option. Can this same code be added under the Display Control, where users edit the styling of each dataset/layerData Inspection lacks functionality to add simple labels for a point dataset/layerA workaround in workbench is to use LabelPointReplacer transformer to create text geomSo the updated UI will need Label section in the drawing style… and as pictured belowability to select the Attribute Value column and make this the label text the font and colour would be nice label size (replacing font size?) may also be of assistance, though projected coordinates are likely needed to display in metresDisplay Control drawing styles to include a Label
At the moment, it takes some effort to figure out what Python install is used by FME Form and what Python install is used by FME Flow. This becomes a problem once additional libraries need to be installed on FME Form and FME Flow, especially if they are installed on the same physical machine or AWS instance. I would like to propose some changes which will improve user experience:making Python install locations more obvious during FME install; having the same default location for FME Form and FME Flow Python installs; exposing Python install(s) used by FME Form in Utilities > FME Options; somehow exposing Python install(s) used by FME Flow in FME Flow WebUI; making repointing FME Form/FME Flow to the preferred Python install… well, effortless.
Can FME add support for Vulcan files (by Maptek): .00t, .isis, .isixIf anyone else is interested, vote for this idea and add a comment about what transformations you envision performing in FME with the Vulcan files.
As noted here, it would be nice to have the ability to write additional components such as Classification, Intensity etc, with our Cesium writer.
Currently, when transferring projects between different environments (e.g., TEST to PROD) in FME Flow, it is necessary to use the same “global” encryption key across those environments.From a security standpoint, reusing the same encryption key across multiple environments is not considered best practice.It would be great to have “project-level” encryption keys, allowing each project to be encrypted independently of a global system key.
Add a 'Case sensitive' option to the Joiner. Sometimes capitalization of attributes differs between source and target attributes. It would be nice if you could just use an option to take this into account or not.
I’m downloading bulk CSV data from an open data site, each download is gigabytes, I would like to set the output filename to a .zip file, to save space.
https://knowledge.safe.com/questions/38771/can-i-use-a-feature-merger-to-merge-partial-names.html https://knowledge.safe.com/questions/39153/merge-features-by-attribute-that-contains-string-f.html?childToView=39163#answer-39163
Hi,some formats (such as the Text File reader) have fixed schemas that will never change. In the case of the Text File reader the only attribute in the schema is the text_line_data attribute.For these fixed-schema formats, I would like to request an enhancement to the FeatureReader to have the schema automatically exposed, even when the Generic output port is configured. Currently, the schema attributes are only exposed for named output ports.For context, I refer to the following Community question: And to my own support question (to which James Cheng provided a very comprehensive reply):https://support.safe.com/hc/en-us/requests/64419I have reproduced James’ reply below, as it so clearly explains the situation:Thank you for raising this. I understand the frustration as I share the same thoughts and can see why you'd expect the text_line_data attribute to just be available when reading a Text File through the FeatureReader. The behavior you're seeing comes down to how the FeatureReader's generic output port works. This port is a catch-all that merges everything into a single stream, designed to handle any format and feature types with varying schemas. Because of this, it doesn't commit to any schema at authoring time, it doesn't make assumptions about which feature types or attributes will be present, so all attributes come through unexposed by default, even for predictable formats. By contrast, when you use a named output port (or a standalone Text File Reader), the schema is known at authoring time, so the attributes like text_line_data are automatically exposed. In essence, by using the Generic port, the trade-off is flexibility over schema awareness, it can handle anything but at the cost of not pre-committing to any specific attributes. However, as you've rightly pointed out though, the Text File Reader always produces a predictable fixed schema with a single attribute, text_line_data, no matter which files/feature types are being read. So there's a reasonable argument that the FeatureReader could recognize this and auto-expose it on the Generic Port since there's no ambiguity what the output will be. Currently, the Generic port doesn't differentiate between fixed schema and variable schema formats as it applies the same "unexposed by default" behavior uniformly across the board. That said, I think this is a genuinely good candidate for a product enhancement for the generic port. I'd encourage you to post this as an Idea on the FME Community, specifically requesting that the FeatureReader auto expose known attributes for fixed schema formats like Text Files on the Generic port and describing your use case. Community support helps the development team gauge interest and prioritize ideas for future releases, and we can link this ticket to the Idea to keep it on their radar. In the meantime, it's worth noting for this specific format, the feature types are all fixed to text_line, so using the default One per Feature Type output port setting will also route all text file features through a single text_line named port, similarly to the Generic Port, which will expose the text_line_data attribute automatically. If your workflow requires the Generic port, then the only available options are manually setting the Attributes to Expose parameter on the FeatureReader or placing an AttributeExposer downstream. regards,Nic
This idea is a specific use case of the more general:This idea exists simply to assist people searching specifically for information regarding exposing the text_line_data attribute on the Generic port of a FeatureReader when reading Text File data.
All the grids in FME servers are not sortable by users, sorting is the very basic function expected by all users from any software these days.Please allow users to click on any column header to sort ascending/descending/removing sort for a given column. The user should be able to hold the shift or control key to choose multiple columns to sort. The sort function should work for all supported data types in the column, e.g. Number, text, date, user, etc.
On FME Flow you can filter failed jobs. It would be great to be able to filter by error message. This way if you’re trying to troubleshoot an error that is occurring you can easily see which scripts have been impacted.
If we are logged into the community can the webinar registration form be auto-populated or just accept the registration from an existing member.It is a little annoying having to constantly fill in the registration form to watch a webinar, especially as I am an existing member of community and all the details are part of my profile.
Currently the VariableSetter/Retriever can be used to set/retrieve just one global variable. It would be more convenient if multiple variables could be set/retrieved at once.
Is there a way to have feature writer (PNG format), to generate .pgw instead of .wld file?For feature writer (JPEG format) it has option to change .wld to .jgw Just wondering if it would be possible to do that with PNG as well? Currently I change the .wld to .pgw manually. I know there’s a way to use SystemCaller to make it change the file extension. But it would be helpful if we can just skip that entirely because it may not work as expected when we Publish workspace in FME Flow. JPEG Format PNG format
When you add a "file" manual key to an automation which get run by an automation app, the option is to choose a file already in the resources of FME Flow. It would be nice to have an option for a user to upload a file like what's already available in workspace apps. For a User Parameter "File" the user is able to upload a file which gets used by the workspace the workspace app runs. The same would be ideal for automation apps.
***Note from Migration:*** Original Title was: Option to use @Value(AttributeName) in the AttributeRenamer for New Attribute Names Add the option to use @Value(AttributeName) in the AttributeRenamer for new attribute names.
I would like the ListSorter to support multiple sort-by criteria, similar to the regular Sorter. Example:Currently (FME 2018.0.1) you cannot use multiple ListSorters to accomplish the same thing, since the ListSorter doesn't preserve the existing item order on duplicate sort keys (PR83992).
Either as a new transformer or as an option in the StatisticsCalculator transformers (standard, raster, pointcloud...list?)
***Note from Migration:*** Original Title was: Add Support for Aggregate Geometry Type (Esri ArcGIS Online (AGOL) Feature Service Writer) Add support for writing Aggregate features with the Esri ArcGIS Online (AGOL) Feature Service Writer.Currently this is not supported: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/arcgisonlinefeatures/quick_facts_arcgisonlinefeatures.htmExample of community discussion of this feature: https://community.safe.com/s/question/0D54Q000080hRcE/cannot-write-to-esri-after-using-aggregator-mutipart-geometry?t=1619549337262
Would be great to have a Search Filter In the dialog which is handy when there are several workspaces in the same repo.
Idea: cancelling a job will rollback the whole transaction of all features for Snowflake WriterObserved behavior: cancelling a job in FME Flow will stop additional features from being written, but features that have already been written to Snowflake are already committed without any rollback of the transaction. There is inconsistency between “Features Written’ as recorded in the job log and actual features written according to Snowflake logs. The job log records zero features written while there have been many features written to Snowflake despite job being cancelled.Desired behavior: cancelling a job in FME Flow will stop additional features from being written and rollback any partial changes the job has just done. Outcome: improved management of jobs.
When downloading data using Data Download service (e.g. from an FME Workspace App), a Zip file is created containing the output files. The zip file is automatically named something that looks like “FME_4B425D3A_1772473610895_13172.zip”. It would be nice if an option was implemented to allow customizing that name to something that is more user friendly. For example allow authors to specify what exact name the Zip file should have, or allow the use of parameters to create a string to use as file name. Even if the final filename has to have some extra characters at the end like 4B425D3A_1772473610895_13172, giving authors some customization capability would be beneficial.
Hello,To continue with data platform integration, is Safe discussing with Databricks to be added to its Marketplace, like with Snowflake? @irenemunoz maybe.
Since it does not seem possible to automatically shutdown an instance in FME Flow Hosted, one workaround we found is to apply schedules to shutdown the instances. However, this is done manually and can be easily forgotten. A good way to ensure the instance has one is to suggest a schedule at the creation, with having a certain default value created. Hope this makes sense, let me know if this sparks any more ideas or if you need further information on the subject!
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.
