Re: [GRASS-user] r.slope.aspect: rejects DCELL precison for map with DCELL precision
On Wed, May 10, 2023 at 9:14 PM Rich Shepard wrote: > I don't understand why a raster elevation map with DCELL precision is > rejected by r.slope.aspect. The region was set to the vector analysis area. > > r.info tells me this about the elevation map: > > ++ > | Map: dem2014Date: Wed May 10 13:47:46 > 2023| > | Mapset: northside_rock Login of Creator: rshepard > | > | Location: Oregon > | > | DataBase: /data1/grassdata > | > | Title:dem_2014 > | > | Timestamp: none > | > > || > | > | > | Type of Map: raster Number of Categories: 0 > | > | Data Type:DCELLSemantic label: (none) > | > | Rows: 1037 > | > | Columns: 1056 > | > | Total Cells: 1095072 > | > |Projection: NAD83(CORS96) / Oregon North > | > |N: 224201S: 223164 Res: 1 > | > |E: 2307121.58W:2306066 Res: 0.99960227 > | > | Range of data:min = 240 max = 820 > | > | > | > | Data Description: > | > |generated by r.surf.contour > | > | > | > | Comments: > | > |r.surf.contour --overwrite input="baseline_dem" output="dem_2014" > | > | > | > > ++ > > grass reports (with the module usage redacted): > r.slope.aspect elev=dem2014 slope=dem2014_slope aspect=dem2014_aspect > format=degrees precision=DCELLl pcurv=dem2014_pcurve dx=dem2014_ew_slope > dy=dem2014_ns_slope mem=2000 --o > Generates raster maps of slope, aspect, curvatures and partial derivatives > from an elevation raster map. > ... > > ERROR: Value out of range for parameter > Legal range: CELL,FCELL,DCELL > > What exactly is out of range? > It's a typo in "DCELL" > > 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
Re: [GRASS-user] v.to.rast questions
On Wed, May 10, 2023 at 12:34 PM Rich Shepard wrote: > On Wed, 10 May 2023, Anna Petrášová wrote: > > > Sounds like the vector geometry was already 3D, that's the case when you > > use use=z. If the vector would be 2D (see v.info) you would have to use > the > > attribute table. > > Anna, > > When I used the 2D file, regardless of which parameter I used or both, > v.to.rast told me the file was not 3D. That's why I converted it. When > 'use=z' failed I tried 'attribute_column=ContourEle' with the same result. > > Now I have the rasterized contour map (image attached) and need to learn > how > to use it to create flowlines, flow accumulations, and more. It does not > have the 1'x1' cells each with a color representing the elevation. > > Is there an r.* module to interpolate elevations between the contour lines > so I have cells? > There is r.surf.contour, so that sounds like the tool you need. > > This is all new to me so I appreciate all the help I get. > > Regards, > > 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] r.slope.aspect: rejects DCELL precison for map with DCELL precision
I don't understand why a raster elevation map with DCELL precision is rejected by r.slope.aspect. The region was set to the vector analysis area. r.info tells me this about the elevation map: ++ | Map: dem2014Date: Wed May 10 13:47:46 2023| | Mapset: northside_rock Login of Creator: rshepard| | Location: Oregon | | DataBase: /data1/grassdata | | Title:dem_2014 | | Timestamp: none| || || | Type of Map: raster Number of Categories: 0 | | Data Type:DCELLSemantic label: (none)| | Rows: 1037 | | Columns: 1056 | | Total Cells: 1095072| |Projection: NAD83(CORS96) / Oregon North| |N: 224201S: 223164 Res: 1 | |E: 2307121.58W:2306066 Res: 0.99960227| | Range of data:min = 240 max = 820 | || | Data Description:| |generated by r.surf.contour | || | Comments:| |r.surf.contour --overwrite input="baseline_dem" output="dem_2014" | || ++ grass reports (with the module usage redacted): r.slope.aspect elev=dem2014 slope=dem2014_slope aspect=dem2014_aspect format=degrees precision=DCELLl pcurv=dem2014_pcurve dx=dem2014_ew_slope dy=dem2014_ns_slope mem=2000 --o Generates raster maps of slope, aspect, curvatures and partial derivatives from an elevation raster map. ... ERROR: Value out of range for parameter Legal range: CELL,FCELL,DCELL What exactly is out of range? TIA, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast: advice needed
On Wed, 10 May 2023, Rich Shepard wrote: Thanks very much. I'm learning many new things on this project and still need to meet regulator's deadlines. Markus, The wiki page on 'Contour lines to DEM' is what I need. Best regards, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast: advice needed
On Wed, 10 May 2023, Markus Neteler wrote: In addition, here is an overview page: https://grasswiki.osgeo.org/wiki/Interpolation Markus, Thanks very much. I'm learning many new things on this project and still need to meet regulator's deadlines. Much appreciated, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast: advice needed
Hi, In addition, here is an overview page: https://grasswiki.osgeo.org/wiki/Interpolation Markus On Wed, May 10, 2023 at 8:16 PM Maris Nartiss wrote: > > I think you need to interpolate and not simply convert vector lines to > raster lines. Make sure lines have an attribute with elevation (or z > coordinate) and use e.g. v.surf.rst module. > > Māris. > > trešd., 2023. g. 10. maijs, plkst. 17:29 — lietotājs Rich Shepard > () rakstīja: > > > > I need to convert a vector contour map to a raster so I can apply the > > hydrologic models modules. > > > > Reading the v.to.rast manual page I learned that I needed to add categories > > to the input contour map. Running v.category added no categories: "0 > > features added." > > > > v.info does not tell me anything about the elevation values of the contour > > lines. Looking at the v.* modules, and trying v.univar, didn't help. I could > > try v.to.3d, but I need information about the vector map's contents. > > > > Which v.db* should I use to find the elevation colum associated with each > > contour line? > > > > 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 -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast: advice needed
On Wed, 10 May 2023, Maris Nartiss wrote: I think you need to interpolate and not simply convert vector lines to raster lines. Make sure lines have an attribute with elevation (or z coordinate) and use e.g. v.surf.rst module. Māris. Interpolating the vector contour file before rasterizing makes sense to me, too. Never before having to convert a vector elevation contour file to a raster file I'd no idea which v.surf.* module to apply. The vector file has a ContourEle attribute with the elevation values. I'm taking your advice and will use v.surf.rast. This project has more topography data issues than any I've encountered since I started using grass with version 4.0 (all integer, all CLI.) Very much appreciated, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast: advice needed
I think you need to interpolate and not simply convert vector lines to raster lines. Make sure lines have an attribute with elevation (or z coordinate) and use e.g. v.surf.rst module. Māris. trešd., 2023. g. 10. maijs, plkst. 17:29 — lietotājs Rich Shepard () rakstīja: > > I need to convert a vector contour map to a raster so I can apply the > hydrologic models modules. > > Reading the v.to.rast manual page I learned that I needed to add categories > to the input contour map. Running v.category added no categories: "0 > features added." > > v.info does not tell me anything about the elevation values of the contour > lines. Looking at the v.* modules, and trying v.univar, didn't help. I could > try v.to.3d, but I need information about the vector map's contents. > > Which v.db* should I use to find the elevation colum associated with each > contour line? > > 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
Re: [GRASS-user] v.to.rast questions
On Wed, 10 May 2023, Rich Shepard wrote: There are several r.resamp.* modules in the core distribution. Please advise me which would be most appropriate for my rasterized contour elevation map. Should I use one of the v.surf.* modules then re-rasterize the resulting map? If so, please recommend the most appropriate v.surf.* module and recommended parameters to use. TIA, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast questions
On Wed, 10 May 2023, Rich Shepard wrote: Is there an r.* module to interpolate elevations between the contour lines so I have cells? There are several r.resamp.* modules in the core distribution. Please advise me which would be most appropriate for my rasterized contour elevation map. TIA, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast questions
On Wed, 10 May 2023, Anna Petrášová wrote: Sounds like the vector geometry was already 3D, that's the case when you use use=z. If the vector would be 2D (see v.info) you would have to use the attribute table. Anna, When I used the 2D file, regardless of which parameter I used or both, v.to.rast told me the file was not 3D. That's why I converted it. When 'use=z' failed I tried 'attribute_column=ContourEle' with the same result. Now I have the rasterized contour map (image attached) and need to learn how to use it to create flowlines, flow accumulations, and more. It does not have the 1'x1' cells each with a color representing the elevation. Is there an r.* module to interpolate elevations between the contour lines so I have cells? This is all new to me so I appreciate all the help I get. Regards, Rich___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast questions
Sounds like the vector geometry was already 3D, that's the case when you use use=z. If the vector would be 2D (see v.info) you would have to use the attribute table. On Wed, May 10, 2023 at 12:14 PM Rich Shepard wrote: > My current topographic vector data file has a column name for the elevation > data, ContourEle. Reading the v.to.rast page there is a use parameter (with > 'z' for elevation) and an attribute_column parmater. Because the vector > map's database table does not have a column named 'z', but the one named > 'CountourEle' I put both parameters on the command line. > > grass told me that I cannot have both, and that using the named elevation > column was not allowed. So I put 'use=z' in the command and the conversion > worked. > > How did v.to.rast know that the column named 'ContourEle' was the z value? > > Should the manual page explain that the use and attribute_column cannot be > used together for elevation? And, when the attribute_column would be > appropriate? > > Regards, > > 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] v.to.rast questions
My current topographic vector data file has a column name for the elevation data, ContourEle. Reading the v.to.rast page there is a use parameter (with 'z' for elevation) and an attribute_column parmater. Because the vector map's database table does not have a column named 'z', but the one named 'CountourEle' I put both parameters on the command line. grass told me that I cannot have both, and that using the named elevation column was not allowed. So I put 'use=z' in the command and the conversion worked. How did v.to.rast know that the column named 'ContourEle' was the z value? Should the manual page explain that the use and attribute_column cannot be used together for elevation? And, when the attribute_column would be appropriate? Regards, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.to.rast: advice needed [RESOLVED]
On Wed, 10 May 2023, Rich Shepard wrote: Which v.db* should I use to find the elevation colum associated with each contour line? Long ago I used the GUI and it had a menu to examine the vector map's table. Now, I just leared that v.db.select will work. There're more columns than I need, but one does have the elevation data. Back to work ... Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] v.to.rast: advice needed
I need to convert a vector contour map to a raster so I can apply the hydrologic models modules. Reading the v.to.rast manual page I learned that I needed to add categories to the input contour map. Running v.category added no categories: "0 features added." v.info does not tell me anything about the elevation values of the contour lines. Looking at the v.* modules, and trying v.univar, didn't help. I could try v.to.3d, but I need information about the vector map's contents. Which v.db* should I use to find the elevation colum associated with each contour line? TIA, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
