Open veroandreo opened 4 years ago
Probably we need a change here for LongLat:
ping @landam :) any chance to have a look at this?
Probably we need a change here for LongLat:
The change should be done in _raster_resolution function, the problem it is to get the right value in degree according to the position on the Earth surface.
Could geodesic lenght be useful?
... the problem it is to get the right value in degree according to the position on the Earth surface.
Could geodesic lenght be useful?
We have length_geodesic()
, maybe interesting?
In this commit in the i.landsat.import addon I propose a simple approach, i.e., using r.import's resolution = estimated
when the target location is longlat. What do you think @neteler and @lucadelu ?
It could work, did you try if you addons works properly?
It could work, did you try if you addons works properly?
Yes, It works as expected. It's r.import
who does the resolution estimation for latlong locations.
Name of the addon i.sentinel.import
Describe the bug When trying to import S2 scenes into a latlong location using
i.sentinel.import
with -r flag, the resolution is set to 10, 20 or 60 degrees instead of the equivalent of 10, 20 and 60 m in degrees. If I import into a UTM location all is fine, as well as if I user.import
instead of i.sentinel.import with a latlong location. As you can see below, r.import estimates a resolution, however, r.sentinel.import uses the nominal resolution in meters anyway.To Reproduce Steps to reproduce the behavior:
Screenshots
System description (please complete the following information):