Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
The Snapper currently has 3 snapping type options, end point, vertex, and segment, but in a lot of cases what I actually want is to snap end points (base snapping type) to either vertex or segments (candidate snapping type).
Include a list of schema attributes with checkboxes to expose in the initial PDF Reader Parameters, like most other readers have.
If the StringCaseChanger parses any values with an incorrect/incompatible character encoding, the translation will fail. It would be helpful if this transformer had a Rejected Port so that I could handle those situations myself rather than having the whole translation fail.
The RasterMosaiker Version 5 comes with a rejected port. However only non raster features are rejected through this port. Rasters that are incompatible with the mosaic (Different number of selected bands, different coordinate system, etc) still cause a fatal error, instead of being rejected.
***Note from Migration:*** Original Title was: Add functionality in the Microstation DGNReader to import the 'Named Group' value Hi,I have recently found out with the help of @danilo_fme (see post:https://knowledge.safe.com/questions/71597/expose-group-element-in-microstation-dgn-v8-file.html?childToView=71710#comment-71710) that it is not possible to import the 'Named Group' value from a Microstation DGN file into FME. It would be great if the DGN Reader was modified to enable the import of this value as an attribute.See attached a document describing the Microstation DGN 'Named Group' feature and also a screen grab of the Element ID properties dialog box with the 'Named Group' feature circled in red, within Microstation.Thanks,namedgroups.pdfdgn.jpg
I have a couple of ideas for enhancements to NeighborFInder. I work in the telecom industry & need to get the pole number at the start & end of fiber line. With that in mind I have the following ideas as enhancements to NeighborFinder1) Modify it to reference Vertex (#) in a line feature2) Modify it to reference X/Y Coordinates from attributes in Line features3) Modify it to allow us to extract only selected features
A new option "Attribute(s) must differ" in FeatureMerger to not merge entities if one or n attributes have the same value.Usefull to avoid "auto merge" if we use same entities in requestor and supplier ports.
It would be very convenient to standardize and always show the supported versions for each supported format in FME. E.g. looking at LandXML, somewhere in the LandXML Reader/Writer information is stated that a restricted subset of version 1.1 is supported and that additional support is planned for the future.It would be nice to see something like this:LandXML Reader/WriterLatest supported versions: 1.0 (full), 1.1 (partly)
Add support for high availability / fault tolerance to FME Cloud.FME Cloud is often touted as an ideal solution for receiving streamed data from web resources for continuous processing but the model falls down if FME Cloud isn't fault tolerant...
the arithmentic editor can be very difficult to use for even mildly complex arithmetic. a mathjax-style display engine would be amazing.
Could nautical miles be added to the GeographicBuffer? It's easy enough to convert and use miles, but would be nice to have the selection.
Workspace-wide settings for tolerance / precision on all geometric operations. The idea is to avoid miniature artefacts from e.g. clipping operations due to floating point imprecisions that are typically smaller than the dataset precision.
I am looking for a font styler that I can use with GeoMedia. I need to be able to set the colour, size, font style and justification. I have tried using other FME stylers and outputting it to an Access Database, but I am having no success.
Currently, FME has the ability to interface with the R Project through the RCaller transformer. This means that R processing is initiated by a run from within FME. It might be useful to run FME workspaces from within R. One way would be to provide an R plugin that wraps FME workspaces. Similar to rGdal or rGdalUtils : https://www.rdocumentation.org/packages/gdalUtils/versions/2.0.1.7https://www.rdocumentation.org/packages/rgdal/versions/1.2-13
***Note from Migration:*** Original Title was: The solution for Access token not found for connection ArcGIS online and FME SERVER Fix connection issue .FME SERVER Connecting to ArcGIS Online via FME Server The below video I have created to show the way how to fix this issue ,I did it and it's work with me https://youtu.be/kWj-LdX-A8E
The current VertexRemover only accepts one vertex index value. If you need to delete multiple discrete vertices, you must use VertexRemove multiple times. I want to specify multiple vertex index values, such as separating them with commas.
And vice versa - click on log line to see related transformer?
Currently there is no way to tell that a workspace or custom transformer stored in a repository has any history without selecting it (checking the box to the left of it) and then hitting the History button at the top of the page, or hitting History and then browsing/filtering the commits. An improvement would be to add an icon to the right of the workspace if it has history (like the star for favorite and binoculars for View Workspace), and allow the icon to be clicked to open the History dialog for that workspace.Might I suggest using one of the official Git logos: https://git-scm.com/downloads/logos, such as: or (or even a pale grey version for when no history exists, and the black or orange one when history does exist).
Existing transformers such as the RasterExpressionEvaluator only perform per-cell calculation. The user will have to make some efforts if a calculation using multiple cell values was required. e.g. the average of 8-neighbor cell values. It may not be impossible in the current FME framework, but would be complicated and inefficient.I hope that a new transformer will be introduced, so that the user can define a script to perform advanced cell value calculations efficiently. In the script, the user can:- retrieve the value of any cell in any band,- refer to the raster properties,- use control statements (for, while, if, etc.),- assign the resulting value to a cell of an existing band or new band (which can be added by the transformer),and so on.Perhaps it would be a kind of Python script editor/executor customized for raster operation.
Not a good start with FME. More time spent telling me to post in the "right area" than necessary.Anyway.....There needs to be a glossary of terms from a database perspective. FME appears to be good at etl in a non spatial world (or at lest that's my priority at present).There are hundreds of readers/transformers/writers and it appears you can use many to achieve a similar result.Finding the best r/t/w is tricky then not knowing the FME terminology adds to the "interest".Thanks.400+ transformers but how many in reality?
when the fme imap subscription has read an email there should be an option for it to either delete or archive the mail
If you load in an ISO time format (for example), it makes sense that you would be unable to convert to a date format, but you should be able to convert to %s without seeing an error.I created a workaround by appending a fake date on the front of the timestamp, but this seems a bit of an oversight?
In the FME interface and documentation, there are many terminologies special for FME.e.g. dataset, feature type, schema, mapping, file-based, folder-base, fanout ...There also are some terminologies having multiple representations to indicate the same concept.e.g.blocking transformers, group-based transformerscomplex list, structured listdata flow, workflow (it's vague whether these indicate the same concept or not)Also no name concepts.Although users can understand those concepts if they read the documentation carefully, it might be better if there were an official FME Glossary. I think such a glossary would help all users to understand FME key concepts more quickly, especially for beginners.
I would like a "Feature Types to NOT read" Option in FeatureReader when using the single output port.For instance, i'm using FeatureReader with the "single output port" parameter to read files inside a Zip file (i dont know filenames inside). But I would like exclude some files if they exist.At the moment i'm using Tester to filter feature types (fme_feature_type_name on Schema port & fme_feature_type on Generic port) but data has been already read so its a performance issue.
Hi guys,It's allmost to simple to imagine that no-one else has thought of this, but when I try to access the elements of a list from an attributecreator, the only possible choices are numbers from 0 to .... for the selection of an individual item of the list. Wouldn't it be a great idea to enable also an attribute reference for a number? So there is an attribute _list_index that I can select as the element sequence number for the element to select? Like the ListIndexer, so one does not have to use that transformer anymore, too.
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.
