Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Clipper: Have an option for overlapping clippers to duplicate the clippee in the overlap region.
Mike by DHI is a common used software for e.g urban flooding analysis, seehttps://www.mikepoweredbydhi.com/. It would be great to be able to work with the format dfs0 (time series) and dfs2 (raster data) in FME Desktop. If possible to read data in FME it can be used for volume calculations of flooded areas, calculate flow to be used for design of stormwater solutions etc. Also makes it possible to perform spatial analysis (flooded area vs buildings etc).
Symbols such as 'Mapinfo Points Of Interest' and symbol types such as 'Webdings' and 'Windings' aren't available to choose from.
Include a feature to import existing .tab files into a 'Mapinfostyler' transformer? Manually setting up each option is time-consuming, especially when there multiple styles to set up.
Wouldn't it be fantastic to have the LeftRigthSpatialCalculator functionality to be included in the NeighborFinder? I just thought of it when I saw the "idea" below:Attribute accumulation for LeftRightSpatialCalculatorhttps://community.safe.com/s/idea/0874Q000000TlehQAC/detailCommunity, what do you think? Pros/Cons?
Would be nice to work with features supporting a 4th dimension. x,y,z,t coordinates. Render is not important, but would make a lovely visual effect if the data inspector supported the timeseries rendering. Scaling time is difficult, but having a max span of T seconds might work?
Often times user load the wrong file in the parameters in FME server. Could we set up a flag to check if they are loading the correct file format?Additionally, it would be great to have a checkbox that could be checked on or off to allow one or multiple files to be loaded. We have some requirements were a user needs to load one file only and they have loaded multiple.Thanks for any help you can provide on this issue.
I am running a process that has 53 stored procedures and its been painful to manually expose the attributes from the stored proc. Can we have a check box/ option to expose all or only some, but have the transformer read the schema? Thanks!
When exposing alot of IFC-attributes you need to select one and one. Make it possible to select multiple attribute.
Allow mouse wheel zoom in workspace. Wheel scrolling is not terribly useful in this area since pan handles that.Thanks for listening.Tyler
After refreshing the FME Server license it is easy to assume that additional engines will automatically be activated. A redirect to the engine management page or a popup with a link to that page will remind the admin that adding new engines is a multi step process.
I realized that when you're doing a loop inside a linked custom transformer, you don't have the possibility to redirect the loop to a private input. If you do that, you'll have a "LOOPBACK_INPUT_TAG" error.So you have to publish the input (even if you don't want it to be visible on the custom transformer).
Version Control is now in FME Server 2017.1As of the FME 2017.1 release, we have added Version Control to FME Server as a technology preview. This means that while it’s not quite ready for prime time yet, it is available to take for a test run.We’d like to call on anyone interested in this new feature and especially anyone who voted on any of the related ideas for this (definitely one of the more popular enhancement requests for FME with a total of 149 votes from 4 ideas!) to try this feature and let us know what you think.Give us your feedbackWe’re actively working on developing this new functionality and we want to hear from you!What works? What doesn’t? Does it fit in with how you currently work with FME Server? Does it line up with how you would have pictured versioning in FME Server? The more context you provide, the better.Please post your feedback as a comment back to this idea.How do I work with this? Simply turn on version control from the web interface. Once it’s configured, you can upload your workspaces to FME Server using the Publish to Server Wizard in Desktop. It will let you create new repositories to group your workspaces as you upload them. Once they are up there, you will be able to view and download past versions of your workspaces using FME Server’s web interface.We’ve put together a video introduction for this new feature covering enabling versioning, viewing history, rolling back, connecting to remote git repositories, preserving history across FME Server upgrades and configuring security settings. Check it out here:https://www.youtube.com/embed/4-XAm7_2O3cFor those who’d prefer the written word, check out the documentation:https://docs.safe.com/fme/2017.1/html/FME_Server_Documentation/Content/WebUI/Version-Control.htmI only have FME Desktop, can I try out Version Control too?Yes, of course! You can download FME Server from our Trial Download Page and install it. If you’re only using FME Server for version control (and not for running workspaces), you can simply dismiss the Engine Licensing Dialog that appears when you open the web interface. Now, you can use FME Server as a central repository for your workspaces and take advantage of other benefits such as easier sharing and collaboration. You’re free to keep using FME Server like this for as long as you want for all your workspace management tasks.
If there is an error in python code(python caller) fme shoex error_line_number + 1I mean if there is an error in line 42 , fme log window tells us error in Line 43. So what I am doing is ... I am minus 1 , and and looking at Line number 42 and fixing the code.it is better to show exact line number in fme log window
During a FME training class, a trainee suggested the option to sort the Data Inspector table window in a way that the selected features would appear at the top of the list.This seems to be possible and useful in the ArcGis Table View.
It would be great to be able to expose attributes at runtime for dynamic workspaces.
https://community.tibco.com/wiki/tibco-spotfire-sbdf-libraryThe TIBCO Spotfire® SBDF Library is a programming library for reading and writing files in the Spotfire Binary Data File (SBDF) format. The library can be used to add support for this format to an application, enabling it to natively create and consume data in a way optimized for analysis in Spotfire. The library is available for both .NET and Java applications.Note: If you are writing an Spotfire extension you should not use this DLL. Instead, use the DLL provided by the Spotfire SDK.
Include HERE Maps Flexible Polyline as format much like the Encoded Polyline is included in the Geometry Encoding.Documentation can be found here: https://github.com/heremaps/flexible-polyline Unfortunately HERE Maps uses another type of encoded polyline as a variation from the standard.This would be great to make API requests and return their version of the polyline, and feed directly into Geometry Replacer to create the Geometry.
Today we can only make use of fme.macroValues[]. This is just a list of ALL parameters in the entire workspace. This no longer works at the moment you start creating custom transformers because the parameter name get extended with the name of the custom transformers it's embedded and you can retrieve those. The parameter content is also not escaped or evaluated when linked to an attribute.A method maybe called fme.getParameter(<parameter name>) that has the same behaviour as the ParameterFetcher would do wonders. Today we need to transform parameters into attributes, pass them through the PythonCaller and remove them again after the PythonCaller. Many additional steps that could be avoided and reduce performance and potential errors.
When working with git and FME together it's pretty difficult to perform code review and to merge changes, at least if the same .fmw file is touched.What would really help is the ability to split up an .fmw into a number of files so that changes and merge conflicts can (more) easily be resolved.For example, one file could be just list the transformers and parameters set, one file to handle the content of comments and bookmarks etc, and one project file which has the positions and workspace parameters etc.If a developer could use a structure like this changes would be much clearer and it would be much easier to compare git-branches.Opening the project file would be the same as opening up a workspace, the files would be compiled together.There would also need to be a way to compile the files into a normal .fmw file so you could include this step in a build pipeline.
Add nextCloud / ownCloud in "select file from web" and add a nextCloudConnector transformer.
If a workspace is set to "ignore failed readers" I notice that there is still an ERROR logged, however, I feel like this should be logged as a warning instead.
To make data inspecting easier sometimes will help to have some of the hidden attributes available in the Table View. Exposing attributes inside the FME Workbench is great but it will be also good to have the same option inside FME Data Inspector; to avoid reprocessing. That is very useful when working with a large dataset with many attributes. I've experienced a need for this while working with BIM/IFC files. Attributes inside Table View can be used for data filtering and that helps a lot while inspecting some dataset. Expose attribute/s functionality inside FME Data inspector can be, for example, implemented as an context menu that opens on the right click while selecting one or more hidden attributes from the Feature Information Window.
In order to switch between connectors styles in the workbench we can just press "Shift+Ctrl+c" in the keyboard. Would it be possible to add "Shift+Ctrl+Mouse Wheel" ?
Reading data from the Esri Mobile Geodatabase will always prefix Tables/FeatureClasses with "main."According to Esri this is the logical database name. It seems this is mainly caused by Esri logics and NOT by SQLite.It would be helpful if the reader had an option to remove this. Similar to what Oracle reader (and maybe others) also allows to do.
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.
