FME Form

I have a point dataset representing the locations of streetlights. I want to replace each point with a small line drawing that symbolizes a streetlight. This symbol is stored as a set of line geometries and can stay line geometry.I suspect I may not be using the correct approach, but here’s what I’ve tried so far:I used a GeometryExtractor to extract the line geometry of the symbol, and a GeometryReplacer to apply that geometry to each point. This almost works — however, instead of placing the symbol at the location of each point, the points are being moved to the location of the symbol. As a result, I end up with over 4000 symbols stacked on top of each other at the original symbol location.I’ve included an image of my workspace to illustrate the issue. 

Hi all,I am working on a script to replicate a set of feature classes from one enterprise geodatabase that we use for transactional editing purposes to another enterprise geodatabase that we use for publication purposes for the organization. This replication script would be scheduled in FME Server to run on a nightly basis.The issue is that the feature classes I plan on replicating have several domains and subtypes applied to them that don’t translate correctly.I’ve been advised to use the ‘Resolve Domains’ functionality and change the configuration from ‘coded domain’ type to ‘char’.My test workflow involves the below:Copying the feature class via the ‘Import Feature Class’ tool in ArcGIS Pro into the target Enterprise Geodatabase to have the feature class available in both geodatabases With FME:Selecting the ‘Resolve Domains’ checkbox in the Writer at the outset, and using the ‘Insert’ and ‘Truncate Existing’In the Writer configuration, changing the ‘coded domain’ type to ‘char’ and

I have a building footprint layer that I am using an oriented bounding box transformer (blue line) and trying to keep the result as close as possible to the original polygon (black line) but for some reason the bounding box is getting squeezed out of shape.  Does anyone have any suggestions as to why the bounding box is not aligning better?I am using it to try and automate the georeferencing of a CAD drawing and using the AffineWarper with lines that come from the corners of the bounding box. I am using the long side angle in the bounding box to rotate the CAD drawing, which in this example is still correct but the length of the long side is incorrect which puts out the affine points and scale calculation.  This is a case where the footprint is a basic rectangle but there are many cases where the footprint is an irregular shape.      

Hi, I have a dxf file with objects in it, their representation is fine, I’m happy with it.However I need to filter these object using an polygon extent. So I read the dxf file using and Autodesk AutoCAD DWG/DXF reader and then lose the linetypes.The information seems to be read because an inspector shows me that the attribute autocad_linetype is correctly read (e.g. symbolLayer1), so it feels like the problem is that the style is not defined and thus FME uses CONTINUOUS in the end. Colors seem fine though. Is there any way to keep these types without recreating everything in FME? FME versions:Form 2023.1.1.1 Best Regards, Julien

 I have an Excel spreadsheet that serves as a data dictionary. After reading a shapefile in FME Workbench, is it possible to use this spreadsheet to dynamically define the data type of each field in the shapefile?

Hi all,I have a CSV file containing stops with fields stop_lon and stop_lat. I’m trying to turn them into geometry and reproject them so I can use them with other layers.My workflow looks like this:CSV → Tester → VertexCreator → CoordinateSystemSetter → Reprojector In VertexCreator I assign X = stop_lon, Y = stop_lat. In CoordinateSystemSetter I set the source coordinate system to EPSG:4326. In Reprojector I reproject to EPSG:7856 (GDA2020 / MGA Zone 56). After running this, the points don’t land in the right place compared to my suburb polygon layer (which is already in EPSG:7856). In QGIS, both layers line up fine (on-the-fly reprojection), but in FME they don’t.Clearly I’m missing something in how I’m handling coordinate systems — but I can’t see where the mistake is. 

Hi, I have a polygon that looks like it has some floating point issues in measures around 0. What is the best way to fix those values without affecting the legitimate values.I’m thinking extracting the measures as a list and then editing the list in python and resetting all the measures from the new list, but that seems a little convoluted.

Hello there, I really have a hard time to understand how to use the "Geometry Validator". I checked the "help" and still not sure how it works.  I checked an example in IMDF validator and not sure what is the column of "Issue to detect" does, such as "contains -0, NaN, or infinity".  I really hope someone can give me a light introduction on this transformer. Thank you and I am really appreciate your help.  

I converted the fbx model to citygml format and opened it in KITModel Viewer, but encountered an error and the model did not display。  

Hello everybody,I hope this is a the right place for a FME Realize question as this is about mobile apps (or is there a Realize subforum I missed?) otherwise please don’t hesitate to move this thread. I am just starting out with FME Realize and I noticed some weird behaviour and was wondering if this is only because of GPS position fluctuations or because of something else.I placed spheres at these two points:When I place one via rotating/moving and lock the model the other one is quite a bit offset. I doubt it is because of my data, as it is measured by a trusted surveyor.  Correctly placed sphere and line.When I now walk over to the point where the other sphere is located it looks like this:Green circle showing where it should be, red where it isWeirdly when I now go back to the first sphere it is also offset:  I tried it with several coordinate systems and which anchor/georef.anchor on and off, but it is never correct. At the moment I am in scalefree UTM.ETRS89 - EPSG25832, though t

Hi! I'm new to FME and I have an issue with published parameters in a CustomTransformer.I created a CustomTransformer name "TeamsConnector" which need to use the published parameters "Message" in a pythoncaller:   Now in my main flow I use twice my custom transformer with different published parameters value. "Message 1" as a value for the first use of my transformer:    "Message 2" as a value for the second use of my transformer:  My issue is when I run the flow instead of having "Message 1" and "Message 2" as expected, I have twice "Message 1": 

I'm trying to create a custom transformer 'FeatureCountLogger' which logs the number of features inputted into this transformer.  The custom transformer contains a PythonCaller with the following code:   import fmeobjects class FeatureProcessor(object):    def __init__(self):        self.featureList = []    def input(self,feature):        self.featureList.append(feature)    def close(self):        logger = open(FME_MacroValues['Summarylog'], "a")        message = FME_MacroValues['Message'] + str(len(self.featureList)) + '\\n'        logger.write (message)        logger.close()      I want to use the logger multiple times, so I created a published parameter 'Message' in the custom transformer, so I can submit the text logged to each instance of the transformer.    When I'm running this I get the following error: Python Exception <KeyError>: 'Message'    It seems like the PythonCaller can't a

Hi, It seems to me that there might be an issue when I'm trying to fetch a parameter value of a Custom Transformer, from a PythonCaller inside that Custom Transformer.  If I do so, I obtain an error. When I try to do so in the main workspace, or when I add the name of the CT in the parameterfetcher, I don't get an error, and it works. See below screenshot and the attached demo workspace for an example.This seems like a bug to me, but it would be nice if the community can have a look alongside me. Kind regards, Thijs Ps. as a sidenote, I came across this Community Question in which the best practice for accessing parameter values inside a PythonCaller is discussed. In it, it is mentioned that best practice is to use param = fme.macroValues[‘parameterName’] in favour of param = FME_MacroValues[‘parameterName’] Additionally, it is mentioned that DaveatSafe created a problem report 4 years ago to make sure that this best practice is also honoured in the script editor for the Python

Hi,I’m having a issue making a TIN properly in FME. Basically FME is interpolating points/vertexes that don’t actually exist in the original data. What I want to do is make a TIN that considers only the vertexes of the features I give to it (point/lines and breaklines). I do not want FME to make up data that does not exist.Does anyone know a way that I can do this?For example in this example this is one break line. It should only have two TIN vertices (the ends). No triangles should be created from any interpolated points However, when I look at the TIN for the same spot it has created 6 vertices I am using FME workbench/form 2023. I’ve been trying different settings for the SurfaceModeller and the TIN generator

Hi, I have a dynamic workspace where I am reading in multiple csv update files for multiple feature types to upsert into our database. I had set the primary key dynamically dependent on the target table in the database. I cannot set a where clause on an UPSERT (which I do use with other feature types that have the ability to do I, U, or D) so went to use the "Row Selection: Columns:" section instead. This parameter does not work in the normal way with attributes. It presumes the selected attribute is the primary key field (no orange left arrow in front of the name), rather than using the value. I tried manually adding @Value(primary_key) (the attribute that stores the primary key column name) in the parameter but the feature writer also presumes it is literal and obviously can't find a column called "@Value(primary_key)" and errors. This is something that I would like to do, and is very much a part of a dynamic workflow. Otherwise I will have to create one dynam

It seems that in the iOS18 update Apple made changes to the HEIC file container that means the FME Feature Reader using HEIF (High Efficiency Image File Format) now fails to read the HEIC files.We are currently using FME 2022.2.Is there a later update that will support iOS18 images? Is there an alternative way to read in these images successfully? 

Hi Everyone, Looking for some assistance, I’m using FME 2023.1.0.0 trying to migrate some existing Survey-123 forms and data with attachments from ArcGIS On-Line to our new Enterprise portal.Our survey-123 form has a singular photos field for tracking a picture of the bus stop, it also has a repeatable photo’s field (table) where the inspector is able to take and attach multiple deficiency photos to the stop if one exists.  In FME, I’m able to read in the AGOL feature service that hosts all of the survey information, I’m also able to write out the tabular information from the point layer to the new Enterprise feature layer that was created when I saved the Survey-123 form in Enterprise.The part that I’m currently struggling with is getting the singular photos to attach when writing the tabular information out to the Enterprise feature service so when I view the points in ArcGIS Pro, they appear in the attachments tab of the attributes editor like they currently do with my AGOL service.

NullAttributeMapper, AttributeCreator or otherWhat do people use to set default values for attributes?In the case that I have is a json document - in the case values are missing I need to set a default value. Ideally I’d use an NullAttributeMapper, however, there are upwards of 10 values I need to set and I don’t want to use 10 of these. The other option I see is an AttributeCreator/Manager with conditional values which is what I would normally do.  

After adding FeatureReader_2, the reading order started prioritizing the XML block. Then, a join occurs with the Data Dictionary block, but since the XML is fully read first, when the flow reaches the FeatureJoiner, the data dictionary has not yet been processed, causing an error.This started after I added FeatureReader_2, because I need it to read shapefile files to extract the name and coordinate system, which are parameters defined in my spreadsheet with the paths to each shapefile.Is there any way to make the XML and Data Dictionary blocks read simultaneously? Or, since the FeatureReader is a reader, will it always have priority?

Hi,I am looking for a writter that will allow me to save blob data in FME Flow. On FME Form I am using AttributeFileWriter that is working completely fine 

Hello Am struggling to combine geometry of an object . I should have 19 objects there is only 1 object which just doesn’t want to combine any unknown reason…..don’t know why ? Any suggestion / idea would be much appreciated.  The reason i am combing objects is to extract the face of each object and then obtain FACE centre point for further analysis.  thank in advance 

Greets,I have two question: First one: how can I clip the green polygons based on the reds one with the same ratio?Second one: is there any way to move the red polygons to match the border of the green polygons. The Red and green polygons not in the same layer

Hi everyone!Today I’d like to share a new approach to building reports in FME, along with an entire family of custom transformers I’ve created to support it. Why I built BRGI’m a long-time fan of the HTMLReportGenerator. It lets me craft reports quickly, and I love the versatility of HTML compared with, say, PDF. I even demo it in every Intro to FME course as a great example of “let FME handle the code.”But as much as I love it, I’ve always hit three pain points:1. Plain styling – it could really use a dash of CSS/Bootstrap.2. Hard-coded content types – adding a new chart or HTML element isn’t trivial.3. Cumbersome feature ordering – managing Sorters and AttributeCreators just to control layout can get messy.Earlier this year I had to build a highly procedural report with lots of HTMLLayouters, AttributeCreators, and Sorters, and the workspace quickly turned into spaghetti. That’s when I thought: I already improved SystemCaller with BetterSystemCaller… why not do the same for report ge

In the stand-alone FME Form my FME script works well. However, using the same script in ArcGIS Pro faced error saying Esri Geodatabase Writer: Feature Type Definition … was requested, but not defined. A possible reason is that you may not have permission to create the Geodatabase. The error number from ArcObjects is: '-2147467259'. The error message from ArcObjects is: {}FeatureWriter or classical Writer, there is no difference. With other FME scripts (created by others) a fgdb can be created. Why not the mine?  

Hi there,I have 2 parcel datasets, a master copy and a weekly update copy that I need to process into the master copy. Each parcel only appears once in each dataset and has a unique parcel ID so matching is fairly easy. I’ve used a change detector to flag any parcels with geometry updates, but now I need to identify the type of change that has taken place. This could involve parcels being split, merged or just the boundary being updated. What is the best way to do this? The logic in my head is this so far:Split parcels - Either, mutliple new parcels being inserted within the boundary of one that has been deleted OR Parcel boundaries shrinking and new parcels being added within boundary of originalMerged parcels - New parcel being inserted that takes the place of multiple deleted parcels OR Parcel boundaries growing to cover extent of deleted parcels