Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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!
***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.
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 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).
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.
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.
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
New Certification for FME Server
When I publish a workspace to FME Server and set the job success and job failure topics for the service I don't see the resulting publication listed in the notifications page (publications) of the web UI. It would be good to list these as workspace publications when this happens. This would also be great when a workspace is published and the Notification Service is set and topics are selected. This should also place an entry in the publications list.
Add all the key/value pairs of a list as attributes. Essentially the equivalent of @SupplyAttributes(&key,&value) for each element in a list.
Add the ability to generate tiles with overlap, either by number of pixels or by distance. Current hack is to get the bounding box, tile it, buffer the tiles, get their bounding box (ensure square corners), clone the image(as many times as there are tiles), and clip the image by the tiles with a group-by such that each tile clips the original image. (This last can be avoided if the clipper can deal with overlaps)
I need to group objects with the same classification if they are close to each other.But each class has its own value for the allowed distance.That value is stored in an attribute.I can group the features in the NeghborhoodAggregator, but can not use the attribute for width and height.I would like the option to use an attribute added to this transformer.
MapInfo supports per row symbology in all supported databases (Oracle, SQL Server, PostGIS, SQL Light).It would be nice if all these database readers and writers support MapInfo Symbology not just Oracle Spatial Object reader.Storing the per row style is the same in all databases as in Oracle: the symbology string (which is the same as in MIF format) is stored in a column usually called MI_STYLE.
With old FME versions, it was possible to use both lowercase and uppercase attributes when writing out to Oracle databases.This is no longer possible since FME 2014 build 14131. The only workaround I found is to copy+paste feature types from old workspaces to new ones. It is not really user friendly and I assume that in this manner the old 2014 Oracle writer is used even with FME 2016.
A transformer that would split each input polygon by any intersecting lines. Sort of like the inverse of LineOnAreaOverlayer. I can accomplish this using existing transformers, but it takes about a dozen transformers to do so (several of them blocking).
I think the 'Accumulation Mode' parameter in the Aggregator should be set to 'Merge Incoming Attributes' by default, when the "Mode" is set to "Attributes Only". No one noticed ever?
The current tool can output a lot of “sliver” holes or spikes if the data is not clean to begin with. The majority of these holes approach or are at zero area. (The hole vertices are essentially collinear.)
***Note from Migration:*** Original Title was: Better and more consistent support for lists/collections (of one) when reading XML Hi,I've just encountered a very irritating problem, that comes from FME handling lists/collections in an unexpected way (at least to me).When I read an XML file, each item may have a collection of sub items, which may contain 0 or more items.When FME reads the parent item, and finds sub items, it stores these in a list.EXCEPT when there's just one sub item! Then the sub item attributes gets stored in non-list multi-level attributes.This is inconsistent imho. If there are _any_ sub items present, a list should be always be generated. [MY SUGGESTION]In the current scenario, I need three transformers to handle the case:Test whether the multi-level attributes exist (single sub item), or the list exists (multiple sub items).Rename the attributes if a single sub item is found.Explode the list if multiple sub items are found.If the list was always generated if there are any sub items, I only need step 3.The multi-level attributes could still be created, if a single sub item is encountered, to keep backward compatability.CheersLars I.
As discussed in this thread, the PDF spec allows for layers to be locked, this means that when the file is opened in a PDF reader the user cannot toggle the visibility of those layers. It would make sense to put general information (in the case of a map: logo, legend, title, grid, map collar etc) on locked layers and only have the user control the map data layers.Right now FME doesn't support this, we have to do this in Acrobat after the file is created, but obviously that's not an option for high volume or automated processes.
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.
