Open ideas have been reviewed by our Product Management and are open for commenting and voting.
In the file geodatabase writer (and maybe others e.g. the SDE geodatabase writer) it could be a good option to set geometry (e.g. 'geodb_point') using an attribute rather than the current drop-down. Just allows geometry to be set earlier in the workspace if required.
The current FME Server backup/restore process is very handy but a bit misleading in that a restore behaves more like a deploy than a true restore. What I mean by this is that if you make a backup, then add some new items to FME Server (e.g. workspaces, resources, etc.), then restore the backup, you will be left with a hybrid configuration - those items which were backed up will be reverted to their previous state but the new items will also still exist on the server.Every other backup system that I know of restores to a known state, not to a mixed state of pre- and post-backup items. It would be great if FME Server could also follow this model, or at least provide an option for this more conventional behavior.
When writing data to PostGIS I want my data to be written into the table as multipolygons so I set the Geometry on the Writer to be multipolygon: However, features that don’t conform to this geometry are being dropped. Leaving Create Generic Spatial Types gives me geometry types that I don’t want to be written into my database (i.e.- geometry collections).It would be great to have an option on the Writer to simplify geometry so my features will still be written. Similar to the Collection Type Handling on the SQL Server Spatial Writer.
The opposite of the attributeExposer. Sometimes I need to temporarily expose an fme_attribute in order to preserve it's value (ex. LineJoiner) or replace it's value (ListIndexer), but would rather not have it trailing through the rest of the workspace, especially when this takes place within a custom transformer.
HiI'm looking at ways to monitor FME Server using the REST API and would like to perhaps query for all failed jobs in the last n days/hours/minutes. It's currently possible with the V3 API to query for failed jobs - e.g. https://myfmeserver/fmerest/v3/transformations/jobs/completed?completedState=failed However, this will return ALL failed jobs. If we are monitoring for recent failures, we would want to query using dates or a timeframe (e.g previous n minutes/hours/days). Currently this is not possible and requires either returning all failed jobs (could be many) and then filtering the results by date on the client.Querying by date seems to be a fairly logical thing to want to do and there are possibly other areas of the API where this would also be applicable.
When filtering jobs on FME Server, the choices available under Status are a) Successful Jobs and b) Failed Jobs. There is however a status called 'Cancelled' (shown with a red circle with a cross in it). Cancelled jobs are also shown when one chooses 'Failed Jobs' but can't be isolated. In my opinion, it would be beneficial to be able to filter for cancelled jobs.
I have a workbench with a multiple choice parameter. Based on what is chosen by the user, I would like to display other parameters associated with those choices (such as the output). The conditional visibility parameter currently only allows 'IS' and 'IS NOT'. It would be nice to have additional operators such as 'CONTAINS' or 'CONTAINS REGEX', similar to what you would find the TestFilter operators.
It would be very helpful if FME Server Security supported nesting Roles!e.g. I have created an Active Directory Connection in FME Server, and I have imported numerous Active Directory Groups - which then become Roles in FME Server. It would be great if I could then add these Active Directory Roles to the existing fmeadmin Role (like you can with Users) - so I can manage permissions in one place!Role A contains Users A, B, C, and Role DRole A - User A - User B - User C - Role D
I would like to be able to set a feature service URL within the ArcGIS Online reader/writer. Doing so would make it easier to change to new services and see exactly which of several similarly named services are in use.
As 3D BIM become more popular in use i would like a way to check the ifc export against a ids file. I am guessing a similar method to Using XML to filter IFC could be used, but maybe a standardized way of doing this quality control could be achieved. Maybe the control could be integrated to the IFC reader, or as a separate transformer.
Context:The FME Flow Gallery App is an excellent tool for presenting multiple workflows to non-FME users, but managing numerous applications can become cumbersome. Enhancements to interface and navigation could greatly improve the user experience. Proposed Improvements:Grouping of Applications: Introduce the ability to group related applications within the Gallery App. This would reduce clutter and make it easier to navigate when dealing with a large number of applications, eliminating the need to create multiple Gallery Apps. Search Bar Functionality: Add a search bar to quickly locate specific applications within the Gallery App, improving user efficiency and experience. Custom Map Interface: Allow the map parameter (e.g., GeometryReplacer) to display directly within the application interface (e.g., on the side of the screen). This would eliminate the need to click and open a separate map, making the interface more intuitive. Data Downloads in Automation Applications: Provide a mechanism for users to download data directly from Automation Applications, such as outputs generated by writers. This would extend the functionality of Automation Applications for data delivery workflows. Improved Text Formatting in Application Titles: Fix issues with letters breaking off from words in application titles, ensuring proper text alignment and readability.
As a workspace owner, I’d like to share the workspace with other users. However, I’d also like to see anytime another user runs the workspace I created. When sharing the workspace, I’d like to have the option to view all logs / automations / workspace apps associated with the workspace that users may create.
As I understand it, the Lenient option states that two polygons are equal if Within(A, B) and Within(B, A). That is, A and B occupy the same space. However, I think that an option is missing that, in addition to checking that they occupy the same space, also checks that they have the same number of vertices even if their order may be different.In my case it is important to perform topological quality control of layers such as land covers. The addition of a new vertex to a polygon, even if it is collinear, is a new version of the polygon geometry.
Add precision setting to all transformers that output dimensions or metric coordinates.To negate the need to add AttributeRounders after (e.g. LengthCalculator) include a precision setting option in the initial transformer.A default setting of 3 (mm) should suffice for most operations.This setting could then be defined as a user parameter for use throughout a workspace. A search shows discussions around precision dating back a decade ago, so I may be late to the party here.
Been having the issue of having to make a larger amount of requests covering smaller areas, instead of the entire extent I’m interested in, from the OGC WMS reader because the HTTP request times out. It would be very helpful to be able to specify the timeout length.
This is a XML-based system. More info can be found here: https://transmodel-cen.eu/index.php/netex/
As per How to Quickly Rename Referenced Attributes in Multiple Transformers | CommunityIt would be great to be able to rename a particular attribute throughout a workspace without having to go through each transformer individually.
When exit-code != 0 please send the features through a Rejected port on the Systemcaller:
This would be beneficial to the AEC community. FME should have an app available in the Procore App Marketplace to make it easier for firms to use FME and build integrations between systems. Asking a firm to enable a custom integration is usually viewed with suspicion; having an official FME app in the store will make the conversation MUCH easier.
Sometimes when dealing with large sets of Columns in the Visual Prview, it would be very useful to keep the Columns... filter choice persistent.So that if I select a different transformer and come back again , I dont have to go and re-filter the column list every time. It remembers the filter I had set and only shows me the columns im interested in at this point.
As per another question, raised by another user, regarding the use of CUDA and GPU support in FME, I would also like to raise this as an idea for future FME releases.My team and I routinely work with large (terabyte) sized images and we would greatly benefit from having GPU processing to improve the performance of our workbenches, particularly in the output stage.Can you please add GPU support (particularly for raster reader, transformers and writers) to your development plans?ThanksBrad
Slideshow allows to automatically step through selected features. As of now it will only display the current feature. This is quite useful for presentation.What I am looking for is a way to let slideshow run and keep features which were displayed already. Kind of an “Add On” or “Collective” mode. It would start with 1 feature, add the second, add third … an in the end all features would be displayed.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.