error: some values are not associated to a friction value

[SaraTschersich]

Hello,

I am stuck at step 5 - Friction.
The plugin merged the layers in step 4 fine. I then assigned custom values to all classes in step 5, but when I hit "Compute friction layer" the following error appears:

"[user error] Some values of (...) are not associated to a friction value {0}"

I initially thought there may be gaps in the merged layer, but I have since tried adding a background layer that covers the entire extent and it hasn't made any difference.

Any idea of how I can fix this?

Many thanks,
Sara

[MathieuChailloux]

Do you have empty cells in your friction panel ?

Can you show me the entire error message please ?

Regards,
Mathieu

[SaraTschersich]

Hi Mathieu,

thanks so much for your response!
No empty cells in the friction panel, looks like this:

The above is basically the whole error, but I am attaching the log here:
BioDisperal_log_Friction_error.txt

Thank you!
Sara

[MathieuChailloux]

It seems to me that 0 value (I guess NoData from an input layer) is expected by BioDispersal at friction step but is not present.
Could you send me your data ? I will try on my environment.
Otherwise you could try to reconfigure your project from scratch.

Regards,
Mathieu

[SaraTschersich]

Hi Mathieu,

I have checked that all layers have the same no data value, which they seem to have (-9.9999). BioDispersal rasterised most of the layers itself. But of course I don't know which layer is creating the issue.
All my input data is here: https://we.tl/t-8wsATAjnLM
Thank you for looking into this for me.
If I should reconfigure my project, what should I do differently/pay particular attention to?

Sara

[SaraTschersich]

I have solved this issue now. All my data layers are binary, but some were set at 1 (present) and no data (absent), whilst two were set at 1 (present) and 0 (absent). I reassigned 0 as a no data value for the affected layers. With these updated inputs the friction layer was created fine (with a new issue, but I will open a new thread for that).