Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I am currently using custom pushbullet transformer with in my workbench to send messages to users for desired coordinates in the event of an earthquake. But I am really looking to have some other transformer which can alert the users with voice calls instead of the messages.
Hi everyone,I'm currently creating a workspace that reads other workspaces and reviews them against our development standards. Unfortunately there are a whole bunch of things I need to test that don't seem to be available in the Workspace Reader.Can you just give us everything? :) I can filter out anything I don't care about, but I can't create what's not available!e.g.All of the information about a database connection (server name, database name).Whether an annotation is attached to a transformer and if so, its ID.Location on the canvas of any particular object.Whether a transformer is inside a bookmarketc etc etc.Thanks!
Suggestion: on a busy canvas, being able to rotate a transformer through 90 degrees i.e. from horizontal to vertical might make for a more ergonomic workspace.
The ability to write DTMs for use in Bentley Microstation InRoads.
I would like to be able to have multiple instances of Workbench open in my Mac OS. I could use that in order to refer to other workspaces while I'm creating a new one. I often copy and paste parameters and transformers from another FME workspace. It's more difficult to do that when I can only have one window open at a time. I'm also just looking at the flow in different workspaces from different projects. I'm not always plagiarizing myself from just one workspace. I also tend to work on more than one thing at a time. Because people in the office will ask me to change something in another workspace that I made while I'm creating a new one. I don't know of any way to open multiple FME Workbench windows on OS X now.
It would be nice if a parameter is shown in bold or another color when the value of it has been changed from its default value. For example, if the default value for Max Features to Log : 200 under Workspace parameters have been changed to 300, this would be shown in bold text.This could be changed in the Logfile and the Navigator.
The original CSV reader had the option to sort, and it was pretty quick too!
We are currently managing about 500+ workbenches, some in the filesystem some on FME Server. We try to name them based on the datasets they are working on and the source and destination systems/databases. We do not know if it´s the best way to keep up with finding them again, but up to this scale it works.A best-practice HowTo or tutorials about workbench documentation and management at larger scale would be great, maybe there are better ways than we do.
We ported all ETL processes to FME to have a single systems for all our dataflows. We tried to maintain a Enterprise Architect documentation about all our sources and sinks and the coresponding FME Workbenches to get a big picture of our dataflows.Since everything is in flow all the time it´s hard to keep up with the external documentation since it´s always manual work. It would be nice, since all needed information is already in the FME Workbenches, and all relevant workbenches are on FME Server, if the system would be self documenting and would generate some sort of enterprise dataflow overview, with all sources and sinks and the workbench names that are feeding and manupilating the data between the systems. Since all relevant wb´s are on the server it would be nice to click on them and get to them in some sort of way.
I can press Ctrl and + on Windows to zoom into text that is in the value portion of an attribute.Example steps to reproduce what I'm referring to:Set up HTTPCaller to make a GET requestOpen the resulting data in Data InspectorWithin the Table View, double-click in the _response_body area at row 1 to view the response in Code View.Press Ctrl and + to zoom in on the textOn the Mac, in Data Inspector, I'd like to be able to press ? and + in order to zoom in on text but I'm not able to do so, making the text difficult to read.
As an FME user, I would like to see support added for insertion scale units on the Autodesk AutoCAD Map 3D Object Data writer so I can specify the units. Currently, the workaround is to use a blank template and specify the units but this is a tedious task that needs to be done each time I want to write a new dataset.It would be great if there was a parameter similar to the one mentioned in this thread: https://knowledge.safe.com/questions/1906/write-dwg-with-coordinate-system-and-units.html
Sometimes in complex multi-drawing (workspace runner) scenarios it would be handy to be able to de-aggregate blocks into their component elements within the workbench instead of the reader.
Hi,I’m trying to build a dataflow using FeatureReader to read my files.Whenever I encounter a file with an error, the log file contains this snippet: 2016-11-24 09:50:12| 994.1| 0.0|INFORM|Expected a value string for '%L1KR', found '%KM1' instead, in line '916' of input file2016-11-24 09:50:12| 994.1| 0.0|INFORM|DSFL halted, approx. line in input file: '916' 2016-11-24 09:50:12| 994.1| 0.0|ERROR |Error DSFL expected a value string from the input file2016-11-24 09:50:12| 994.1| 0.0|INFORM|Closing the DSFL readerHowever, the feature output by the “<Rejected>” port of the FeatureReader only contains a single “_reader_error” attribute with very limited content:Error DSFL expected a value string from the input fileWould it be possible to enhance this error output significantly, preferably adding more error information (e.g. the offending line number), but at least so that the error message attribute reflects the full error messages shown at the top in the log file ?CheersLars I.
Import --> Dataset option to be added to JSONFlattener, feature reader (output port --> attribute to expose). Also applicable on JSONFragmenter, etc...
Imagine, some day, a new dimension in Workbench with transformers in 3D...So we could connect transformers in every direction of the space and move everywhere in the workspace.Transformers could be cubes or octahedrons or even dodecahedrons according to the number of needed ports.I don't have enough talent to draw my vision with a 3D software, but you probably got it.Ok it was my "friday delirium". I'm not even sure if it could be practical to use.
Hey guys,When utilising MapInfo Extended writer DELETE operation, the features are flagged for deletion, however the database is not "packed" at the end, and I have to go into map info to perform this operation to permanently remove these features. This causes large file sizes if there are constant deletions and additions on a native x file.Thanks,James
Hello,I often work with DGN files, especially version V7, and many times I need to map, if element is view dependent or not... As I mentioned below, value for this attribute is filled only in version V8. How complicated is to add support of this attribute in version V7, please?Thank You so much!Luboview-element.jpg
I'd like traceability as to who modified what workspaces/topic assignments/etc. It would be nice to be able to see what is taking place in an FME Server. Especially a production instance.
From FME2018.0 it is possible to collapse bookmarks. Maybe it is an idea as well to collapse annotations into an icon. It would be nice if you could choose between two or three different icons, for example an exclamation mark, a question mark and a ligthbulb. The different icons (maybe it should be possible to manually add them) can be you used to distinguish between the type of annotation
Currently to use the batch deploy option the workspace must have a writer. If there is not one, the option is greyed out. Given that are multiple ways to create data via transformers, this restriction no longer makes sense.
https://github.com/mapbox/geobuf Geobuf is a compact binary encoding for geographic data. Geobuf provides lossless compression of GeoJSON data into protocol buffers. Advantages over using GeoJSON alone: Very compact: typically makes GeoJSON 6-8 times smaller. 2-2.5x smaller even when comparing gzipped sizes. - Very fast encoding and decoding — even faster than native JSON parse/stringify. Can accommodate any GeoJSON data, including extensions with arbitrary properties. The encoding format also potentially allows: Easy incremental parsing — get features out as you read them, without the need to build in-memory representation of the whole data. Partial reads — read only the parts you actually need, skipping the rest. Think of this as an attempt to design a simple, modern Shapefile successor that works seamlessly with GeoJSON. Unlike Mapbox Vector Tiles, it aims for lossless compression of datasets — without tiling, projecting coordinates, flattening geometries or stripping properties.
It would be great if FME could check if all destination files are free for writing, and not currently locked by another application, during startup. Especially AutoCAD oder Excel file are often affected by existing locks that cause the workspace to fail at the very end causing some considerable aount of wasted time. If a destination file is locked the workspace should stop before any reader / transformer starts to work.
With a new computer and 64GB RAM there is not much that can slow down my computer to a halt. Using SurfaceModeller, working with raster and liddart takes time, howeve it does not render my computer laggy/non-responsive when running. Even with large datasets.But when using the PointCloudSimplifier this happens. It seems to be using 115% CPU. 60% memory still available, "no disk or network activity". Nothing else is running, computer is restarted and I have tried different las-files, smaller, larger etc. If it runs for 2 minutes or 2 hours the behaviour is the same.Is it possible to tune this transformer to use a little less CPU so you can "work normally" withouth this lag?
The ESRI SDE Reader should support circular arcs (like the File GDB Reader)
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.
