Re: [GRASS-user] Working with multiple Landsat tile row/paths

[Ken Mankoff]

Hi Stefan,

On 2016-06-14 at 01:26, Blumentrath, Stefan  wrote:
> Did you consider using
> https://grass.osgeo.org/grass70/manuals/r.import.html r.import
> reprojects on import.

This solves the issue. Thank you.

  -k.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Working with multiple Landsat tile row/paths

[Blumentrath, Stefan]

Hi Ken,

Did you consider using https://grass.osgeo.org/grass70/manuals/r.import.html
r.import reprojects on import.

Cheers
Stefan

___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Working with multiple Landsat tile row/paths

[Ken Mankoff]

Hi List,

I'm working with multiple Landsat scenes from different rows/paths that all 
overlap on my one point of interest. The row/paths are from different times, so 
I don't think the gdal tiling command is an option.

Path/row 208/5 and 209/5 both seem to import into the same location.
But path/row 210/4 and 210/5 don't into the 209 location.

Since all scenes do contain the same point of interest, should I use the "-o   
Override projection (use location's projection)" flag to r.in.gdal? Or is there 
some other suggested method or gdal command to work with these? Or do I import 
each image into its own location, and then use "r.proj" to import them all into 
one unifying location?

Thanks,

  -k.


ERROR: Projection of dataset does not appear to match current location.

   Location PROJ_INFO is:
   name: Universal Transverse Mercator
   proj: utm
   datum: wgs84
   ellps: wgs84
   zone: 33
   no_defs: defined

   Dataset PROJ_INFO is:
   name: Universal Transverse Mercator
   proj: utm
   datum: wgs84
   ellps: wgs84
   zone: 35
   no_defs: defined

   ERROR: zone
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user