Authoring

Hello, I have a field in a database where KML's are uploaded and stored in Base64. Is there a way to export those and convert them to KML within FME? My end goal was to convert to KML, then covert them to shapefile for a Portal Layer. For example attached is one of the files encoded that I confirmed is a KML by manually decoding it outside of FME. I tried the BinaryDecoder transformer, but I wasn't sure what to do with the result. 

Last week we upgraded FME Server to 2020.1. Since then our Data Streaming and Job Submitter Services as applied via webhooks don't work anymore. The log files indicate some AccessDenied-problems.localhost_access_log: Post call receiveddatastreaming and jobsubmitterservice logs: request received. Fatal error: Service failed: java.nio.file.AccessDeniedException: E:\\FMEServerData\\resources\\system\\temp\\requestdata\\1710266074152417324FME Server runs on a service account with admin rights to all of the server.How to solve this?

I've got a bunch of AGOL Feature Layer (hosted) created with different schemas and I'm combining them into One AGOL Feature Layer (hosted). I can see the AGOL READ is seeing the "Photo Attachments", I can fix schema/attribute variations but "Photo Attachments" are not moving across the New Feature Layer.

I have a fairly complex workspace that does a few different things. Is there a way that I can select a transformer and copy all its dependencies as well? It's able to do a similar thing when we run the left green arrow in feature cache mode. It'd be great to see an ability to select and copy the objects as well if we want to pull it out into a separate workspace.

This morning I stumbled upon the Recorder and Player. After reading the documentation I was really eager to try them out in a workspace for storing temporary files. We also tested the performance by comparing with a FeatureReader / FeatureWriter and we didn't find any big differences when the compression-level of the Recorder was low. However when increasing the compression level, the performance was increasingly worse with the Recorder in comparison with the FeatureWriter. Is the only advantage of the Recorder in stead of the FeatureWriter that it can compress the data? When do you use the one or the other?Thanks for your thoughts!

What should I do if I have an idea for improving FME? Previously I sent these to FME's support team and they filed it in their internal tracking system, but I never knew if others had the same ideas or maybe even some alternative ideas and approaches. I really wish I could see what everyone else thinks. Is there a better way?

Hi I have a table containing 2 columns StartPt and EndPt [see attached]. I would like to find all the connected nodes for each StartPt in the table. For example, the connected nodes for Startpts 107224 and 100561 are: StartPt EndPt107224 100561107224 101420107224 107197107224 107196100561 101420100561 107197100561 107196100561 103058 Any suggestion how this can be achieved in FME. Alternatively, I could look at doing this via a stored procedure. 

I have some difficulty with using Feature Writer and Oracle Spatial in FME version 2020.2. My workbench reads from a Shapefile and then I'm using Feature Writer to write the features into Oracle for which I then want to trigger another process. The format I am using is Oracle Spatial Object. The problem is that the Feature Writer will not write the geometry to the records, so I end up with a table with a blank geometry column. I've carried out some investigations to narrow the source of the problem. If I choose Geopackage (instead of Oracle) the geometry is written. If use the standard Oracle Spatial writer with same connection then the geometry isalso written. What am I doing wrong for the Feature Writer to behave like this or is there a bug? Is there a work around?

I can connect everything up but I get an error when I use either the Column Match or the Where clause options. I am not trying to update the geometry at all just hyperlinks to documents. Thanks ===========================================================================FileGDB Writer: The `LMS_PERMITS_KEY' attribute could not be written. The containing feature has been dropped+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Feature Type: `Lands/IPCoROW'Attribute(encoded: UTF-8)  : `DOCLINK' has value `HTTPS://GISAPPS/GIS/LANDS_DOCS/TTLSE/51368,111-63345/120-V1-120-V1-587291 T3NR2W SEC 8.PDF'Attribute(string)      : `Easement_Key' has value `45031'Attribute(encoded: UTF-8)  : `HISTDOC1' has value `HTTPS://GISAPPS/GIS/LANDS_DOCS/EASEMENTS/111DISTRIBUTION/587291 T3NR2W SEC 8.PDF'Attribute(string)      : `filegdb_type' has value `geodb_no_geom'

I want to make an Automation where the flow goes first trough an workspace which reads data from an database. Depending on the feature type it then goes to different Automation Writers. Each of these ports are then connected to its own workspace so it can be run parallel. Eventually they merge back to another workspace which writes back the data to the database. The problem I have now is that thousands of features reach the Automation Writer thus kicking of the next workspace thousands of time. Obviously that is not what I want. What is best practice to collect and group these features and pass them on as one feature. I tried using the Aggregator Transformer and adding the parameters to a list, but it seems that it is not supported by GeoJSON. I use FME Server 2020.2

Simple task of applying attributes from a polygon onto points.Whats faster - Spatial Relator or Point On Area Overlayer?Let me know brains trust.

Has anybody tried reading data from a PI Historian database with FME?I know it has both ODBC and JDBC connection options.If so, could you share some knowledge?Thanks, Erik Jan

I cannot get the ExcelWriter to use the ExcelStyler's formatting. I have found a demo worksheet in another question which works fine. I have deleted the writer and replaced it with my own (I think identical) writer, but it's not working and I have no idea why! I have attached both worksheets. If someone could point out the difference between the two I would be very grateful. I've tried a diff checker against the XML code in the files, but nothing is jumping out at me.

A question about how FME handles multiple spatial columns in the same record in an oracle spatial table. So say I have a table with 2 spatial columns, SHAPE and SHAPE_PT So, Oracle spatial Reader, If i leave it with the Parameter to Handle Multiple Spatial columns to No, when I run it, it will log choosing SHAPE to hold geometry at runtime. If I use a SQLExecutor using Oracle Spatial Object type, and I run it, at runtime, it will log choosing SHAPE_pt to hold geometry at runtime. So 2 questions: 1- if I leave the reader to Handle Multiple Spatial columns to No, can I always be sure it will always pick the SHAPE column and not the SHAPE_PT ? 2 - In the SQLTransfomer, I do not see any option to handle Multiple Spatial Columns, is that option there someplace and I am nto just seeing it? Is there a way to tell it to use one geometry column vs the other ?   

Is there a way to write a tables schema and data type out to a text file?

Hello,I am publishing workspace to Data Download service. I would like to edit the path in the resulting ZIP file, according to this article: https://community.safe.com/s/question/0D54Q000080hM9QSAU/how-can-i-change-the-folder-structure-returned-in-the-zip-file-from-fme-servers-data-download-service?t=1612527866370It works when I upload the workspace from Desktop 2019.1 to Server 2019.1. But it is not working when I upload from Desktop 2020.2.2 to Server 2020.2.2.  In zip there are still "default" paths like CSV_1 or TXT_1 folders. I want there no path, just result files directly inside the zip file. I tried to upload from Desktop 2019.1 to the latest Server, but it did not help.I tried to restart Desktop, put there new wri

Hi : We are trying to use the fmelicensingassistant_cmd utility to check for FME Desktop license counts prior to running some of our scripts that launches (fme.exe). Without doing this pre step, we end up triggering a very unfriendly error when no licenses are available, and users would think the system is broken. From my testing so far, it seems the utility is always returning 1 more license being used than actuals. (as compared to running the LMTOOLS on the licensing server) And, if all licenses are actually in use, the utility will take roughly a minute to respond, at which point it will still, report that all licenses are in use. Neither is desirable and this behavior prevents us from actually determining available licenses. Is there anything I am doing wrong?  By the way the specific license type we are looking at is the Smallworld license.This is the command I'm running:fmelicensingassistant_cmd.exe --query <

Is it possible to expose fme_basename on schema features, when reading in just a schema using a FeatureReader? I've tried exposing it on the reader parameters for an excel file, but it does not come through. Adding an AttributeExposer reports it as missing.Thanks

I use FME 2020.1.3.What I want to do is to use a FeatureReader to read a PostGIS DB depending on created attributes ( usual generic approach) and to write them to an other PostGIS DB with an FeatureWriter, using Published Parameters to define the destination. As I use the generic port as outpur from the FeatureReader, the data loses its data-type information. I know, that those informations are given through the Schema port of the FeatureReader and that there is a way to merge them again to the data.I found serveral post about this topic (https://community.safe.com/s/question/0D54Q000080hbiSSAQ/generic-attribu

I know how to use ListConcatenator in order to concatenate all list values into a single attribute. However, what can I do if my feature has multiple list attributes? I want to concatenate all values of all lists into respective single attributes. The resulting single attributes should have the names of the original list. I don' know the names of the lists in advance.Examples:colour{0} = 2 colour{1} = 3 colour{2} = 2single attribute colour = 2,3,2shape{0} = triangle shape{1} = square shape{2} = circlesingle attribute shape = triangle,square,circleThanks for any help

Hi All, I tend to use the workspace description parameter to track my overall changes and updates to the workbenches I create. This is handy for me to have a way to track things within the workbench itself, without having to keep notes elsewhere on what i've done. However, it's not exactly easily "user facing" for the others in my organization. I'd like to be able to pull the overview, help and history from the workspace parameters in order to have them exported out alongside the reports that i'm generating if possible. I don't see them stored as standard parameters that FME can fetch in something like ParameterFetcher. Perhaps this information is accessible in the FME python API somehow?

This is my initial data:Name,Value sza034,ber_afu sza033,ber_awn sza034,ber_afl sza033,ber_afu sza034,ber_afu sza032,ber_awn sza034,ber_afl sza033,ber_fff sza033,ber_bgt sza033,ber_afu sza033,ber_jijThe result has to be a matrix, with a row for each unique name and a column for each unique value.the fields in the matrix have to be filled with "yes" or "no":Name,gschber_afl,gschber_afu,gschber_awn,gschber_fff,gschber_bgt,gschber_jij sza034,yes,yes,no,no,no,no sza033,no,yes,yes,yes,yes,yes sza032,no,no,yes,no,no,noBy using the Aggregator, AttributeSplitter, ListDuplicateRemover and ListSorter, I managed to get for each name a list with its unique values. But how can I write this matrix now?Thanks in advance.Vera

Hi All, I'm trying to create a series of basic maps to illustrate address points which are broken into clusters. The cluster size range from 16 to 600, some clusters are beside each other in built-up-areas.  When processing each cluster it seems the extent(or boundbox) of each map clips layer data in overlapping areas. Can anyone suggest what i may be doing wrong? or another approach. Many thanksKieran  

I am using a FeatureReader to read a Postgres db table. As I want the workspace to be easily migrated from developement to production system, I use Published Parameters to supply the connection parameters, meaning I use a parameter committing the name of a FME-DB-Connection and two parameters (Published_Parameter_Schema.Published_Parameter_Table) for the Feature Types to Read. Unfortunately, no output is generated from the generic port (no error message in the transition log), even if I expose the attribute within the FeatureReader or with an AttributeExposer afterwards.As a workaround, I use a AttributeCreator to commit the Published Parameters for the schema and the table into attributes before using them as input for the FeatureReader. With exposing the attributes from the Postgres-DB inside the Transformer, this works fine. But I keep wondering, why it doesn't work using Published Parameters directly? 

Having an issue using a FeatureWriter with the following parameters (see screenshot):Feature Operation = fme_db_operationTable Handling = Use ExistingUpdate Spatial Column(s): NoRow Selection = WHERE clause  I have features coming into the FeatureWriter that are both fme_db_operation INSERT and UPDATE (see 2nd screenshot). My understanding of the Update Spatial Column(s) parameter is based on the help that states "Update Spatial Column(s) is a writer format parameter that is in effect only when the feature operation for a feature is Update".   However, with this set to No, my Inserts don't get geometry (writing to ArcSDE)