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 was curious if there was some way to set FME Server up so that if a job from a workspace that was already running, the new job would either be cancelled or sent to the queue/held until the current job got done running. This would be useful especially for jobs automatically submitted through schedules or automations when writing out so you don't write double records.I think I'm basically asking for this, but productized so we don't have to implement it in each workspace that's in a schedule. Additionally, it might be something that I could see added into the automation functionality on FME server.
Give the option to provide the capability to enforce password renewal for users in FME Server.
Today I was investigating the use of a PUSH subscription (HTTP POST) to notify some other application about the results of their job.This application (SAS) needs a quite specifically formatted XML-body to understand my message. I was unable to parse this from a XMLTemplater and textwriter in the workspace, through a notification, to the body the PUSH subscription sends to the provided URL.The alternative was a more text-like body, I could easily get to the subscription, Only that needed to be presented as an application/x-www-form-urlencoded contend type. A content type the push subscription does not support.I ended up making a workspace subscription and a small workspace with a HTTPCaller converting the subscriber_content to the desired body format. This is a bit like building the PUSH Subscription service I would like to see.Would it be an idea to upgrade the PUSH subscription, give it some more content-type methods (perhaps even more REST methods) and a template for the body and perhaps for the URL? Like a mini-HTTPCaller / XMLTemplater / JSONTemplater combination?Kind regards,Martin
The same as the (2D) Generalizer, there should be a 3D Generalizer. I've created a custom transformer by myself that is doing the trick.
There isn't a truly easy way to generate a file (excel, CSV, etc) and then email the file after it is finished being created. I run into the issue on large workflows that the emailer tries to email before the separate sheets have all been written to an excel workbook, and sometimes the emailer tries to run before the workbook is even created. Why does the workflow end when I'm writing to a file?
Hello,When reading metadata features from file geodatabase Reader or SDE reader, the attribute geodb_feature_dataset is not being populated (missing). it would be useful to have access to that information in many cases (selection, filtering, modify/update metadata, etc).Bug reported with case C142892 with Safe Support
When using Feature Caching, currently "Run to this" will load all Feature Types of the Reader, which is very time consuming on large datasets. It would be much nicer if it only imported the Feature Type from the Reader that the current "Run to this" is actually in need of.
PATH Reader: Add where clause "like" functionality to only read certain filesCurrently, this reader forces the user to read all the files (w/ properties) into memory and THEN filter them in the workspace for size, date, etc.I contest that I can get these properties much much faster via DOS DIR command written to .txt -- why can't the reader do this upfront?
***Note from Migration:*** Original Title was: GeoPackage-writer registers the proper geometry type in GPKG_GEOMETRY_COLUMNS for tables with features of a single geometry-type Feature tables in GeoPackage are registered in the GPKG_GEOMETRY_COLUMNS table with their geometry column, SRS and geometry type. Right now FME registers all tables with the common geometry type GEOMETRY. For tables that contains features with only one single geometry type FME should register this geometry type in the GPKG_GEOMETRY_COLUMNS table as defined in the GeoPackage-specification. For example, a table with only point features (geopackage_type: wkb_point) should be registered as a POINT geometry type instead of the GEOMETRY geometry type. This will help other applications (like QGIS, for example) to better understand the contents of the GeoPackage table.
Even though I've been using FME for some years for some reason I've only just discovered the Workspace Runner when I was researching the ability to set the paths for readers and writers using attributes.The current version of Workspace Runner appears to mostly fulfil this in that it identifies the paths for the primary input and output and I can use an attribute to define common base folder paths (which I can then pass to multiple workspaces). The problem I'm having is with workspaces that have not only a primary input and output but also a feature writer embedded within the flow. The Workspace Runner is not identifying the output path for this feature writer as a parameter which means if this changes I need to go in and set it manually which largely negates the reason I was using a Workspace Runner in the first place.Would it be possible for the Workspace Runner to be developed so that it would also identify the folder paths for feature writers (and most probably feature readers).Many thanks
In the Esri ArcGIS Online (AGOL) Feature Service Reader, allow connecting to a feature service via entering the AGOL Item ID as a value. This could be a seperate parameter field or maybe this could be an option via the text editor for the Feature Service parameter field?Currently FME populates a list of feature services retrieved from AGOL, however you cannot find a feature service via its AGOL Item ID.While the pre-populated list is great, the list can be very long both to generate and to sift through. Often to be certain I'm selecting the correct Item, I have to hunt the feature service down in AGOL to figure out which folder it is in. It would be helpful to have the option of simply pasting the Items unique global ID as a value.The screen capture below clarifies how the current lookup functions, as an example I am selecting a feature service titled "RC_TPW_StreetLight_Replace_pnts_Public"Screen capture below clarifies the AGOL Item ID I am referring to. In this case, viewing the item titled "RC_TPW_StreetLight_Replace_pnts_Public" in AGOL exposes the ID as 4707e815a61c47cfbf8438e528db5aa0Thank you for considering this idea!Edited for clarity
In case the SQL statement in a SQL Executor transformer returns more than one record, it would be very beneficial to have an option to add those records as a list to the original feature.At this moment the feature is causing an error and will be rejected.
Would it be possible to add more flexibility to the building of action parameters? For now the text editor only offers to concatenate elements (event or automation attributes) and write free text. It would be nice if we could directly generate a parameter with more text editing options or even Jqueries. This could also be through an action dedicated to create keys if it is too complex to add it to the text editor. It would save us from generating dedicated workspaces for simple text operations.
Please can you add a new FME Feature Function which calculates the current date and timestamp?You have a Timestamp() function but that requires an input string and you have a Timestamper transformer but I think it makes sense to have a Now (or Today) function similar to applications like Excel.This means you can then test a date/time attribute against the current date/time in a Tester transformer without needing an additional transformer or use of Python.
Would be great to be able to extract metadata stored in Revit sheets.
When using relationships in the Salesforce Reader with a custom SQL statement, the fields from related objects do not automatically populate in the schema. This leads users to believe that the query is not pulling this data. The current solution is to expose these related attributes with the AttributeExposer which is not intuitive for users attempting to use the Salesforce Reader. Related issue: https://knowledge.safe.com/questions/103783/salesforce-reader-can-a-soql-select-statement-incl.html
It would be useful if the RubberSheeter could perform warping operations for raster geometries.
Often me and my co-workers share workspaces between others, but we might not be aware of Startup/Shutdown Python scripts existence that use the published parameters, so for example, if one deleted a reader where the script utilizes, it will definitely encounter an error.My idea is an alternative to other ideas:- https://knowledge.safe.com/idea/27309/startup-and-shutdown-scripts-with-regular-transfor.html- https://knowledge.safe.com/content/idea/52718/startupshutdown-scripts-on-the-canvas.htmlHow about turning the color of the Scripting icon of the Navigator window into green , as well as the corresponding tree child to indicate existence of a script in the workspace once filled out. ( see snapshot for illustration as a draft idea.)
It would be great if an admin could add a message to a user or group - and this would be displayed at the frontpage of the user after logging in. Ideas for what could be shown here:- Maintenance notice: Will be down for maintenance x-y- Uptime notice: Only up between 9am and 4 pm- Other message: -- For help - go to this URL-- For assistance, call XXXEtcetcetch
Currently The ACAD Civil 3D Reader does not fully support all labels. Could all types of labels be added to the reader? Or at the very least, could the documentation be improved to clearly state which types of labels are, or are not supported. The document below alludes to some label support for parcel segments but it isn't very clear.https://knowledge.safe.com/articles/20153/autodesk-autocad-civil-3d.htmlFor example, the reader cannot read a pipe label of entity type "AeccDbPipeLabel". Unfortunately, the logging in FME for skipped features is not very informative. It took a lot of sleuthing of FME and Autodesk documentation to figure out why the pipe labels weren't being read. For a list of Autodesk civil 3D label types please see the link below.http://docs.autodesk.com/CIV3D/2012/ENU/API_Reference_Guide/net/Autodesk__Civil__DatabaseServices__LabelType.htm
I would like to be able to write an AutoCAD Architecture file so that geometries can be written as a particular object such as walls, doors, windows.Either going from a DWG or Revit file to an AutoCAD architecture file would be good so that these kinds of objects can be written appropriately.(If you are interested in reading AutoCAD Architecture objects, this idea is tracked here)
I would like to publish my Esri MXD file to PMF (Published Map Files) using FME.Currently, I use the Publisher extension in ArcGIS and have to publish the MXD manually but I would like to automate this with FME.
When creating Justify aligned Paragraphs/Headings using the MSWordStyler transformer, with Content type set to Heading, Paragraph or List item, the last line of the Justify aligned chunk of text is spread out on the entire row/line. Using an MSWord Basefile with Headings set as Justified or setting Aligment to Fully Justified in Paragraph parameters just messes up the text.I think there is a problem with the line termination encoding used by FME.
***Note from Migration:*** Original Title was: Custom width setting for Readers, Writers, Transformers etc instead of fixed/dynamic Currently Readers, Writers and Transformers use dynamic width.For aesthetic and readability's sake it would be preferable to be able to change this according to one's preferences, as a preset.
This may have been suggested in the past, but I can't seem to find any mentions, and it's still a good idea.When translating data to a database of any kind, FME will create the needed tables to accomadate the translated data. If no data is processed to a given destination, no tables are created.So, FME knows how to create the table, but doesn't due to lack of data.The often proposed work-around (create a dummy feature, and delete it) is really not good, and is more of a hack than a solution.If an additional option (Force table creation) was available, when the attribute definition is fixed (manual), which is often the case when using "Generate" to create the workspace, transferring a full database would be a much easier task. FME should then just process all writers without data, and create the table if it has a fixed schema.
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.
