# Crop production, appears to be an issue with the input data

**URL:** <https://community.naturalcapitalalliance.org/t/crop-production-appears-to-be-an-issue-with-the-input-data/2640>\
**Category:** Software Support\
**Tags:** crop-production\
**Created:** [April 1, 2022, 10:53am UTC](https://community.naturalcapitalalliance.org/t/crop-production-appears-to-be-an-issue-with-the-input-data/2640 "2022-04-01T10:53:32Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![esoth](https://avatars.discourse-cdn.com/v4/letter/e/9d8465/32.png) [@esoth](https://community.naturalcapitalalliance.org/u/esoth)\
**Post date:** [April 21, 2022, 8:41pm UTC](https://community.naturalcapitalalliance.org/t/crop-production-appears-to-be-an-issue-with-the-input-data/2640/5 "2022-04-21T20:41:12Z")

</div>

Hi @lukezw,

The error is happening because the rasters downloaded directly from EarthStat do not have a nodata value set. The model shouldn’t care about that, it’s a small bug that I have targeted to fix in the next release. But in the meantime, you can get around it by setting a nodata value for the raster. [Here are instructions](https://gis.stackexchange.com/a/389588/184068) for how to do that in QGIS. I recommend using a nodata value of -1 so it won’t conflict with the real data.

Hope that helps, and thanks for reporting these issues!

---

_[View the full topic](https://community.naturalcapitalalliance.org/t/crop-production-appears-to-be-an-issue-with-the-input-data/2640)._