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.
If I want to chain several AttributeFilters together to drill down, shouldn't it filter out attributes in the output so that I can only select from the previously filtered attributes? Instead when importing a second AttributeFilter, it gives me everything again. To me, that's a bug, but maybe you intend to have access to everything? What about having a "Local" setting to only show attributes not filtered? Otherwise you have to pick through the import of attributes again. Thanks!
A job submit by the FMEServerJobSubmitter will never post to a topic on success or failure, even if it was registered with it at publishing time. Nor is there a way to set a topic to post to within the FMEServerJobSubmitter. It would be great to be able to chain and control jobs with the FMEServerJobSubmitter, and still make use of the power of FME Server notifications/automations.
Currently it is possible to set a network based resource connection on FME Server with a name using forbidden characters for an equivalent user parameter in FME Desktop. For example, you can set a resource connection with the following name (not the display name), 05-700-FMESERVER, which will give $(05-700-FMESERVER) when browsing it for a folder connection in a workspace on FME Server. You can use this key to call the connection. However, setting a user parameter in FME Desktop is impossible with the name 05-700-FMESERVER... Which is bothering when you want to test your workbench locally before to publish it. Harmonizing the naming convention and constraints would be really great.
***Note from Migration:*** Original Title was: HTTPCaller transformer - adjustable Query String Parameter & Multipart Upload grids/tables Parameters for some Rest API can be a few (maybe 4 or more) and it would be nice to be able to adjust the grids to see more rows. Looks like it's locked to two right now but you can scroll up or down.
HiIt it would be great having a transformer similar to ESRI's ArcGIS Raster "Reclassify" and "Relcass" by Table tools.Thanks
I ran into a problem where couple of my workspaces crash before I get to saved the workspace (it seem to always crash when I'm working on adding logic into Test filter for some reason). I think it would be nice if there's a way we can recover the workspace partially or full workspace if we ran the workspace with cache on or something like that and the workspace will be located at temporary files directory where cache file was saving at.
I still run into the issue of the GDrive connector failing and terminating the workspace for failed HTTP errors. For my case these are internal server errors (code 500), stating "Daily Limit for Unauthenticated Use Exceeded". This was explored in this thread, but the issue still exists even with a custom web connection using a Google API key, and the limits (viewed via the drive API console) are nowhere near being exceeded. I believe an automatic retry of failed HTTP requests would fix this issue, as suggested in the drive api guide by including an "exponential backoff".
We receive 100s of flood studies that contain flood extents, depths, velocities supplied in ESRI Gridfloat (.flt) format that are need to to be integrated into our GIS systems.It would be really great if FME would support this format, at least as a Reader as it would really help our workflow, which currently has alot of manual steps that really take up way too much time.The forum post https://community.safe.com/s/question/0D54Q000080hGJySAM/flt-to-icad-format suggests that Safe were considering implementing this, but as this is over 5 years old it's worth chasing up!
The autocad_hatch_associative atribute in the ACAD Reader indicates if an hatch is associative or not but it is available only in read mode. Its use in the ACAD writer would be welcome.
The Point Cloud XYZ reader is great at reading large tablular data quickly, however I think it would be beneficial if it could create multiple point clouds based on an attribute in the table.For example, utilising what i think would be the most obvious method, I would read in the entire table and create one point cloud feature. Lets say its 800 million points, but I have 1200 unqiue ids in that point cloud. I want to create a point cloud for each of those 1200. So I then use the pointcloudsplitter, but that is going to take ages.I instead want to be able to choose an attribute in the reader, that holds those 1200 unique ids, and have a point cloud created for them when I first read in the data. I presume that it could be significantly quicker.
Add the ability to write custom key-value metadata to the output parquet files.Request originated from this Forums post.
Linear referencing is hard in FME. It needs a much more robust set of transformers. If a route name is set, then I cannot use the <default> route in other transformers such as PointOnLineOverlayer. The NeighborFinder does not return measures as documented. Linear Referencing is an important tool for transport networks. I have had a look at the Hub custom transformers and am appalled at the complexity to do any simple operation. All that chopping just to get a distance down a polyline!
In FME Server there is currently no way to manage the names of your repositories either through the Web Interface or via the Rest API. It would be nice if there was an option to easily rename repositories rather than having to create a new one and republish workspaces.
The option to import values for coded domains in the (file) geodatabase writer
SQL executor add 'Application intent' parameter.On a reader of sql non spatial you can set 'Application intent' to read only, but not on sql executor. So if your windows AUTH is set to read only you cant use sql executor on that database. This is very frustrating as its very difficult to fully automate my work flow.
When running any workflow with Enable Cache Features turned on, even though the workflow may not use any spatial transformers, if the reader detects a set of coordinates, FME automatically builds spatial indexes for each transformer the data passes through. This slows down the workflow considerably and can cause it to crash if large volumes of data are being processed. One solution (as suggested by 1Spatial) is to manually check the readers to ensure that any field that may been detected as a coordinate is changed to a different type, e.g. varchar, before running the workflow. This works but is labourious.Alternatively, and my suggestion, wouldn’t it be simpler for FME to add a switch to allow spatial indexing to be turned off when not required?
As an FME Server user, I want to be able to trigger an Automation when a message is received from an Apache Kafka queue.
It would be great if an alternate shared resource path for custom transformers could be implemented (with associated fine-grained security settings).This idea is a duplicate of:https://community.safe.com/s/bridea/a0r4Q00000FuTxPQAV/finer-control-over-fme-server-shared-resources-location-and-permissionsRe-posted to help with searches looking specifically for FME Server custom transformer configuration.
This idea is targeted to custom transformer deployment on FME Server but can be applied more generally to shared resources on FME Server.Currently, custom transformers can be deployed to either a Repository, or to the Resources > Engine > Transformers folder as a shared resource.Transformers deployed as a shared resource are available to all workspaces at runtime, which is very effective for ensuring consistency across an organisation.The issue is that there is no simple way to manage this single resource across a large organisation with multiple development groups and I'm currently working with an organisation that has the "Engine" resource folder locked down so that only administrators can upload data there, to avoid inadvertent uploading of transformers that could potentially impact multiple workspaces.It would be great if alternate shared resource paths could be implemented, either as entirely separate locations, or as sub-folders under the current path. (e.g. Engine > Transformers > [my sub-folder name]). In conjunction with this, sub-folders should allow for separate permissions than those of the main Engine folder.Implementing the above would allow for different development teams to manage their own shared resources without impacting the entire organisation, and without needing to grant blanket permissions to the entire "Engine" folder.
It would be nice if we can choose an ArcGIS webmap to use as the basemap of the GeometryPicker. This would be very nice to use with the Web App.
This is a follow on from my previous idea C658999. The latest version works well and outputs the target compression ratio used for my ECW files but the "Actual Compression Ratio" attribute is not working / does not seem to have been fixed. I am struggling to calculate the ratio myself. I have the correct formula, but I can't combine all of the necessary attributes (particularly file size) to perform the calculation. I can use some transformers to generate the file size but it takes hours if I have geometry attached, but I need the geometry for other things. I also can't subtract the header information to get a more accurate compression value. Can you please update the ECW reader to include / fix the Actual Compression Ratio. Thanks.
We can already write into an existing table in h_store format using text type (thanks to Takashi for the tips). It would be great that postgres/gis writer recognise h_store type. Consequently, we would be able to create a new table containing h_store type using FME ( currently, I use SQL instead)
The ProjectWiseWGSConnector List action needs an option to add search filter (e.g. regex on doc name), so it can improve the performance of the list action and narrow down the returned results.
Currently, the Geometry Parameter only supports the LL84 coordinates. It would be nice if we can generate the value with a different coordinate system when a user specifies a location/shape.
It's not uncommon to gzip files before uploading to s3. A nice to have would be the option to auto unzip following download and the option to gzip on upload.It's a bit tricky right now to achieve this
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.
