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.
It would make life a lot easier if there was an x,y search in the data inspector. I have to find a lot of features by their location and its awkward to try and pin point an area. The mark location is nice but if there was a zoom to location I would make use of that.
***Note from Migration:*** Original Title was: SpatialRelator / Spatialfilter: Add a note in the log when coordinate systems are different SpatialRelator / Spatialfilter: Add a note in the log when coordinate systems are different
Add an additional column to enter an error text or concatenated text in the AttributeValidator would be cool...
It would be nice if an existing FME Cloud instance could be copied or moved to another region that is supported by FME Cloud. Right now a new instance needs to be launched in the new region and a migration of FME Server has to be performed.
In the Mac version of Workbench the tabs are a much darker shade of gray than in Windows. This makes it difficult to read the text on the tab. Could the user be allowed to change the color of the tab like they can for annotation/bookmarks? This would make the text more readable and allow more customization within the workspace.
When trying to clip a raster to a polygon if the spatial extents don't match, no warning is given, no errors. Just no features are written out, but reports 'success'.
I would like some mechanism to dynamically add attributes to a writer – presumably linked to some transformer. Note that this is not a dynamic schema -- The attributes do not exist on the source data, and I don’t know ahead of time what the attributes will be so I can’t manually add them to the writer. An example is any key/value pair from a list (ListHistogrammer for instance) where I would like the attribute name (key) added to the writer.
It would be nice if there was a native fme transformer to intelligently join file path components, similar to python's os.path.join.ie concatenate all the parts with exactly one directory separator ( or /) unless already included in the part, ignore empty parts except the last.So something likeattr1: d:attr2: dir1attr3: dir2attr4: dir3dir4attr5: {missing}attr6: file.extwould become d:dir1dir2dir3dir4file.extEven better if it could work with either a series of attributes or a list
If that is even possible……Assuming you are reading in poitclouds and want to make hillshades - using the ArcGIS hillshade_3D function - out of them.So you read the poitclouds make the raster with a DEMGenerator.Now you want to call the ESRI hillshade function (and other functions) with a PythonCaller using arcpy.But first you have to save the raster on disk, so ESRI can access it by reading it in again.In Python arcpy you can use the ESRI in_memory workspace:env.workspace = r"in_memory"env.overwriteOutput = TrueinRaster = FME_MacroValues['inRaster']inRemapFile = FME_MacroValues['inRemapFile']arcpy.HillShade_3d(inRaster,"TMPRaster", azimuth, altitude, modelShadows, zFactor)OutRaster = ReclassByASCIIFile("TMPRaster",inRemapFile)OutRaster.save(FME_MacroValues['OutRaster'])arcpy.Delete_management("in_memory")The raster comes to the PythonCaller as an FME object.So instead of reading the raster from disk again, it wold be great,if you can write the raster (or any other point, line or polygon Feature)directly into the “memory workspace” of ESRI.With a parameter – lest say selfdistruction Yes, or No – you can copy the feature into the memory workspace,or move it there and delete the FME object from memory.After the ESRI functions you can read the object back from the ESRI memory into the FME memoryand the translation continues in FME with some tiling or reasampling the raster and writes the rasters finally to disk.
Please improve transformer documentation specifically on the Join On parameter. @takashi provided a good on his blog: http://fme-memorandum-takashi.blogspot.com/2013/10/join-on-parameter-of-featuremerger.html. It would be nice to include links to samples, if any.
***Note from Migration:*** Original Title was: Add "Attributes that must differ" like in the MATCHER to some (or even all?) transformers that use "group by" e.g. in the commonsegmentfinder with that you could connect the same source-line-Features in Base and candidates and you could easily find common Segments in one source by Setting "Attributes that must differ" to the ID of the source
It would be nice if tutorial web pages did not assume you knew certain steps by saying things like "Upload your data to your server instance", but could also be cumbersome for more experienced users to see all that. It would be better if this were handled similar to ESRI's online courses where the details of a task are hidden unless a user clicks to show them. This avoids opening a new web page with previous instructions on it where the user then has to read through and find the pertinent information. Instead the task would say "Upload your workspace to the server instance (show me how)" and clicking on "show me how" would expand, on the same page, a set of bullet point instructions on uploading data to a server instance. This keeps the user on a single page and does not make them find where they were in the text when they come back from another page. This way the experienced user does not need their hand held, but novices have direct access to what they need to know,
***Note from Migration:*** Original Title was: upgrade Neighbourfinder (and networktopologybuilder) with function "used geometry" Problem:I often Need only to use start- and end-Vertices of lines to pass through the neighborfinder-transformer (as well as Networktopologybuilder)So I must use the Workaround to:1. use the Counter to get an ID for the lines2. coordinateextractor 2 times do get first and last coordinate3. vertexcreator to create start and endpoints4. use the neighbourfinder to find out wheter a line's start- or end-vertex is nearby (what I actually wanted to know!!)5. use the featuremerger with the original Feature to get the Information on the original-FeaturePossible Solution:Upgrade the Neighbourfinder with the Parameter "used base geometry" with the possible values:"All Geometry" -- means the whole geometry, including lines between Vertices"Start-Points""End-Points""Start and End Points""All Vertices"This could be also helpful with the networktopolgybuilder (Start and Endpoint could help!!), because a lot of users seem to have problems with selfintersecting Features and other "invalid" Features (sometimes the Invalidation is only in FME, not in Reader or writer, where e.g. selfintersections are allowed)
***Note from Migration:*** Original Title was: Add the ability to create a new layer in an existing feature service on ArcGIS Online
The xmlTemplater currently resolves most html entities such that é becomes é. In cases such as where I'm trying to generate html, I would like the option to preserve the entity as is, rather than resolving it.
Improve WorkspaceRunner so that when running asyncronously (Wait for Job to Complete = No) it keeps track of all fme.exe PIDs till they end and only there it finishes the parent WorkspaceRunner.Reporting full time of execution and realistic end of all JOBS it fired for execution.
***Note from Migration:*** Original Title was: FME Objects: introduce setPartAt() and removePartAt() methods for all aggregates/multis I would love to see 2 new methods on all aggregates/multis (FMEAggregate, FMEMultiSurface, FMECompositeSurface etc.) classes in the FME Objects Python API, as this allows us to manipulate parts in a less tedious manner.I'd like to be able to just replace or remove a specific part by its index, using a setPartAt() and a removePartAt() method.Now, we can only append a part (appendPart()) or remove it from the end (removeEnd/LastPart() - I see both names in the API), but what if I simply like to replace some part by another geometry or remove one part? Then I'd have to create a new empty aggregate, read the parts from the current aggregate using getPartAt() and then copy over the ones I want to preserve in the new aggregate using appendPart(), adding/skipping the parts I want to replace/remove respectively. The biggest problem here is that I loose all transformation matrices in the process, so I also need to copy those over. Using the proposed methods, we could just leave everything intact.
When you use a Triangulator on some surface that has a transformation matrix, the matrix is always applied. I propose that FME respects the matrix and leaves it intact, performing the triangulation on the local coordinates of the geometry. Or at least make it optional.Now, I realize that this wouldn't work for aggregates/multis, because these might have a "parent" matrix and "child" matrices, whereas the result of the Triangulator would just create one big mesh. That could be dealt with in one of the following ways:For these types of geometry, just apply the matrix (keep current behavior)Only apply the child matrices, but keep the parent matrix intact and transfer it to the output meshTriangulate all non-aggregate/multi child parts and leave all matrices intact, which means that the output will not be a mesh but remains an aggregate/multiI'd prefer option 2 or 3, but of course, this could also be another option which can be set on the Triangulator.
***Note from Migration:*** Original Title was: How about adding a 'clip or no clip' toggle in your Overlay transformers? They force clipping now. You do have the SpatialRelator and SpatialFilter transformers to address it, but it seems much less intuitive
I would like to argue for more consistency in the log messages that readers generate. Specifically the message about which source file is being read.For example the Shape reader says: Opened Shape File 'C:FMEData2016DataElevationModelContoursJ11.shp' for inputThe MITAB reader says: Opened native MapInfo file `C:FMEData2016DataParks\\Parks.tab'The PostGIS reader says: Reading POSTGIS table: 'public.steden'...The ACAD reader says: Successfully opened the 'Release2013' AutoCAD file 'C:/FMEData2016/Data/Transportation/Roads.dwg'Note that the wording is slightly different but at least these readers all report which file they're reading. The GML reader doesn't though... it shows quite a lot of information about how it's reading the file, except the filename. So when I was doing a bulk load of a large dataset, 90+ GML files of 300+ Mb each into 15 PostGIS tables, which failed about halfway through I had no easy way of finding out which files had processed properly and thus could be skipped in the next load.I ran into this issue when using the GML reader (FME 2016.1.2.1), but with 360+ readers there might be more that have this shortcoming.
The "Set Default Value" option in the AttributeManager only works for new attributes.That forces me to use a NullAttributeMapper for each different default value (multiple attributes).Adding this to the AttributeManager (Set a default value for Null and Empty attributes) would reduce the number of transformers in my workspace.
***Note from Migration:*** Original Title was: Allow for support of multiple custom Python interpreters on the same system for FMEServer (and Desktop)
FME is currently unable to read Civil3D surfaces directly from the Civil3D dwg file. I have posted my workaround HERE but it is not perfect and requires too much pre-processing before you can read in FME. Also, you would have to remember to repeat those steps every time the source surface changes. I've also experimented with a workspace to derive the boundaries from the LandXML file, instead of one extracted in Civil3D, then trim the surface to those boundaries. But it only works if a boundary was input in Civil3D, still not perfect and still requires a LandXML file be created after every surface change.
***Note from Migration:*** Original Title was: If a job fails for any reason, send to Amazon Alexa (+ others) and have her alert this in some way Failure emails are nice, but I'd love to have this in addition -- it's especially great for environments with multiple Echo / Echo Dots. Someone would hear a verbal cue or special alarm -- maybe I'd even get out of bed to go resolve / restart -- would save a lot of cycle time on bleeding edge new development.Can you tell I had an easily resolvable failure shortly after I went to bed last night (wasted 8 hours of cycle time)?=)
***Note from Migration:*** Original Title was: Warning for deleting a workspace, if it is still scheduled task for this job available! An important alarm message should be implemented that a warning appears on the web interface when deleting a workspace if there is an associated scheduled job.Currently, only the workspace is removed (without reference to a scheduled job).If the workspace is deleted, the scheduled job is still active, and then logically fails. Ideally, a query would be desirable if the associated scheduled job should also be removed.
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.
