Skip to main content
Solved

VertexExtractor not working in FME 2024.2


agelfert
Contributor
Forum|alt.badge.img+8

As mentioned in another post, I'm currently upgrading a bunch of workbenches to run on FME Flow 2024, some of them many years old. Typically, for anupgrade, I will go through each workbench, upgrade all transformers, readers, and writers, then run it in test desktop (workbench) environment, then publish to and test in a test server (flow) environment.

In, FME 2024 the Vertex Extractor gives me bogus results, even after upgrading all the constituent transformers in this custom transformer. It looks like X and Y, or Lat and Lon, are reversed.

When I open the CoordinateConcatenator (arrow above), I see this:

Default setting

While I haven’t dug through the rest of the custom transformer, this - frankly - looks counter-intuitive.

When I change that to “XYZ”, everything runs just fine and results are as expected.

 

My tweak

I have tried to compare my version (I’m assuming that upgrading all components makes it uptodate) to older versions to see whether upgrading might have introduced this problem but I see the same from the screenshot in older version of the Vertex Extractor.

Has anyone come across this? I’m using 3D data for this. Never had an issue before. But I also don’t remember that I have tried to upgrade the components inside this particular custom transformer before. So it’s possible I have carried over an ancient version through a number of upgrades. Never noticed any adverse consequences though.
 

Best answer by DanAtSafe

Hi ​@agelfert , there must have been a problem with the CoordinateConcatenator some time between FME 2016 and 2019 where "X Y Z" changed to "X Z Y". However, this didn't change the behavior and it continued to concatenate in "X Y Z" order - until the fix that ​@takashi noticed from build 24734.  You should only see the problem if running FME 2024.2+ and the VertexExtractor is embedded in the workspace.

We will fix the VertexExtractor on the FME Hub very soon; until then, the fix is very simple: open the CoordinateConcatenator and reset the Coordinate Elements to "X Y Z".

View original
Did this help you find an answer to your question?

9 replies

takashi
Influencer
  • April 18, 2025

Hi ​@agelfert ,

I was able to reproduce the issue.
It seems that the implementation of CoordinateCocnatenater has been updated in FME 2024.2 and it cause the issue, I guess.


Hope some one from Safe explain abount this. > ​@DanAtSafe ?


DanAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • April 18, 2025

Hi ​@agelfert and ​@takashi,

I’m unable to reproduce the problem with the CoordinateConcatenator.  I only see “X Y Z”. What was the build number before upgrading the workspace, and what is the current 2024.2 build number?

Thanks


takashi
Influencer
  • April 18, 2025

Hi ​@DanAtSafe ,

Thank you for your response.

In my environment - Windows 11, FME Form 2024.2.3, the issue was reproduced with the attached workspace example. y and z will be swapped in the resulting vertices as shown below.

orange: input geometry - 3D rectangle polygon, z is identical for every vertex

points: extracted vertices

 


danilo_fme
Evangelist
Forum|alt.badge.img+45
  • Evangelist
  • April 18, 2025
takashi wrote:

Hi ​@DanAtSafe ,

Thank you for your response.

In my environment - Windows 11, FME Form 2024.2.3, the issue was reproduced with the attached workspace example. y and z will be swapped in the resulting vertices as shown below.

orange: input geometry - 3D rectangle polygon, z is identical for every vertex

points: extracted vertices

 

 

Awesome.


DanAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • Best Answer
  • April 19, 2025

Hi ​@agelfert , there must have been a problem with the CoordinateConcatenator some time between FME 2016 and 2019 where "X Y Z" changed to "X Z Y". However, this didn't change the behavior and it continued to concatenate in "X Y Z" order - until the fix that ​@takashi noticed from build 24734.  You should only see the problem if running FME 2024.2+ and the VertexExtractor is embedded in the workspace.

We will fix the VertexExtractor on the FME Hub very soon; until then, the fix is very simple: open the CoordinateConcatenator and reset the Coordinate Elements to "X Y Z".


agelfert
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • April 19, 2025

Thanks for looking at this. Your timeline makes sense based on the history of my workbench having been upgraded a few times over the years, plus, at some point, featuring an embedded transformer. Really a strange one! But it hasn’t stopped me from getting thing to work. Happy Easter !


DanAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • April 21, 2025

Hi ​@agelfert JFYI, I’ve updated the VertexExtractor.


agelfert
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • May 13, 2025

Thanks, all who chimed in here. Glad it’s gotten looked at. upwards and onwards.😀


gmbutler2
Contributor
Forum|alt.badge.img+10
  • Contributor
  • May 16, 2025

@DanAtSafe Is the VertexExtractor being lifecycled?  I have a workspace where I was using the VertexExtractor and when I open it I get an error popup saying the VertexExtractor is no longer installed.  Then I go into my workspace and I find that where I had it in my workspace, it removed itself and now my workspace is completely broken.  And when I try and load it back in from the FME Hub, it does nothing.  I’m running FME Database Edition (floating) FME(R) 2020.0.1.0 (20200407 - Build 20218 - WIN64)

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings