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: List of created variables (through VariableSetter) as attribute input in VariableRetriever transformer
Could the Redirect To Inspector menu item be added to the toolbar as a default? Or alternatively, would it be possible for Workbench to remember my button layout between updates?
Dont necessarily want to create a parameter but a note in the parameter popup that is just free form text.
Quite frequently I need to delete all but one or a few readers or objects on a workspace. For example, when re-using only one chain on a previous workspace, or inspecting 20+ shapefiles for relevant objects.Then it would be good to select stuff to keep, then hit Invert selection and Delete to get rid of unwanted stuff.
I often have multiple transformers to handle a small function that are part of a larger component that is already within a bookmark. It'd be handy to be able to create one annotation bubble with a description of them small function. For example, create a name attribute by using an AttributeSplitter to split a string then set the name attribute value to one of the list elements using an AttributeCreator. Create an annotation "Create name attribute" and attach it to both the AttributeSplitter and AttributeCreator transformers.
Administration page can reference the obsolete notification (watch directory, schedulers...) or subprocess with option (kill old process)
I'm quite new to the docker and docker cloud.It would be really useful if you could provide a standard stack file for the docker cloud enviroment. It should be quite similar to the compose file:http://downloads.safe.com.s3.amazonaws.com/fme/beta/docker-compose.ymlStack file definition of docker cloud:https://docs.docker.com/docker-cloud/apps/stack-yaml-reference/
In the current version of the FME(2015.1.2.1), it is not able to adjust the order of the transformer's port, so the situation as the following figure, will produce a line of cross.If allow the user to adjust the order of the port, Will be able to reduce the occurrence of this situation.
Would like the option on the PointOnRasterValueExtractor to not interpolate. Just extract the value directly under the input point. This seems like it would be an easy one to add. Thanks for the consideration.
***Note from Migration:*** Original Title was: Automatically import of the possible attribute values if chosen Attribute to Filter by has values for coded domains (for AttributeFilter)
CartoDB supports a limited number of data types - string | number | datetime | boolean. Currently when attributes on the CartoDB Writer are set to "automatic" the integer data types come across as strings. These then have to be fixed manually.
Enable the CartoDB Writer to create PK and BTREE indexes on attributes
The Directory and File Pathnames (PATH) reader in conjunction with the File Copy writer is very useful to construct or rearrange the directory hierarchy in the disk system.The features from the PATH reader have several attributes storing file path components (full path, directory path, file name with extension, file name without extension, and extension), but the parent folder name is missing.C:/abc/xyz/parent/file.extOf course it's easy to extract the parent folder name from the full path or directory path using a transformer such as the FilenamePartExtractor, but I feel something redundant.Sometimes the parent folder name will be used to create a new attribute (e.g. the destination file name), so I think it would be more convenient if the PATH reader could retrieve the parent folder name (e.g. "path_foldername").
***Note from Migration:*** Original Title was: Improve Accessibility of Newly Created Attributes in AttributeCreator/Manager GUI In FME 2016+, you can access newly created attributes in an AttributeCreator/Manager for setting other attributes in the same transformer through the GUI (e.g. Text Editor, Arithmetic Editor, etc.) like this.However, in the Conditional Value setting, the new attributes cannot be accessed. Although you can enter an expression with the new attributes manually (e.g. "@Value(new_attr1)") and it works fine, the background of the parameter field is still colored with pink.It would be convenient if new attributes could also be accessed through GUI for conditional value setting.
For instance: I use a system parameter to define a folder for a writer, in this case an Excel writer.Problem: A writer set to $(FME_SHAREDRESOURCE_DATA)${USERNAME} est.xls will find or create the appropriate folder. But right click on the feature type and select Inspect and the Data Inspector gets confused because it will look for D:FME_support${USERNAME} est.xls.Idea: Either let FME Desktop resolve the system parameter before sending the path to the Data Inspector or make the Data Inspector able to resolve the parameter on its own.Result: Much more easy to do a quick Inspect when using system parameters.
Is it possible to add the index/PK/not null constraint creation feature on User Attributes to FeatureWriter when the Format is a database? Just like in the writers.
This might be old news, but I want the VertexCreator to be improved. This idéa goes back to the age of 2DPointCreator-days.I guess I'm not the only one to, at first, mix the x and y attributes up, and has to change their settings after first run. Well, changing them is quite a few clicks and scrolls in the list of attributes.I'd like to have a "change places" button next to the x and y fields och the VertexCreator.In addition, it would be nice for the fields to be auto populated on connection, finding attribute values like x/y lat/long n/e etc.
The ESRIJSON writer apparently does not write 3D coordinates in FME 2016Writing 3D coordinates would be very interesting in future releases given the 3D developments in the ESRI JS API 4.x.
***Note from Migration:*** Original Title was: Add Additional Tables to a reader after it has been creaded with workflow option: Individual Feature Type After you add a some tables to a reader, as a individual feature type, It is not possible to add tables from that same database. This slows down the process of loading tables into FME as the user has to go back and add the connection information or change it (if their last database was different). It would be really great if I could simply add more tables to an existing reader that appears as a separate feature type.
Tool set for creating cartographic output, similar to pdf styler but for designing map layouts, north arrows, legends, inserts etc. This tool set would then be fed into by other transformers- Mapnik for the image, a table for legends and attributes for text etc. I rasied a similar idea regarding creating legends but I think a whole carotographic output tool would be very useful.
There are some geospatial tools based on Accumulo or HBase databases residing in a Hadoop environment, e.g., GeoMesa, GeoTrellis, GeoWave. It would be nice if FME supports some of those NoSQL data streams.
Due to the variety of FME Desktop versions used by clients, I have 6 versions of FME Desktop installed on my work computer. It would be nice if there was a way to to apply/update a license to all installed versions of FME simultaneously. My thought is that, when I open the Licensing Assistant for any of the installed versions, and apply a new license, it would be awesome if a dialog appeared asking if I would like to apply the license to all installed versions of FME Desktop, with Yes and No response buttons.
Would be great to have a transformer to read RavenDB format.
FME has the ability to write a compressed shapefile. However, the standard extension is .shz, which is not recognized by QGIS, which can read compressed shapefiles, but not with the shz extension, only zip.I would like to extend the functionality in FME to write to a zip extension, without having to run some shutdown script.
As a user, I want to use the exif metadata of my picture file to be read by the Exif reader so I could use the metadata for my translation.
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.
