Re: [GRASS-user] Starting GRASS [RESOLVED]
On Sun, 26 Sep 2021, Moritz Lennert wrote: As mentioned in an earlier mail: you have to include the mapset directory in the path. Moritz, Mea culpa! I point to the location but not the specific mapset. I was likely insufficiently uncaffinated when I tried to invoke GRASS. Thinking back to when I used the GUI I always had to select a location and a mapset. Why I haven't remembered this is my problem. Advice firmly set in my grey tissue. Thanks, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Starting GRASS
Rich, As mentioned in an earlier mail: you have to include the mapset directory in the path. Moritz Le 26 septembre 2021 16:28:59 GMT+02:00, Rich Shepard a écrit : >I don't know why I'm suddenly having problems starting GRASS when it's never >before been an issue. I should be able to be in any directory when GRASS is >started because ~/.grass80/rc lists the GISDBASE as /data/grassdata. I >assume that the location in that file can be replaced by specifying the >location onthe command line. > >But, this is not working. > >[rshepard@salmo ~]$ grass /data/grassdata/columbia_river_dtms >Starting GRASS GIS... >ERROR: is not a valid GRASS Location because PERMANENT >Mapset is missing >Maybe you meant a different directory. >Exiting... > >/data/grassdata is the GISDBASE, not a location. I get the same error if the >PWD is /data/grassdata or if I specify the fully-qualified path on the >command line. I'm out of ideas why I'm now having these issues and a clue >stick will be very helpful. > >TIA, > >Rich >___ >grass-user mailing list >grass-user@lists.osgeo.org >https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Starting GRASS
I don't know why I'm suddenly having problems starting GRASS when it's never before been an issue. I should be able to be in any directory when GRASS is started because ~/.grass80/rc lists the GISDBASE as /data/grassdata. I assume that the location in that file can be replaced by specifying the location onthe command line. But, this is not working. [rshepard@salmo ~]$ grass /data/grassdata/columbia_river_dtms Starting GRASS GIS... ERROR: is not a valid GRASS Location because PERMANENT Mapset is missing Maybe you meant a different directory. Exiting... /data/grassdata is the GISDBASE, not a location. I get the same error if the PWD is /data/grassdata or if I specify the fully-qualified path on the command line. I'm out of ideas why I'm now having these issues and a clue stick will be very helpful. TIA, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] imported .tif maps lose all data
On Sun, 26 Sep 2021, Moritz Lennert wrote: If you set your region correctly before importing all the files, you could also use the -r flag of r.in.gdal, no ? Moritz, The problem is that I don't know the region's extents now. The project location is a point and I have bathymetric and topographic maps that extend well behond that point. Thanks, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] imported .tif maps lose all data
If you set your region correctly before importing all the files, you could also use the -r flag of r.in.gdal, no ? Might possibly be slower, though, then determining which files to import before running r.in.gdal as Micha suggests Moritz Le 26 septembre 2021 14:44:46 GMT+02:00, Rich Shepard a écrit : >On Sun, 26 Sep 2021, Micha Silver wrote: > >> If that's the case, perhaps a quick `gdalinfo` loop over all 77 topography >> maps in advance will help to find the relevant ones. You get the corner >> coordinates in the gdalinfo output, so you'll be able to find those that >> overlap the project region before importing to GRASS. > >Micha, > >That's an excellent idea. I was going to use r.info or r.report on all maps >and build a text table of the corners, then find the minimum and maximum of >each corner and build the region using those values. > >I have the lon-lat of the project area and can reproject that to State Plane >then find the one or two maps that enclose that area. > >It's common for many of us who are closely focused on an issue to not see >other possibilities. Outsiders see things we don't. > >Toda, > >Rich > >___ >grass-user mailing list >grass-user@lists.osgeo.org >https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] imported .tif maps lose all data
On Sun, 26 Sep 2021, Micha Silver wrote: If that's the case, perhaps a quick `gdalinfo` loop over all 77 topography maps in advance will help to find the relevant ones. You get the corner coordinates in the gdalinfo output, so you'll be able to find those that overlap the project region before importing to GRASS. Micha, That's an excellent idea. I was going to use r.info or r.report on all maps and build a text table of the corners, then find the minimum and maximum of each corner and build the region using those values. I have the lon-lat of the project area and can reproject that to State Plane then find the one or two maps that enclose that area. It's common for many of us who are closely focused on an issue to not see other possibilities. Outsiders see things we don't. Toda, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] imported .tif maps lose all data
Hi Rich: On 9/26/21 2:36 AM, Rich Shepard wrote: All my previous work with GRASS since 4.0 had one large map that covered a larger region than needed for the project so I would define a project area within it. These LiDAR topography maps cover a very large spatial area and I have no idea with one (or two) actually include the project's area. So I need to import them all then find the appropriate one or two. If that's the case, perhaps a quick `gdalinfo` loop over all 77 topography maps in advance will help to find the relevant ones. You get the corner coordinates in the gdalinfo output, so you'll be able to find those that overlap the project region before importing to GRASS. Micha 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 ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
