Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I want to use a user parameter in order to have multiple Readers include, exclude or only read out of date records. The nicest way to do this would be to use a choice user parameter and put this in the WHERE Clause in the Reader. However, this will not add to the text box, when double clicking, if I type it in manually it will insert the display value, instead of the ‘choices’ value. Seems like a bug that has been temporarily ‘fixed’ by disabling its use.I am only using a single choice. Hope this request can put it back on the radar. FME(R) 2023.2.2.0 (20240205 - Build 23781 - WIN64)
Currently we can change the hostname that is used in the Web Application Server to reach FME Server via a different URL and port. But if the machine name that was used as a hostname during the installation is changed we need to reinstall FME Server to update the hostname. It would be nice if we could change the machine name/hostname for an entire FME Server installation in one single setting. This would come in very handy for duplicating FME Server installations on several machines (e.g. DEV, STG, PROD).
When working on a workbench it can be really frustrating to have the previous translation log vanish entirely on any subsequent run. Rather than having to copy the logs out each time, it would be nice if FME could store the previous xx many logs for your review. Additional options could be:pinning/ saving specific log entriespersist logs across workbench sessions.it would tick off previous ideas mentioned here (https://knowledge.safe.com/content/idea/28258/add-translation-end-datetime-to-the-log.html )It can be particularly frustrating when you're working with partial runs and lose the error you're debugging.
Have just come across an issue importing attribute names using attribute values from an Excel spreadsheet. A whitespace is somehow being added after the value that is imported, in some cases, even when I go and manually trim the attribute values in the spreadsheet beforehand. Adding an option to ensure whitespace is trimmed from attribute names or values that are being imported into the AttributeExposer could be a useful option to ensure that attributes are imported as desired without the additional whitespace.
When working with large number of readers all with different geometries it can be hard to keep track of what is what, also it is time consuming to check each feature type and then annotate everything. A small symbol that sits above or on the Reader or something visible when clicking to expose attributes would be quite beneficial.
It would be really amazing to beable to author Simplified Bounding Box Revit Families from Existing Contents bounding boxes or from Lists in Excel etc. On Many projects were we don't need detailed content but would like to beadle to Batch generated it. This is used a lot in Labratory work and its something that happens often in Visulizatoin where the "simple" families are replaced in a rendering tool.
The idea is to incorporate reprojectors into the FeatureReader. Often I use FeatureReaders to read from a WFS, ESRI REST service etc. The data is never hosted in the coordinate system I need so if I use an Initiator spatial filter I need Reprojectors before and after the FeatureReader. I propose for the FeatureReader to have an 'Initiator coordinate system from/to' parameter and an 'Output Coordinate system from/to' parameter that would save the need for two transformers in the workspace.
Database writers offer a "Table Handling" property with a "Truncate Existing" Option.This option may be inefficient if a foreign key constraint has been set on the table. A simple solution would be to implement a "Truncate Cascade Existing" Option.
Find it a little frustrating when adding a writer to a canvas with multiple readers that the feature type definition defaults to ‘copy from reader.’ Could the default be ‘automatic’ instead?
With latest update (2021.1) FME is not reading the Autocad Temporary Block Name (*U000) anymore. It's important and usable data that complements original blockname, so i would like if it's possible FME to read them again.Best RegardsRenato F
***Note from Migration:*** Original Title was: Text size in the JSON XML transformers for the XQuery text editor too small on Mac When using any of the XML JSON - Templater, Flattener, etc. when entering the query in the text editor, the font is so small it's unreadable on a Mac. It will not allow you to change the text size and none of the zoom options work. Other text editors are ok on the Mac.
When configuring a worksdpaceapp with the services of data upload for a final user there are some limitating issues as:The name of the readers has to be the same (a reader with different name than the configured in the process doesnt work). -> Could be great to have a standard reader only defined by the geometry type and not limited also by its name.The name of the fields has also to be the same. It is possible to prepare a configuration with user parameters to ask the user about the names of the fields and configure the process identifying them but it is extremely complicated and gives bugs. -> Could it be possible that FME server allows a pre-reading of the uploaded file and allow you to select the fields that matched with the process (like in QGIS modeller) or allow you to make a choice list (with user parameters) from the uploaded file to let the final user select those ones necessary for running the workspace (in the case obviusly that they are named differently than in the configured process).
I often put Terminator nodes on joins that are not expected to fail and TestFilter nodes meant to be exhaustive as kind of assertions to make sure my data makes sense. However, if these assumptions start breaking, they usually break for more than one feature, and if that happens, debugging this once it’s already been pushed to FME Flow becomes a game of whack-a-mole (with the reported error actually hiding a dozen more), unless we modify the flow in order to debug the error.I do have custom solutions to buffer errors in some cases, but getting this to work is complex and requires a lot of carefully arranged transformers for each potential termnator.(ProritySwitch is used to ensure no features can come through until all errors have been handled. It’s a custom transformer, more info here) It would be conveinient if Terminators could be configured to buffer all errors instead of terminating on the first one, to allow outputting and formatting all errors at the same time.
Viewing the table list, by pressing the table-list button, for database readers can be slow when there are many tables to scan in the DB.What if FME saved the table list during the session, so that reopening the table list would show a pre-scanned list.(There could be a button like in the Workbench Transformer gallery, to force FME to re-scan the table list.)Even better would be to have FME store the pre-scanned table list with the DB-connection and have it auto scanned in the background...
I utilize the custom transformer ListElementExtractor version 1. I have a strong need to make the destination attributes into a dynamic list. it is currently capable of using a space delimited text value (no spaces allowed in the attribute name). I would like to be able to read the list fme_attribute_info{}.field_name and create the new destination attributes for the incoming data.I currently use a concatenator LF to build a single attribute from all field names and then an element counter to verify which block version it is reading in order to manually build each list of tags separately.I wish that it would take an attribute or even just use the field_name list as the destination attributes.to allow me to populate attributes names and values with one transformer.
Hello, I am wondering how often the Coordinate System Library in FME is updated. In Iceland we have to regularly update our national coordinate system due to tectonic movements. In the last 20 years two new coordinate systems have been registered at epsg.io, ISN2004 and ISN2016. However, in the FME Coord Sys Library, only the outdated one, ISN93, is available.Is there a way to add new coordinate system defintions manually to the Library, or is there a way to request Safe to add new systems to it? Thank you very much!
***Note from Migration:*** Original Title was: File geodatabase writer - import/show existing domains as selectable drop-down list If writing to an existing geodatabase with an existing list of domains, it would be helpful to be able to import/see a list of the existing domains to choose when specifying a field's domain in the writer feature type. This saves typing the name (potential for typos or copying/pasting etc.) and having to 'create' the domain values as currently these need to be specified. The field type and width would still need to be set in the feature type, as these are not held in the domain definition.My other related idea here in case the two link: https://knowledge.safe.com/content/idea/93213/file-geodatabase-writer-set-coded-domain-field-wid.html
Enhance the feature service writer (AGOL, Portal, ArcGIS Server) to enable the user to configure whether an update operation should update the geometry or just the attributes, in line with other writers.
When the GeographicBufferer was replaced by the Bufferer (Version 15) there was a severe performance drop when buffering by non-ground units. Originally raised by @jdh on the forums, this performance issue continues to be a problem on the release of FME 2021.0, Bufferer version 17.While the workaround is relatively easy by reprojecting the data before a bufferer, this seems like a backwards step compared to what the GeographicBufferer provided.
When using the 'POD Writer', when you select a compression tolerance of <1 it adjusts to '1' which reduces the density of the point cloud so data is lost. Could FME disable this adjustment and allow the compression tolerance to be less than 1?
This idea came out a use case of years of fme server jobs being developed and maintained several fme developers over the years. I find my self wishing there were a feature in fme server (like power automat / flow) where after a certain amount of fails the schedule will be suspended automatically and then the scheduler (owner) gets an email notification. This kind of behavior might be easy enough to put together with the current out of the box tools that FME Server give you. However I see a lot of value in a default (or opt on install) configuration where after N amount of successive fails the fme server author/user gets a notification to the email on the user account and after N+ successive fails the schedule gets put into a suspension (maybe a new middle Yellow State) on the schedule view right side (active/suspended/disabled).
Currently you can use RasterExpressionEvaluator to map ranges to values with @if function, e.g.@if(@isnodata(A[0]), 0, @if(A[0]<-20, 1, @if(A[0]<-10, 2, @if(A[0]<-5, 3, @if(A[0]<-3, 4, @if(A[0]<-1, 5, @if(A[0]<-0.1, 6, @if(A[0]<0.1, 7, @if(A[0]<1, 8, @if(A[0]<3, 9, @if(A[0]<5, 10, @if(A[0]<10, 11, @if(A[0]<20, 12, 13)))))))))))))It would be convenient if you could get the same result with a transformer having more user-friendly interface like AttributeRangemapper.
Today, I am working and struggling with a simple task. I have an admin access in our fme server, where I want to clean up the user list, particularly by deleting some of the users. Before that, I wanted to check the list of items the user owns, but I couldn't find one. I think FME server needs to have such thing to make the work easier!
***Note from Migration:*** Original Title was: Chain workspaces within a single automation together - abort all when one fails. When you use a Jobsubmitter to start multiple workspaces and those also might use Jobsubmitters, it is nice by using the FMEJobSubmitter that if any child-workspace stops then also the main-workspace fails. It would be nice with this behaviour also in FME Server AUTOMATIONS. So that you could "group" and cancel all other actions when one of them fails. Same behaviour as running FMEServerJobsubmitter
The RasterCellValueReplacer currently only allows you to specify 1 range of values. I would like to be able to specify multiple ranges (similar to how the AttributeRangeMapper works for attribute values)
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.
