Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I would like to read in Softree Terrain files (.terx) into FME. Sample file: https://support.softree.com/download_file/view/2716/792
Would be great to have a button on the scheduled job page (#/schedules/edit/CATEGORY/NAME) that you could click that would go to a filtered completed jobs page that shows the job history for that scheduled job.
I want to get the following dataFME 2020.0.0.0 Beta (20190920 - Build 20090 - WIN64)FME Desktop Professional Edition (floating)As Parameters within a workspace to be able to write which version of FME converted the file. Is this possible both on Desktop and Server?For instance:FME_VERSIONFME_BUILDFME_BITFME_PLATFORM
During a FME Advanced training a student asked how he could use the Sampler transformer to get a randomize sample of 10% of the features. As the sampler rate in the transformer doesn't support to be set by an attribute this is a hard task.So this request is both for:1. Make the sampler rate to be set by an attribute2. Support a percentage as sampler rate
I was running a workbench from G: and wanted to view my logs. So I set my writers to output a log file for G:Logs but it didn't want to do it. When I created the folder 'Logs' it worked fine.In future releases it would be great to have FME automatically generate the neccessary folder(s) to place a log file in
It's is horribly painful to have a complicated workspace running for hours (or days!) only to have it fail when the shapefile writer hits the 2GB file limit.It would be nice if there was an option to automatically close the original shapefile and start writing a new shapefile (filename_1) when either the dbf or the shp file gets too close to the 2GB limit.
In Automations, in order to use this functionality for workspace job chaining I need the ability to pass workspace published parameters along, as you do with output keys. In my scenario I would like the output dataset of the first workspace to be used as a source dataset in the second workspace and this needs to be dynamic as my original file will come in from a trigger. For this to work I need to be able to pass attribute values out from the workspace action.
Currently if the Feature Reader is set to Generic (Any Format) and the Input Format is set to <Guess format name from extension> and the format name is unrecognized then it reverts to a NULL reader.|WARN |Generic Reader: Unable to guess a valid reader name from dataset 'x'. A NULL reader will be used instead.A NULL reader produces no features, so this ends the translation successfully.The trigger feature should instead be routed through the invalid port so the issue can be caught and dealt with, or at the very least cause a translation failure.
Looking for a transformer to establishing the largest rectangle that would fit inside a given polygon. The mathematics behind it is extremely complex, though would be happy if it only worked with convex polygons to simply things.This idea isn't exactly new.Previously raised in a few questions:2015 - https://knowledge.safe.com/questions/4879/maximal-rectangle.html 2018 - https://knowledge.safe.com/questions/65011/maximum-inside-rectangle-from-an-polygon.htmlHowever, I don't believe it has been raised as an idea yet.
It would be great to have a visual clue on the canvas when redirect to inspector is selected, e.g. changing the colour of the writers
If I understand it right, the ArcSDEQuerier uses the Esri Legacy ArcSDE Reader to connect to an SDE and therefore is kind of a legacy transformer. Would it make sense to update it to use the newer SDE Reader? If not, I think it would make sense to add at least the "Populate from Connection File" option that was added in FME 2015 to the Esri Legacy SDE Reader. The other day it took me 30 min to figure out how to set up the instance string for the connection until I saw that option in the Reader and copied it from there.
When working with large 3D-models and objects you often need to deaggregate. Is it possible to speed this up? For instance by "reverse-group" this deaggregation? So if 1 terrain model consist of 10 terrain-tiles - FME can deaggregate all of them simultaneously. Without having to wrap the Deaggregator within a Custom Transformer and create a group by from that?
***Note from Migration:*** Original Title was: Reading from ZIP files - extract only file specified to use less disk space in TEMP folder Reading files from inside ZIP files is a great feature of FME. But behind the scenes what happens is that FME extracts the files from the ZIP file to the FME TEMP folder and reads them from there. That's fine if it's a small file, but where the extracted files take up a lot of disk space, it can easily eat up your FME TEMP folder disk space.The problem is made worse if you have concurrent Workspaces running, because each Workspace will extract the ENTIRE contents of the ZIP file, even if you only want to read ONE file out of it. I spent most of today trying to figure out why a process was failing and eventually discovered that running 3 Workspaces concurrently, each reading a single file from a ZIP file that takes up 10 Gb when fully extracted used up all my FME TEMP space.I have a couple of suggestions:1) The FME log is not very helpful in this situation. It simply says that it failed to open the file for reading and tells you to check the file exists and that you have privileges. But it refers to the original copy of the file in the ZIP file, not the extracted version in the FME TEMP folder. It would be more helpful if it could alert you to the lack of disk space and/or refer you to the location in the FME TEMP folder.2) I'm using the Path Reader to get the list of files in the ZIP file, then sending one file name to a child Workspace to process. So it would be more efficient for the Workspace to only extract the file it needs from the ZIP file, rather than the whole lot.
The new Socrata reader/writer can see the location data type but presents it as varchar 255. It is a tuple of two address values followed by a bracketed coordinate pair, the three components are newline-separated, and its maddeningly difficult to parse. How about we expose all this by default?https://data.hawaii.gov/Transportation-Facilities/Map-of-EV-Charging-Stations-in-Hawaii/a4df-teiy
Would it be possible to add support for the built-in coordinate systems in both AutoCAD and MicroStation? Both let their users define a coordinate system, but I don’t think FME reads the setting?
It is now possible to produce superlight raster combining GPKG format and WEBP compression with GDAL. It could be great if FME could also support this.
For shapefiles, FME has the ability to create a spatial index for ESRI, but of course that requires an ArcGIS license to create (and another to use).Might I suggest creating a QGIS compatible spatial index instead/as-well? That way folks who don't have ArcGIS can still enjoy fast shapefiles.And as a bonus (probably a different PR), FME could probably integrate the spatial index handling with "search envelope" for shape reader and read the QIX file to speed up reading in those scenarios.
It would be useful to be able to extract the geometry of a partial shapefile, when the .shx and/or .dbf are missing.The shapefile reader could have a parameter that controls whether to fail on incomplete data or let it pass.
Hi, when using Listindexer there is a possibility to add a suffix, I would like to have an option to rename the new attributs instead of having to add an Attributrenamer for each...
We use the HTML Extractor a fair bit when prototyping processes internally, but it'd be very useful to be able to use XPath in addition to CSS Selectors when extracting values from HTML.Main benefit is that XPath allows for much more granular queries for selecting tags/text and can do plenty of things that CSS selectors cannot do.I have fiddled a bit with using the various XML transformers to extract XPath, but with standard HTML websites rarely being valid XML, it gets trickier to troubleshoot extracting values from 'bad' sources
Hi,So i’v stumbled across this completly new database technology which manage in a beautiful way to seal the gap between relational and document databases. It completly remove SQL, with a new query language they call edgeql. Its pretty amazing. They have support for gis functionality soon. And alot more. Go check it out at edgedb. Reader writer with fme 2020?
At the moment the XMLValidator only provides the option to validate agains a schema, if the location for the file is provided as a local path. It should allow for URLs and more important to use the schema specified in the XML file.
Dashboards are also interesting to show to non FME-server users. It is now limited to FME-server users.Would it be possible to make specific dashboards available:to users in the same network or to public users in general orlink via email
I would love to see:* Similar functionality as python subprocess.Popen(...) - pipe stdin from attribute or file - pipe stdout, stderr to attriutes or files* timeout handling* arguments from list attribute or selection of attributes* handling of filesystem encoding* free coffee wherever I go =)
***Note from Migration:*** Original Title was: JSONFragmentor and JSONExtractor should include _json_error{} on rejected feature When receiving invalid JSON, the JSONFormatter and JSONFlattener transformers both include _json_error{}.message, _json_error{}.line, _json_error{}.column, _json_error{}.severity attributes in addition to the fme_rejection_code. The JSONFragmenter and JSONExtractor only have the fme_rejection_code, which is often not as useful as one would want. Additional information is available in the log, but it would be nice if it were available on the feature like the other two JSON transformers.|WARN |JSONFragmenter (JSONQueryFactory): Unexpected character: '''. One of the following characters was expected: '"', '}' |INFORM|JSONFragmenter__Rejected_: Feature is: |INFORM|+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |INFORM|Feature Type: `JSONFragmenter__Rejected__LOGGED' |INFORM|Attribute(string): `fme_feature_type' has value `Creator' |INFORM|Attribute(string): `fme_geometry' has value `fme_undefined' |INFORM|Attribute(string): `fme_rejection_code' has value `NO_RESULT' |INFORM|Attribute(string): `fme_type' has value `fme_no_geom' |INFORM|Coordinate System: `' |INFORM|Geometry Type: IFMENullVS|WARN |JSONFlattener (JSONQueryFactory): Unexpected character: '}'. The following character was expected: 'l' |INFORM|JSONFlattener__Rejected_: Feature is: |INFORM|+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |INFORM|Feature Type: `JSONFlattener__Rejected__LOGGED' |INFORM|Attribute(encoded: UTF-8): `_json_error{0}.column' has value `419' |INFORM|Attribute(encoded: UTF-8): `_json_error{0}.line' has value `1' |INFORM|Attribute(encoded: UTF-8): `_json_error{0}.message' has value `Unexpected character: '}'. The following character was expected: 'l'' |INFORM|Attribute(encoded: UTF-8): `_json_error{0}.severity' has value `invalid value' |INFORM|Attribute(string) : `fme_feature_type' has value `Creator' |INFORM|Attribute(string) : `fme_geometry' has value `fme_undefined' |INFORM|Attribute(string) : `fme_rejection_code' has value `NO_RESULT' |INFORM|Attribute(string) : `fme_type' has value `fme_no_geom'
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.
