Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
Hi,The FeatureWriter is powerful, but the button "Apply to..." is missing. Is it possible to add it?Thanks!Rémi
One very frequent issue that I've come across is the need to record the timestamp during a model. Currently, the main way to do this without having different timestamps across a dataset is to capture the timestamp at the beginning of the model and then to store it in a parameter.It would be great if instead, I could use a built in parameter, such as FME_RUN_DATETIME.This parameter would capture the datetime when a model is run for use in later calculations, attribution, custom logs, and fanouts as needed without having to add multiple transformers to each model.
Add the fourth dimension to the CoordinateRounder, so that it will be able to round not only XYZ but also M (measures, used in linear referencing).
FME Data inspector have a function of Filter Features,But it seems to work only on Feature View,and not on Table View.Most of the time, filtering the features, but also hope that the Table View can keep synchronized,If this function can work both on the Feature View and Table View,It may be more convenient.
Would be awesome to have a writer (& reader) to esri big data store.
Currently, FME writes NITF 2.1 and does it wonderfully, but it would be helpful if there was an option to create NITF 2.0 compliant output under the MIL-C-89038 standard.
Currently, when using AttributePivoter the resulting features have the "pivoted" attributes unexposed. This behavior does not replicate what some users would expect from a "pivot." For example, when creating a Pivot Table in Excel or using popular R packages reshape or tidyr, one expects the resulting pivoted table to contain exactly the rows, columns, and cell values specified. The resulting table of exposed attributes in FME does not look like that. Therefore, users currently must add an AttributeExposer after the AttributePivoter. That's well and good, but why not add an option to expose attributes in the AttributePivoter to avoid this step? This section in the transformer could mirror the "Attributes to expose" parameter in the XMLFlattener or JSONFlattener. Even better would be allowing these parameters to get their value from an attribute or through an Import feature such as is available in the AttributeExposer. See this related idea.While we are at it, do any other transformers need an "Attributes to expose" parameter that currently don't have one? I see a few existing ideas: BulkAttributeRenamer XMLXQueryExploder
In the transformers that combine features (Dissolver, Aggregator, RasterMosaiker, BoundingBoxAccumulator, etc) the Accumulation Mode is one feature, none, or merge all.It would be nice if we could select which attributes to merge in the same way we can if we are generating a list.
Todo: For the PostgreSQL/PostGIS writer, add a checkbox to force the schema, table name, and all column names to lower case.Why: When converting from databases like Oracle where everything is by default uppercase, to PostgreSQL where everything by default is lowercase, the Dynamic setting creates everything as-is, which is normally good - but in this case keeps everything uppercase which is undesirable. Adding a checkbox to force everything lower either at the writer level (most desirable), or the table level would be most helpful.My use-case: I have an Oracle production GIS database with over 4600 tables to convert to PostgreSQL. I don't look forward to having to touch each stream to add a bulkattributerenamer and set the schema and table names.
To be able to have the width of Max as an option in the SQL server writers/ feature writer. varbinary(max) or varchar (max) etc
As mentioned in this question and discussed in the answers, it is now almost impossible to make FME export an XML document with a <![CDATA[ ]]> section a.k. literal character data.My intended use was to communicate some HTML-formatted descriptive text in a XML-response about the capabilities of a transformation. This can thus be presented to the end user of the application communicating with my service.My preferred implementation would be to add a XQuery function in the XMLTemplaterget-attributeget-xml-attributeget-cdata-attributeKind regards,Martin
It would be very useful to be able to set a "Translation Timeout" as a workspace translation parameter, like this: If the total runtime of a translation exceeds this timeout configuration, then the translation immediately terminates with a timeout error. To my knowledge, currently we can only control job expiration times for jobs submitted to FME Server, as an advanced parameter of the FMEServerJobSubmitter transformer. That's great for many use cases, but it doesn't help with controlling timeout issues for job chains run locally with FME Desktop, or for hybrid desktop/server workflows. I feel like a more object-oriented approach would involve allowing the workspace author to set a default timeout from within the workspace, regardless of whether it will be running on desktop or server.This translation timeout parameter could then be linked to a published or private parameter, depending on the use case. As a published parameter, the workspace could then be cleanly integrated into a controlled complex job chain.Perhaps there are some under-the-hood complexities that I am unaware of that would prevent this type of functionality?
I'm trying to do the "right thing" and use the FeatureJoiner instead of the FeatureMerger where possible, however, there is a pattern which I commonly use which is not supported by the new FeatureJoiner.In the FeatureMerger I can specify hard-coded values for the joins, so I quite often join on "1" = "1" (the actual values don't matter, as long as they are the same). I do this to validate that one path of my workspace has produced a result, before continuing with the rest of the translation, or if I want to join all attributes from features in one translation path with all features from another path.The new FeatureJoiner requries me to specify an attribute for my join values so, in order to acheive the above, I would need to use an AttributeCreator to supply a dummy value to each translation path, before using the FeatureJoiner. This is possible but is an extra step that I don't need to do with the FeatureMerger.Please allow the FeatureJoiner join fields to specify a value, rather than requiring an attribute.
I have a couple of ideas for enhancements to NeighborFInder. I work in the telecom industry & need to get the pole number at the start & end of fiber line. With that in mind I have the following ideas as enhancements to NeighborFinder1) Modify it to reference Vertex (#) in a line feature2) Modify it to reference X/Y Coordinates from attributes in Line features3) Modify it to allow us to extract only selected features
For a long time, most major OGC WFS servers have supported stored queries: ArcGIS, Degree, GeoServer, MapServer. In many cases, for performance reasons, WFS servers will not let you query more than one feature type at a time unless you define how the 2 are to be joined. Because these joins are hard to define, one of the easiest approaches is to define the join within a stored query. For example - give me all the parcels and roads in the town of Spuzzum. The only way to execute a stored query from FME's WFS reader now is to include the stored query parameters on the initial dataset getCapabilities request url, for example: http://gisserver.domain.com:6080/arcgis/services/SampleWorldCities/MapServer/WFSServer?service=WFS&version=2.0.0&REQUEST=getFeature&TypeName=cities?tIndex=0&count=5&STOREDQUERY_ID=urn:StoredQueries:AttributeDemo&myrank=3 Any parameters you add to the wfs request url eventually get passed to the getFeature request. But this isnt very intuitive so it would be nice to have this added to the WFS parameters user interface. Heres a good link describing most basic types of stored queries that it would be good to be able to support: https://enterprise.arcgis.com/en/server/10.3/publish-services/linux/communicating-with-a-wfs-service-in-a-web-browser.htm
Vector Tiles are awesome, and are gaining traction quickly. It would be superb to support vector tiles as a streaming output from FME server. It would also be valuable to download all vector tiles in bulk, so users can choose to host the tiles themselves (e.g. behind a CDN).https://www.mapbox.com/vector-tiles/FYI GeoServer already supports MVT. https://2016.foss4g-na.org/session/vector-tiles-ge...The major web map frameworks already support MVTI've been told this relates to PR#45586
Give the AttributeValueMapper the ability to map more than 1 field at a time... go on... you know you want to! It'll save having to do this kind of thing:https://knowledge.safe.com/questions/71480/attributevaluemapper-equivalent-to-lookup-and-repl.htmlThank you...
It would be great if the Orientor could have an option that fixes the orientation of all faces of a solid so that they all orient one of outside or inside.
Hello,please, is it possible to add typical combobox to PDFPageFormatter transformer parameters, for "Page Width" and "Page Height"? I miss quite a lot the offer to choose width and height according to attribute value.I miss combobox for parameters Page Width and Page Height like that:Thank You so much!Lubo
If you have multiple attributes that you want to split the same way, e.g. by pipe or space, it would be useful to have an option in the AttributeSplitter to do this rather than having to insert multiple attribute splitters one after the other. You would specify the delimiter and then in a separate section all of your attributes - you could toggle which ones you want to split and give the list name for each one there and then.
Right now the Autodesk Civil 3D reader in FME 2018 doesn't support Assembly and Subassembly entities:AutoCAD Reader: Entity type of 'AeccDbAssembly' found, but not supported. Skipping entityAutoCAD Reader: Entity type of 'AeccDbSubassembly' found, but not supported. Skipping entityWorking with infra-BIM projects we often encounter these entities in Civil 3D data.
Now that map making is a lot easier with the mapnik transformer I think a map legend maker would be very useful, as well as templates, north arrows etc The ability to search through all the datasets used and auto create a legend would be brilliant.
Support connections to Civil 3D survey databases.This would be helpful for syncing attributes in a projects survey database with other databases. More specifically point data in survey databases.I know Autodesk added an api for survey in 2017 and they've upgraded the file type of the survey database in 2018. Project survey databases reside localy in the project directory and use data shortcuts in Civil 3D to connect the database to the projects drawings. The database is a Microsoft® SQL Server® Compact 3.5 database. New and converted survey database files for 2018 have the file extensions SDBX and SDXX.
Hi,I would love for the possibility to add multiple output ports on both python transformers.
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.
