Having some problems moving some landsat 8 composite images into a different location/mapset with the same projection. Have tried r.proj (this produces the ‘ERROR: Input raster map is outside current region’) and v.in.region method (this produces a ‘blank’ map). Not sure if the resolutions need changing with g.region?
On Tue, Mar 24, 2015 at 2:09 PM, Paul Shapley <p.shapley@gmail.com> wrote:
Hi Users,
Having some problems moving some landsat 8 composite images into a different
location/mapset with the same projection. Have tried r.proj (this produces
.. please do not reproject, it will alter the data.
For simple moving (different locations, same projection), use r.pack
and r.unpack.
On Tue, Mar 24, 2015 at 9:18 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi Paul,
On Tue, Mar 24, 2015 at 2:09 PM, Paul Shapley <p.shapley@gmail.com> wrote:
> Hi Users,
>
> Having some problems moving some landsat 8 composite images into a
different
> location/mapset with the same projection. Have tried r.proj (this
produces
.. please do not reproject, it will alter the data.
For simple moving (different locations, same projection), use r.pack
and r.unpack.
So I guess we miss a version of g.copy which would be able to copy from
different Database/Location (with same-projection check)? (Even
implementation through r|v.pack and unpack would be possible.)