Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Topographic plans from surveyors that use the survey module of Civil3D typically contain lots of feature lines (and survey figure lines). It would be more efficient to read feature lines directly in FME. Together with its properties (from property sets). Reader support for Survey Figure Lines would also be nice.In 2021.0 release, a feature line that was used to build a corridor in the Civil3D DWG is read as an alignment, but no properties are found, neither with AttributeExposer. For an ordinary feature line (not linked to a corridor) nothing is read by FME.
Currently, the ArcGISOnlineConnector cannot download ESRI multipatches that are published as a Scene Service. The only way to download multipatches through the Connector, is by downloading them as Scene Packages (SLPKs). However, since SLPKs cannot be read with FME, this does not allow for further processing inside the workspace.
I would be nice to be able to create a user parameter by right clicking in the Parameter Name column, and select "Create User Parameter" from the dropdown dialog.Sometimes you build your workspace backwards, and want to create a User Parameter to assign a value to an existing attribute.
When using a SQLExecutor in a workflow, I want to overwrite an existing attribute on a feature. However, this also applies to the fme_feature_type which is now set to "SQLExecutor". Because of this, I have to store the original fme_feature_type in a temporary attribute and then reassign fme_feature_type after the SQLExecutor. It would be fantastic if there were an option to "Overwrite fme_feature_type" that was defaulted to false.
When using a ListElementCounter it would be nice to have an option to count elements with attribute values that are unique only.
Add Web Connection for OAuth2 authorization to gather Google Fit data. Link for scopes: https://developers.google.com/identity/protocols/oauth2/scopes#fitness
It would be very useful if the Schedules in the FME Cloud Management Console would have an option to compensate for Daylight Savings. As it is now, you have to manually edit your schedules twice a year, and if you have many instances it could be a lot of work. I am looking for a function like on my router (screenshot), where I manually can edit settings for Daylight Savings. We either really need this option or if you could abolish Daylight Savings... Your call, Safe :-)
Hi all,At my company we process a lot of measurement data with FME. The visual preview tool in the Desktop is really the best tool ever in development. But I am missing some features.Is it also possible to add dynamic charts in the visual preview? We can use the chart generator, but that one is too static. We always divert back to Python (plot.ly) or to Tableau Desktop for the troubleshooting. It would ease up the development if that would be possible.
Loving the new Parameter manager in 2021, but it seems we've lost some functionality in the definition of the Number parameter type.In 2021 we can set a range limit and choose whether to accept integers or floats. Prior to this we had the range limit and selected the number of decimal places allowed. I found this far more useful to limit the number of decimal places being entered to keep things simple for the user.For example if my workspace just expects a number like 5.1, I don't want the user to be able to enter 5.12345684935153. It is pointless and means FME has more work to do to render the parameter value to be as expected.While the drop-down choice between integer and float is quick and easy, is would be handy if when float is selected, a further parameter is activated to set the number of decimal places.
No description is available.
***Note from Migration:*** Original Title was: Histogram view for better classification and analysis (AttributeFilter, AttributeRangeFilter, Inspecor) Including an histogram view (number of features with attributes value, regression curve, mean, natural breaks...) to those transformers or the inspector would help to define ranges for numeric data and check data quality for categorized data. Most people need to load the data with qgis or arcgis to do it and it is a waste of time. This should really useful associated with feature caching mode.related ideas :https://community.safe.com/s/idea/0874Q000000TlJHQA0/detailhttps://community.safe.com/s/idea/0874Q000000Tl6SQAS/detail
***Note from Migration:*** Original Title was: Allow Geometry Type Multipatch to Esri ArcGIS Online (AGOL) Feature Service Writer Would it be possible to enable Esri ArcGIS Online (AGOL) Feature Service Writer with the option to write Multipatch features to ArcGIS Online?Currently these are the geometry types allowed: arcgisonline_pointarcgisonline_multipointarcgisonline_polylinearcgisonline_polygonarcgisonline_no_geom
What would really help with authoring high-performance workspaces, is to change a reader or writer into respectively a FeatureReader or FeatureWriter. This allows more versatility to switch from "dumb" (=traditional) reading and writing to "smart" reading and writing (more easily do actions after writing, or read in batches). This idea would lower the barrier for authors to transition to more advanced ways to read and write data.
Currently, the OBJ writer names each texture noname[n].jpg. This can be a problem when importing multiple OBJs into a model or data store when texture files have the same name. It seems that changing the Appearance Name with AppearanceSetter has no effect on OBJ texture names. My suggestion: iBy default, the OBJ writer should save textures for an OBJ as Basename[n].jpg. Or at least honor the AppearanceName. Currently, achieving unique texture names requires a lot of awkward hacking. This fix would make for improved file hygiene and much simpler workflow. Thank you.
***Note from Migration:*** Original Title was: Write out to separate levels for tagsets and geometry in the Microstation DGN Writer It would be really useful if there was the ability to separate out the levels for geometry and its associated tagset in the Microstation DGN Writer. This is required by my organisation so that the file can pass our internal CAD Quality Assurance tests. At the moment the <tag name>.level format attribute is only supported by the Microstation DGN reader and not the writer.
The crux of the idea is outlined in this question: https://community.safe.com/s/question/0D54Q00008VsdhhSAB/gltf-output-is-transparent-when-it-shouldnt-really-beBut the idea is this:When writing out texture materials to GLTF (and 3DTiles) which contain and alpha channel (e.g., a png), change the default alphamode from BLEND to MASK.This would solve many rendering issues which pop up from BLEND rendering. This is not a one size fits all as BLEND could indeed be what is desiered so as follow up suggestion:Add an option on the gltf reader to select the default alphamode - This is what is used when exporting from Blender (https://docs.blender.org/manual/en/2.80/addons/io_scene_gltf2.html).A step further still would be to allow a geometry trait whitch could dictate which alphamode is used (e.g., gltf_alphamode). At present this is a pretty big issue for us
For example after creating a temporary path I want to download my item to _dirpath and can't pick the attribute, I have to use @value(_dirpath).
We're increasing usage of HTTPCaller to interact with on-premise enterprise system APIs (mainly Cityworks). In reviewing some of the job logs for Automations that contain HTTPCaller transformers, I notice repeated messages like this:HTTP transfer summary - status code: 200, download size: '1061 bytes', DNS lookup time: '2.5e-5 seconds', total transfer time: '0.135342 seconds'While that lookup time is marginal (0.000025 seconds), in a workspace where 10K or more features pass through, it adds a bit of overhead and seems to make redundant DNS lookups (I can't think of a situation at the moment where the HTTPCaller will hit different servers in the same flow of data). Would it be possible to cache the DNS lookup when the first feature passes through and just use the cached value for subsequent features? Or if for some reason there would be switching of servers, cache the unique servers DNS results and use them as appropriate?
Currently we can only read/write feature service from AGOL in fme. As we deal with lot of raster data avilable as Raster service in AGOL. Need a reader for Raster service from AGOL
Ability to read from http://www.maptiler.com/ with a WMTS Reader. Consider a WMTS Reader for this service.
Not just a reader for maptiler (like https://knowledge.safe.com/idea/49606/maptiler-wmts-reader.html) but a wmts reader for general use. i.e. PDOK or your own WMTS.
Clipping Meshes now involves Deaggregating, Surfacedraper, TinGenerator, Clipper, Triangulator and takes quite a lot of time on large areas. Would it be possible to implement this faster within a MeshClipper that takes a Mesh as input and gives the same clipped Mesh as output? Would be great for dealing with large terrain, even though they are tiled.
A lot of users of our 3D data would like to export textured multipatches in ESRI FGDB from our 3D platform. FME Cloud doesn't support that at this moment.
Basically I want to pivot my table so that the Value of the attribute to analyze is the value of the new columns. To make sure I have one attribute per column, I first created a list of the actions based on the same group by as the pivoter with the addition of the column attribute and then concatenated that in one attribute. Now I want to see my group by attributes in the rows, with the column attribute as columns and the values (text) of the Actions as values for their columns.
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.
