Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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...
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.
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).
And vice versa - click on log line to see related transformer?
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.
Currently, FME has the ability to interface with the R Project through the RCaller transformer. This requires knowledge of the R Project language.It might be useful if FME had transformers that made it easy to harness specific functionality/algorithms possible in the R Project. One example of just such an algorithm is the Minimum Spanning Tree. My question for you is what R Project functionality/algorithms would you like to be easily accessible in FME? Another way to think about this is what statistical or analytical problems do you want to solve as part of an FME workflow?
I'm really excited about the RasterConvolver transformer in the 2018.1 beta. However it applies the convolution filter to all bands. It would be nice if this transformer supports band selection and only applies the convolution filter to the selected bands.
For a long time, most major OGC WFS servers have supported stored queries: ArcGIS, Degree, GeoServer, MapServer. In many cases, for performance reasons, WFS servers will not let you query more than one feature type at a time unless you define how the 2 are to be joined. Because these joins are hard to define, one of the easiest approaches is to define the join within a stored query. For example - give me all the parcels and roads in the town of Spuzzum. The only way to execute a stored query from FME's WFS reader now is to include the stored query parameters on the initial dataset getCapabilities request url, for example: http://gisserver.domain.com:6080/arcgis/services/SampleWorldCities/MapServer/WFSServer?service=WFS&version=2.0.0&REQUEST=getFeature&TypeName=cities?tIndex=0&count=5&STOREDQUERY_ID=urn:StoredQueries:AttributeDemo&myrank=3 Any parameters you add to the wfs request url eventually get passed to the getFeature request. But this isnt very intuitive so it would be nice to have this added to the WFS parameters user interface. Heres a good link describing most basic types of stored queries that it would be good to be able to support: https://enterprise.arcgis.com/en/server/10.3/publish-services/linux/communicating-with-a-wfs-service-in-a-web-browser.htm
MapInfo has a new format called the MapInfo Extended format supported from MapInfo Professional version 15.2. The format enables a few new capabilities but most notably the ability to break the 2GB file size barrier and store multiple character sets in the same file:http://web.pb.com/mapinfopro-oct-2015/MapInfo-Pro-v15.2-Breaking-Down-BarriersIt appears that the latest Beta of FME 2017.0 b17215 now includes a Reader for this new format, but this is a vote for a Writer for the same format please!
**I'm still using 2017.1, apologies if this has been resolved in a later version**Currently when you use AttributeValueMapper, the import allows you to import duplicate values rather than check if you've already got the value and mapped it in the transformer. Can this be enhanced to recognise the values already mapped rather than keep adding the same value again? Or even better, to enable you to sort on the 'Source Value' field?For Example, I'm consolidating a few datasets in FME hence might use the import feature twice once for a shapefile, another for a KML. I have High=1, Medium=2, Low=3 imported and mapped from the shp, then import the values from KML and get High (already exists), Very Low (new), Medium (already exists).
I think it would be great if the featurewriter could support multiple formats and coordinate systems simultaneously so we don't have to have several featurewriters for the same data.e.g. If each of the feature types added to the writer below could maintain their own format and coordinate system that would be awesome.
The layer name is available in fme_feature_type but the feature service that contains the layer isn't available.
Vector Tiles are awesome, and are gaining traction quickly. It would be superb to support vector tiles as a streaming output from FME server. It would also be valuable to download all vector tiles in bulk, so users can choose to host the tiles themselves (e.g. behind a CDN).https://www.mapbox.com/vector-tiles/FYI GeoServer already supports MVT. https://2016.foss4g-na.org/session/vector-tiles-ge...The major web map frameworks already support MVTI've been told this relates to PR#45586
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.
