Skip to main content
  • EN

I am having issues with FME reading the Band Value incorrectly or applying a conversion.

Could you please attach a sample DEM dataset and a workspace which reproduce the issue?

 

File is too large to attach. I could email if you want to take a look at it...

Thank,

Chad

File is too large to attach. I could email if you want to take a look at it...

Thank,

Chad

It's enough to attach only a small sample data that can reproduce the problem. Consider using the Clipper or the RasterTiler to make a sample.

 

 

I will clip a portion and send...

CK

When I clip in FME it gives this error:

USGS_DEM Writer: The maximum number of decimal places allowed for the format attribute 'dem_spatial_resolution_z' when expressed in 'FEET' is 1. The value '0.0014411999999999999' must be reduced to 1 decimal place(s)

A fatal error has occurred. Check the logfile above for details

... Last line repeated 2 times ...

usgs-dem.zip

the attached zip the band is at a zero precision, that is the only way I could clip and export. The attached screen shot shows what the elevation should be in this area. Let me know if this helps.correect-elev.png

the attached zip the band is at a zero precision, that is the only way I could clip and export. The attached screen shot shows what the elevation should be in this area. Let me know if this helps.correect-elev.png

Interpretation of the clipped raster is Int32, whereas the original interpretation shown in your screenshot is Real64. The change of interpretation is the direct reason why cell values have been rounded into zero precision. Is it the original issue - "DEM Band Value Incorrect"? If so, we will have to investigate your workspace to clarify why/when the interpretation has changed.

 

 

If you want to take a look at the original DEM here is the link:

ftp://data.ga.lsu.edu/lidar/2000_state/la_lidar_dem/2909001ne_dem.zip

The attached shapefile is of the area of interest that the screen shot I sent shows elevation of -0.3' and FME reads different. When I clip the DEM it changes the value so I cannot send a clipped area of the DEM.

Thanks,

Chad

dem-clip.zip

fme-screenshot.png

Hi @tbs_gis_team,

Thanks for reporting this to us and providing your sample datasets. A developer confirmed that it looks like our USGS_DEM Reader isn't applying the elevation of the local datum to individual elevation values within a profile. I've opened up a case for you, for which you should have received a notification email.

As a workaround for the provided dataset specifically, try using an Offseter to offset Z by -0.312000006437302. I hope that helps!

Hi @tbs_gis_team,

Thanks for reporting this to us and providing your sample datasets. A developer confirmed that it looks like our USGS_DEM Reader isn't applying the elevation of the local datum to individual elevation values within a profile. I've opened up a case for you, for which you should have received a notification email.

As a workaround for the provided dataset specifically, try using an Offseter to offset Z by -0.312000006437302. I hope that helps!
Thanks for the information, let me know if the reader is updated. The process would be reading multiple files and not sure if that offset would apply to all datasets.

 

Thanks,

 

Chad

 

 

I'm glad to report that the fix for this issue has been included in the latest FME release (FME 2018.1.0.2, build 18547). Thanks @tbs_gis_team for bringing this to our attention, and for helping us make FME even better!

Reply


Community Stats

30,108
Posts
114,295
Replies
37,743
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.