EWA Resampler hardcodes fill value to NaN

[djhoese]

A colleague tried to use EWA resampling on regular (non-dask) numpy arrays that were integers. She got errors about NaN not being able to be converted to an integer so she then specified the fill value with fill=0 and still got the same error. Turns out I have the fill value hardcoded to NaN:

pyresample/pyresample/ewa/ewa.py

Lines 170 to 171 in 1f4c7fb

	results = _fornav.fornav_wrapper(cols, rows, data_in, out,
	np.nan, np.nan, rows_per_scan,

This means integer data isn't actually handled. I need to create some tests for this to prove that there isn't some other reason I hardcoded this.

[djhoese]

Doesn't look like I'm doing this in the dask version of the EWA resampling code:

pyresample/pyresample/ewa/dask_ewa.py

Lines 400 to 410 in 1f4c7fb

	# determine a fill value if they didn't tell us what they have as a
	# fill value in the numpy arrays
	if fill_value is None:
	fill_value = self._get_default_fill(data_in[0])
	data_out = []
	for data_subarr in data_in:
	res = self._run_fornav_single(data_subarr, out_chunks,
	self.target_geo_def,
	fill_value,
	**fornav_kwargs)

[mraspaud]

Does it make sense to allow ewa on integer data? Because averaging is happening...

[djhoese]

Yes it has a maximum weight mode that is similar to nearest neighbor.