Skip to main content
Solved

RasterExtentsCoercer not retaining attribute data


rclarkenz
Contributor
Forum|alt.badge.img+2

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

Best answer by takashi

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.

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

4 replies

takashi
Evangelist
  • Best Answer
  • October 29, 2018

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.


fmelizard
Safer
Forum|alt.badge.img+19
  • Safer
  • October 29, 2018
takashi wrote:

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!

 


rclarkenz
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • October 29, 2018
takashi wrote:

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.

takashi
Evangelist
  • October 30, 2018
fmelizard wrote:
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)


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