Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Running into this and it would be a lot cleaner if it was integrated into the Snipper transformer. See this Question
Hi,It would be awsome if it was possible to parameterize which interpreter to use. (store the settings in the fmw workspace) This would make FME much better to work with different python environments and it would be easy to work with different python virtual environments.
Add S3 Storage Class to the S3Connector. Right now it lands as Standard. Then we have to add a lifecycle rule to transition to S3 Intelligent-Tiering and then we can leverage our Intelligent-Tiering Archive configs.
Surprised this isn't a thing... Would sure be nice to have @DateTimeFormat support epoch Milliseconds instead of pushing it out to seconds and then having to multiply that by 1000.
Please add support for 'variance' column type to ODBC 3 driver. Or your next version of that driver.
I have been using the SnowFlake (spatial) writer now for some projects, and experience Snowflake to be quite picky when it comes to the geography it accepts...Not particular Safe Softwares problem, but while struggling I often enounteredIf you would like to continue loading when an error is encountered, use other values such as 'SKIP_FILE' or 'CONTINUE' for the ON_ERROR option. For more information on loading options, please run 'info loading_data' in a SQL client.after the error message generated by the copy-command (copy-ing the contence of a .gz file to the table).Could I please have some way of setting these ON_ERROR flags in the snowflake writer? Ofcourse aware of possible data corruption, I still would like them, if even only for debugging...Kind regards,Martin
When testing workspaces on FME Desktop I usually have many log messages turned on. When I publish them to FME Server I want to turn some of them off. When I go back again to developing I have to turn them on again on FME Desktop.Solutions:1. Add an option when pushint "Publish to FME Server" to change logging level when publishing a workspace - so you can keep the logging level you have on Desktop, and publish another loging level on the same workspace on FME Serveror2. Be able to change loging-level on workspaces through FME Server GUI
The extent of the canvas begins limited to your screen area, and the normal way to expand that available area is to click and drag an item on the canvas out beyond the screen space.What if the canvas could also be expanded simply by panning and scrolling across the canvas?I like to work with the transformers always centre screen, because the space on the right is the space to develop, the space to think. I never want to be cramped against the canvas edge on the right of the screen without space to add more transformers. So when I start authoring a workspace I always drag an empty annotation far off to the bottom corner to expand the canvas to give me space to work with. That is a workaround, but it would be far simpler if the act of panning to the edge of the canvas would expand the canvas.Or, another way of solving this would be to make it that when you pan to the right edge of the canvas, the maximum panning extent should be reached when that canvas edge touches the left edge of the screen, instead of the right edge of the screen as it does currently. Then, adding new transformers in this state would be done past the edge of the canvas, which would automatically extend it same as it currently does. Limiting the panning extent in this way would also prevent a possible issue of new users panning around an infinite canvas unable to find their transformers.Example:
Manifold GIS is a software package that performs spatial data inspection and analysis. It's extremely lightweight and fast, taking advantage of GPGPU processing. Allowing FME to interact with Manifold directly as well as its .map files would be a huge advantage for many GIS analysts.
In the Alert section in FME Cloud, it is only possible to choose one email to notify if e.g. Primary Disk Usage above 90% for 10 minutes , but we often collaborate on projects and need to get notified as soon as possible even when a colleague is sick or not able to view his/hers mail. What about being able to choose several emails, or at least two, instead of making several alerts for the same notification, just so that more people can get the same notification.
When working with a linked custom transformer, I often have to temporarily embed it to properly debug it. Then I have to export it to make it linked again. However, when I do that, any version history on the transformer is lost, as the versions start over at 1. This will, of course, break any other workspaces using the linked transformer that have not yet ready to upgrade to the new version.When exporting, there needs to be an option to add a new version to the .fmx, rather than merely overwriting it.
It looks like the AttributeManager doesn't offer the ability to Expose attributes that exist on a feature as yet and then do something to them, like rename. This would extend its capability.Merged Ideas:Add "exposer" to AttributeManager by bakkermans on May 1, 2016Is it possible to add the function of the AttributeExposer to the AttributeManager?
Hello,when working with linked custom transformers I often have to temporarily embed the transformer to properly debug a workspace. However, there is no good way to revert to the originally linked transformer. Once the transformer has been embedded I either have to remove all versions of the transformer to insert a linked transformer again (which means I have to repopulate all parameter values and properly connect the transformer) or I can overwrite the existing custom transformer which replaces the transformer via the "Export as Custom Transformer" option.I think an option to transform an embedded transformer to a linked one would be nice. Does anyone have another good way to develop/debug custom transformers that are integrated in multiple workspaces?
Just googled this and I'm sure there's a way somewhere, but if you want to read just the attributes and not the geometry for features, e.g. to query/review just the attributes, a 'table only' option could be useful to reduce read times where you have a large number of features. Admittedly I'm not certain how much overhead geometry actually puts onto the reader!Seems like this might have occurred to someone earlier, so if it's old hat then that's all good!
Would be great to do away with the type (metric & repository) and combine them so then you can select both repositories AND/OR metrics as rules.
On the item page of a hosted service you can export to fgdb and other formats.The benefit of this over an fme reader and writer workflow is the easy preservation of unique ids, relationships and attachments. This also takes no local compute power/time. Please make a way perform to the "Export To FGDB" (or other formats) found on the hosted feature layer item page within FME.There is already a method to download items from arcgis online with the use of the ArcGISOnlineConnector (https://docs.safe.com/fme/2020.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/arcgisonlineconnector.htm)If we could create the fgdb through fme, we could also download and manipulate it within a workspace. I'm doing some lengthy transformations on a million+ records. Performing these actions through the Online Readers/Writers is taking hours (90% is reading from the REST API) and I need to reduce that time.I also see this workflow being a simple daily backup tool for ArcGIS online. Thanks!
It would be very useful if the feature types were written in the order in which they are arranged by the user. In this way, writing to databases with foreign key restrictions would be simplified.
Add the ability to expose paper space sheet names via the Schema Port within the FeatureReader when reading AutoCAD DWG files. Currently, a solution suggested by @jedi121 (https://community.safe.com/s/question/0D54Q000080hBiUSAU/how-to-read-all-paper-spaces-from-acad-file) works well for the DWG Reader but does not expose all sheet names within the FeatureReader transformer.Or can you add an option to read all DWG sheets in the AutoCAD DWG reader parameters vs. manually selecting them? Maybe add the option here: I am attempting to read all sheet names for a DWG file using parameters within a FeatureReader.
The Clipper (in FME 2019) seems to reject vertically oriented area features. It should clip them properly like it does with with other areas.Our use case is generating 3D Block models with Buildings and Terrain, we have a nice workflow working, however, the vertical wall features are getting rejected which results in holes in the model.Of course this feature would also help: https://knowledge.safe.com/content/idea/19471/clipping-operation-for-surface.html or this: https://knowledge.safe.com/content/idea/86914/meshclipper-or-3dclipper-or-anygeometryclipper.html With 3D picking up more it would be really great to see better behaviour with Clipping 3D features. #3DisTheNew2D
I use TestFilter as a means to allow only certain feature classes to be downloaded from an ArcGIS enterprise geodatabase. If I didn't have TestFilter populated with the specified feature classes, someone could conceivably guess the name of a non-public feature class and download it. I have well over a hundred feature classes listed in TestFilter. When I need to find one of the feature classes, or have added one or more feature classes, things get messy real fast when trying to locate a specific feature class. If sorting and/or searching (including wildcard) was enabled on TestFilter, my task would be much easier. Thanks!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.