A space to discuss FME Form
Recently active
Hello,I am currently working with some database PostGIS rasters and wanted to import some into FME 2024.1, using a filter to only select 2 out of 11030.To do so, I tried both a SQL Executor and a FeatureReader (as both enables PostGIS raster reading).The SQL Executor filters the rasters correctly but doesn’t create the geometry and returns an error in the log file.The FeatureReader loads the 11030 rasters without filtering, suggesting a problem with the “WHERE clause”.I tried the same thing using FME 2023.1 and the SQL Executor is working under this version. I am wondering if there is a bug in the FME 2024.1 version.The problem was the same for the Feature Reader.A colleague said that the Feature Reader outputs everything as well in previous versions of FME (2022.2 and 2021.1).Do you know when the FME 2024.1 bug will be corrected?We are linking our work with ArcPro and we know we will have to use FME 2024.I am enclosing a share folder with the different logs (as txt) and the 2 workbenc
Hello,I’m having problems trying to write into a Azure Storage Table using the Azure Storage Table writer.It works for all text fields read from CSV but not possible both from Parquet file or Oracle connection where I include also floating or integer fields. The error is always the followingMicrosoft Windows Azure Table Writer: Failed 'INSERT' for rows in table 'xxxxxx'. Server response: 'HTTP Error Status Code #400: 0:One of the request inputs is not valid.'Suggestions?Thanks in advance,Roberto
This week I looked at this question on the community. "I have a 100 ft line that curves and then turns back into a straight line. How can I use FME to only gather the straight line after the curve only. I basically want to cut out the curve and only grab the line after the curve." This isn't too difficult, but what's interesting is the contrast with last week's question. Last week (click the link to check it out) I took a linear feature like this, created a list of its vertices, and processed those numbers directly. This week I could do the same, but instead I'm going with a spatial approach. In short, I'm going to divide the line into two-part segments, calculate each segment's angle (bearing or azimuth), and test how much each segment differs from the previous one. Preparing the DataThe first step is to prepare our data by chopping it into two-point lines. The alternative is to just extract the coordinates and work on them (as I did last week) but this time it's just that bit easier
I authored some scripts years ago that use the ArcSDEQuerier transformer to query for records in a versioned 10.1 ArcSDE Geodatabase. The machine that FME resides on has FME 2019.3.1, both ArcGIS 10.1 and ArcSDE 10.1, and both Oracle 32-bit (ArcGIS) and 64-bit (ArcSDE) clients installed. The scripts have worked for years without issue. Recently, I’ve had to modify them a bit and on a development FME machine, the ArcSDEQuerier transformer works fine, but promoting them to another same-build FME machine has had some odd results. If I use the exact scripts/workspaces from the dev machine, the ArcSDEQuerier throws the error seen below. Or if I open scripts that were already on this machine, untouched, the ArcSDEQuerier also throws the same error: However sometimes, and I stress sometimes, if I open a brand new workspace and add a single ArcSDEQuerier, I can connect to the same DB using the same credentials without issue: I know the obvious answer is that something has changed with ArcSDE,
I am trying to use the duckdb summarize commandhttps://duckdb.org/docs/archive/0.9/guides/meta/summarizein an in memory duckdb using the sqlexecutor:SUMMARIZE SELECT * FROM read_parquet('/Users/x/Downloads/Address.parquet');This doesn’t return any results/attributes but ‘runs’ successfully in FME. In DBeaver it runs no issues.Any idea is there is a trick to get this working?Many ThanksQ!
Hi, I’m trying to calculate the volume of various areas of beach using point cloud data. I want to calculate it above a horizontal plane at a level input as a user parameter and I have individually references mif/mid polygons demarking the areas.I have been using the method at the below link as a starting point, but the problem is the beach is sloping, not flat, meaning using the z.median value gives an incorrect result.https://support.safe.com/hc/en-us/articles/25407483031053-Volume-Measurements-with-the-VolumeCalculatorAny suggestions for a solution would be gratefully recieved!
Hi all,I’m working with a Feature Service containing approximately 1,000,000 sensors stored in a spatiotemporal big data store. I need to update 10,000 of these sensors based on their unique string ID, like sensors-0x21222.Currently, I'm using the FeatureWriter for the 'Esri ArcGIS Portal Feature Service' with the 'Use Global IDs' option enabled and 'Upsert' set as the 'Feature Operation' in the Feature Type. However, 'Upsert' requires a global ID.This approach feels very constrained, as it requires importing all 1 million records, merging them, and finding the global ID for each update.Is there a way to update a Feature Service using a primary key or unique field (such as upserting with a where clause) rather than relying on global IDs? This current method doesn’t seem ETL-friendly, as it requires importing parts of the dataset just to make updates.Thanks in advance for any guidance! Edit:Maybe I don't understand it. But for every featureservice/layer/featuretype I need to add, to fi
