Skip to main content
  • EN

Hi,

 

I noticed the following behavior.

I created two shapefiles for this test : line.shp and surface.shp

Both contain several feature including one with multiparts (multiline and multisurface).

 

When using CoordinateExtractor with mode Specify Coordinate + index=0, I get in the _x and _y attributes the first point of the first part of line/surface.

I assumed I would get the same with @XValue() and @YValue() but it is not the case for the multiparts features.

For those I get a point far far away from the feature, with integer values for X and Y.

 

Anybody knows why ? Is it a normal behavior ?

 

Tested on FME 2018.1 and 2019.0, see enclosed test workspace on FME 2019.

It doesn't seem like normal behaviour to me (it's also happening in FME 2020 by the way). I would recommend sending this in to Safe's support team.

The easy workaround is to use the CooridnateExtractor of course.

@Evaluate(@Coordinate(x,0)) & @Evaluate(@Coordinate(y,0) give the same integer figures for the multiparts.

Interestingly @Evaluate(@Coordinate(x,1)) & @Evaluate(@Coordinate(y,1)) return the correct first coordinate for the multipart features

Apparently de-aggregating the multi feature helps....

It doesn't seem like normal behaviour to me (it's also happening in FME 2020 by the way). I would recommend sending this in to Safe's support team.

The easy workaround is to use the CooridnateExtractor of course.

I filed a report. Case number C153869.

In the meantime yes I will use CoordinateExtractor.

@Evaluate(@Coordinate(x,0)) & @Evaluate(@Coordinate(y,0) give the same integer figures for the multiparts.

Interestingly @Evaluate(@Coordinate(x,1)) & @Evaluate(@Coordinate(y,1)) return the correct first coordinate for the multipart features

Indeed, it's weird...

Hi @p.jeremie The CoordinateExtractor is hiding the first coordinate for aggregates. I don't know why the @XValue() and @YValue() don't also skip the first vertex. Y is the number of coordinates in the first element. For multipart polygons, X=4; for lines, X =2.

Hi @p.jeremie The CoordinateExtractor is hiding the first coordinate for aggregates. I don't know why the @XValue() and @YValue() don't also skip the first vertex. Y is the number of coordinates in the first element. For multipart polygons, X=4; for lines, X =2.

Hi @danatsafe. Indeed, it makes sense now.

FYI I filed a report. Case number C153869.

In the meantime yes I will use CoordinateExtractor.

Reply


Community Stats

30,194
Posts
114,615
Replies
37,857
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.