Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be nice if the Feature Joiner had the ability to scan for duplicates on the Left or Right entry point with the option of routing them through their own outputs. I think this would improve the ability to control what type of join is being created.
I would like the ability to expose (or create) on each feature the path that feature took in the workbench. I think this could be best executed in a list format, where for example, the first transformer a feature passed through is feature_path{0}.transformer. The second transformer would be feature_path{1}.transformer...etc.I think this could help with pinpointing errors in the workflow.
Currently (2019.1) you aren't able to upgrade the tranformer via the Navigator pane if the transformer is inside a closed bookmark. You first have to expand the book mark first before upgrading it. It would be nice to not have to expand each bookmark to expose the transformers before upgrading.
It would be nice if the PointOnLineOverlayer could include Elevation (Z) and Measures (M) coordinates for multiple overlaps when Generate on Point to a List is selected as the output. Currently, it only returns Z and M for the first route in the list of multiple overlaps. Then the logic you've build to choose the correct route/segment would have every element including M & Z stored together in a single List Element.My Example has multiple routes/segments returned:But only a single measure is available for processing:It would be nice if the coordinate information could be included in the output List if user needed it.
I have workbenches who works with a lot of data (1 million features). i combine the data from different sources. but if i inspect the result, the inspector takes a long time to build up all the features.I want to add an number of features in de inspector. so when the workbench works all the data it show only the given number of features. (no number it shows all features, of course)
Could a parameter be added to insert a new line before and/or after a text line writes a feature/many features, for appending to existing files? E.g. appending FME workspace log files just to create that separating between successive process run logs. This can be worked around using e.g. creators, counters and sorters but an in-writer option would be tidy.A second idea would be that you could insert a header/footer block of text/more than one line.
It would be good to match ESRI JSON output format to ESRI Enclosed Format so that it can be used for AWS Athena tables.
***Note from Migration:*** Original Title was: ArcGIS Online and Portal feature writers to support adding and updating attribute indices If you are maintaining large feature layers that will be queried with non-cached expressions then maintaining indices on query fields will prevent full table scans on query. At the REST level it means passing JSON to addToDefinintion or updateDefinition, like this setting up a unique index on a field 'id':{"indexes" : [{"name" : "idIndex","fields" : "Id","isAscending" : true,"isUnique" : true,"description" : "Unique index on primary key field ID"}]}If the writer could do this it would help a lot.
Hi,We will be using workspace runner to perform running 1+ workspaces one-after-one or repeating the same workpace number of times in batch mode.For instance, if we have GDB with 10 million features and we have to use the same contents in more than 1 workspace then we have to read more than 1 times based on workspaces requirement.In order to eradicate this repeated activity (reading same data multiple times), if we have transformer which passes data from one workspace to other workspace such that we can run the workspaces in parallel as well one after other (based on preference). This transformer will reduce alot of hours (lead time).Pratap
In the FME Server 2019 beta, you can add triggers, actions, etc, but while you can add all these, there is no warning if you save them without altering anything. That is you can add a process to call a workspace caller, but never call a workspace in it. So it may be easy to overlook a piece of the puzzle.It would great if on save the automation was checked to see if the details are filled in, in all the automation and warned if not (e.g. type = trigger or type=sender means they are blank, while workspace types would have empty WORKSPACE). You could choose to save, but be aware that bits are missing.
Trying to troubleshoot jobs with the new workspace viewer is hard. Is it possible to include the actual name (which matches the log name i.e. TestFilter_28) in the popup or as the tab name like it does in desktop?
It would be neat to have a mobile app that allowed me to provide all the sensor data from my phone to a workspace run on FME Server or FME Cloud.I'd want to be able to use any FME Server, probably multiple and any workspace. In some cases I would just want to run the workspace, but in other cases I would want the output of the workspace to be provided back to the phone. For example: PDF, Powerpoint, or cool stuff like Augmented Reality or any new app that might come out and which uses data.I don't want a complicated app! Just let me run the tasks (workspaces) and see the result.
The current FME(2016.1.0.1) only allow the user to save one setting. But many times we need to switch between in many Settings, I hope I can save multiple setting, and can be set each name.
The ArcGIS Online reader and writer are quite slow to use. For every feature type, in every AGO reader and writer, FME currently loops through all accessible groups twice (once to find the feature service, once again to find the layer). When a user only has access to a few groups within his organization, it's merely an annoyance. When a user has access to a large number of groups, waiting for FME to find the correct layer can add minutes to the time it takes to run a workspace. There is a workaround where the HTTPCaller can be used to directly access a layer, much faster than the AGO readers/writers can, but this method has several other downsides. It would be great if the official AGO readers/writers could be improved to be a lot faster.
From @lefred06 at https://knowledge.safe.com/questions/96349/s57-customized-files-location.html Customized S-57 CSV files should be stored outside of the FME installation directory so they aren't lost when FME is upgraded or reinstalled.
We run 32 and 64 bit versions of FME Desktop along with Dev and Prod environments for FME Server. Some of the more complex workspaces we create involve a fair bit of manipulation of inputs, outputs and resources between these instances.I am currently in the process of writing a startup python script to identify which environment (desktop 32, desktop 64, Server Dev, Server Prod) a workspace is running on - this works. From there I can read a config.csv which has parameter names and a separate column for each environment - this also works.The next step would be to set appropriate user parameters, to circumvent the need for manual changes in the different environments, but this seems to be a sticking point as user parameters need to be predefined.Could provision be made for the dynamic creation and setting of user parameters at startup?
I have a workbench where I have multiple readers and each reader goes to their own DuplicateFilter. Each DuplicateFilter creates a DuplicateRemover table in the Temp folder. When the reader finishes, I wish the DuplicateRemover temp file used for that reader would be cleaned off. I've begun running into memory issues as the files I've been reading in have grown.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.