Morten W. Hansen

Following the CF conventions, the parameter names either start with ```x_```/```y_``` or ```eastward_```/```northward_```. If these parameters are projected (i.e., ```x_```/```y_``` ), shouldn't it then be enough to simply calculate eastward...

This issue can be closed and left to be handled by users. In general, it is important to follow the CF-conventions and focus on eastward/northward vs x/y directed velocities.

Yes, the scripts seem to work when nansat is installed as `python build_ext --inplace` but with the regular `python setup.py install` the mapper fails because the perl scripts (now in...

Btw - I also removed the try-except lines in `__getitem__` - if such value replacements fail it should cause errors, otherwise we'll get difficulties in debugging when problems arise... Please...

Don't worry about that now - we can reproject the image to make it work later. It should be tested in any case but first the export function should be...

Great - that will probably work and both issues should be solved :) perfect - thanks! - mars 2015 21:47 skrev "Asuka Yamakawa" [email protected]: > It is related to issue42....

@akorosov - would it be possible to follow up on this? It's so annoying when the attribute names are changed.... I also discovered that gdal creates a new history attribute,...

Which versions of nansat and openwind are you running? I can't reproduce the error. It is correct that the "SAR_look_direction" name has changed in nansat but it shouldn't be a...

ok - I have changed the version numbers of nansat and openwind in `setup.py`. If you run `python setup.py install` in openwind, it should work. Also, it should work with...

Strangely, this seems not to be fixed anyway. At least in master. Reopened to check and correct later...