Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Right now, selecting Segment Snapping while using the AnchoredSnapper means that candidate features will also be snapped to line segments within the specified tolerance. However, candidates will also still be snapped to vertices, and the AnchoredSnapper even prefers vertices to segments, even in Segment Snapping-mode. My use case is that I need to snap certain features to the closest point on a line. However, in some cases there is a vertex nearby that is not the closest point, but still within tolerance, and the AnchoredSnapper prefers these points. I can probably find some workaround, but a simple checkbox to force the AnchoredSnapper not to snap to vertices but only segments would be a cleaner solution.
Do you have plans to include a Rocket.chat connector in the transformer list?
When working with Linked Transformers and editing, saving. It is cumbersome to always have to restart a new FME Workbench to reload the Custom Transformers after saving an edit. A button to "Force refresh" of initialization of Custom Transformers / formats etc would be great.
There is now an FMEAR app for iPhones and iPads. There is development planned for an Android version. Is there any interest in a Microsoft based version for Surface tablets?
Business case: downloading a folder from the share data folder in FME server is not an option in 2017. It forces the user to select all individual files to download.My Scenario:I have a project that needed to run 3 models with a Job submitter service as I was writing back to the Shared Data folder. The second model takes the out put from the first as input, then the 3rd takes the results form the second to run.-- for technical reasons I couldn't get everything in the same model. It would have been nice to be able to also download the zipped folder as each step ran so that the user can see the data transforming at each step.
Possiblity to cancel Jobs direclty from the "Job Submitting Page" would be nice
Currently FME support upto LAS version 1.4. Would be great to be able to work with versions 2.0 and 3.0 as well.
***Note from Migration:*** Original Title was: A good method of upgrading FME Server between without using extra licenses for a testing environment
It would be useful to embed connection parameters when dealing with sql executor
ArcGIS ships with tile cache definitions for example in Pro at:C:Program FilesArcGISProResourcesTilingSchemesIt would be handy to import these when writing Geopackage - provided the scheme is compliant.@jakemolnar
To update a reader - just right click on it and select Update. As it is (unless I missed something - possible), when I modify a table or view in Oracle, to get the reader updated I have to presently: Click on Readers -> Update Feature Types... Select Reader it belongs to (hope you remembered) Click on Parameters... button (Thankfully 2015 "remembers the username and password") - Click on the ... button for the Table List Deselect everything I don't want to update Select the thing I do want to update Click OK Click OK Click OK Painful, lengthy, potentially error-prone process... do I need to say more?
Uploading the same named workspace seems to make no changes sometimes. (cached maybe?) current Workarounds are - rename the workspace to another name. Restart fme GUI sessions re-login (slower than 1st option) So can a 'replace' option in the upload to fmeserver from desktop to force the changes... to the same workspace. Maybe a replace, append or modified mode option? If possible.
Support reading/writing to HDFS and Hive and others -- indicate in the comments your ideas.
I often need to add spatial tables (PostGIS) and non spatial tables (PostgreSQL) in the same workspace.For spatial tables, I'm adding a PostGIS reader.For non spatial tables, I'm adding a PostgreSQL reader but I need to uncheck spatial tables because I dont want to read them with the PostgreSQL reader (the PostGIS reader already read them).And if I have many tables, it's not convenient.So I would like a parameter for the PostgreSQL reader to include/exclude spatial tables from the tables list or a symbol in the tables list to distinguish spatial and non spatial tables, or a button "select/unselect spatial tables".
I have a number or workspaces that have become too big to see in full when I zoom all the way out. Now, I know what you're going to say: "Surely that goes against best practice!" or "Get a bigger monitor!" or even "Can't you now just use collapsible bookmarks!"Well I just think that this would be a nice to have. I'm kind of proud about how big my workflow is. I've documented it well and it's laid out in a way that makes sense to me. What are your thoughts on this?
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.