Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
When working with workspaces from version control systems like git or svn or when moving project folders relative paths make life much easier.Here are some ideas:option to automatically replace all paths with relative pathssupport relative paths in advanced browserpossibility to check workspace if all paths in workspace are relative...
The ISO8211 reader is a fantastic Reader for reading the ISO8211 dataset. However, the reader only accepts data with a file with extension "dde". Given the IHO S-57 ENC data (in *.000), its updating files (in *.001 *.002 etc extensions) and Catalog file (in *.031 extension) are in the ISO8211 data structure, the ISO8211 Reader does not allow these file unless the user manually changes the file extension into *.dde which are of inconvenience. Hence it is suggested that the ISO8211 reader could accept the iso8211 files with file extension other than *.dde.
Line features could have common attributes, eg line id or line name. The total length of a line by the common attribute is used to calculate against another translation, e.g. clipper. Lines outside clipper will reduce the total lengths to multiple line features of the same name and these collection of featured can then be calculated against the original length of the line to determine of percentage that are outside the clipper.
***Note from Migration:*** Original Title was: PDFPageFormatter will Auto-Centre and Auto-Scale the Data on its Input Ports to fit the Corresponding Boxes PDFPageFormatter will auto-centre and auto-scale the data on its input ports to fit the corresponding boxes. Very handy for raster and vector data, but not desirable for text data. Add a checkbox property to the location-box whereby this behaviour can be toggled (or add left/right alignment options). Additionally, when auto-scale is off, add a toggle to enable word-wrap of long text.
In the Edit Notification Service Properties when uploading a fmw to FME Server, it would be nice to add a option to set a job tag, currently I can do this by manually edting the target URL in the subscription, but everytime I re-upload the fmw, that seems to get over-written.
Can we have the Open Document Spreadsheet format added? It's an ISO format. And it's XML based (but don't tell Don!). There are probably open-source implementations of the reader you can use.Given Excel and CSV are such important formats, ODS makes sense too; especially when you consider that governments are (finally!) moving towards a requirement for data to be in open formats.
***Note from Migration:*** Original Title was: Call PCL (Point Cloud Library) point cloud processing functions in FME workflows The open source Point Cloud Library (PCL) has a wide variety of Point Cloud processing algorithms. FME 2017 ships with the Point Cloud Library, but few of its algorithms are currently exposed. Please tell us what algorithms you'd like to see, what what workflows you imagine accomplishing, in the comments below.
We have the ability to write out .FFS for ingestion into Illustrator/MapPublisher FME Auto. It would be nice to be able to read the Ai file back in to gain access to map views, map layers, etc.
The ability to select which attributes to include in a list is a great improvement in FME 2017, however when dealing with dynamic scenarios you don't know what attributes are available. The alternate option of All Attributes will also include many fme/reader attributes that are generally unwanted. I'm looking at you multi_reader_full_id, multi_reader_id, multi_reader_keyword, multi_reader_type.It would be nice to have the ability to exclude certain attributes from the list.
Would it be possible to add an option to filter out tiles that have only 0 or 255 values in it? I have been doing this with list range extractor, but I can only able to find tiles that have all 0 or 255 values, not ones that have all 0 or 255 values. It would be great to have this happen within the webmap tiler saving other steps in the chain.
When using fanout option in the PDF writer it keeps all records in memory until all features has been processed, then its starts the writing process. This is actually a big flaw, it should write features one by one and not store them in memory.
I read a few articles about VariableRetriever and VariableSetter, which don't execute int the right order.What do you mean about VariableRetriever that stop until the variable set by VariableSetter has its value ? (a bit like a FeatureHolder)
Add formats that store indexes to the DatabaseJoiner transformer - like MapInfo TAB, ESRI SHP file, etc. that includes indexing on the writer.My use case is looking in tile grids,.. rather than having to convert to a database format to use the Joiner, or having to read all the data using a FeatureMerger, I would like to be able to be to read features based on a where clause directly from the file (or on the FeatureReader), so using the Joiner (or a where clause on the reader if it was possible) I could do that
Add support for an FME date calculation function (either as a datetime function or within a transformer such as DateTimeCalculator) that works on a 5-day week or 'business days' system. Excel has a NETWORKDAYS function that takes a start date, end date, and holidays input to do this kind of calculation.
It would be nice to see the feature number going into and out of a transformer with hidden connections. Much like the number of features coming out of a Rejected port.
BE great to get FME updated to the latest NetCDF releasehttp://www.unidata.ucar.edu/blogs/news/entry/netcd...
Add support for writing Sketchup in Linux (not sure if this is possible at all?)
I'm using the new "FME Workspace (FMW)" reader (2016) and I love it (before I was using a Workspace to parse the XML header inside FMW files to get Tranformers list or versions).But it seems that the feature type "Transformers" is unable to read/list normal transformers inside custom transformers (am I wrong ?).So I would like the abilty to see informations about normal transformers inside custom transformers (maybe with lists ?).
Currently the ListRenamer allows you to promote a list list{}.x -> x{}, but there is no mechanism for the reverse. x{} -> list{}.x
This data is used by print viewer "Field Access to Automated Records" created by the NMT Corporation
I would like to have a Feature Type TransformerInputPorts at the FME Workspace Reader.Similar to the existing feature type TransformerOutputPorts.I'm using a custom transformer throughout numerous workspaces for which I would like to evaluate all input ports of that custom transformer that are connected / not-connected in these different workspaces.
Currently, "Format Parameters" tab exists in nearly all feature types. This allows users to quickly choose values (usually parameters, attribute name etc), however it often fails to allow for attribute values to be chosen, even those these are valid in most instances. For instance, the jpeg writer allows parameters to define compression or optimize the jpeg. But you can not use a dynamic attribute value to set these with "Format Parameters". Expose these as "Format Attributes" and then you can pass a dynamic attribute. By not showing these abilities in "Format Parameters" users don't believe they can accomplish as attribute values. Updating these, would then convey some of the true strengths of FME
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.
