Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
With normal writer, You can duplicate the Feature Type. But in thenFeatureWriter, You can not do it. Sometimes, Different Featrue Type have the same attributes, just different Geometry, The duplicate function will be very useful. I hope add duplicate Feature Type to FeatureWriter.
Would be useful if there was an option to save a copy of a workspace. Sometimes I like to back them up before I get REALLY crazy (i.e. try a different method, transformer, parameters, etc.) and don't want to press Ctrl/Cmd+Z a bunch of times.
Zwift.com provides a VR for riding bikes on trainers. There are many times I'd love to "relive" the biking experience after the fact. For example, I was dying on a hill one day. I went to work the next day to download open source DEMs and see just how bad that hill really was. Zwift rides can be downloaded in *.fit files.
Please add support for GeoSciML__If you are interested in FME adding support for this format, please provide us with more information by voting and describing your use case!
***Note from Migration:*** Original Title was: Provide setting to allow transformers to be expanded horizontally by default so their complete name is readable I have no idea if this is just me but I make sure the name of every transformer is completely visible. For transformers with longer names, this requires me to double click the right side expanding it so the complete name is readable. Can't this functionality be default when adding a transformer to the workspace?
Adding a background mapAdding a background map could be done straight in the Data Inspector main UI. Now it's a bit tedious to go to Tools > FME Options and set the background map there.Multiple background mapsAt the moment, you can have only 1 background map at a time in Data Inspector. There should be a possibility to add several background maps to the same view.Background map opacityNow background maps are lacking opacity control.Save background map for later useWhen you change your background map settings, the previous background map is gone. It should be possible to save the settings in the same way you can do for Database Connections.These problems occurred, when I was setting a WMS background map. I changed it later to a different background map, but wanted to go back to the WMS background map. I had to set all the WMS parameters again.
In the current ChangeDetector, Original Unchanged and Original Deleted features have Ports, while Revised Added features also have a port. Can we please have a "Revised Unchanged" port added?This is because the ChangeDetector can be used for just some attributes, rather than all attributes, meaning it may be testing a range of scenarios, yet we lose the "Revised Unchanged" features by using the transformer, and this may be the subset we want.
Not just the current "Feature Information" windows which can be used in Debugging, but Inspectors would pop up. (This is the so-called Frankenbench showed at the FME UC)
I've been using a competitors product a bit of late and one great feature it has that makes FME very frustrating is how long inspectors take to open . Often all you need is a couple of data rows to decide what you want to do and the alternative product allows you to click on any transform post run and INSTANTLY see 1Mb of data for each input and output port. This makes building workspaces so much faster. The sacrifice to make this possible is the configurable 1Mb limit on the data. I can't find a way to come close to this in FME DesktopSo, - When doing a full inspector allow preview of the data that opens very fast.
The latest builds for Mapnik allow for Vector tiles services for map services. Would it be possible to set something up using FME server and this technology? Currently the WMS and WFS feeds using FME server are a little clunky to use and quite slow.
Currently there is no facility to change the FME Cloud account URL after creating the account. Even though the documentation here suggests that the account URL can be altered by changing the Account Name, it doesn't work properly. eg: if the current URL is https://<instance name>-<base url 1>.fmecloud.safe.com and if we need to change it to https://<instance name>-<base url 2>.fmecloud.safe.com Therefore, it is worth to add the capability of changing the account URL at least for instances launched after the changes. It is awesome if the changes to URL can be applied to all the instances including existing instances.
The current credentials file that can be downloaded after an FME Cloud instance has been created only contains usernames and passwords. It would be useful if the instance url is in there too (I just had to pass 12 sets of credentials to trainees...)
I see that the Database Joiner transformer only supports the Open API for file geodatabase, it would be useful if it suppported ArcObjects as well.To flesh this out a little more, basically allowing the same functionality as the ArcObjects reader when bringing in a file gdb table in this tranasformer would be useful. Of coruse the workaround is to add a reader and feature merger, but the functionality in the single transformer would be useful.
I'm interested in reading data from Bentley's new Open-source JavaScript library, iModeljs.Hi FME Users, If you are also interested in FME adding support for this format, feel free to provide us more information by voting and describing your use case!
What I really love in the new versions of FME is the 'Attribute Tree'. This occurs if you place a . (dot) into a attribute name. It is a great way to group attributes (from different streams) into sub groups.For example in this project I have global parameters that are generated in the beginning and used in every feature.If I create a new attribute before this transfomer, all AttributeKeepers need to be adjusted. It would really help to wildcard these groups, because I know I need all my "global." attributes.So a small toggle on the main group with 3 modes:- empty (no childs)- block (some childs)- circle? keep all childs, without having to reselect when a new one is added to the groupThe last option would be a dynamic selection. For example: keep all " _global.* " attributes
It would be nice to enabel/disable the filled background for every bookmark in the properties seperately.In this way the user would have more possibilities to design a complex workspace more clearly. For example, some bookmarks could be displayed with a fill color and others without.At the moment you can only generally set whether the bookmarks should be displayed with filling colors or without a filling color.
You could read the images that are inside a tab of an excel file
Similar to this idea: https://knowledge.safe.com/content/idea/87500/process-started-by-the-systemcaller-should-end-if.html I think more should happen when a user has aborted a workspace (or at least it could be an option workspace parameter).In this case I think that a defined python/tcl shutdown script should run even if the user aborts the workspace.As mentioned in this Q/A https://knowledge.safe.com/questions/87933/python-shutdown-scrips-when-workspace-cancelled.html there is a limitation when it comes to live streams, the only workarounds being pretty ugly in nature.
***Note from Migration:*** Original Title was: Portal Reader Feature Service Parameter - allow portal items shared to the connected user to import the service's layer list In the reader's Parameters Constraints box, when a feature service list is displayed in the dialog, only the feature services owned by the connected user can display a Layer list pop up. If a selected feature service not owned by the connected user and the Layer ellipsis is clicked a Python Exception <KeyError>: u'items' appear.
It would be great if FME could support open location codes like Google's Plus Codes This would be a really useful alternative for places that aren't easily located otherwise. I'd like to see this functionality supported in the GeometryReplacer or GeometryExtractor.
Inspired by https://knowledge.safe.com/questions/74227/smooth-line-keeping-vertex-positions.html
Hyattached the dataset that I used to test center line replacer
Original Title: Extraer geometrías de las anotaciones de un PDFOriginal title translated to english for improved searchablityPara agilizar trabajos, con base cartográfica, sí se tienen que dibujar áreas sobre una cartografía existente. Usando las anotaciones del PDF, se podrían exportar también al igual que el resto de información.English translation: To expedite cartographic-based work, areas do have to be drawn on existing cartography. Using the PDF annotations, they could also be exported just like the rest of the information.
I've been experimenting with the System caller to run third party command line tools. It works great for the most part, however, when you stop the workspace the called process keeps running.It would be nice if the call could be killed/cancelled when the FME process is aborted. The problem is compounded when the sub process leverages the folder created by the TempPathNameCreator - If the FME process is aborted then these files do not get cleaned up.Idea comes from this QA: https://knowledge.safe.com/questions/87473/process-triggered-from-system-caller-does-not-end.html
InfluxDB is fast becoming the most popular Time Series Database for DevOps, IoT sensors, financial data,etc. It is an Open Source platform that composed of 4 services called the TICK stack. Telegraf is the "T" and is has a plug-in architecture for reading and writing to many different databases and data sources. InfluxDB is the "I" and is a NoSQL DB but supports SQL style queries, a scripting language called TICK script and a newer fuller featured language called Flux. Chronograf is the "C" and is a browser based client for configuring, visualizing and creating alerts. Kapacitor is the "K" and is and is a real-time data streaming and processing engine that allows you to do simple and complex operations on your data. I use InfluxDB to capture GNSS data in real-time. It would be great to be able to read that data directly and process it with various translators to calculate volumes, generate contours, convert to different coordinate systems, etc, etc. It is also great for downsampling and thinning data and even has fill methods for interpolating over data outages if you want.
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.
