Using transformers to modify data.
Recently active
Hi all.I'm using a dynamic writer to output a series of features as tables in an SQL Server database, adding a fixed schema name in the "Table Qualifier" parameter.However, FME completely ignores this setting, and outputs all features to the default "dbo" schema.I've then tried to add it to the "Table Name" parameter (with "fme_feature_type_name" in "Schema Definition Name"), but then it just errs because the data features "fme_feature_type" now contains my added schema.Is this really WAD ?Why doesn't the dynamic writer accept and use the setting in "Table Qualifier" ??
For example:In the parameters dialog of the writer-plugin a file was chosen from the hard disc and the filename is availiable in the parameters list.Now if we add the FeatureTypeImporter in the FME via Writers - Import Feature Types ... and select in the Format: field the FeatureTypeImporter we want to have this file displayed in the Dataset: field.The Dataset field is defined in the fmf file of the FeatureTypeImporter and a default value is set there.There also exists a parameter in the writer fmf file for this file.
Hello, I have an FME Server Workspace that uses a Python Caller to write custom EXIF tags to a JPG. I want these images to be provided directly to the user via data streaming. The only way I have found to accomplish this so far is to pass the image path to a filecopy writer. This works OK - It will display the image, and if saved - it will retain the custom EXIF tags - however, when saving the image - it wants to save it as the .fmw workbench name (and .fmw as the filetype). Does anyone have any suggestions to get around this? It seems that the mime-type isn't coming across using the data streaming. FYI - I have tried a JPG writer at the end (feature reader - feature writer), but this cuts out the custom EXIF tags.
Hello, I’ve used FME Desktop in the past to convert a planning applications shp (points) file to a csv file for use in PowerBI. To get data working in PowerBI certain set fields need to exist (in the output csv) that are not in the planning apps shp file: Name, Icon and Color (sic). This is where Name is typically the main reference value in the dataset (e.g.: the site name or an planning ID), Icon is the name of the icon type to be used in PowerBI (e.g.: hexagon-thick) and Color is the colour PowerBI uses for the icon (e.g.: #8B0000). So, when creating this output csv for use in PowerBI I read in the shp, connected to a AttributeReprojector to convert to LL-WGS84 (because the source shp was in EPSG:27700 and PowerBI requires LL-WGS84). I then connected to an AttributeManager where I 1) renamed the Planning application number field to 'Name', 2) added a new field called 'Icon' (with the value of ‘hexagon-thick’ for all records, 3) added a new field called 'Color'
Is it possible to read all layer names from a DWG source file? By all I also mean the layers which do not have any features on them. For example, if I have a DWG file with the following layers and numbers of features on them:L_01 (with 10 features)L_02 (without any feature)L_03 (with 1 feature)L_04 (without any feature)I want to somehow get access to all the layer names, i.e. L_01, L_02, L_03, and L_04 in FME, even though L_02 and L_04 do not have any features. Alternatively, is there a way to convert a DWG file to a DXF file such that all layers are preserved (i.e. , again, also those that do not have any features on them)?
I would like to import Autocad(.Dwg) file data into an Azure SQL table.In this table, I have the field GDB_GEOMATTR_DATA wich is populate by ESRI (Arcgis Pro) to store complex geometries. How can I populate such GDB_GEOMATTR_DATA field with FME? I tried to use the geometryExtractor transformer but it's not working. @Takashi Iijima, @jdh, @Hans van der Maarel and others, any thoughts? Thanks,
Hello , i am using GDB writer to write my output as GDB .but I have found most of times ,it create a folder that contain different files but when I view the output of writer again in FME ,I got no data to read .but for the same canvas ,when I use writer Esri shape File ,it save well and when I view the shape file output again in FME ,I found the data .it works great with shape file but GDB not at all . what is the solution to save my output as GDB ? Do there some restrictions should I look before writing my data into GDB? FME Desktop professional 2021
I am new to FME and am having trouble with a CADRG exporter. I need to limit the number of colors to 216 on the export however FME exports at 217 rendering the image all black on avionics software.
Hello community!I have 4 point clouds that I would like to aggregate. By aggregating the clouds with the "point cloud combiner" I lose the color information, why?
Hi altruist, I have a very large datasets of daily records of soil moisture data which a FME workspace is getting failed to process. So, I have broken down by Financial Year by using testFilter and intend to produce average SM value by FY (as you can see in the image). Now I have to use a series of other transformers on each of the FY output that need to be repeated for each FY output port. Can anyone suggest which process would do it faster so that I can do like a batch process for each FY without manually changing the trigger etc? Looking for kind response.
Hi,I've got a problem with the ListExploder. I am trying to divide a well-formed XML based on a XML-tag. This itself works fine, but the problem is, that all Object, wich get rejected lose there geometry information. I can see it in the DataInspector, the Min and Max Extent shows "nan". Leaving out the ListExploder, the geometry is visualized, so it seems clear, that the objects loose their information at the <Rejected>-Output-Port of the ListExploder.This problem appears since we installed FME Desktop 2022.2. I tried the same workflow with an older version (2020.1.3.0) and there it works as expected. I put on a screenshot to clarify the situation in FME 2022.Does anyone know about this problem? Any solution would be helpful. Thanks in advance and greetings,André
Hello, I have a feature class from an geodatabase that contains larger and smaller features that overlap one another. I sort these features to have the larger features come before the smaller features. The attributes of the feature class are: Id and date The goal is to union the smaller and larger overlapping features, but only keep the attributes of the larger overlapping features. Since there is one feature class the overlapping areas share the same attribute names. Therefore, I use the AreaOnAreaOverlayer transformer, with accumulation mode set to Use Attributes From One Feature. However, I am unsure of the behavior of Use Attributes From One Feature accumulation mode. Which attributes are copied over to the resultant feature when the overlapping features are unioned? The document mentions the following for the Use Attributes From One Feature accumulation mode: "Takes all attributes from one representative feature" How does the AreaOnAreaOverlayer determine which of the
Workflow description· FMEServerJobSubmitter Version 3 in Desktop starts a sub-script with for instance published parameter /GeoBIM/Konfiguration styrfil· If I run the script FME Server runs the script with parameter /GeoBIM/Konfiguration, styrfil So as you can see there has been input a comma sign which is not correct· And furthermore - if I try to change the FMEServerJobSubmitter Version 3 published parameter the transformer automatically (without me telling it to update) updates itself to FMEServerJobSubmitter Version 4 leading to:· When I then try to run the script with FMEServerJobSubmitter Version 4 it ends up in Rejected with error ERROR_INVALID_INPUT_PARAMETERS and Reason - invalid input parameters for workspace X'Hence I will now create a library with FMEServerJobSubmitter Version 3 preset transformers in version 2021.2.4 (where editing parameters works fine) so that I can copy these into our scripts in 2022.2 to make this work I'm surprised
I'm not sure what I'm doing wrong, but I'm trying to move data from a editing GDB environment to a production GDB. Everything else works fine, except when it comes to importing the relationship class for my attachments. I get the error: "Unable to create table/feature class/relationship class of type 'geodb_invalid'. Creation of this type is not currently supported by FME, and must be done through Esri tools" Does this mean I can't import the relationship in FME and should be doing it in ArcGIS Pro? Thank you.
Line:01020000A0E610000005000000E040A17B843554C0C987F51E7593414000000000000000006CDB4900853554C0AFD3A0F17893414000000000000000002D2683FB813554C0D677B1BD8E93414000000000000000005A484B8E7F3554C025457646AB9341400000000000000000C4B449797B3554C01A0A32C8AC9341400000000000000000 Using SQL the wkt converts to these 5 points: -80.83621111628918 35.15201174725332 0,-80.83624274456605 35.15212841370464 0,-80.83605850036174 35.1527936092895 0,-80.83591039039439 35.15366440558345 0,-80.83566124151099 35.15371038859685 0 Lat and long are also reversed in the output. I would like to do this conversion in FME for spatial analysis of the full data base. Thank you,Matt
I have this equation in Excel:=A2-($A$2-$G$2)*B4/SUM($B$4:$F$4)this A2 and B4 has to change every row. so that the value I just got from the current row calculation needs to be used in the next step.9.83,8.82,7.56,6.41,5.41,5minus0,1.01,1.26,1.14,0.99,0.4it starts with 9.83-0, then 9.83-1.01, then the result which is 8.81-1.26 and so on.how can I write this equation? or how can I get the result of previous row calculation in the current row?
Hi community, A client I am working for recently upgraded their FME Desktop/Server installation from version 2018.1 (20180717 - Build 18520) to 2021.1 (20210730 - Build 21619). I upgraded the workspaces and I am currently in the process of testing. I noticed that a workspace ("gdb2gml.fmw", attached to this thread) behaves differently in FME Desktop 2021.1. The purpose of this workspace is to read a File Geodatabase, map the attributes to a specific format and write to a GML. The output file (GML) is validated against an XSD file (XSD-file and input GDB also attached to this thread). The validation in the GML writer should fail. The File Geodatabase contains an illegal feature (a multipart polygon) which is not allowed as a geometry for this feature class. In the GML writer, the setting 'validate output file' is set to Yes. In FME Desktop 2018, this multipart feature is detected by the validation and the workspace fails. This is the expected behaviour. In FME Deskt
With FME upgrade to 2021.2.0.1 my workbenches are failing . I have used aggregator and geometry Validator . Also it gives application error if I try to run it from Command prompt.
Greetings,What is the best way to duplicate a writer? Using copy/paste only duplicates the annotation. Thank you. TylerFME 2022.1
How do I convert .osm data into shapefile using FME?
Converted ArcGIS Pro Annotation (geodb_pro_annotation) to Standard Annotation (geodb_annotation) with the help of Dynamic File Geodatabase reader and Dynamic File Geodatabase writer. Enclosed the developed FME workspace template for your reference. However, when opened the generated output Standard Annotation (geodb_annotation) feature class in ArcMap (version 10.8.1), getting an error saying "One or more layers failed to draw". Please refer to enclosed screenshot from ArcMap and help to advice how to handle this situation. Found no issues with the output when used Static File Geodatabase reader. However in our case, need to use the Dynamic File Geodatabase reader only. Thank you..! Note: Enclosed FME workspace created using FME(R) 2022.1.0.0 (20220704 - Build 22618 - WIN64)
I have made a workbench that contains an Emailer. I did not notice this directly, but the Emailer is a Package. I saved the workbench to a network location so my colleagues can run the workbench as well. And wrapped it in a Workspace Runner workbench so the workbench is not open for editing when colleagues run the workbench. But since this year I notice that the WorkspaceRunner fails because the Emailer package is not installed. This Emailer is installed as soon as the Workbench containing the Emailer is opened. My workaround now is adding a Emailer Transformer to the WorkspaceRunner workbench so the Emailer is installed when this workbench is opened. Hope this helps others that use WorkspaceRunners and Packaged Transformers in there workbenches.
Bulk copy failed on table 'tv.vagnat_framtida' using delimiter ':'. Error was 'ERROR: invalid byte sequence for encoding "UTF8": 0xc3 0x3aCONTEXT: COPY vagnat_framtida, line 33This error kept me busy for some hours exploring character encoding in shapefiles, FME and PostGIS. Which did not help. Not until I did some data digging and found the error.The data in a shapefile apparently comes from a qualified geodata store, and some long text fields have been truncated in the conversion to shape, leaving what appears to be incomplete character codes. And this causes PostGIS problems. The error message comes from deep within PostGIS. I have tried to cut a few bytes from the string with SubstringExtractor, but then the whole string became HEX. Very strange. Since it is invalid data, there seems to be no way of catching these characters with any of the FME string tools. And the error appears only in the Postgis writer, not before so it cannot be logged.Basically, I am looking for suggestions
Hello, I am trying to create a Json schema using the Json Template but I receive the error: JSONTemplater_2 (XMLTemplaterFactory): The following error occurred near line 21, column 20 of the query:JSONTemplater_2 (XMLTemplaterFactory): invalid expression: syntax error, unexpected ":", expecting "," or ")"JSONTemplater_2 (XMLTemplaterFactory): An error occurred while executing the 'PROPERTIES' queryJSONTemplater_2 (XMLTemplaterFactory): The following error occurred near line 6, column 9 of the query:JSONTemplater_2 (XMLTemplaterFactory): An error occurred while executing the process-features functionIf I validate my Json on line seems to be correct but in FME doesn't work.Do you have some suggestion?Attached the file that I am using ThanksMax