Re: [GRASS-user] Issues with 8.0.dev
On Fri, 24 Sep 2021, Maris Nartiss wrote: first – loc should be just "lon_lat" without a full path. Use dbase parameter if location is in a different GISDBASE. second – map names are without "/". Māris, Some times I seemed to have issues with 'first' if I didn't put in the full path to the GISDBASE. My fault on 'second'. I highlighted and copied rather than rekeyboarding. third – you do not reproject or copy to PWD. You always do actions in the mapset you selected at the start of GRASS work session. GRASS is designed with pull not push in mind – you always pull into active mapset. Reprojection – pull from source location/mapset to current mapset (and thus the CRS of current Location). It is the in the PWD of the desired target mapset in which I start GRASS. Hope this helps to clarify things. Yep. It was 1 and 2 that were the problem. Thanks again, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Issues with 8.0.dev
On Fri, 24 Sep 2021, Maris Nartiss wrote: How did you do the copying? I just tested copying, displaying and removing without problems. Probably you should provide exact commands you used to aid reproduction or spotting a problem. Māris, I provided the commands and the results in my original messages. I'll try again today and see if anything's different after logging out overnight and logging back in on this host. Regards, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Issues with 8.0.dev
On Fri, 24 Sep 2021, Micha Silver wrote: What do you mean by "put it in the wrong mapset"? You can't put the output of v.proj or r.proj into anything but the current mapset. If you tried to set the output name with a '/' then that's the source of the problem. Micha, You are, of course, correct. Yet, when the current mapset is not the one in which you want that map it's the wrong one. It's not GRASS that put it in the wrong mapset it was my starting grass in the wrong mapset and not changing before importing/reprojecting. I had target_location/mapset1 and target_location/mapset2. With grass in target_location/mapset1 I imported the data. It belongs in mapset2. So it was in the wrong mapset for this project. I copied it from mapset1 to mapset2, the removed it from mapset1. Regards, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Issues with 8.0.dev
Hi Rich: On 9/24/21 12:17 AM, Rich Shepard wrote: Today I pulled changes from the main branch, configured, built, and installed the latest source from the 8.0.dev source. When I start grass I see what I believe is the build number: Welcome to GRASS GIS 8.0.dev (63fca9fb2) There are some issues that did not occur before. For example, I reprojected a vector map from one location to another, but put it in the wrong mapset on the new location. I copied it from one mapset What do you mean by "put it in the wrong mapset"? You can't put the output of v.proj or r.proj into anything but the current mapset. If you tried to set the output name with a '/' then that's the source of the problem. Another point caught my eye in an earlier post. You mentioned the need to reproject some data twice. I can't imagine any workflow where that would be necessary. Suppose you got some data in three different coordinate systems, projA, projB and projC. And you chose to do all your work in projC. Then: * You create three locations, let's call them tmp_loc_A, tmp_loc_B and working_loc_C. * Start grass in tmp_loc_A: grass /tmp_loc_A/PERMANENT * and import the data that is in that CRS. Probably r.external and v.external would be OK to save disk space. * Switch to tmp_loc_B and get the data that is in that CRS:g.mapset loc=tmp_loc_B map=PERMANENT then r.external, v.external as needed * Switch to working_loc_C, g.mapset loc=working_loc_C map=PERMANENT * and reproject all vector and raster maps from each of tmp_loc_A and tmp_loc_B: v.proj loc=tmp_loc_A map=PERMANENT input=vector_1; r.proj loc=tmp_loc_A map=PERMANENT input=raster_1, etc. etc...Same for tmp_loc_B * Now you can blow away both tmp_loc_A and tmp_loc_B HTH, Micha to the other but when I try to remove it from the wrong mapset (g.mapset -p shows features) I get an error: g.remove -f type=vect name=channel_contour_lines Removing vector WARNING: Illegal filename . Character not allowed. WARNING: Illegal filename . Character not allowed. ERROR: Vector map not found in current mapset g.list type=vect WARNING: Illegal filename . Character not allowed. channel_contour_lines the_property Thoughts? 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
