PARC no longer recognizing NoData values?

[Stephen Chignell]

Hi all,

I am working with the latest release (VisTrails 2.2.3, SAHM 2.0.1) and am having trouble with PARC.

I have a study site that includes a number of areas that I want to exclude from the model.

I have masked these pixels out by changing them to NoData (white). All the pixels that I want the model to use have a value of 1 (black).



However, when I give this template (or others) to PARC, it only clips the predictor layers to the rectangular extent of the template, and does not mask out the NoData values. I have tried changing the size of the template and changing the values. I've also tried running it with PARC's "IgnoreNonOverlap" option both on and off.

It's strange because I've used this exact method in the past and never had this issue.

Thanks!
-Steve

[Jarnevich, Catherine]

Hi Steve,

I know Amanda ran into an issue this summer, and I think it ended up being related to an odd projection.  Amanda, do you remember what we figured out was causing the problem?  I'll look through emails and see if I can find the resolution.  Steve, what coordinate system are you using?

Cheers,
Catherine

--
You received this message because you are subscribed to the Google Groups "VisTrails SAHM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vistrails-sahm+unsubscribe@googlegroups.com.
To post to this group, send email to vistrails-sahm@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Catherine Jarnevich
Research Ecologist
U.S. Geological Survey
Fort Collins Science Center
2150 Center Ave Bldg C
Fort Collins, CO 80526
970-226-9439

[Stephen Chignell]

Hi Catherine, thanks for looking into this! I'm working in WGS84 GCS (unprojected). Could that be an issue?

-Steve

On Thursday, October 12, 2017 at 4:49:27 PM UTC+2, jarnevichc wrote:

Hi Steve,

I know Amanda ran into an issue this summer, and I think it ended up being related to an odd projection.  Amanda, do you remember what we figured out was causing the problem?  I'll look through emails and see if I can find the resolution.  Steve, what coordinate system are you using?

Cheers,
Catherine

On Sun, Oct 8, 2017 at 3:23 AM, Stephen Chignell <schi...@rams.colostate.edu> wrote:

Hi all,

I am working with the latest release (VisTrails 2.2.3, SAHM 2.0.1) and am having trouble with PARC.

I have a study site that includes a number of areas that I want to exclude from the model.

I have masked these pixels out by changing them to NoData (white). All the pixels that I want the model to use have a value of 1 (black).



However, when I give this template (or others) to PARC, it only clips the predictor layers to the rectangular extent of the template, and does not mask out the NoData values. I have tried changing the size of the template and changing the values. I've also tried running it with PARC's "IgnoreNonOverlap" option both on and off.

It's strange because I've used this exact method in the past and never had this issue.

Thanks!
-Steve

--
You received this message because you are subscribed to the Google Groups "VisTrails SAHM" group.

To unsubscribe from this group and stop receiving emails from it, send an email to vistrails-sah...@googlegroups.com.
To post to this group, send email to vistrai...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Ryan Anderson]

Hi Steve,

I recently had a similar issue and was able to resolve it. I believe in my case the specific value being used as NoData was not being recognized as NoData in SAHM. I spoke with Nick about this, and it seems -128 NoData values aren't recognized, whereas 255 values are. I was able to take a raster that I knew worked in SAHM, then extract it to the extent of the raster where NoData were not being recognized. Hopefully that makes sense, although I know that solution might not be an option for you. You might try exporting the raster to a different bit-depth with a different NoData value to see if that resolves your issue. Hope that helps!

Best,
Ryan

[Stephen Chignell]

Hi Ryan, 

Sorry I somehow missed your post until now! Thanks for this, I'll definitely give it a try next time.

-Steve