Re: [GRASS-user] Issues with 8.0.dev
On Thu, 23 Sep 2021, Rich Shepard wrote: There are some issues that did not occur before. More: g.region vect=channel_countour_lines ERROR: Vector map not found GRASS new_loc/bathymetry:new_loc > g.list type=vect channel_contour_lines GRASS new_loc/bathymetry:new_loc > d.erase python3: can't open file '/data/grassdata/new_loc/bathymetry/.tmp/salmo/MONITORS/wx0/render.py': [Errno 2] No such file or directory Huh? Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Issues with 8.0.dev
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 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
[GRASS-user] GRASS8.0dev not recognizing raster maps
This is probably PBKAC (Problem Between Keyboard And Chair) and I'm not seeing why. I created a location using a .tif file for the projection and region information. Then, using r.in.gdal I imported 77 .tif maps. The location is columbia_river_dtms, the mapset is PERMANENT, and in fcells are the maps: ]$ ls PERMANENT/fcell/ dtm_110 dtm_142 dtm_15 dtm_175 dtm_181 dtm_208 dtm_215 dtm_31 dtm_39 dtm_48 dtm_64 dtm_111 dtm_143 dtm_150 dtm_176 dtm_182 dtm_209 dtm_243 dtm_33 dtm_4 dtm_49 dtm_71 dtm_112 dtm_144 dtm_151 dtm_177 dtm_183 dtm_210 dtm_244 dtm_34 dtm_40 dtm_5 dtm_79 dtm_113 dtm_145 dtm_152 dtm_178 dtm_184 dtm_211 dtm_251 dtm_35 dtm_41 dtm_50 dtm_80 dtm_12 dtm_146 dtm_16 dtm_179 dtm_19 dtm_212 dtm_252 dtm_36 dtm_42 dtm_51 dtm_81 dtm_13 dtm_147 dtm_17 dtm_18 dtm_205 dtm_213 dtm_274 dtm_37 dtm_43 dtm_6 dtm_82 dtm_14 dtm_148 dtm_174 dtm_180 dtm_206 dtm_214 dtm_30 dtm_38 dtm_44 dtm_63 However, when I start grass in that location (/data/grassdata/columbia_river_dtms) g.list type=rast produces no list of maps. When I try to display a map on wx0 grass responds: d.rast map=dtm_110 ERROR: Raster map not found What might I be doing wrong? Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Project from UTM to State Plane & define region [UPDATE]
On Thu, 23 Sep 2021, Rich Shepard wrote: Am I correct in thinking that now I have the projection correct I can reproject a map then set the region to it? Nope. Won't reproject a raster map. The projection information is somehow still incomplete. See my fist message on this thread. Help's still needed. Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Project from UTM to State Plane & define region [UPDATE]
On Thu, 23 Sep 2021, Rich Shepard wrote: I need help to get out of the weeds in which I floundered. Apparently creating the location with the EPSG code of 2856 was insufficient to define all CRS parameters and the region. Progress has been made, but there's a discrepancy in the outputs of g.proj and g.region that I want to resolve: g.proj -p -PROJ_INFO- name : NAD83(HARN) / Washington South datum : nad83harn ellps : grs80 proj : lcc lat_0 : 45.3 lon_0 : -120.5 lat_1 : 47.3 lat_2 : 45.8 x_0: 50 y_0: 0 no_defs: defined -PROJ_SRID- SRID : EPSG:2856 -PROJ_UNITS unit : meter units : meters meters : 1 g.region -p projection: 99 (NAD83(HARN) / Washington South) zone: 0 datum: nad83harn ellipsoid: grs80 north: 1 south: 0 west: 0 east: 1 nsres: 1 ewres: 1 rows: 1 cols: 1 cells: 1 Am I correct in thinking that now I have the projection correct I can reproject a map then set the region to it? Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Project from UTM to State Plane & define region
On Thu, 23 Sep 2021, Rich Shepard wrote: I need help to get out of the weeds in which I floundered. Apparently creating the location with the EPSG code of 2856 was insufficient to define all CRS parameters and the region. Reading the g.proj manual page I tried: g.proj -c "+inv +proj=lcc +lat_0=45.3 +lon_0=-120.5 +lat_1=47.3 +lat_2=45.8 +x_0=50 +y_0=0 +ellps=GRS80" Which resulted in an error and wiped out the PROJ_INFO file so g.region -p was almost all blanks. Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Project from UTM to State Plane & define region
Having created a new location using EPSG:2856 I tried to reproject a mapset that defines the region I want to use for this project: r.proj loc= map=bathymetry in=local_depths The result was not as I expected: Found 3 possible transformations Operation 1: Description: Inverse of SPCS83 Washington South zone (meters) + Inverse of NAD83 to NAD83(HARN) (28) + UTM zone 10N Area of use: United States (USA) - Oregon and Washington. Accuracy within area of use: 0.05 m PROJ string: +proj=pipeline +step +inv +proj=lcc +lat_0=45.3 +lon_0=-120.5 +lat_1=47.3 +lat_2=45.8 +x_0=50 +y_0=0 +ellps=GRS80 +step +inv +proj=hgridshift +grids=us_noaa_WO.tif +step +proj=utm +zone=10 +ellps=GRS80 This is the most appropriate as the other two are used in the whole world and states other than Washington and Oregon. But, I don't know how to use this information now that GRASS gave it to me. The second problem is: ERROR: Input raster map is outside current region g.region -p projection: 99 (NAD83(HARN) / Washington South) zone: 0 datum: nad83harn ellipsoid: grs80 north: 1 south: 0 west: 0 east: 1 nsres: 1 ewres: 1 rows: 1 cols: 1 cells: 1 I need help to get out of the weeds in which I floundered. Apparently creating the location with the EPSG code of 2856 was insufficient to define all CRS parameters and the region. TIA, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Which EPSG code for location default?
On Thu, 23 Sep 2021, Jeff McKenna wrote: - goto https://epsg.org Jeff, Thanks for excellent advice. I decided to be consistent and use the NAD83(HARN)/meters EPSG for Washington South to be consistent with what I've used in other projects and other states. That EPSG code is 2856. Now I'll create a new location with that projection and reproject all imported maps to that location and rename it to the project's location name. I think it was in the late 1980s-early 1990s that I used UTM zones before switching to State Plane Coordinates. On this project the first data set I imported used UTM Zone 10 and I stuck with it ... until now. Regards, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Which EPSG code for location default?
On Thu, 23 Sep 2021, Micha Silver wrote: IMHO you should *not* do that. Just create a new Location. Micha, I thought that would be the answer. Then I need to reproject all data at least twice, then rename the new location. Regards, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Which EPSG code for location default?
On 9/23/21 3:38 PM, Rich Shepard wrote: Yet, ... I have a question: is there a way in grass to change the PROJ_INFO in the PERMANENT mapset of a location to a new projecion? Or, do I manually edit that file? IMHO you should *not* do that. Just create a new Location. Thanks in advance, 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 https://orcid.org/-0002-1128-1325 ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Which EPSG code for location default?
On Thu, 23 Sep 2021, Jeff McKenna wrote: On 2021-09-23 8:55 a.m., Jeff McKenna wrote: NAD83 / UTM zone 10N + NAVD88 It could also be that no one yet has submitted this to the EPSG geodetic committee, for inclusion (UTM zone 10N with that vertical datum). *hint* *maybe you should* (PS I've submitted several, just use the mindset "well someone has to") Jeff, Interesting. Actually, since this project (like all of them) have data sources using different projections I don't care which is used as long as I can reproject data from the source to a single appropriate one. I could use Washington State Plane (South) and that would work just as well, So.all of my answers to you are very unhelpful, ha. Not at all. But that's all I've got for you now. And that's good enough. Yet, ... I have a question: is there a way in grass to change the PROJ_INFO in the PERMANENT mapset of a location to a new projecion? Or, do I manually edit that file? Thanks in advance, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Which EPSG code for location default?
On Thu, 23 Sep 2021, Jeff McKenna wrote: Taking a look at your output, my brain said "good question", ha. Jeff, There are so many value-specific codes I didn't see an overall code. Usually the key line to look for is the "AUTHORITY:" line, which yours lacks. Ah-ha. That's good information. So the usual next step is to start searching on https://epsg.io for the text "UTM zone 10N". But more recently the official EPSG homepage includes a search tool that does a live search on its own database (giving guaranteed accurate/uptodate responses): - goto https://epsg.org - click the top menu: EPSG Dataset/Text Search - enter: UTM zone 10N and press "Go" - gives a response of 12 items EPSG:26910 does look somewhat similar :) I'll check for myself; I had the impression that all EPSG codes were four digits. Hope that gives you some hints... (at least on the official EPSG code perspective) It certainly does. Thanks very much, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Which EPSG code for location default?
On 2021-09-23 8:55 a.m., Jeff McKenna wrote: NAD83 / UTM zone 10N + NAVD88 It could also be that no one yet has submitted this to the EPSG geodetic committee, for inclusion (UTM zone 10N with that vertical datum). *hint* *maybe you should* (PS I've submitted several, just use the mindset "well someone has to") So.all of my answers to you are very unhelpful, ha. But that's all I've got for you now. -jeff -- Jeff McKenna GatewayGeo: Developers of MS4W, MapServer Consulting and Training co-founder of FOSS4G http://gatewaygeo.com/ ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Which EPSG code for location default?
Hi Rich, Taking a look at your output, my brain said "good question", ha. Usually the key line to look for is the "AUTHORITY:" line, which yours lacks. So the usual next step is to start searching on https://epsg.io for the text "UTM zone 10N". But more recently the official EPSG homepage includes a search tool that does a live search on its own database (giving guaranteed accurate/uptodate responses): - goto https://epsg.org - click the top menu: EPSG Dataset/Text Search - enter: UTM zone 10N and press "Go" - gives a response of 12 items EPSG:26910 does look somewhat similar :) Hope that gives you some hints... (at least on the official EPSG code perspective) -jeff -- Jeff McKenna GatewayGeo: Developers of MS4W, MapServer Consulting and Training co-founder of FOSS4G http://gatewaygeo.com/ On 2021-09-22 7:49 p.m., Rich Shepard wrote: Applying gdalsrsinfo to a shapefile's .prj produced these results: PROJ.4 : +proj=utm +zone=10 +datum=NAD83 +units=m +vunits=m +no_defs OGC WKT2:2018 : COMPOUNDCRS["NAD83 / UTM zone 10N + NAVD88 height", PROJCRS["NAD83 / UTM zone 10N", BASEGEOGCRS["NAD83", DATUM["North American Datum 1983", ELLIPSOID["GRS 1980",6378137,298.257222101, LENGTHUNIT["metre",1]], ID["EPSG",6269]], PRIMEM["Greenwich",0, ANGLEUNIT["Degree",0.0174532925199433]]], CONVERSION["UTM zone 10N", METHOD["Transverse Mercator", ID["EPSG",9807]], PARAMETER["Latitude of natural origin",0, ANGLEUNIT["Degree",0.0174532925199433], ID["EPSG",8801]], PARAMETER["Longitude of natural origin",-123, ANGLEUNIT["Degree",0.0174532925199433], ID["EPSG",8802]], PARAMETER["Scale factor at natural origin",0.9996, SCALEUNIT["unity",1], ID["EPSG",8805]], PARAMETER["False easting",50, LENGTHUNIT["metre",1], ID["EPSG",8806]], PARAMETER["False northing",0, LENGTHUNIT["metre",1], ID["EPSG",8807]], ID["EPSG",16010]], CS[Cartesian,2], AXIS["(E)",east, ORDER[1], LENGTHUNIT["metre",1, ID["EPSG",9001]]], AXIS["(N)",north, ORDER[2], LENGTHUNIT["metre",1, ID["EPSG",9001, VERTCRS["NAVD88 height", VDATUM["North American Vertical Datum 1988"], CS[vertical,1], AXIS["gravity-related height (H)",up, LENGTHUNIT["metre",1, ID["EPSG",9001] The data are the Columbia River and southern Washington state. It's been a couple of decades since I last dug into proj and I'd appreciate being pointed to a document that will teach me which of the several EPSG codes above is the one to which I want to apply to PROJ_INFO in the PERMANENT mapset. 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
