Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

On Thu, Oct 4, 2018 at 6:54 AM Nikos Alexandris wrote: > > (For context see previous messages in this thread) > In this case > r.in.gdal in=NETCDF:"g2_BIOPAR_LST_201606220100_GLOBE_GEO_V1.2.nc":LST out=import -o --o r.in.gdal -a would do more harm than good. The warning > > 360 degree EW extent

Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

(For context see previous messages in this thread) Nikos A: >> g.region raster=g2_BIOPAR_LST_201606220100_GLOBE_GEO_V1.2.nc_LST >> -pag w=-180 e=180 Markus M: >this shifts the grid by half a cell to the east. The -a flag does >not mak sense because 1) you want to force new extends, 2)

Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

Nikos wrote: >> Import using r.in.gdal, _without_ any of `-l` or `-a` and then I get the >> closest to the reported spatial resolution. Else, with `-a`, for >> example, the spatial resolution is not as close to the "original" one. >> Makes sense? Markus M: >what would be the output

Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

On Mon, Oct 1, 2018 at 4:28 PM Nikos Alexandris wrote: > > Nikos wrote: > > >> Import using r.in.gdal, _without_ any of `-l` or `-a` and then I get the > >> closest to the reported spatial resolution. Else, with `-a`, for > >> example, the spatial resolution is not as close to the "original" one.

Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

Nikos wrote: gdalinfo NETCDF:"g2_BIOPAR_LST_201606220100_GLOBE_GEO_V1.2.nc":LST Driver: netCDF/Network Common Data Format Files: g2_BIOPAR_LST_201606220100_GLOBE_GEO_V1.2.nc Size is 8064, 3584 Coordinate System is: GEOGCS["unknown", DATUM["unknown",

Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

On Tue, Sep 25, 2018 at 4:51 PM Nikos Alexandris wrote: > > * Veronica Andreo [2018-09-25 08:24:44 -0300]: > > >AFAIU, plate carree (lat long grid, no meters) is deprecated, and you > >should use latlong instead. I had a similar issue with modis ocean color > >products. > > > >Do you at least

Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

* Veronica Andreo [2018-09-25 08:24:44 -0300]: AFAIU, plate carree (lat long grid, no meters) is deprecated, and you should use latlong instead. I had a similar issue with modis ocean color products. Do you at least get the same number of row and columns that is described by gdalinfo when you

Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

On Tue, Sep 25, 2018 at 1:25 PM Veronica Andreo wrote: > > AFAIU, plate carree (lat long grid, no meters) is deprecated, and you should use latlong instead. I had a similar issue with modis ocean color products. > > Do you at least get the same number of row and columns that is described by

Re: [GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

AFAIU, plate carree (lat long grid, no meters) is deprecated, and you should use latlong instead. I had a similar issue with modis ocean color products. Do you at least get the same number of row and columns that is described by gdalinfo when you import? HTH, Vero El mar., 25 sep. 2018 7:25,

[GRASS-user] EPSG 32633 and spatial resolution for hourly LST product from Copernicus

The hourly 5km LST product from Copernicus, as per the product user manual (https://land.copernicus.eu/global/sites/cgls.vito.be/files/products/GIOGL1_PUM_LST-I1.40.pdf) "is displayed in a regular latitude/longitude grid (plate carrée) with the ellipsoid WGS 1984 (Terrestrial radius=6378km).