Authoring

Hello!I recently upgraded to the new FME 2019.0 (yay!).This has had an interesting side-effect for running workspaces using the workspaceRunner for me. I have the following setup (I simplified the names for ease of explanation):Workspace 1 runs periodically and checks for changes in a datasetIt pushes the changes to workspace 2 using the workspaceRunnerWorkspace 2 receives a change, and it dynamically starts all workbenches within a folder (let's say 3 and 4)Workspace 2 starts workspace 3 and 4 using the SystemCaller, as it's near-impossible to use the workspaceRunner with a dynamic path AND parametersWorkspaces 3 and/or 4 start and do their workIn 2018.1 this worked fine, but since upgrading this setup has started spawning command line screens whenever a change occurs. This is royally annoying as it moves the focus from the screen I was working on, to these screens. They look like this:(These screens show the output for running FME from the command line).This only happens when

I am looking to see if there are ways to build your own custom translators in FME to convert precision agriculture machine data formats. For example, *.yld/*.fld files from Ag Leader, *.gsd/.gsy from John Deere to other outputs such as *.gdb, *.txt, etc.

hello,Currently i try to do a batch deploy an apply the same workbench on 89 file. When I use the "batch deploy", all the files are process but the files are saved under the same name which means that they are deleted as they go along, in the end I only have 1 file left instead of the 89 starting...The output file names are defined in relation to a number extracted from the input file name and stored in an attribute. I think that's where my concern comes from, but I don't know how to solve it.Example :Input files is name "trajectory0001.txt" and it have this constitution :In the FME I extract the filename and I keep the decimal part and I put it in new attribut (call "line").So I have these file in output.The output file is name 001.csv because I based the file name on the value of "line" attribut. My reader is may be wrongly defined so that it always takes the same file name but I'm not sure.I don't know how to solve my problem .

I am writing data to a JSON file to get it in proper JSON format for later use of a Web API using HTTPCaller.The "records" in the JSON file seems to be separated like this: "description" : "" } }, (is this CORRECT separation of JSON features?) { "json_featuretype" : "NewFeatureType", When reading the file later using FeatureReader, I get the expected number of "records". However, the resulting JSON textdata contains all the JSON data for all the records, every time a new record is read. This means, I get a lot of equal database records created in stead of individual records. Any ideas on how to get the right part of JSON data from each "reading"?

I am aware that 2018 FME added the ability to copy-paste between like transformers, however it does not appear that I am able to copy/paste between all like transformers. An example of where this functionality does npt exist is when trying to copy a row between an AttributeCreator and an Attribute Manager or AttributeRenamer and an Attribute Manager or vice-versa. Copying rows would be useful when cleaning up/simplifying my processes for efficiency gains.Digging into this a little bit, I found that when it comes to using conditional values for the new attributes I can for example copy the Conditional Values from the Attribute Creator... (See Edit note below)... While Conditional Values is positive functionality, in my opinion this is adding an unnecessary step, it should be simply.I have seen essentially this same Idea marked as Released so maybe I'm missing something? Is there another Idea floating around out there that did not get implemented yet?Examples of released Ideas includ

In FME2018 if a Workspace runner ran, then any inspectors would be shown in the Data Inspector. Here is an example of the FME2018 display where the Runner launches 3 target workspaces:The last tab presents the Workspace Runner's inspectors:In FME 2019, only the Workspace Runner inspectors generate a Data Inspector view:We use the Data Inspector views generated by target workspaces to spot check that objects at least lie within certain borders (e.g., county). I never realized the utility of this until it was gone.In the 2019 parcel runner. Below are more screen prints and log outputs.Cheers,PeteP.S. Dale saw this at the World Tour and told me to write it up...

I have a large polygon dataset on which I want to run an AreaOnAreaOverlayer. The transformer take a very long time to run because there are ~100,000 polygons and I don't have any way to group the polygons.It's occurred to me that I could enable parallel processing if I could group the polygons into subgroups that actually overlap each other. I can do this manually by lassoing the polygon groups by eye in ArcGIS and adding a unique value to a new field for each subgroup but I wondered if there was a clever way to automate this in FME?Below is the layer of polygons on which I want to run an AreaOnAreaOverlayer (I'm hoping to create a layer with no overlaps of all of the polygons intersected and attributed with a count of how many overlaps there are in each polygon)I imagine it will run faster if I can group them into layers that don't overlap at all, and then use that field in the "Group By" parameter. I'd be really grateful for any advice about any stage o

Hi, Having upgraded to FME Cloud 2019 I've noticed that when going to running a workbench, the auto-generated URL which used to be available in the advanced settings is no longer available. Has this moved elsewhere or has it been depreciated? Thanks

Hi all,My workspace is using the transformer FeatureWriter in SQL Server.I would like to recover the attribute Operador from my source data. The attribute Operador was simulated to be the transformer fme_basename.How can i extract it after the transformer?Attached my template file.ThanksDanilo de Lima

I'm running some jobs on the server than can take quite long. I use the REST api to get the status of the job, e.g. aborted, queued, in process, success... I also noticed a statusMessage field (e.g. "Translation was successful"). Can this be updated while running the script to provide more information for users?

I have lost the instructions for the FME Solar Powered plane. I was wondering if anyone had a copy of them as a pdf.

I have the following list as an example:Original list:mylist{0}.attr1 = a1mylist{0}.attr2 = a2mylist{0}.attr3 = a3mylist{1}.attr1 = b1mylist{1}.attr2 = b2mylist{1}.attr3 = b3mylist{2}.attr1 = c1mylist{2}.attr2 = c2mylist{2}.attr3 = c3mylist{3}.attr1 = d1mylist{3}.attr2 = d2mylist{3}.attr3 = d3mylist{4}.attr1 = e1mylist{4}.attr2 = e2mylist{4}.attr3 = e3 I want to regroup this list elements by recreating multiple lists by grouping the elements into 2 pairs while taking into account the previous element index as follows: New regrouping of elements:lstGroup1{0}.attr1 = a1lstGroup1{0}.attr2 = a2lstGroup1{0}.attr3 = a3lstGroup1{1}.attr1 = b1lstGroup1{1}.attr2 = b2lstGroup1{1}.attr3 = b3 lstGroup2{0}.attr1 = b1lstGroup2{0}.attr2 = b2lstGroup2{0}.attr3 = b3lstGroup2{1}.attr1 = c1lstGroup2{1}.attr2 = c2lstGroup2{1}.attr3 = c3 lstGroup3{0}.attr1 = c1lstGroup3{0}.attr2 = c2lstGroup3{0}.attr3 = c3lstGroup3{1}.attr1 = d1lstGroup3{1}.attr2 = d2lstGroup3{1}.attr3 = d3 lstGroup4{0}.attr1 = d1lstGroup4

Hello,I'm working on a project where we need to run a mean-shift algorithm on a very large raster dataset. We've been able to do it with the Orfeo Toolbox in QGIS, however we've had some pretty serious stability issues with QGIS itself, and therefore we would like to run the algorithm itself in FME Workbench instead. Does anyone know if it is possible to import the source code or a bat-file and run it as a transformer in FME? Or, does anyone know if there is a transformer that is capable of performing mean-shift algorithm on raster datasets?

I am looking for a way to close FME Workbench once a translation has completed. Is there an option somewhere for this, or possibly a shutdown script that could be used for this purpose?Ideally the solution would close only the current instance of FME Workbench, and leave other instances open.Thanks in advance

I need to change MicroStation Level names. I have tried using SchemeManager, AttributeManager and AttributeRenamer. All of which I can use a csv file to indicate which is the source and which is the destination level names. none of the transformers work. The output always writes the source level names not the destination level names.

I am stock…I am sure this is super simple but, I can seem to find an easy solution.I have two feature classes, one consist of 522 circles the other is a series of points (over 25000) of them. The points are in the circles and some of the circles overlap each other. Therefore, some points are in many circles…What I am trying to do here is to combine the attributes from the points to the attributes of the circles they intersect.The featureMerger does not work has the only relation between my two features are their location. I thought I solved it with PointOnArea but it only tell me how many point are in the circle…

Our jobs pull from APIs with ever changing results. The caches WILL change. But FME 2019 won't let me re-run with feature caching on thinking that the data will be the same. It won't.

Hello, I've come across the following error when validating AWS credentials for S3 Bucket Modified Trigger in automation: Not able to determine region for ca-central-1.Please upgrade to a newer version of the SDK: I can work with this path and bucket (download and upload from/to this path) in FME Desktop as well as run my workspace through FME Server (FME Cloud in this case), but having issues setting up a trigger to run the workspace when bucket changes.Has anyone had similar issue?Thank you.

Hi I am working with a workspace where I want to us the output of one transformer and use it as in input in many areas in my work space.Is there a "transformer" that allows you to "transport" your features across the desktop rather than having many lines all over the desktop. This way I can keep the workspace neater.

I published a project to FME Server and am utilizing the 'Workspace Sharing' function so that Users do not have to authenticate for this particular project. When they click the Sharing Link, the screen display 'FME SERVER' at the top. Is it possible to modify the 'branding / splash page' to utilize our utility name and logo to ensure the employees that they are within a secure trusted internal site??

I have a disabled inspector connected to a <rejected> port. When I run it without feature caching enabled the whole fmw runs successfully. When I run it with feature caching enabled it fails:2019-04-09 11:10:25| 893.2| 0.0|ERROR |PointOnAreaOverlayer_15_<Rejected> (TeeFactory): PointOnAreaOverlayer_7_<Rejected>: Termination Message: 'PointOnAreaOverlayer_7 output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Translation > 'Rejected Feature Handling' to 'Continue Translation''2019-04-09 11:10:26| 894.7| 1.5|ERROR |PointOnAreaOverlayer_15_<Rejected>: Termination Message: 'PointOnAreaOverlayer_7 output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Translation > 'Rejected Feature Handling' to 'Continue Translation''2019-04-09 11:10:27| 895.9| 1.2|ERROR |FeatureJ

Hello FME community,I have a fairly complex series of workspaces that dynamically harvest, validate and write featuretypes. We harvest using WFS and online GML.I have an issue where in FME Desktop (2018.1.2-b18590) the FeatureReader reads both the schema and the features, but in FME Server (2019.0-b19238) it doesn't create a schema feature in the gml FeatureReader, so when I want to dynamically write to my database it doesnt recieve a schema feature.The XSD and the GML are findable and downloadable by FME Server. The steps to reproduce this behaviour is to run it in Desktop, publish it FME Server.See attached an isolated Workspace to show my problem with the logfile saying in FME Server: 103 INFO Merged 0 schema features read from 1 datasets into 0 resulting feature types104 WARN UniversalReader -- readSchema resulted in 0 schema features being returned105 WARN Reader Parameter(0) = >https://geotest.drenthe.nl/website/ngr/am.xml168 WARN Reader Directive(..)176 WARN UniversalReader -

I combine 3 to 6 smaller 3in tif aerials to create a PRM grid we use. They look great when viewed in ArcvIew, Autocad, Photo Viewer but in GTechnology they are horible with strips. The raw 3in look great in Gtechnology by themselfs but not combined? We had 6in raw tif but those combine work prefectly in Gtechnology so I can confused since there is not much to change.

I have the following workflow:1. SDE reader reads the polygon feature which will be used for clipping feature types;2. FEATURE_TYPES public parameter is fetched. It lists what feature types to read;3. A few Testers and FeatureReaders is used (depending how many layers are in the DB):If FEATURE_TYPES contains FeatureX When FeatureReader is initiated to read only what FeatureX;4. All features read are passed on to the Clippee, etc. Is there any better workflow which reduces Testers and FeatureReaders to be used? I tried using one FeatureReader and query the feature types to read, but FeatureReader always reads all the features and passes only the ones, what are queried. This is not good, considering the different DB features have millions objects and reading all of them is time consuming.So if DB contains, for exmaple 60 layers, I need to use 60 Testers and 60 FeatureReaders. It's insane. 

How is it possible to retriew more information in the RESULT DATA window on fme server? I currently only get "FME_FAILURE" and "A fatal error has occured. Check the logfile above for more details." I would like for the message from the terminator to be wieved here. When a job terminates on the server, it does not passes the Termination Message on to the statusMessageattribute from the job result. I am using version 2017.1 17725 WIN 64 on both server and workbench.