Skip to main content
  • EN

My features have an attribute _mapsheet. When I use the inspector I can see the _mapsheet attribute is populated when it comes out of the FeatureReader

But then when I check the attribute after it has been through the RasterExtentsCoercer (which I have named RawRasterExtent in my workspace) the attribute is no longer populated.

I had this workspace working in FME 2017. Is this a bug in 2018? Or is there something extra I need to do.

TIA

Hi @rclarkenz, I was able to reproduce the same symptom as yours, with FME 2018.1.0.3. The RasterExtensCoercer (Extents Type: Raster Extents or Data MBR Extents) won't propagate user attributes of the input feature to the output feature.

It seems to be a bug. @DanAtSafe, can you please check this one?

Format attributes seem to be preserved, so as a workaround in the interim, you could expose "fme_dataset" in the FeatureReader and merge back all the attributes after the RasterExtentsCoercer.

Hi @rclarkenz, I was able to reproduce the same symptom as yours, with FME 2018.1.0.3. The RasterExtensCoercer (Extents Type: Raster Extents or Data MBR Extents) won't propagate user attributes of the input feature to the output feature.

It seems to be a bug. @DanAtSafe, can you please check this one?

Format attributes seem to be preserved, so as a workaround in the interim, you could expose "fme_dataset" in the FeatureReader and merge back all the attributes after the RasterExtentsCoercer.

Hi @takashi I can't reproduce the problem with FME 2018 or 2019. If you have a demo then please send it to https://www.safe.com/support/report-a-problem/ Thanks!

 

Hi @rclarkenz, I was able to reproduce the same symptom as yours, with FME 2018.1.0.3. The RasterExtensCoercer (Extents Type: Raster Extents or Data MBR Extents) won't propagate user attributes of the input feature to the output feature.

It seems to be a bug. @DanAtSafe, can you please check this one?

Format attributes seem to be preserved, so as a workaround in the interim, you could expose "fme_dataset" in the FeatureReader and merge back all the attributes after the RasterExtentsCoercer.

Thanks @takashi this work around worked for us.
Hi @takashi I can't reproduce the problem with FME 2018 or 2019. If you have a demo then please send it to https://www.safe.com/support/report-a-problem/ Thanks!

 

Hi @DanAtSafe, in my observation, the symptom occurs when the attribute name starts with an underscore (_) and the Extents Type parameter is set to "Raster Extents" or "Data MBR Extents".

 

See also this workspace: b18552-rasterextentscoercer-missing-attributes.fmwt (FME 2018.1.0.3)

Reply


Community Stats

31,821
Posts
120,861
Replies
39,452
Members

Latest FME

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.