Open ideas have been reviewed by our Product Management and are open for commenting and voting.
When inspecting data in 3D which has Lat Long for X and Y and meters (or feet) for z the data inspector doesn't handle this very well. The Z axis is treated at Lat Long and so gets greatly graduated. This is not uncommon and can be quite confusing. Especially for new users. There is no way of 'fixing' the view without reprojecting the whole dataset. A button in the Data Inspector to view all units in equal units would be pretty nice. This is essentially already done in 2D where all data get reprojected to match the basemap.
Hi there. It would be super cool if we can read and write geoparquet format files (https://github.com/opengeospatial/geoparquet).
When FME gets to supporting OpenAPI in the HTTPCaller, then to the extent that OpenAPI supports the various pagination approaches, make them available in the transformer.
VUE file reader, a solution to handle 3D models (graphics and object properties) asociated with Intergraph Smart 3D y SmartPlant an data formats .VUE and .MDB2. Hexagon SmartPlant does not support full potential to export to IFC format, so a VUE reader and a transformation process from VUE to IFC files in FME would provide interoperability for AEC companies working with Hexagon software.
Along themes mentioned in https://community.safe.com/s/bridea/a0r4Q00000Hbr7TQAR/reading-from-zip-files-extract-only-file-specified-to-use-less-disk-space-in-t?currentpage=5andhttps://community.safe.com/s/bridea/a0r4Q00000HbrNzQAJ/select-data-in-compressed-files-eg-zip-downloaded-from-an-url-same-way-as-fr?currentpage=7I've got a few hundred zip files, with around 1000 files in each one. The reason they are zipped is because they are json files, so compress quite well, and handling 100,000 files in a directory gets unwieldy.when reading the features in using a wild-carded reader e.g. *.zip[***.geojson]the behaviour seems to be that it sits there for a long, long, long time before starting to read any features. Combined with the messages in the console, this makes me think it's unzipping every zip file before starting to read any features, rather than unzipping and reading in parallel ?Would be far better to skip the entire unzipping and writing to disc stage and just stream the zip file contents, unzipping the the data stream as it gets pulled off the stream and piping it into next process step.There is a python based streaming reader herehttps://stream-unzip.docs.trade.gov.uk/getting-started/https://stream-zip.docs.trade.gov.uk/similar lib herehttps://github.com/allanlei/python-zipstream
Is it to much to ask for, or is a Rust sdk possible in the future?
Whenever Actions - Remove is done on a Schedule, Resource, Repository, etc... the box next to the, for example, Resource that you want to remove is at first checked, then the checkmark disappears when you do Actions - Remove; it would be more reassuring to the FME Flow users to keep the check mark in the box to left of whatever is to be removed, rather than have the check mark disappear once dialog box for Actions - Remove appears.
Hi there,When the PointCloudCombiner is applied to polygons, it produces grids of points separated by the Point Interval covering those polygons. Would it be possible to add an optional 'origin' to the PointCloudCombiner, to give more control over the positioning of those grids? Thanks a lot!
It seems as if currently there is no possibility to populate a choice parameter dynamically, based on scripted parameters. To illustrate the idea a bit...Offering our clients the possibility to convert geo-data from our database into CAD files we need to know what datasets are available to choose from. Having a Python script returning the table names of the database is easy enough, but then the choice parameter does not take the list to select from.Hence, it would be very nice if we could offer a choice list that's more dynamic.
When working with many values in the AttributeValueMapper, like the case when you have imported from a lookup table, it would be very useful to sort both the columns Input Value and Output Value both numerical and alphabetical. Just like the Table view in Data Inspector works.(there were an old similar idea which got sort of an answer but manual sorting is not what I need when I have many values in the AttributeValueMapper transformer: https://community.safe.com/s/bridea/a0r4Q00000HbrJdQAJ/sorting-attributes-attributevaluemapper )
It would be great to get a warning when publishing a workspace to FME Flow if any disabled Readers/Writers or Transformers are present in the workspace. Often Writers in particular are disabled while testing new changes and I have accidently published these workspaces without realising.
Azure Services Bus as an option in an Automation Trigger, to receive messages from the Azure service bus and use them to start other workspaces. On the FME Hub, there is already an AzureServiceBusConnector transformer. An integration into an automation trigger would be a great addition to this transformer.
This is a minor user experience request. I want to see full version number in the window title and startup screen. Recently, I was using FME Workbench 2022.2.24 yet, both the window title and startup screen only showed a partial version number, "FME Workbench 2022.2." Since I had both 2022.2 and 2022.2.24 installed, this was confusing. I checked FME Form 2023.0.1 and see that it has the same behavior; it only displays "2023.0" in the window title and startup screen.This should be easy to implement and it can only help users. I suspect that the reason the full version number is not displayed is merely because FME has always done it that way. Thank you for your consideration.
This idea is a follow up on the following question I created on the FME Community; https://community.safe.com/s/question/0D7Dm000000dkmTKAQIn short, I noticed that the StatisticsCalculator always expects Summary statistics. In case you only want to calculate Cumulative statistics, you either need toignore the error/warning (redCogwheel) indicating; 'Parameter 'Statistics to Calculate: ' must have a value'provide a dummy attribute to calculate regular 'summary statistics'.Something about that doesn't feel right. It would be nice to also have the option to only create Cumulative Statistics. I guess that may be possible by embedding the regular 'Summary statistics' in a Checked ParameterGroup (and be default checked), similar to how that is currently the case for Cumulative statistics (default unchecked).
This idea is a bit of a follow up on the following question I created on the FME Community; https://community.safe.com/s/question/0D5Dm00000goQFoKAMIt feels a bit odd that in the 'Feature Information' window you can sometimes see that an attribute is of (Data) type 'bytes', but nowhere in transformers or functions of Workbench you seem to be able to leverage this information. E.g. the following two features;feature 1; text (bytes): 48656C6C6Ffeature 2; text (string: UTF-8): 48656C6C6Fare virtually inseparable/indistinguishable in FME. A sample dataset is attached (as zipped FME Feature Store (FFS) file). Therefore, I think it would be nice if the Data Type 'bytes' could get a bit more formal position in FME. E.g.;When testing/filtering with 'Operator' = 'Type is', add the ability to select 'Bytes' as a type.In AttributeManager/AttributeCreator (as of 2023), add option to set Type equal to 'Bytes'In Python FME (Objects) API, add 'bytes' as a formal data type. See e.g. the following; fmeobjects.FMEFeature.getAttributeType — Python FME API FME 2023.0 b23309 documentation (safe.com)
SummaryWhen adding readers and writers please create more readable and useful names for the navigator.DetailsWhen you add a reader or a writer the default name is not very useful for example:<not set> [ARCGISPORTALFEATURES]I find my navigator is much more readable when I rename the readers and writers something like this:Esri ArcGIS Portal Feature Service READERSo using the format description not the short name and specifying reader or writer (because after almost 20 years of using FME I still cannot distinguish the reader/writer icons).
The native Revit Writer only has support for surfaces.It would help the asset management flow to also have support for line and point objects.Point and line data can be used for referencing predefined classes in object libraries or as a basis for new drawings.This is in line (pun intended) of the Revit way of constructing objects such as walls based on heartline or outside line (inner or outer face)
With the current Directory Watch capability, a trigger message is fired for every file change that occurs in the watched directory. This is fine when a workbench is required to process each file change.In the scenario where multiple files are copied into the directory that you want to process all at once (e.g. copy in multiple mid/mif files to be converted into one file geodatabase), a trigger is fired for each file, where you would ideally want one trigger message to say "this directory content has changed".I would like to see an option on the directory watch configuration to allow either one trigger per file change (i.e. the current situation) or one trigger per directory change (i.e. where one or more files have been changed/created). This will then allow the associated workbench to be run once to process all files in the directory.
Extend the HTMLReportGenerator Parameters window some more to make more room on the Content Settings side. At present it's too difficult to review / write codes. I'm having to use VS Code first then Add the Attribute Values where needed.
For easier readability: Add icon in Feature Information window showing datatype . Similar to what is here: https://ux.stackexchange.com/questions/43695/graphic-representation-of-various-data-types
I'm a big fan of the History window. I don't think that many people know about it and it's really useful.I think it could do with a bit of care though. For example recently I was missing the Save action in the timeline. There's probably other actions I can't think of right now that should appear there too.
Add Timeout Parameters to JSON Readers, you can put a API URL into the json readers and it works, however some API's are really slow and it will timeout. You can work around this by using the HTTP Caller, but having the json reader is a lot nicer, as the reader parses the json into attributes itself.
It looks like FME's SketchUp Reader only supports the .skp file extension.We have customers who use Rapid Sketch files (.rs) and require conversion to Esri format. Is it feasible to add support for the .rs sketch file format in FME? Thanks!
It would be helpful if a "Data Type" column was added to the AttributeManager, so we could view/change/set the data type of each attribute. Another option would be to allow the data type to be set manually when a new attribute is created.I know it is possible to set the data types on the writer feature type, but I think this would be especially helpful when creating a new attribute. Additionally, if I am copying an existing AttributeManager (within the same workspace, or into a different one) it would be nice if I could set the data type for an attribute once, and that would be preserved when the transformer is copied - That way I wouldn't have to manually change the data type on every output feature type.
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.
