Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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'
***Note from Migration:*** Original Title was: usinf FME with SuperStars Open Data API (as used by the UK Gov's DWP Stat-Xplore site) FME 2019 fileAPI Call the the UK Governement Department of Works & Pensions Stat Xplore cross tabluation system (documentation). This is based on a API stystem by WingARC in Australia (documentation).you need to log in and get an API key to use itthen you need to use Stat XPlore as usual, to build the table you want.when ready, choose Open Data API (JSON) from the Download Table optionsthis will give you the JSON Query string, copy and paste that into the Upload Body parameter of the HTTP_Caller, along with the API Key in the Header section.In this example, you will get the National Insurance Registrations each Barnsley and surrounding local authorities, for the last 18 years. Hopefully you'll find it useful as a starter for 10 for your own API Calls.things you might find helpful: - it builds a dymanic JSON query string to get the data out of the massive multi-level array, in the correct too. - it accepts JSON and outputs a tabular format, useful for writing to databases etcDWP_API.fmw
From this Q&A: Extracting transformation MatrixI need to extract IFCDIRECTION and IFCCARTESIANPOINT from IFC geometries. A workaround is to extract the transformation matrix from log and parse that, but it's a roudabout way.It would be great if the coefficients of transformation matrix could be extracted as feature attributes (or the IFC reader could read direction and Cartesian point coordinates optionally).
I have recently spoke with Trimble Priority Support in regards to their SSF/DDF/WPT Reader/Writers. They explained to me that they are no longer supporting them. With no plans to upgrade or maintain them. They also lock users into using 32bit FME rather than 64bit. Safe should take these over so they are not lost with future upgrades to FME.
It might be useful if Attributes/Lists to Hide option could be added to the AttributeExposer. Something like this.
There are some transformers having no input port, which will be "starter" of the translation in a workspace. e.g. Creator, SQLCreator, PythonCreator etc.Currently there is no way to explicitly control the executing order of them, but I think it would be useful if users could control the order optionally.An advantage is that performance (processing time and/or memory usage) of some transformers can be improved if the order of inputs could be controlled correctly. e.g. Clipper: Clippers First, FeatureMerger: Suppliers First, SpatialFilter: Filters First.Additionally, it would also be useful if there were a workspace parameter that determines which run first, readers or starter transformers.
My idea is a "papercraft writer". Papercrafts are small paper models that can be made from paper by cutting and gluing them together.It would be awesome to read 3d model files (citygml, obj, ...) in fme and have the possibility to write pdfs with cutout-sheets for little papercraft /papertoy models. So we could offer the citizens of the city as a fun gimmick to export their own building as a handicraft sheet.
The JSONUpdater would benefit from having the standard set of attribute accumulation mode parameters to allow attributes from the Update features to be included on the output Document feature.
Based on this question I need to be able to run different workspaces as a result of an email to a single email address.At this moment FME Server 2017 does not allow multiple Email publications with the same email address (but with different Subject filters).Allowing more than one Email publication with the same email address would allow easy filtering based on the Subject line to trigger different topic and so different subscriptions.It can be done by introducing an additional layer of workspaces, using FMEServerNotifier transfomers, but that makes the workflow more complex.So I would like to be able to have multiple publications looking at the same email address.
I've inherited an old 2015 FME Server with 60-100 workspaces spread over 20 folders. The server hasn't been maintained.We want to set up a new folder structure to use the server before we start to deal with the legacy content. However it is difficult to differentiate our new content from what is there already.I would love to be able to drag and drop the existing workspaces into other folders on the FME Server without having to republish, with all the scheduling remaining in place. It would really help us deal with the legacy content on the server, some of which we will have to continue to maintain.
It looks like in FME 2017 email attachments path is not configurable anymore and is set to $(FME_SHAREDRESOURCE_SYSTEM)temp/emailattachmentsIt would be handy to be able to configure this parameter via config file.Thanks,
We have lots of best practices for Desktop/Authoring but not on how to set up Server. Like naming convention suggestions, security suggestions, etc. How do you best structure a server installation.
Complementary to the StatisticsCalculator transformer, wouldn't it be great to have a separate FME transformer that emulates Excel's Regression function. In this case, esp. for spreadsheet lovers, we don't need to do an additional step of first writing our results into Excel then separately do Data --> Data Analysis --> Regression, in Excel.Possible features for the proposed RegressionAnalysis transformer include Linear Regression and Multi-Variate Multiple Regression. Well if it's too much of an ask, we could perhaps start with Linear Regression functionality... :-)However, if this functionality is already available in 2016.1 or in any planned future releases (BTW I'm still using 2014), please treat this post as a question rather than a suggested new idea. Otherwise, please let me know if this is possible at all.Thanks,Wilfredo de Vera, P.Eng.Data Specialist
Once again, there's a need to read an old raster format to extract data. This time it's DjVu which has been up for discussion before: https://knowledge.safe.com/questions/83571/djvu-file-format.htmlThe solution now is to use ImageMagick (see this idea: https://knowledge.safe.com/content/idea/97094/incorporate-imagemagick-in-to-fme.html)But I suggest that FME should read DjVu native.
Every day I use the featureMerger a lot and actualy most of the attributes of the Requestor and Supplier are the same... Why isn't there an automatic join?
***Note from Migration:*** Original Title was: XML/GML : Generate subelements through xml_parent_i, xml_id attributes without xsd It would be nice if we could create sub elements in xml/gml writers without xsd, just by giving the right xml_id xml_parent_id attributes for different feature types without the need for complex list, aggregates or xmltemplater.
Hi, is it an idea to create an FME Option that enables that transformers are auto-adjusted to the length of the name of the transformers? If one has a large title, one gets a stretched transformer and if it is a short one, the transformer is kept compact.
When using GroupBy it would be nice to have a counter for this transformer.If there is a GroupBy on the Counter that could be another option.
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.
