FME Form

XML to excel convert- how to convert below xml file in excel?All attributes should be populate in single row with separate columns<PlaceList><Place><LocationList><Location type="MAIN"><Address><ParsedList><Parsed languageCode="en-GB"><CountryCode>IND</CountryCode><PostalCode>303805</PostalCode><Admin><AdminLevel><Level2>Rajasthan</Level2><Level3>Jaipur</Level3><Level4>Amber</Level4></AdminLevel></Admin></Parsed><Parsed languageCode="hi-Latn" languageType="TRANSLITERATION"><CountryCode>IND</CountryCode><PostalCode>303805</PostalCode><Admin><AdminLevel><Level2>Rajasthan</Level2><Level3>Jayapur</Level3><Level4>Ambar</Level4></AdminLevel></Admin></Parsed><Parsed languageCode="hi"><CountryCode>IND</Coun

I have a workspace that creates .png (image) files based on business needs. I'd like to send one email with the png files attached. The problem is, the name and number of the png files will vary with each run.  Currently, I have one aggregate feature with the paths of each png file stored in a list. This one feature is being fed into the emailer to trigger the send of one email.  How can I configure the feature coming into the emailer transformer, and the emailer attachments section, to send the png files regardless of how many there are? Thanks!

Hi all,I need to connect to a linked server in my SQL Server. Is there a method of connecting to a Server Object using FME?Alternatively I have a query that collects my data but running it through the SQLCreator doesn't produce any attribution (presumably because FME doesn't natively connect to the data).ThanksNeil

I am trying to drop features in the PythonCaller (see below my code). I manage to delete attributes and geometry in the last else statment, but for some reason the feature itself is not deleted. The number of features in the input and output is namely the same, while the geometry is gone (Look at the image below)  . I just find it interesting to see that the features without geometry are still kept. Does anyone know how I can drop the features in the Pythoncaller in the else statement when I am removing the redundant geometry?import fmeobjects def processFeature(feature):         lstAttributes = feature.getAllAttributeNames()        testList:=['B-OI-KL_ET_MS_KABELBED-G']         for lvl in lstAttributes:            if lvl == 'igds_level_name':                levelName = feature.getAttribute(lvl)                if levelName in testList:                    print(levelName)                    #print(levelName)                    for attr in lstAttributes:                         if len(at

Hi! Is there any way to set up a XYZ Tile background such as https://tile.openstreetmap.org/{z}/{x}/{y}.png (works fine in QGIS) into the FME Data Inspector?I suppose this type of service doesn't work like a WMTS service. Thanks for your clarifications! Best regards, Olivier

Now I'm suffering from keeping the attributes with the same schema. My workspace is quite simple, just reading IFC and writing IFC. I only need to remove some fearture types. So I think it's not necessary to do some touchups. And I'm trying to change some reader/writer parameters to solve the problem. Unfortunately, it doesn't work.From the IFC reader, we can see some IFC attributes which are regarded as geometry traits (IFMENull).After running the workspace, I found the all the IFMEAggregate with named "IFCPropertySet" were disappeared. Originally, there are 15 IFMEAggregates, including "Part 0:IMEAggregate (18 Parts)", Part 1 which is IfcMaterial, and Part 2 to Part 14 which are IfcPropertySet. After running the workspace, only 18 Parts are kept from original "Part 0:IFMEAggregate (18 Parts)" and its level is going up to the top.I'm not sure whether it's related to the setting of Representation Contexts. Does anyone have any idea?

Hi all, I'm running into an issue when trying to INSERT & TRUNCATE an existing ArcGIS Portal feature layer via an FME writer. The error message I am receiving can be seen below: ArcGIS Portal Feature Service Writer: Encountered an unexpected error. The error code from the server was '500' and the message was: 'Cannot perform operation. Invalid operation parameters.'. Details: '' I've read through a couple of older posts about this issue and followed the suggested fixes, but these don't seem to help in my case - fixes include checking there isn't a mismatch in schemas, and reducing the 'Feature Per Request' in the writer settings. To see if there was an issue with updating more complex feature layers, I have tested with a simple feature layer and still having the same error message. This polygon feature layer (3x rows, 1x string field) was published from ArcGIS Pro to Portal and can be read into FME with no issue, but the same error oc

Similar question is already asked here Does any one has migrated data or know how to migrate data into raster data type into ESRI feature class. Screenshot attached for better understanding...

Only the latest version of Proj (version 9.x) supports transformation (3D -heights!) between the norwegian Nautical Sea Chart Zero (EPSG:9672 and EPSG:9883) and NN2000 (EPSG:5941, EPSG:5942, EPSG:5973 etc.), but also between Nautical Chart Zero and ellipsoidal heights. This does provide a number of advantages, including the possibility of seamless transformation of z-values between sea and land data in Norway. (E.g. from EPSG:5973 to EPSG:9883) FME currently uses PROJ version 7 in the PROJReprosjector- Are there any plans to upgrade to version 9? Do you have any other suggestions on how to transform data in FME from EPSG:5973 to EPSG:9883? Thank you.

Is there a way to write a new line in an excel cell?

After transforming some bands of a raster (CSAR) in the Rasterexpressionevaluator, they are renamed to the same name (3bands get the same name) but I would like them to keep the original name. I think this is an error in the Rasterexpressionevaluator. In order to set the bandnames to their original name, I have tried the rasterbandnamesetter but it does not work as the bandnames are no attributes. The transformer does not seem able to reach the bands stored in the IFMERaster object. How to rename these bandnames ?  Thank you!

Hi all, In the last few days we've set many small steps leading up to the problem we now have. We have polygons, where one attribute of each polygon is a list of bird species, which occur in that area. This list is of course different for all polygons, the polygon-specific list. We also have a list of bird species which should occur in that area. This list is the same for all polygons (in this subset), the general list. Now, we would like to compare the list of each polygon, with the list for all polygons. We have tried many transformers, and our last option (at the moment) is the PythonCaller, where we hardcode the second list as a set, and compare it with the polygon-specific list, converted to a set. We group by the id of the polygon, because we want to compare each polygon-specific list to the general list. This is our Python-code:import fmeimport fmeobjects x = {'item 1','item 2','item 3'} class FeatureProcessor(object):    def __init__(self):        self.feature_list = []        

I am trying to update a shp file in Arconline with new data. I am trying to replace the data which is the same and add new data that may have been added. I am using truncate and " update "in the ESRI AGOL writer to make sure this happens. But I run into this error when running this "ArcGIS Online Feature Service Writer: Encountered a feature for feature type 'WatercourseLink_Clip_test' that is missing the ID attribute 'OBJECTID'. This attribute is requiredARCGISONLINEFEATURES writer: A fatal error has occurred. Check the logfile above for detailsClipper_INSIDE_-1_17_Player (RecorderFactory): ARCGISONLINEFEATURES writer: A fatal error has occurred. Check the logfile above for details" But as far as I can tell both the source data which is being uploaded to update the exisiting data and the exisiting data in AGOL both already have ObjectID's. Any help would be greatly appreciated as I think im missing something quite simple here 

This is my JSON file. I want to insert, in "structure_ids" array, the value 79538. Maybe the problem is my value, I can't write it like that. Thanks for your help 

I have created a workbench on my desktop that will be running each night on a server. Both my machine and the server is using Windows-1252.The workbench run fine on my desktop but on the server i get the error POSTGIS writer: Internal Error: Failed to copy attribute 'NØYAKTIGHET' to 'nã˜yaktighet'I dont have any encoding issues on my desktop which make me wonder if the translation fail due to this. I cannot see any other reasons why this would fail?The server is running 2022.1.2.0 (20220831 - Build 22627 - WIN64)The desktop is 2021.1.0.0 (20210630 - Build 21607 - WIN32)Both are using the same locale as far as i can see. Any ideas how i can fix this? My first try will be to install 2022 version on my desktop, but I doubt that would make any difference.     

Hi!I am familiar with the consept of reading IFC and writing IFC in FME. I also have successfully created a workspace that can read various geometry formats and write to IFC with custom propertysets. Now I'm trying to create a workspace that can read IFC, modify or add propertysets and write back to IFC without breaking the structure of the IFC file. For example, I have a IFC with slabs. I want to add some propertysets to the slabs and write it back to slabs. I have seen the example where you can modify properties for spaces, but I'm having problems applying the workflows to IFC. All in all I think FME has potential for improvement in handling IFC-files in an intuitive way. Does anyone have any good examples of workflows for the described purpose that can be shared?

Coordinate system setter is in the workspace, so I can select local coordinate, but I want to add offset value in somewhere in the workspace. Please kindly let me know how to add off set value (Latitude shift, Longitude shift, and height shift). Thank you.

I’m using FME 2020.2 (FME(R) 2020.2.0.0 (20201027 - Build 20787 - WIN64)) and I have ArcGIS Pro 2.6 and ArcGIS Desktop 10.4 (with 64 bit background geo-processing) installed. I have a File Geodatabase (FGDB) that FME is unable to read.  The error I'm getting is : “It could have failed to open because it contains ArcGIS Pro-only features, for example Arcade expressions. If this is the case, please install ArcGIS Pro-compatible ArcGIS Sever and 64-bit FME." This FGDB contains a relatively new ESRI field type called contingent values on a feature class.  ESRI notes this makes the FGDB incompatible with ArcMap and releases prior to ArcGIS Pro 2.3 and ArcGIS Enterprise 10.7.x. It appears that FME is defaulting to using the ArcGIS Desktop libraries rather than the newer ArcGIS Pro libraries when both application are installed. The only work around I have identified at this time is uninstalling ArcGIS Desktop.  Once I do this FME will read the File Geodatabase without any errors

Like described in the header, In short I'm wondering what the default (X,Y) coordinate order conventions are in FME (particularly in relation to the 'Lat/Long vs Long/Lat discussion')? Reason/motivation of the questionThe reason I'm asking is that in quite some workspaces I prompt users to enter an extent for a particular area (mainly to filter out data for the user defined area). Recently a user asked me if it was possible to incorporate an option to also allow the input extent to be entered by means of explicit Bounding Box (BBOX) coordinates in the form of a specific envelope, i.e. to enter both the (Xmin, Ymin) AND the (Xmax, Ymax) coordinates.Of course these explicit coordinates are meaningless without knowing how to interpret them (i.e. without knowing the underlying coordinate system). In the Netherlands it turns out that the vast majority of spatial files make use of the 'RDNew coordinate system' (EPSG:28992). However, I also wanted to give users the opt

I would like to get the predominant line for each polygon. I have tried using the 'CenterlineReplacer' but that doesn't work well since a lot of these shapes aren't long and narrow areas.  I only need one line per polygon, but it needs to be straight. The length of the line doesn't matter. I'm interested in the direction. Does anyone have an idea about how I can approach this task? 

Trying to remove the editor tracking fields. I can, run to, in Attribute manager and see the fields removed but in the File GDB preview, I still see them.

Hi I am trying to uninstall FME (2020.002) using Windows Add/Remove Programs. However, it just hangs on 'Gathering Information'. This is the second time I have tried - first time I left it for 24hours and no progress. Anyone go any ideas how I can remove it completely?

I am receiving this error below when I try to retrieve the getJSON variable:Python Exception <Exception>: Unable to update feature service layer definition.Object reference not set to an instance of an object.(Error Code: 400)Error encountered while calling function `processFeature'PythonCaller_3 (PythonFactory): PythonFactory failed to process featurePythonCaller_3 (PythonFactory): A fatal error has occurred. Check the logfile above for detailsA fatal error has occurred. Check the logfile above for detailsJSONFormatter (JSONFormatterFactory):This is the code in PythonCaller (simplified for readability):import fmeimport fmeobjectsfrom arcgis.gis import GIS def processFeature(feature):   getJSON = feature.getAttribute('JSON')   gis = GIS(profile='username')    lyr = gis.content.get('item_id').layers   for lyr in gis.content.get('item_id').layers:      lyr.manager.update_definition(getJSON)I know getJSON is giving me issues because if I replace lyr.manager.update_definition(getJSON

Custom format of version 2017.x (32-bit) not working when saved with 2022.1 (64-bit) version. Enclosed the custom format of version 2017.x for your reference. Above screenshot shows the v2017 custom format when consumed as Workspace Resource in FME Desktop v2022.1. Above screenshot shows the v2022.1 custom format (same old v2017 custom format opened and saved in FME Desktop v2022.1) when consumed as Workspace Resource in FME Desktop v2022.1.