Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
I was running a workbench from G: and wanted to view my logs. So I set my writers to output a log file for G:Logs but it didn't want to do it. When I created the folder 'Logs' it worked fine.In future releases it would be great to have FME automatically generate the neccessary folder(s) to place a log file in
Currently if the Feature Reader is set to Generic (Any Format) and the Input Format is set to <Guess format name from extension> and the format name is unrecognized then it reverts to a NULL reader.|WARN |Generic Reader: Unable to guess a valid reader name from dataset 'x'. A NULL reader will be used instead.A NULL reader produces no features, so this ends the translation successfully.The trigger feature should instead be routed through the invalid port so the issue can be caught and dealt with, or at the very least cause a translation failure.
Looking for a transformer to establishing the largest rectangle that would fit inside a given polygon. The mathematics behind it is extremely complex, though would be happy if it only worked with convex polygons to simply things.This idea isn't exactly new.Previously raised in a few questions:2015 - https://knowledge.safe.com/questions/4879/maximal-rectangle.html 2018 - https://knowledge.safe.com/questions/65011/maximum-inside-rectangle-from-an-polygon.htmlHowever, I don't believe it has been raised as an idea yet.
When a single parameter is selected, right-clicking will give you the option to convert from a public to a private parameter and vice versa. But that option is not available if multiple parameters are selected.
Add the ability to generate Metadata for existing image files such as TIFF or JPEG. For example, I have a directory of tiffs, and I want to go ahead and generate Application specific Header files such as tabs, tfw’s and ERS. At the moment we are having to go back and use global mapper to generate these files.This is also Important to not re-write the image itself as if the format is lossy compressed, each re-write degrades the image.
Hi,It would be great to have the possibility into the Excel Writer to choose the Start Column value with an attribute value.See this post for infos : https://knowledge.safe.com/questions/96709/excel-start-column-value-option.html?childToView=96769#answer-96769
I would like the ability to expose (or create) on each feature the path that feature took in the workbench. I think this could be best executed in a list format, where for example, the first transformer a feature passed through is feature_path{0}.transformer. The second transformer would be feature_path{1}.transformer...etc.I think this could help with pinpointing errors in the workflow.
***Note from Migration:*** Original Title was: ArcGIS Online and Portal feature writers to support adding and updating attribute indices If you are maintaining large feature layers that will be queried with non-cached expressions then maintaining indices on query fields will prevent full table scans on query. At the REST level it means passing JSON to addToDefinintion or updateDefinition, like this setting up a unique index on a field 'id':{"indexes" : [{"name" : "idIndex","fields" : "Id","isAscending" : true,"isUnique" : true,"description" : "Unique index on primary key field ID"}]}If the writer could do this it would help a lot.
It would be helpful if the COLLADA reader would support reading Geometry definitions stored in the DAE as definitions so we could use the Shared Item tools. Currently the COLLADA writer supports this - I can create a COLLADA file with a single model but unfortunately it seems when reading that these definitions are read as aggregated mesh objects. When writing the same file back out to COLLADA the size blows up because a new geometry definition is created. When working with a file with 1000 of such geometries it blows up from about 1 MB to over 250 MB...
I love the glTF writer and we have been using it a lot in conjunction with our Cesium based applications to help bring customer data into their interactive 3DCityModels.glTF is awesome because it supports both vector (lines/points) and True 3D surfaces. One issue we're running into, however, is that I'm unable to style the vector features in the output. The fme_color attribute appears to be ignored and the GeometryColorSetter/AppearanceSetter rejects it because it is InvalidGeometry...This means we're unable to bring in colors from CAD drawings which makes it lose some of its valueI would love if the gltf Writer would recognise the fme_color attributes.
When using the File Geodatabase Open API Reader, any domains are automatically resolved to their values. Please can an option be added to the Reader so we have a choice about whether this happens, as we do with the ArcGIS version of the Reader.See...https://knowledge.safe.com/questions/73616/resolve-domains-in-file-open-api-geodatabase.htmlhttps://knowledge.safe.com/questions/72775/is-the-fgdb-open-api-reader-able-to-read-fgdb-doma.htmlIt appears that a few people would find this useful.
I would like it to be possible to read the generated marks of a pdf, to be able to export them.This could generate pdf for changes, and then reload in the spatial database where the pdf was generated.
The 2019 version of the ChangeDetector has some great functionality updates. Since the fréchet distance is already calculated to determine if a feature is geometric match, it would be nice if we had the option to add that value as an attribute on the updated feature.ex.ChangeList{0}.action modifiedChangeList{0}.attributeName geometryObjectChangeList{0}.originalValueChangeList{0}.revisedValueChangeList{0}.frechetDistance 2.3
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.