[GRASS-user] Re-projection fails

I've started a new thread on this issue: it's more specific.

The script that imports the LiDAR topographic map works:

GRASS Dixie_Mountain_2010_LiDAR/PERMANENT:~ > r.in.gdal in=$HOME/projects/oregon/northside-rock/data/LDQ-45122F8/2010-USACE-Columbia-River/Bare_Earth/be45122f8/hdr.adf out=2010_topo mem=2000 --o
Importing raster map <2010_topo>...
  100%
GRASS Dixie_Mountain_2010_LiDAR/PERMANENT:~ > g.list type=raster
2010_topo

The imported 2010_topo exists in the designated location and mapset.

But, the script to re-project this map fails. I think it has something to do
with how I'm mis-using Micha's suggestion of assigning the re-projected
output to an environmental variable, NSR.

grass /data1/grassdata/Oregon/PERMANENT

g.mapset -c NSR_2010_DEM

GRASS Oregon/NSR_2010_DEM:~ > NSR=`r.proj -g loc=Dixie_Mountain_2010_LiDAR map=PERMANENT in=2010_topo method=lanczos mem=2000 --o`
Input map <2010_topo@PERMANENT> in location <Dixie_Mountain_2010_LiDAR>:
Selected PROJ pipeline:
+proj=pipeline +step +inv +proj=utm +zone=10 +ellps=GRS80 +step +proj=lcc
+lat_0=43.6666666666667 +lon_0=-120.5 +lat_1=46 +lat_2=44.3333333333333
+x_0=2500000 +y_0=0 +ellps=GRS80
************************
GRASS Oregon/NSR_2010_DEM:~ > g.list type=rast
GRASS Oregon/NSR_2010_DEM:~ >

There's no output and I'm not seeing why that is.

TIA,

Rich

···

On 01/05/2023 19:52, Rich Shepard wrote:

I’ve started a new thread on this issue: it’s more specific.

The script that imports the LiDAR topographic map works:

GRASS Dixie_Mountain_2010_LiDAR/PERMANENT:~ > r.in.gdal in=$HOME/projects/oregon/northside-rock/data/LDQ-45122F8/2010-USACE-Columbia-River/Bare_Earth/be45122f8/hdr.adf out=2010_topo mem=2000 --o

First comment: I think you should not have GRASS map names starting with a digit.

Can you change the above to

output=topo_2010

??

Importing raster map <2010_topo>…
100%
GRASS Dixie_Mountain_2010_LiDAR/PERMANENT:~ > g.list type=raster
2010_topo

The imported 2010_topo exists in the designated location and mapset.

But, the script to re-project this map fails. I think it has something to do
with how I’m mis-using Micha’s suggestion of assigning the re-projected
output to an environmental variable, NSR.

grass /data1/grassdata/Oregon/PERMANENT

g.mapset -c NSR_2010_DEM

GRASS Oregon/NSR_2010_DEM:~ > NSR=r.proj -g loc=Dixie_Mountain_2010_LiDAR map=PERMANENT in=2010_topo method=lanczos mem=2000 --o
Input map 2010_topo@PERMANENT in location <Dixie_Mountain_2010_LiDAR>:
Selected PROJ pipeline:
+proj=pipeline +step +inv +proj=utm +zone=10 +ellps=GRS80 +step +proj=lcc
+lat_0=43.6666666666667 +lon_0=-120.5 +lat_1=46 +lat_2=44.3333333333333
+x_0=2500000 +y_0=0 +ellps=GRS80


GRASS Oregon/NSR_2010_DEM:~ > g.list type=rast
GRASS Oregon/NSR_2010_DEM:~ >

The first run of r.proj (with the -g flag) only gives you the target region settings. You now need to set the region with those settings, and then run r.proj again (without -g) do actually do the work.

g.region -ap $NSR

r.proj loc=Dixie_Mountain_2010_LiDAR map=PERMANENT in=2010_topo method=lanczos mem=2000 output=topo_2010 --o

There’s no output and I’m not seeing why that is.

TIA,

Rich


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

-- 
Micha Silver
Ben Gurion Univ.
Sde Boker, Remote Sensing Lab
cell: +972-523-665918

On Mon, 1 May 2023, Micha Silver wrote:

First comment: I think you should not have GRASS map names starting with a digit.

Micha,

I should know better. Darn!

Can you change the above to
output=topo_2010

Done.

The first run of r.proj (with the -g flag) only gives you the target
region settings. You now need to set the region with those settings, and
then run r.proj again (without -g) do actually do the work.

g.region -ap $NSR

r.proj loc=Dixie_Mountain_2010_LiDAR map=PERMANENT in=2010_topo method=lanczos mem=2000 output=topo_2010 --o

I wondered about that. I've certainly forgotten a lot of grass since I last
used it.

All fixed now.

Many thanks for your patience, Micha.

Regards,

Rich