Re: [GRASS-user] r.category value range
On 04/02/15 15:51, Moritz Lennert wrote: On 04/02/15 15:45, Moritz Lennert wrote: On 04/02/15 15:23, Markus Metz wrote: On Wed, Feb 4, 2015 at 1:14 PM, Moritz Lennert wrote: On 04/02/15 11:48, Martin Album Ytre-Eide wrote: Hello! I trying to set a label for a range of values in a raster. I am using r.category (grass 7.0) "r.category map=lwc_2014 separator=':' rules=lwc.rules" My lwc.rules looks like this: 0:30:0.9 31:90:0.7 91:252:0.5 so, r.category does not seem to read my range, but in stead gives me labels for value 31 (label=90:0.7) and value 91 (label=252:0.5) Any clues to what I am doing wrong ? or is r.category not working as intended? You should use r.recode, not r.category. According to the manual, r.category should work with these rules. You're right. Sorry, I wrote to fast. Actually the manual also says concerning the example: "The format is given as follows (when separator is set to colon)". So, AFAIU, you have to set the separator parameter to whatever separator you use in the rules. Sorry, I really should take the time before I write. I can reproduce the issue actually: g.copy raster=geology_30m,mygeol r.category mygeol rules=- separator=':' < Looking at the code, I actually think that r.category works well in terms of setting the label for the range. At least the cats file reads: # 948 categories 0.00 0.00 0.00 0.00 217:270:1 405:862:2 910:948:3 which looks correct to me. However, it does not know how to display it in a decent manner. The same goes for d.legend. Or r.what. IIUC, modules that read cat values just don't seem to have been foreseen for this case. So, for the OP, I would go back to my original answer to suggest using r.recode. And maybe someone who understands the code better than me can clarify how GRASS is supposed to actually use such range labels ? Moritz ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] r.in.onearth in GRASS 7
Hi, I just try to follow some examples r3.out.vtk to get some nice 3D plots in paraview. http://grass.osgeo.org/grass70/manuals/r3.out.vtk.html In the manual there is an example that uses the r.in.onearth add-on (http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.in.onearth ) that is only available in GRASS 6. Is there a similar simple tool available in GRASS 7? Or is there any other easy way to drap a satelitte image over a e.g. DEM for viewing in paraview? /Johannes ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.category value range
On 04/02/15 15:45, Moritz Lennert wrote: On 04/02/15 15:23, Markus Metz wrote: On Wed, Feb 4, 2015 at 1:14 PM, Moritz Lennert wrote: On 04/02/15 11:48, Martin Album Ytre-Eide wrote: Hello! I trying to set a label for a range of values in a raster. I am using r.category (grass 7.0) "r.category map=lwc_2014 separator=':' rules=lwc.rules" My lwc.rules looks like this: 0:30:0.9 31:90:0.7 91:252:0.5 so, r.category does not seem to read my range, but in stead gives me labels for value 31 (label=90:0.7) and value 91 (label=252:0.5) Any clues to what I am doing wrong ? or is r.category not working as intended? You should use r.recode, not r.category. According to the manual, r.category should work with these rules. You're right. Sorry, I wrote to fast. Actually the manual also says concerning the example: "The format is given as follows (when separator is set to colon)". So, AFAIU, you have to set the separator parameter to whatever separator you use in the rules. Sorry, I really should take the time before I write. I can reproduce the issue actually: g.copy raster=geology_30m,mygeol r.category mygeol rules=- separator=':'
Re: [GRASS-user] r.category value range
On 04/02/15 15:23, Markus Metz wrote: On Wed, Feb 4, 2015 at 1:14 PM, Moritz Lennert wrote: On 04/02/15 11:48, Martin Album Ytre-Eide wrote: Hello! I trying to set a label for a range of values in a raster. I am using r.category (grass 7.0) "r.category map=lwc_2014 separator=':' rules=lwc.rules" My lwc.rules looks like this: 0:30:0.9 31:90:0.7 91:252:0.5 so, r.category does not seem to read my range, but in stead gives me labels for value 31 (label=90:0.7) and value 91 (label=252:0.5) Any clues to what I am doing wrong ? or is r.category not working as intended? You should use r.recode, not r.category. According to the manual, r.category should work with these rules. You're right. Sorry, I wrote to fast. Actually the manual also says concerning the example: "The format is given as follows (when separator is set to colon)". So, AFAIU, you have to set the separator parameter to whatever separator you use in the rules. Moritz ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.category value range
On Wed, Feb 4, 2015 at 1:14 PM, Moritz Lennert wrote: > On 04/02/15 11:48, Martin Album Ytre-Eide wrote: >> >> Hello! >> >> I trying to set a label for a range of values in a raster. >> >> I am using r.category (grass 7.0) >> >> "r.category map=lwc_2014 separator=':' rules=lwc.rules" >> >> My lwc.rules looks like this: >> >> 0:30:0.9 >> 31:90:0.7 >> 91:252:0.5 >> >> so, r.category does not seem to read my range, but in stead gives me >> labels for value 31 (label=90:0.7) and value 91 (label=252:0.5) >> >> Any clues to what I am doing wrong ? or is r.category not working as >> intended? > > > You should use r.recode, not r.category. According to the manual, r.category should work with these rules. Markus M ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.gdal and .raw files
Mistery SOLVED.. the file got damaged during copy. The proper file is read by gdal and obviously by grass. sorry for noise madi On Wed, Feb 4, 2015 at 11:54 AM, Margherita Di Leo wrote: > > > On Wed, Feb 4, 2015 at 11:24 AM, Markus Neteler wrote: > >> >> - copy-paste the command here >> > > $ gdalinfo mosaic_RGB.raw > ERROR 4: `mosaic_RGB.raw' not recognised as a supported file format. > > gdalinfo failed - unable to open 'mosaic_RGB.raw'. > > >> - run "file thefilename" and post the output? >> > > $ file mosaic_RGB.raw > mosaic_RGB.raw: empty > > >> >> And which OS, > > > Lubuntu Osgeo-Live 8.0 > > >> which GRASS version? >> > > GRASS GIS 7.1.svn (r64388) > > ciao madi > -- Best regards, Dr. Margherita DI LEO Scientific / technical project officer European Commission - DG JRC Institute for Environment and Sustainability (IES) Via Fermi, 2749 I-21027 Ispra (VA) - Italy - TP 261 Tel. +39 0332 78 3600 margherita.di-...@jrc.ec.europa.eu Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] generalize polygons including holes
On 04/02/15 11:36, Robert Nuske wrote: Hi GRASS-Users is there a way to generalize polygons including their holes? I am not too worried about topology, there are only polygons of one class in the dataset. I tried the following v.generalize in=m3 out=m5 type=area method=douglas threshold=5000 which simplified the "outer boundaries" okay but did not touch the "inner boundaries"/ holes of the polygon. Outer boundaries are on the left side in the picture and holes on the right http://i.imgur.com/hHKr15m.png It looks like the red boundaries are the generalized version of the original blue ones. Is that correct ? Are you sure that the original boundaries of the holes are identical to the new ones ? Could you display the result with polygon fill color set to transparent ? Moritz ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.category value range
On 04/02/15 11:48, Martin Album Ytre-Eide wrote: Hello! I trying to set a label for a range of values in a raster. I am using r.category (grass 7.0) "r.category map=lwc_2014 separator=':' rules=lwc.rules" My lwc.rules looks like this: 0:30:0.9 31:90:0.7 91:252:0.5 so, r.category does not seem to read my range, but in stead gives me labels for value 31 (label=90:0.7) and value 91 (label=252:0.5) Any clues to what I am doing wrong ? or is r.category not working as intended? You should use r.recode, not r.category. Moritz ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] generalize polygons including holes
Hi GRASS-Users is there a way to generalize polygons including their holes? I am not too worried about topology, there are only polygons of one class in the dataset. I tried the following v.generalize in=m3 out=m5 type=area method=douglas threshold=5000 which simplified the "outer boundaries" okay but did not touch the "inner boundaries"/ holes of the polygon. Outer boundaries are on the left side in the picture and holes on the right http://i.imgur.com/hHKr15m.png Suggestions are very welcome. cheers robert ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.gdal and .raw files
On Wed, Feb 4, 2015 at 11:24 AM, Markus Neteler wrote: > > - copy-paste the command here > $ gdalinfo mosaic_RGB.raw ERROR 4: `mosaic_RGB.raw' not recognised as a supported file format. gdalinfo failed - unable to open 'mosaic_RGB.raw'. > - run "file thefilename" and post the output? > $ file mosaic_RGB.raw mosaic_RGB.raw: empty > > And which OS, Lubuntu Osgeo-Live 8.0 > which GRASS version? > GRASS GIS 7.1.svn (r64388) ciao madi ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] r.category value range
Hello! I trying to set a label for a range of values in a raster. I am using r.category (grass 7.0) "r.category map=lwc_2014 separator=':' rules=lwc.rules" My lwc.rules looks like this: 0:30:0.9 31:90:0.7 91:252:0.5 so, r.category does not seem to read my range, but in stead gives me labels for value 31 (label=90:0.7) and value 91 (label=252:0.5) Any clues to what I am doing wrong ? or is r.category not working as intended? Martin ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.gdal and .raw files
On Wed, Feb 4, 2015 at 10:59 AM, Margherita Di Leo wrote: > On Wed, Feb 4, 2015 at 10:51 AM, Markus Neteler wrote: ... >> What does gdalinfo report on the file? If that works, r.in.gdal will work, >> too. > > Says that it is not recognised as a supported file format. Do you mind to - copy-paste the command here - run "file thefilename" and post the output? And which OS, which GRASS version? ciao Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.gdal and .raw files
Markus, On Wed, Feb 4, 2015 at 10:51 AM, Markus Neteler wrote: > On Wed, Feb 4, 2015 at 10:45 AM, Margherita Di Leo > wrote: > > On Wed, Feb 4, 2015 at 10:30 AM, Markus Neteler > wrote: > ... > >> ... are you using the same GDAL version in QGIS and GRASS GIS? > > > > 1.10.1 (2013/08/26) > > Not that new :-) > So am I :-P (You're right) > > >> But if it is a mosaic, the camera file got already postprocessed? > > > > Yes, sorry if I was unclear on this. It comes with its .hdr, in which I > read > > it's been postprocessed with ENVI. > > Aha, so it is an ENVI file. > > > However my curiosity was about qgis > > handling it and grass not, using the same version of gdal.. > > What does gdalinfo report on the file? If that works, r.in.gdal will work, > too. > Says that it is not recognised as a supported file format. > Important: > > http://www.gdal.org/frmt_various.html#ENVI > "To select an existing ENVI raster file select the binary file > containing the data..." > > Maybe you specified the hdr file? > Nope. I'm sure I specified the raw file. > > Markus > -- Best regards, Dr. Margherita DI LEO Scientific / technical project officer European Commission - DG JRC Institute for Environment and Sustainability (IES) Via Fermi, 2749 I-21027 Ispra (VA) - Italy - TP 261 Tel. +39 0332 78 3600 margherita.di-...@jrc.ec.europa.eu Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] t.register: ERROR: day is out of range for month
Hi, the problem is that the model year has 360 days, ignoring the Gregorian calendar that is the based on absolute time in GRASS. Hence, the 29. and 30. February do not exist in 1951. You can use relative time with a daily resolution, so you don't have to to deal with Gregorian calendar time. t.create temporaltype=relative ... t.register start=0 increment=1 unit="day" ... Best regards Soeren 2015-02-04 5:27 GMT+01:00 RichardCooper : > Apologies for re-posting, but I noticed that much of the post's content > disappeared in the email. > > Also, as an update I tried to add both a start and end date to the input > file (following the t.register manual) but still get the same error on > running t.register: > > ERROR: day is out of range for month > ERROR: Unable to convert string "1951-02-29"into a datetime object > > The process in more detail: > Aim: to process and analyse a 360 day (30 day/month) climate database > > t.create --overwrite output=cahpa05216fgh_stvds type=stvds semantictype=max > title="cahpa_05216fgh_prcp_stvds" description="CAHPA05216 for MAPSETfgh > Precipitation STVDS" > > t.register --overwrite input=test_stvds type=vector > file=/home/rcooper/glist_fgh_vectors.out > Gathering map information... > ERROR: day is out of range for month > ERROR: Unable to convert string "1951-02-29"into a datetime object > > > Sample of 360 day file input to t.register: > ... > bnd_cahpa_f1jan_05216_nc_remapped_nc_28|1951-01-28 > bnd_cahpa_f1jan_05216_nc_remapped_nc_29|1951-01-29 > bnd_cahpa_f1jan_05216_nc_remapped_nc_30|1951-01-30 > bnd_cahpa_f1feb_05216_nc_remapped_nc_1|1951-02-01 > bnd_cahpa_f1feb_05216_nc_remapped_nc_2|1951-02-02 > bnd_cahpa_f1feb_05216_nc_remapped_nc_3|1951-02-03 > ... > bnd_cahpa_f1feb_05216_nc_remapped_nc_28|1951-02-28 > bnd_cahpa_f1feb_05216_nc_remapped_nc_29|1951-02-29 > bnd_cahpa_f1feb_05216_nc_remapped_nc_30|1951-02-30 > bnd_cahpa_f1mar_05216_nc_remapped_nc_1|1951-03-01 > bnd_cahpa_f1mar_05216_nc_remapped_nc_2|1951-03-02 > bnd_cahpa_f1mar_05216_nc_remapped_nc_3|1951-03-03 > bnd_cahpa_f1mar_05216_nc_remapped_nc_4|1951-03-04 > ... > > GRASS version: 7.0.0svn > GRASS SVN Revision: 64042 > Build Date: 2015-01-10 > Build Platform: i686-pc-linux-gnu > GDAL/OGR: 1.11.1 > PROJ.4: 4.9.0 > GEOS: 3.4.2 > SQLite: 3.7.9 > Python: 2.7.3 > wxPython: 2.8.12.1 > Platform: Linux-3.2.0-31-generic-pae-i686-with-LinuxMint-13-maya > > > > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/t-register-ERROR-day-is-out-of-range-for-months-tp5185155p5185370.html > Sent from the Grass - Users mailing list archive at Nabble.com. > ___ > grass-user mailing list > grass-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.gdal and .raw files
On Wed, Feb 4, 2015 at 10:45 AM, Margherita Di Leo wrote: > On Wed, Feb 4, 2015 at 10:30 AM, Markus Neteler wrote: ... >> ... are you using the same GDAL version in QGIS and GRASS GIS? > > 1.10.1 (2013/08/26) Not that new :-) >> But if it is a mosaic, the camera file got already postprocessed? > > Yes, sorry if I was unclear on this. It comes with its .hdr, in which I read > it's been postprocessed with ENVI. Aha, so it is an ENVI file. > However my curiosity was about qgis > handling it and grass not, using the same version of gdal.. What does gdalinfo report on the file? If that works, r.in.gdal will work, too. Important: http://www.gdal.org/frmt_various.html#ENVI "To select an existing ENVI raster file select the binary file containing the data..." Maybe you specified the hdr file? Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] t.register: ERROR: day is out of range for month
On Wed, Feb 4, 2015 at 5:27 AM, RichardCooper wrote: > Apologies for re-posting, but I noticed that much of the post's content > disappeared in the email. > > Also, as an update I tried to add both a start and end date to the input > file (following the t.register manual) but still get the same error on > running t.register: > > ERROR: day is out of range for month > ERROR: Unable to convert string "1951-02-29"into a datetime object The issue is that this date did not exist: grassuser $ > cal 2 1951 February 1951 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 > Sample of 360 day file input to t.register: > ... > bnd_cahpa_f1feb_05216_nc_remapped_nc_3|1951-02-03 > ... > bnd_cahpa_f1feb_05216_nc_remapped_nc_28|1951-02-28 > bnd_cahpa_f1feb_05216_nc_remapped_nc_29|1951-02-29 <--- remove ... > bnd_cahpa_f1feb_05216_nc_remapped_nc_30|1951-02-30 <--- remove > bnd_cahpa_f1mar_05216_nc_remapped_nc_1|1951-03-01 ... The list may only contain existing dates. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.gdal and .raw files
Markus, On Wed, Feb 4, 2015 at 10:30 AM, Markus Neteler wrote: > On Wed, Feb 4, 2015 at 9:46 AM, Margherita Di Leo > wrote: > > On Tue, Feb 3, 2015 at 9:22 PM, Markus Metz > >> On Tue, Feb 3, 2015 at 2:41 PM, Margherita Di Leo > >> wrote: > >> > anyone has experience with .raw files? I happen to have one to analyze > >> > (quite large indeed) and r.in.gdal doesn't seem to support it. > However, > >> > for some magics, qgis is able to open it and I'm now converting it to > tif. > > ... are you using the same GDAL version in QGIS and GRASS GIS? > 1.10.1 (2013/08/26) > > >> > But it's taking kinda forever. Any better idea? > >> > >> A .raw file could be a raw data file from a digital camera, but it can > >> also be anything else. Can QGIS tell you what kind of file this is? > > > > It is mosaic from digital camera (RGB). > > But if it is a mosaic, the camera file got already postprocessed? > Yes, sorry if I was unclear on this. It comes with its .hdr, in which I read it's been postprocessed with ENVI. However my curiosity was about qgis handling it and grass not, using the same version of gdal.. > If not, there are various formats: > https://en.wikipedia.org/wiki/Raw_image_format#File_contents > > ciao > markusN > -- Best regards, Dr. Margherita DI LEO Scientific / technical project officer European Commission - DG JRC Institute for Environment and Sustainability (IES) Via Fermi, 2749 I-21027 Ispra (VA) - Italy - TP 261 Tel. +39 0332 78 3600 margherita.di-...@jrc.ec.europa.eu Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] temporary files of grass.script.array
Hi, I just tested in trunk, and it works: The temporary file that is create when assigning a raster to an python array is deleted once e.g. the python session is closed again. So this would be a nice thing also to have implemented in the next RC of GRASS7. /johannes On Tue, Feb 3, 2015 at 11:35 PM, Markus Neteler wrote: > On Tue, Feb 3, 2015 at 4:23 PM, Glynn Clements > wrote: > > The temporary files were supposed to be deleted when the array object > > was destroyed. However, this relied upon the ._close() method, which > > is no longer used. r64426 (trunk) should fix this. > > Please let me know if that should be backported then. > > Markus > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.gdal and .raw files
On Wed, Feb 4, 2015 at 9:46 AM, Margherita Di Leo wrote: > On Tue, Feb 3, 2015 at 9:22 PM, Markus Metz >> On Tue, Feb 3, 2015 at 2:41 PM, Margherita Di Leo >> wrote: >> > anyone has experience with .raw files? I happen to have one to analyze >> > (quite large indeed) and r.in.gdal doesn't seem to support it. However, >> > for some magics, qgis is able to open it and I'm now converting it to tif. ... are you using the same GDAL version in QGIS and GRASS GIS? >> > But it's taking kinda forever. Any better idea? >> >> A .raw file could be a raw data file from a digital camera, but it can >> also be anything else. Can QGIS tell you what kind of file this is? > > It is mosaic from digital camera (RGB). But if it is a mosaic, the camera file got already postprocessed? If not, there are various formats: https://en.wikipedia.org/wiki/Raw_image_format#File_contents ciao markusN ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.gdal and .raw files
Hi Markus, On Tue, Feb 3, 2015 at 9:22 PM, Markus Metz wrote: > On Tue, Feb 3, 2015 at 2:41 PM, Margherita Di Leo > wrote: > > Hi, > > > > anyone has experience with .raw files? I happen to have one to analyze > > (quite large indeed) and r.in.gdal doesn't seem to support it. However, > for > > some magics, qgis is able to open it and I'm now converting it to tif. > But > > it's taking kinda forever. Any better idea? > > A .raw file could be a raw data file from a digital camera, but it can > also be anything else. Can QGIS tell you what kind of file this is? > It is mosaic from digital camera (RGB). Thanks, madi > > Markus M > > -- Best regards, Dr. Margherita DI LEO Scientific / technical project officer European Commission - DG JRC Institute for Environment and Sustainability (IES) Via Fermi, 2749 I-21027 Ispra (VA) - Italy - TP 261 Tel. +39 0332 78 3600 margherita.di-...@jrc.ec.europa.eu Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
