On Sun, 15 Sep 2019, Markus Metz wrote:
You should now use
r.proj loc=Oregon map=topography in=n45w121
and not r.unpack, that is a completely different workflow that has nothing
to do with reprojection.
Markus M,
I've tried two approaches to getting the 10m DEM (upper, left corner at 46N,
On Sun, Sep 15, 2019 at 8:39 PM Rich Shepard
wrote:
>
> On Sat, 14 Sep 2019, Markus Metz wrote:
>
> > gdalwarp estimates the target extents unless you use the -te option. In
> > contrast, r.proj uses the current region. r.proj can estimate the target
> > extents with the -p or -g flag. I suggest
On Sat, 14 Sep 2019, Markus Metz wrote:
gdalwarp estimates the target extents unless you use the -te option. In
contrast, r.proj uses the current region. r.proj can estimate the target
extents with the -p or -g flag. I suggest to first check you current
region in the target location/mapset and
On Sun, 15 Sep 2019, Markus Neteler wrote:
How do I copy maps from one location to another when the projection of both
is the same?
With r.pack/v.pack, then r.unpack/v.unpack.
Markus,
Well! I definitely missed recognizing these as the answer when I looked at
the list of modules. Perhaps
Rich Shepard schrieb am So., 15. Sep. 2019,
01:47:
>
> How do I copy maps from one location to another when the projection of both
> is the same?
>
With r.pack/v.pack, then r.unpack/v.unpack.
Markus
___
grass-user mailing list
On Sat, 14 Sep 2019, Rich Shepard wrote:
Stepping away from the issue for a while often lets in the light of
understanding, as it did in this case.
Wrong. The source and destination locations have the same projections:
Input:
name: NAD83(HARN) / Oregon North
datum: nad83harn
ellps: grs80
On Fri, 13 Sep 2019, Rich Shepard wrote:
Reprojecting a 10m DEM fails. Following are the command and input/output
projection and map description information. Screenshots of the input and
output maps are attached.
I need to understand why the output is wrong.
Stepping away from the issue for
On Sat, Sep 14, 2019 at 1:15 AM Helmut Kudrnovsky wrote:
>
> Rich Shepard wrote
> > Reprojecting a 10m DEM fails. Following are the command and input/output
> > projection and map description information. Screenshots of the input and
> > output maps are attached.
> >
> > I need to understand why
On Fri, 13 Sep 2019, Helmut Kudrnovsky wrote:
a good thing to see if reprojection of raster data works correctly, is
comparing before/after r.proj with gdalwarp (1) results.
(1) https://gdal.org/programs/gdalwarp.html#gdalwarp
Helmut,
I'll try gdalwarp. Scanning that web page suggests it
Rich Shepard wrote
> Reprojecting a 10m DEM fails. Following are the command and input/output
> projection and map description information. Screenshots of the input and
> output maps are attached.
>
> I need to understand why the output is wrong.
>
> Command:
> r.proj loc=Oregon map=topography
10 matches
Mail list logo
