Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
***Note from Migration:*** Original Title was: Include the possibity to edit the aliases of fgdb attributes within the workbench There is already a possibility to expose the aliases of an FGDB reader but if we could edit the aliases (with a lookup table or other feature to join on) and write them, it would be nice.
***Note from Migration:*** Original Title was: Version Control: Allow other files in Repositories to be versioned (e.g. Source Data, Custom Transformers) Version Control is a great new feature that will allow users of FME Server to better track when FME Workspaces are uploaded to FME Server.This idea is to extend functionality to cover items that are published with the workspace, such as Custom Transformers, and Source Data. (In other words, other data that also exists in the same Repository as the Workspace.)
Hi Team,A suggestion of Idea is has a Writer for format - Maptech BSB Nautical Chart.There is a Reader and I would like to know if has a implementation in the future.Thanks in Advance,Danilo
Make sure that the following attributes are available on ALL formats (seems to be missing still in FME2019 on DWG atleast)- fme_feature_type- fme_dataset- fme_basename Workaround mentioned here: https://knowledge.safe.com/questions/105379/where-are-the-fme-dataset-and-fme-basename-attribu.html
I suggest that the Drawing System Variable feature in the DWG-readers also should include the system variable PLINEWID. This will make the process of CAD-->GIS easier to achieve the correct global line widths
I suggest that two new attributes are added for the feature types Transformers, Readers and Writers in the FME workspace reader (FMW) that stores the canvas_position_x and canvas_position_y. The reason behind this is that we are visualizing workspaces in the graphml format and to draw the workspace as it's shown in FME Desktop the position is essential. Right now I retrieve this information from the fmw-file with a Text File reader but the process is tediously.
some users could probably use 'Monthly' also
To my knowledge, the GDAL libraries GDAL and OGR are built in FME. However, apparently not all GDAL tools are utilized. Particularly, I miss gdal_rasterize, but others of the tools could be incorporated as transformers.https://gdal.org/programs/index.html#
Currently you can only launch an instance of FME Server on FME Cloud using the dashboard or API. Add support to provision instances using a scheduler GUI on the FME Cloud dashboard. This would allow you to bring an instance up for a period of time every day, week or month. Since pricing is hourly you can keep costs to a minimum only paying for the server when you are using it.
Add github as "Shared FME Folder". This way you have version control of all items used in FME
Is it possible to speed up the DWG-reader in the same way that the CSV-reader have been speeded up? Using the "tables/pointcloud" reading method?
FME Server uses Distinguished Name (DN) to associate a user with Active Directory. The DN name is a composite of many AD components and is not fixed (e.g. CN=Jeff Smith,OU=Sales,DC=Fabrikam,DC=COM). Therefore if there orgnaisation unit changes or is renamed, or they marry and change there surname, etc, etc the link will be broken between FME Server and Active Directory. They will be no longer able to access FME Server, although they will still be listed as a user. I have seen this occur in many organisations.I believe a better approach is to use the Active Directory SID which I do not believe changes for a user, and is unique to a domain. The other component to use would be a domain, as there may be more than one domain connected to FME Server. This way we would maintain a consistent link that is not affected by most AD changes.
Add support for CIM XML writing.
Somebody has published a workspace to 3 services on FME server.As an Admin of this server I do not want the workspace to be published by 1 of those services.But I can not remove the workspace from that service without removing the workspace completely.Allowing an Admin user or the user who published the workspace to remove workspaces from a selected service would avoid removal of the workspace completely followed by publishing it with the 2 allowed services.
***Note from Migration:*** Original Title was: Move workspace service registration and notification settings from Publish Wizard to Web UI
A Loop in the new automations would be great. Like in the Custom Transformers.
It would be great to have a warning on non existing EPSG (Here typo : EPSG4326 instead of EPSG:4326)2020-01-22 10:00:07| 1.6| 0.0|ERROR |Reprojector: Reproject: Could not reproject the geometry of the preceding feature: Reprojector: Could not create reprojection engineError log could be more explicit :ERROR | Destination Coordinate System badly initialized.
After merging multiple tables together to pass all incoming features through a same transformer construct it would be convenient to have the option to remove or unexposed missing attributes in transformers as "FeatureTypeFilter", "BulkAttributeRemover", "AttributeManager" and the like. This would make it much easier for a following routing action by an attribute like fme_feature_type leaving missing attributes behind. I am aware that the state "Missing" actually marks an attribute as non existent in FME terms as a table column but it is kept exposed to any following transformer connected to. Having a huge quantity of attributes makes it difficult to identify an attribute one will work with and most of all slows down response time of some dialogues (especially AttributeManager) significantly. It would probably free up some memory in use by the FME process.
***Note from Migration:*** Original Title was: Active Directory Users: Option to view AD Server associated with each user account I would like to be able to identify what AD server each AD user originated from directly in the FME Server Web UI. This would be helpful because if I need to remove an AD Server I must first remove all the associated user accounts, however if I have multiple AD servers configured it is not easy to identify which users need to be removed. Currently I can only get at this information using the Rest API.
I would really like a 5-10min weekly informal podcast from Safe Software discussing "smaller" topics more thoroughly with the Safe Staff. Similar to Coders on Couches (https://www.safe.com/blog/2017/08/episode-5-coders-couches-drinking-coffee-drones/ ) - just as a podcast.
***Note from Migration:*** Original Title was: Add the ability to Query partitioned CosmosDB collections to the Azure CosmosDB reader I have a v.big project going on at the moment where we are having to partition our cosmosDB collections due to the amount of data we are using. It would be very useful if this ability could be in place asap.
By default the textures is stored as PNG inside the SKP model, which takes up a lot more space than for example jpeg.It would be great if there was an option to choose JPEG instead of PNG for internal textures in the SKP writer.
A simple request really.I'm appreciating the new dark mode on 2019 Beta, however the difference between enabled/disabled connectors seems less apparent than on the white background and can be missed. A greater visual variation between the two would be useful, maybe also for transformers too.Thanks, Glenn
Just like the normal counter, it would come in handy if the ModuloCounter also had the scope global/local available. Now, you have to put different counternames to start from 0. It took me some time to figure out that the scope is global by default.
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.
