Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Have an FME Desktop workbench ‘remember’ it’s Server workbench counterpart so republish is always enabled (store link as a FME Server Param?) when the workbench is closed.Although this just saves some seconds in publishing, it’ll make the desktop and sever more seamless. Sometimes you need to make one quick change and to quickly hit republish,which becomes disabled once you close that workspace, would help.
Can FME add 3DML as one of the supported formats for the reader/writer? This will help us to import stuff from the 3D gaming world into a traditional GIS system.
I've really come to appreciate the FME Knowledge Center. The recent enhancements for filtering search results, browsing content from FME employees and blog posts is absolutely great.Recently, I was wondering if another user would be visiting a GIS conference that I was attending, but I couldn't find a way to send him a message. Wondering what others think about adding a direct message or chat feature?
Currently, FME writes NITF 2.1 and does it wonderfully, but it would be helpful if there was an option to create NITF 2.0 compliant output under the MIL-C-89038 standard.
Sometimes the auto-layout function causes connections to cross each other or overlap with other transformers. This idea is to avoid overlaps, since we know they are not best practice.Objects should be laid out in such a way as to avoid overlaps or - if necessary - connections could be converted to tunnels (if they are very long and overlap a lot of other objects).
Currently I have a seed file that has upwards of 400 levels within it and potentially upwards of 20,000 or more levels. I have these levels because I work for an electric utility that does maps identifying circuits visually by addressing colors. I output my data to a level based on the circuit_id and this puts all of my conductor on separate layers with bylevel set as the color. Then I simply assign a color and update my seed file for future use. However, every file now has all of the potentially 20,000+ levels creating a large level library. I simply delete all the unused levels once I open the file but I was hoping there was a way for fme to write the output file using the seed file, but upon completion remove all unused levels within the output so that you only have levels for what are used within the drawing.To clarify, I use a seed file in the writer, and the seed file has multiple levels defined, but the data I am writing may not have features for every level, and I want the writer to remove a level if it turns out to be empty.Is there a way that this can be a future enhancement or an enhancement added during a later patch? That I think is an awesome idea, does anybody else?
Currently, when using AttributePivoter the resulting features have the "pivoted" attributes unexposed. This behavior does not replicate what some users would expect from a "pivot." For example, when creating a Pivot Table in Excel or using popular R packages reshape or tidyr, one expects the resulting pivoted table to contain exactly the rows, columns, and cell values specified. The resulting table of exposed attributes in FME does not look like that. Therefore, users currently must add an AttributeExposer after the AttributePivoter. That's well and good, but why not add an option to expose attributes in the AttributePivoter to avoid this step? This section in the transformer could mirror the "Attributes to expose" parameter in the XMLFlattener or JSONFlattener. Even better would be allowing these parameters to get their value from an attribute or through an Import feature such as is available in the AttributeExposer. See this related idea.While we are at it, do any other transformers need an "Attributes to expose" parameter that currently don't have one? I see a few existing ideas: BulkAttributeRenamer XMLXQueryExploder
In the transformers that combine features (Dissolver, Aggregator, RasterMosaiker, BoundingBoxAccumulator, etc) the Accumulation Mode is one feature, none, or merge all.It would be nice if we could select which attributes to merge in the same way we can if we are generating a list.
The idea is instead of having connections entering junctions from the left and exiting to the right, build in the function to 'rotate' junctions so connectors can enter top/exit bottom, enter the bottom/exit top, or even enter right/exit left.Hopefully this isn't too hard to add and will make workbenches a lot easier to organise without it looking like spaghetti.
In addition to ensuring that "Database Connections" are used for workspaces, ensure no plain text passwords remain anywhere in an FME Server installation.
Todo: For the PostgreSQL/PostGIS writer, add a checkbox to force the schema, table name, and all column names to lower case.Why: When converting from databases like Oracle where everything is by default uppercase, to PostgreSQL where everything by default is lowercase, the Dynamic setting creates everything as-is, which is normally good - but in this case keeps everything uppercase which is undesirable. Adding a checkbox to force everything lower either at the writer level (most desirable), or the table level would be most helpful.My use-case: I have an Oracle production GIS database with over 4600 tables to convert to PostgreSQL. I don't look forward to having to touch each stream to add a bulkattributerenamer and set the schema and table names.
It would be helpful if the Bentley MicroStation Design Reader supported reading native Microstation fonts - Perhaps, via an option to reference an .rsc file.
I would really like the option to double click an attribute in a text or arithmetic editor and have the full attribute selected, i.e. the @Value(attribute_name)At the moment double clicking on the attribute name only highlights the text inside the brackets. This is no good if you want to double click on a Feature Attribute to swap the attribute
To be able to have the width of Max as an option in the SQL server writers/ feature writer. varbinary(max) or varchar (max) etc
If you're having to rerun a translation multiple times or coming back to a workbench after working on something else I think it would be really handy if the translation log showed the date and time the job finished.
It will be useful to implement REST API calls to detach existing Static IP from an instance and assign it to another instance.
The online FME Server Authoring Course is good, but quite limited in terms of getting the most out of the product. For custom solutions, the API is really where its at and the Server Playground is a good starting point. However would it be a good idea to include two online FME Server courses: one for authoring and one for API development? A bit like the way the two Desktop courses are basic and Advanced, my idea is that Authoring and API Development are two possible FME Server course titles.
The internets suggest they're a GeoTIFF file, but when I force them to read into FME as a GeoTIFF it loads weirdly (looks as though it's loading multiple pyramid levels on top of one another?)
It would be helpful (especially to FME beginners) if workspaces (templates) would be provided to demonstrate how each regular transformer works. Each workspace should allow the user to test a regular transformer with various parameters setting and see the result visually as much as possible. How about starting from some most used transformer?
As mentioned in this question and discussed in the answers, it is now almost impossible to make FME export an XML document with a <![CDATA[ ]]> section a.k. literal character data.My intended use was to communicate some HTML-formatted descriptive text in a XML-response about the capabilities of a transformation. This can thus be presented to the end user of the application communicating with my service.My preferred implementation would be to add a XQuery function in the XMLTemplaterget-attributeget-xml-attributeget-cdata-attributeKind regards,Martin
It can bit a bit of a hazzle working to improve existing custom transfomer. To be able to save the custom transfomer in a new version, you have to close down the project open it up, to be able to select modify as new version, this is tricky if you have already started to modify the existing transformer and you don't want changes to the existing version. What would be nice would be an option to save as "new version", and an option in the workbench to update the custom transformer to a newer version.
It would be great if FME could monitor log files of one database, and when a transaction occurs, relay that change to another type of database in real time.
Could we please have a new transformer that enables basic vector operations [intersection, difference and union as a minimum] between two geometry columns (i.e., columns that have been created using GeometryExtractor within a processing sequence) and stores the result as a geometry column that can be accessed using the GeometryReplacer. This feature request acknowledges that the AreaonAreaOverlay does this job when configured correctly with other transformers. However this requires two datasets to be compared across all spatial combinations each time the process is run which can take a very long time for very large row counts. It is common in spatial database thinking, to have long term storage of multiple geometries that travel together in the same rows (with incremental update at times) and to do repeat assessments in different queries. The proposed transformer would in effect enable the multi-geometry operations that are possible (and extremely useful) as in the Oracle as an example: SDO_GEOM.SDO_INTERSECTION, SDO_GEOM.SDO_DIFFERENCE and SDO_GEOM.SDO_UNION operators (google these words for details)Having multiple-geometry operations would speed up very large and repeated table vector operations that compare two shapes in the same row.Thank you
Repeat shown warnings at the end of a log file. Now you have to search through the log file to find the warnings.
As data storage and transfer costs are billed in addition to the FME Cloud instance cost, it would be handy to be able to track usage over time. The current Billing Dashboard provides month-to-date metrics but it would be nice to be able to see daily transfer and storage usage (in KB/MB/GB, rather than - or in addition to - $USD). This information could be displayed in a graph or table. See this question for further details: https://knowledge.safe.com/questions/75739/fme-cloud-data-transfer-statistics-reporting.html
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.
