Skip to main content
Question

RasterExpressionEvaluator result issue

  • December 15, 2016
  • 4 replies
  • 88 views

Hello everyone,

I need help to understand what’s wrong with my workbench. I’m trying to calculate an expression between two rasters.

To explain the data, I’ve got 2 GEOTIFF with the same projection, the same cells number and the same NoData value :

  • TELECOM containing pixels values 1 or 0 (signal coverage or not, 0 as NoData)
  • POPULATION containing inhabitants value or 0 (NoData)

Here is my workbench :

After execution, the Data Inspector result window :

The result seems to be wrong for 2 reasons :

  • When I click on the cell value for each raster, I’ve got this result
    • Light gray : POPULATION (pixel value 0.68)
    • Dark gray : TELECOM (pixel value 1)
    • Black : RESULT (pixel value 0 NoData)…But 1*0.68 is not 0
  • There is a gap between the source and the result data in the west side of the layer
    • Light gray : RESULT
    • Dark gray : POPULATION

Am I missing something ?

Thanks in advances.

Aymeric

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

daveatsafe
Safer
Forum|alt.badge.img+24
  • daveatsafeSafer
  • Safer
  • December 15, 2016

Hi Aymeric,

This does seem like quite unexpected behavior. Would you mind sharing your source data and workspace with us? Please email the workspace to support@safe.com, with Attn Dave in the subject line.

Kind regards,

Dave Campanas

takashi
Celebrity
  • takashiCelebrity
  • December 16, 2016

Hi @aymfr17,

  1. In my experiences, the RasterExpressionEvaluator could generate such an unexpected value if the source rasters have Nodata definition. Try removing Nodata from the source rasters beforehand with the RasterBandNodataRemover. You can restore Nodata definition after the calculation with the RasterBandNodataSetter if necessary.
  2. It's unclear that the gap has been caused by the RasterExpressionEvaluator. Check if the the extents of the two source rasters are exactly same, without cell value calculation.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
  • aymfr17
  • Author
  • December 16, 2016

Hi Aymeric,

This does seem like quite unexpected behavior. Would you mind sharing your source data and workspace with us? Please email the workspace to support@safe.com, with Attn Dave in the subject line.

Kind regards,

Dave Campanas

Thank you for your quick answer Dave.

 

It's not necessary. Takashi already found what was wrong with my data!

 

 

Kind regards,

 

 

Aymeric

 

  • aymfr17
  • Author
  • December 16, 2016

Hi @aymfr17,

  1. In my experiences, the RasterExpressionEvaluator could generate such an unexpected value if the source rasters have Nodata definition. Try removing Nodata from the source rasters beforehand with the RasterBandNodataRemover. You can restore Nodata definition after the calculation with the RasterBandNodataSetter if necessary.
  2. It's unclear that the gap has been caused by the RasterExpressionEvaluator. Check if the the extents of the two source rasters are exactly same, without cell value calculation.
Thank you Takashi, everything's working fine now!

 

 

You're right, the two raster extents were slightly different causing this gap (removing the NoData maked it appear).

 

If somebody encounter the same issue :

 

- Clip the smallest raster by the BoundingBox of the biggest one (BoundingBoxReplacer)

 

- Resample the biggest to fit the smallest (RasterResampler)

 

 

Kind regards,

 

 

Aymeric

 

Community Stats

32,887
Posts
124,768
Replies
41,538
Members
Terms & ConditionsAccessibility statement
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.