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.
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
Dynamic Lists: Remove element from a list and add element to a list with a specified index.
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.
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.
Add this format in FME
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
The 'Update Type' etc. required in the XMLUpdater is different depending on whether the XML tag already exists or not ('Replace Contents' or 'Insert' respectively). This makes it very awkward to deal with XML of unknown completeness.There should be a way to create a tag , including all the hierarchy above it, if the tag doesn't exist and just 'Replace Contents' if the tag does already exist.e.g. Update TypeXML PathValue TypeValueInsert or Replace Contents/metadata/dataIdInfo/idCitation/date/reviseDateXML/XQueryfme:get-attribute("_timestamp")...should generate...<metadataxml:lang="en"> <dataIdInfo> <idCitation> <date> <reviseDate>20161116</reviseDate> </date> </idCitation> </dataIdInfo> </metadata> ...whether the starting document was <metadataxml:lang="en"> </metadata> or<metadataxml:lang="en"> <dataIdInfo> <idCitation> <date> <reviseDate>Yesterday</reviseDate> </date> </idCitation> </dataIdInfo> </metadata>
The first thing I have to do every time I open a XMLUpdater's properties is stretch the form to near whole screen width.The first thing I have to do every time I open a XMLUpdater's properties is to adjust the column widths in the 'Updates' list so that the 'XML Path' and 'Value' columns are wide enough to see their contents properly.The properties page should either remember what size it was previously and what the column widths in the 'Updates' pane were OR it should size itself to show all of the widest record in the 'Updates' section or to be the whole width of the screen, whichever is the lesser.
***Note from Migration:*** Original Title was: S3ObjectLister: Option to list folders (including empty) as unique or separate features Currently the S3ObjectLister (FME 2017.0 Build 17201) will list all File objects. Please vote for this Idea if you would like this transformer to have the option to list Folder objects as unique/separate features.
Currently, the SNSSender can only reference existing attributes or user parameters (FME 2017.0 Build 17201). If the Subject and Message parameter values could be set with the Text Editor, it would be possible to create dynamic values, e.g. "Current Status is @Value(_status)!"The current workaround is to use the AttributeManager to create an new attribute is this way, and then reference it in the SNSSender. It would great to have a one-stop-shop!
The XMLUpdater properties page doesn't expand vertically past the size where 5 rows are visible in the 'Updates' pane. It should stretch as far as I want it to.The updates soon get unwieldy even so. I should be able to create and name tabs in the 'Updates' pane that collect my updates into related groups (I currently have to have a separate XMLUpdater transformer for each set of update operations so I can organise them into self-documenting functional groups).
Please vote for this Idea if you would like to see the transfer status (e.g. % complete) when uploading using the S3Uploader. When I upload large files with the S3Uploader, I have no indication if my FME Workbench is stalling or if it's in progress!This enhancement might not be possible if AWS doesn't provide this information using their endpoints.
***Note from Migration:*** Original Title was: attribute names import function in "Attributes to Remove" in Dynamic Properties.
It will be a new version between FME Server and FME EnginesSimple Business requirement:Run a workspace from REST ApiEnable websocketdisable notification servicedisable shedulersdisable administration FME Uidisable clean notificationdisable smtp serviceWhat do you think about this idea ?Thx
Some Readers are used to access data that may be static (doesn't change at all or changes rarely) or during development/debugging one should consider not hitting a DB server frequently with the same query. So all or some Readers should have an option to mark it as 'static', and some caching mechanism would be implemented.
More responsive with mobile
Make it possible to use stardate as an option in logfiles
When joining tables from different sources, it helps to know if the data is constrained by the database to being unique and not null instead of doing a pre-join validation (duplicates + nulls).
The extraction of specific content of the web page, Generally use HTMLToXHTMLConverter, then use the method of extracting XML elements to obtain, but many pages can not be converted successfully into XHTML. if JavaScriptCaller can support DOM, Be able to use some of the features of DOM, such as getElementById (), getElementsByTagName (), and so on. This will be more easy to get web elements.
Currently on a two input port transformer like NeighbourFinder:"in order" means that an entire group must reach both ports before the next group reaches either port, for the transformer to work as expected. I would like the order by group to work independantly, such that PortA can receive the first feature of Group2 before PortB receives all the features of Group1
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.
