Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
***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: 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
***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.
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.
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: Allow for support of multiple custom Python interpreters on the same system for FMEServer (and Desktop)
***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.
Dynamic Lists: Remove element from a list and add element to a list with a specified index.
AEC Geometry & Extended Data from Autocad Architecture to SHPAdd the ability to export the geometry and extended data definitions of AEC objects from autocad architecture and combined the geometry and data into shapefile - also setting the coordinate system - currently done via map 3d
Hi, I have to replace all z-values=0 with a NULL value. Unfortunetely the CoordinateReplacer doesn't accept NULL-values, even when created using a NullValueMapper before. I figured out, that it works when I replace them by the value "NaN". But I think it's not really obvious to the user and it would be better to have a NULL-Value in the rightclick-list of the Replace-field, like in the AttributeCreator for example.
test-precision.fmwThe idea is around one to be able to maintain a “grid”/coordinate precision for geometry handling within a workspace. Using certain transformers introduces back a higher precision => re-introduces the limitations of floating points that we have currently in FME. Let’s say, rounding the coordinates, or using a a source with a certain precision + doing a spatial intersection (lines, areas) removes the rounding and mixes rounded coordinates, where we have not intersected for instance, with higher precision where intersection happened. Attached a workspace to mimic the issue. Rounding again coordinates will fix the problem on this small example, but the problem can be bigger with higher amount of geometry, trying to maitain shared boundaries, etc. Rounding will also be a be random to closest coordinates and can create small difference in coordinates of features sharing same end points, boundaries, etc.
Add this format in FME
Ability to apply conditional Group By. It could prevent to carry and generate additional attributes if Group By had the option of being a conditional test, or if expressions could be used. Group if a certain attribute is in range of another. Using expressions would be useful for instance while acting on the result of ‘If, Then, Else expressions’. In summary make the group by more dynamic.
Right now, to assign an annual subscription to an instance other than the one initially specified, the instance assigned to the subscription has to terminated to release the subscription. It would be nice if the account owner could choose to which instance he wants to assign his annual subscription in a more flexible way.
Standardization Agreement (STANAG) defines processes, procedures, terms, and conditions for common military or technical procedures or equipment between the member countries of the alliance. Each NATO state ratifies a STANAG and implements it within their own military. The purpose is to provide common operational and administrative procedures and logistics, so one member nation's military may use the stores and support of another member's military. STANAGs also form the basis for technical interoperability between a wide variety of communication and information systems (CIS) essential for NATO and Allied operations. There are several STANAGs like this. For example some imagery related STANAGs: STANAG 4545 (Edition 1, Amendment 1, 14 April 2000): NATO Secondary Imagery Format (NSIF) STANAG 4609 (Edition 1, 23 March 2005): NATO Digital Motion Imagery Standard STANAG 7023 (Edition 3, 16 September 2004): NATO Primary Image Format (NPIF) Support for STANAG specifications in FME would be a good break through in the defence and intelligence domain across the globe. Hope this idea gathers momentum and STANAG is implemented in FME. Here is a link to STANAG on NATOs's site: www.nato.int/docu/update/2007/pdf/majic.pdf
It would be nice if there was a mechanism for leaving feedback on items on the FME Hub, particularly custom transformers.
Orbit allows you already to export to many "standard" formats. However, it uses also its own file formats with some advantages over the non-native ones. These would be Orbit Vector File .ovf, Orbit Vector Tiles .ovt and Orbit XML File .oxf:You can find more information on these formats on the Orbit Knowledge Base: https://orbitgt.com/kb/technology/supported_formats/index?s%5b%5d=vectorNote: there is already an FME extension for Orbit: https://orbitgt.com/kb/technology/supported_formats/vector/fme
***Note from Migration:*** Original Title was: attribute names import function in "Attributes to Remove" in Dynamic Properties.
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.
