Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Request: Please add parameter options for for the Esri Geodatabase Open API reader that allows us to ignore the FeatureDataset path to featureclasses I have an esri GDB with featuredatasets (see featuredataset image)With FME using Esri Geodatabase (file geodb) reader and an ESRI license... it nicely drops the featuredatasets for feature types.... and keeps the featureclass nameDistributionCarrier_HV_OHUse the Esri geodatabase (Open API) reader however and you get ... featuretypes with the featuredatasets in the path. No parameter option to ignore themxxxxxx_Distribution_Carrier/DistributionCarrier_HV_OHI workaround for the OpenAPI is to use stringreplacer to format them such that I can get to the featureclass names, Thanks to AI assist in 2023.1, I can now write regex !
When I hit backspace in FME Flow Hosted, it can potentially delete an action on the canvas. Surely this functionality should only be reserved for the DELETE key. You're often typing in other parts of the window and hitting backspace all the time so if your cursor is not in the dialog box...boom! you've deleted some of your work on the canvas.Maybe others will vote this up or please correct me if I'm wrong here. Thanks :)
Support writing transparent rasters to Adobe Geospatial PDF.
Add the WMTS format to the list of formats supported by the Data Inspector background map.
***Note from Migration:*** Original Title was: Parameters for 'Number of Retry' and 'Time Delay' in some transformers when failed. It is nice to have parameters to set number of retries and time delay between retries in case of connection failure in some transformers connecting to external services such as HTTPCaller, FTPCaller.
Description: FME is a powerful data integration tool used by many organizations to move, transform and validate data across multiple systems. As the complexity of FME workspaces grows, it can be challenging to ensure that code quality and security best practices are being followed. A SonarQube plugin for FME would be a valuable addition to the FME ecosystem, providing a powerful linting tool that can identify issues, suggest improvements, and flag potential security vulnerabilities in FME workspaces.Use case: The plugin could be used by FME developers, data analysts and IT teams to enforce coding standards and best practices, improving the overall quality and maintainability of FME workspaces. The plugin would allow developers to catch issues early in the development cycle, reducing the risk of errors and security vulnerabilities in production. The plugin could also provide detailed reports that could be used by IT teams to monitor and manage code quality across multiple FME workspaces.Features: The SonarQube plugin for FME could include the following features:Linting of FME workspaces, with suggestions for improvementsIdentification of potential security vulnerabilitiesIntegration with the SonarQube dashboard for easy reporting and managementCustomization of linting rules to fit specific coding standards and best practicesIntegration with FME Server for continuous integration and automated testingImpact: The SonarQube plugin for FME would be a powerful addition to the FME ecosystem, providing a valuable tool for improving code quality, reducing errors and ensuring the security of data integration workflows. This plugin would be a great investment for organizations that rely on FME for critical data integration tasks.
A workbench parameter "Ignore Failed FeatureTypes" for readers (just like "Ignore Failed Readers") that makes the workbench fail if set to NO would be helpful if you need to know if a featuretype you want read has been deleted (or renamed).
When you have a transformer that allows you to select multiple attributes (e.g. Attribute Keeper), have a counter that shows how many have been selected and from how many, e.g. 15/80. Thanks.
Currently what you can do with JSON Query in FME is very limited. It would be great to have more advanced support per https://docs.jsonata.org/simple, where for example once could extract the last item in array (json[-1]) or get objects in reverse oder (json[-2] etc.), get items in an array based on the value of an attribute (ex: json["columns"["type"='Data']]...maybe not exactly this syntax but you get the point...). This would avoid having to fragment a lot of useless data and then use Testers and TestFilters to weed out what you want.
At the moment, you can only validate attributes of layers, blocks, dim styles or text styles that are used.I would also like to read unused items (within unpurged drawings), so I can validate the entire DWG.
Add DD-MM-YYYY / DD/MM/YYYY as an auto FME recognised date format
I would like to have an option in FME Desktop to set a default priority when publishing a workspace to FME Server.Running a workspace with a user-defined priority is now possible with the transformer FMEServerJobSubmitter, FmeServerConsole and Schedules. When a workspace is launched on FmeServer with the service JobSubmitter, I wanted it to be executed with a default priority.Other default values could be tags, timeouts, notifications, etc...A workaround for this issue can be found in the answer of jonathan in this question: Can you assign a priority when publishing a workspace to FME Server? - FME Knowledge Center https://fmecommunity-ideas.s3-us-west-2.amazonaws.com/tm-priority.png">
Make it easier to upgrade user parameters with just one click, similar to upgradeable Transformers.Currently, when updating older Workspaces in FME, Transformers can be updated easily with one click, but user parameters, which changed between versions, can't be updated the same way. Old user parameter defintions causes problems in other parts of the Workspace where these user parameters are used. As a current workaround, I delete, recreate, and link the new user parameter in order to get the latest version.
Hello community,Safe Mobile team is working on new Data Express functionality that will allow capturing device bearing/direction as a parameter value or as a part of location parameter value. We would like to gather some feedback from users and future users of FME mobile apps to make sure the new functionality will help you solve problems you are working on and will be as user friendly as possible.As you might already know, we have added EXIF GPSImageDirection tag support for photos taken with FME Data Express camera. This tag value specifies the direction the device was pointed to when the photo was taken. However, quite likely, there are some scenarios that require capturing device bearing without taking a photo. We would like to hear more about these scenarios.Some of the questions we are discussing now:Would it be sufficient to add device bearing to the Location parameter value? Are there scenarios where using Location parameter wouldn't be logical/user friendly and a separate parameter for device bearing value would be preferred? Is device bearing needed on location only? Are there scenarios when the user would need to select a point on the map and then specify a direction from the selected point/to another point of interest?If the bearing is captured as part of the location parameter value (i.e. on the map), should the bearing be somehow selected/specified on the map (e.g. top of the map) or should still the device direction be considered?Please tell us more about your tasks and scenarios and share your implementation ideas and requests.Thank you in advance for your input.
A common case I find myself dealing with is performing joins between two data sets just to filter out values of my primary set that are not in some reference list. In this case, I'm not interested in the attributes of that reference list, only that the joining process removes the entries that don't match. In SQL, this would be the equivalent of something like this, with an inner join:SELECT person.*FROM personINNER JOIN person_car ON person.person_id = person_car.person_id...or in the more explicit way, with an actual semi join:SELECT * FROM personWHERE EXISTS ( SELECT * FROM person_car WHERE person.person_id = person_car.person_id)The benefit of this is that the attribute list of downstream features cannot be altered by the join, which is useful for dynamic workbenches and dynamic transformers.This would be a simple matter of adding a "Discard supplier attributes" mode to FeatureJoiner and FeatureMerger.
It seems that the current Cesium 3D Tiles Writer always creates only a single level of detail (LOD) tileset containing every feature as-is. A rendering application attempts to render the most detailed tileset even with small zoom level and could fail if the number of features was very large.It would be ideal if the writer could create multiple LODs tilesets (rough to detailed) and a tileset.json so that any rendering software can render them appropriately according to zoom level.
Depending on format used it might be handy to have the ability to comment out line in editors, Note similar to idea hereUse case: shape file, file geodata base, Feature Service implementation of a geometry area./*@round(@Value(SHAPE__Area),-1) <--would like to comment out this*/@round(@Value(Shape__Area),-1)
The ability to directly paste a cURL command from my browser's network traffic into the httpCaller. If this transformer adopts the configuration of the cURL, including all headers and query parameters, they no longer need to be manually replicated (error-prone).
A @PreviousTransformer() attribute written on Rejected features.Our team has extensive "Error catching" for workspaces, where we create "error reports" for features which are rejected from transformers. We typically use an AttributeCreator, and nearly every one lists the previous transformer for faster debugging. Having this attribute would enable us to create presets and/or an Error Report Custom Transformer for many rejected ports, rather than many, many AttributeCreators for the various transformers with rejected ports.
Please consider adding a System Event for Schedule Created. I would like the option to create an Automation when a Schedule is Created it runs an Automation that makes a call to the Rest API to share that schedule with the appropriate Roles/Users. This would ensure neither the Schedule Owner/Admin is responsible for maintaining these permissions which could become tricky to keep track of if there are a high number of schedules being created on a regular basis. This is needed because newly created schedules cannot be shared automatically apart from as the superuser (https://knowledge.safe.com/idea/99535/fme-server-security-full-permissions-for-individua.html).
Our IT department wishes to have all connections to the central admin database (MS/SQL) identify themselves properly. I.e. not as e.g. ".Net SqlClient Data Provider" etc.FME does identify itself as "FME(R) 2016.1.0.1" in this case, but it would be nice, if one could overwrite the connection default "Application Name", e.g. with a optionally custom workspace related name.Cheers
Hi,it would be nice to have the same option as in ArcMap when visualizing data either in visual preview or data inspector where you can choose to only show the tabular information of selected features. Simple functionality, always useful.
(Even) ESRI provide a cheap option for folk to have GIS at home for private use. It would be wonderful if Safe would consider doing the same for us FMEers.
This idea is a follow up on the following question I posted on the FME community; &#039;Paste as Text&#039; option for Copy-Pasting to Annotations in WorkbenchPersonally I prefer to have the option to paste content in plain text to (Annotations) in Workbench. When using ctrl-v (as I am used to), the original formatting is preserved.redgeographics pointed out to me that Pasting via right-click -> paste strips the formatting.Although I'm glad there is an option to paste as plain text (without formatting), it's not clear if it is designed to work like this. Also I believe that the current implementation is not so intuitive. Therefore, the core of this idea is to improve the (user experience) upon using different 'paste as' options for (annotations in) Workbench.Some idea's;Within the FME Workbench options, add a default 'Paste as' behavior when using ctrl-v for pasting to workbench.Expand the right-click menu, and split the current 'Paste' option into two new options; 'Paste as Plain Text' and 'Paste as formatted Text'.
This was mentioned at the FME UC in Bonn 2023 in one of the slides for a potential upcoming enhancement and I'd just like to take the opportunity to discuss why I think it would be quite helpful in certain workflows. I think It would be especially helpful to certain applications/companies in the 3D modelling space or online shopping services etc.At present we have a process which takes a set of 3D models (various typical city 3d models) and we build a catalog out of these with the help of FME. As part of that process we call a 3rd partly tool to create both, a preview and icon, out of the models which are included in the catalog. Obviously having this supported directly in FME would be beneficial. I'd also like to add a workflow where that users can upload their own models and in the process an icon is generated. It's much nicer in some ways than a file name or description. At present because our upload process is hosted on FME Cloud I do not have access to the 3rd part tool (Node.JS based).
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.
