Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Add an option for handling "Polygon start/end points" to the Generalizer transformer. The Generalizer doesn't generalize polygon start/end points. In cases such as "Remove first colinear point from polygon", @jdh found that when you want to remove a colinear point which is also happens to be the first/last vertex in a polygon, the Generalizer doesn't remove it. In this instance, an important corner vertex is removed.
It seems we cant use TLS/SSL connection with MongoDB reader & writer, right ?MongoDB logfile :[initandlisten] waiting for connections on port 27017 ssl [listener] connection accepted from XXXXXX:60097 #1 (1 connection now open) [conn1] Error receiving request from client: SSLHandshakeFailed: The server is configured to only allow SSL connections. Ending connection from XXXXXX:60097 (connection id: 1) [conn1] end connection XXXXXX:60097 (0 connections now open) So I would like the TLS/SSL support with MongoDB in FME...
This might already be an idea mentioned here that I simply have not come across yet. But in a recent chat I was recommended to post this as an idea here to be voted on.What I suggest is a scheduling method on server which allows all workspaces in a single repository to be ran as a batch set, or in an ordered set by the user. This would be accomplished with a single scheduled time of start at the schedule page on server and choosing the repository alone to run all workspaces within. As far as I know, currently each workspace has to be scheduled individually, regardless if it resides in the same repository.If there is a method already in place in 2018 server which can perform this I am not aware and would love to learn how to do it.Thanks,Todd
***Note from Migration:*** Original Title was: Option to limit the number of Data Inspector instances launched from FME Workbench After a couple of hours of working with FME I find I usually end up with 3-4 different instances of FME Data Inspector open. It's hard to keep track of why FME Workbench launches new instances of Data Inspector but if I could limit it to only having one open it would be great. Not having to search for a tab in multiple instances of Data Inspector would save me loads time.
A onedrive for business Transformer ( just like O.D Personal) or a way to upload files easier to sharepoint would be a massive benefit. Cant believe this is already no available as most companies use Microsoft.Thanks,
Calculate Fréchet distance (similarities) between two geometries I'm not sure if this should be an option or mode on an existing transformer, or a brand new one. The Frechet Distance is a measure of similarity between geometries that takes into account the location and ordering of the points along the curves. Basically an "ish" measurement to see how similar geometries are. Maybe a ChangeDetector with a tolerance of some kind? https://en.wikipedia.org/wiki/Fr%C3%A9chet_distance
When using the AttributeManager I think an enhancement would be if the possible actions should start with a distinctive letter (eg "Set Value", "Leave or Ignore" (for Do Nothing), "Rename", "Forget" (for Remove), "Default" (for Set Default Value) so that one can select and then easily act by hitting a single key.
Would be awesome to have a writer (& reader) to esri big data store.
Make the import button on AttributeFilter more intelligent so that it only imports new values.Currently the Import button will add values that already appear in the "Possible Attribute Values" list, then the transformer fails.
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.
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.
