Re: [GRASS-user] Exporting RGB Composite Images to GeoTIFF
Le lundi 01 août 2016 à 14:45 +0200, Markus Neteler a écrit : > What options should I be selecting to export the image? Is there a > simpler method to exporting the image that I am not aware of? > > Maybe other users have a suggestion here. Michele, maybe it does not make sense but did you try my suggestion applying gdal_translate and its "-expand rgb" option to your GeoTIFF ? Yours, Vincent. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Exporting RGB Composite Images to GeoTIFF
Hi Michele, On Fri, Jul 29, 2016 at 6:05 PM, Michele Toma wrote: > Hi Moritz/everyone, > > I really appreciate all of the information. > > The original issue was exporting an RGB composite image from GRASS to a > GeoTIFF format that could be opened in Global Mapper. I had created a > pansharpened RGB image and attempted to export the image, but the settings I > used created entirely black images. It is important to understand if there was really no data or simply a wrong color table applied. > When I exported using r.out.gdal with no create options, the resulting image > would not open in Global Mapper. I then tried to export without the color > table which gave me a grayscale image. So, my understanding was that the data > type was wrong. Unfortunately - in addition - GeoTIFF cannot represent all data types. > The errors I got when trying to export as Byte said to try using Float64 You could round the values after having multiplied them by 10 or 100. I agree, too many possibilities existing... >. But after trying to use that data type and all other data types in the drop >down list, I ended up with a black image. In addition to changing the data >type, I opted to skip exporting the color table according to the directions on >the r.out.gdal documentation page. What options should I be selecting to >export the image? Is there a simpler method to exporting the image that I am >not aware of? Maybe other users have a suggestion here. > When trying to export in QGIS, I use GRASS tools to open the rbg composite > raster and then right click on the layer -> Save As... The options that I use > are "export as a rendered image" and in create options: "No compression". > This seems to work for me. Fine. > However, I have run into another issue where I cannot get rid of the black > borders/null data that surround the image. The borders are removed in GRASS > after running r.null on the rgb composite image. They reappear when opening > in QGIS using GRASS tools. (Note: I am using QGIS 2.8.2). For this here a method, it uses r.clump: http://courses.neteler.org/selective-data-removal-elevation-map-floodfilling/ (in my example for elevation models but it works the same for imagery). Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-PSC] [GRASS-dev] Comment regarding PSC election
On Mon, Aug 1, 2016 at 10:19 AM, Helmut Kudrnovsky wrote: > Markus Neteler wrote ... >> https://trac.osgeo.org/grass/browser/grass/trunk/contributors_extra.csv >> >> to also reflect the last 5 years of contributions from people without >> SVN write access. >> This list of contributors should be considered by the CRO as part of >> the voting group. >> >> Please let us know if a name is still missing there. > > Adam Laza? > > for reference see e.g. > https://lists.osgeo.org/pipermail/grass-commit/2016-August/039939.html Yes, of course! Added. I'll also check the other GSoC contributors. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-PSC] [GRASS-dev] Comment regarding PSC election
Markus Neteler wrote > (sorry for cross-posting) > > On Tue, Jul 26, 2016 at 12:05 AM, Markus Neteler < > neteler@ > > wrote: >> On Mon, Jul 25, 2016 at 11:33 PM, Michael Barton < > Michael.Barton@ > > wrote: >>> My perspective is that active contributors to the project should vote. >>> How to define them is a >>> more complicated issue and one of the things that prompted the long >>> email chain in the PCS IIRC. >> >> Indeed >> Additionally, it is *very* complicated to define who is a community >> member. >> >> Two options yet to consider: >> >> - the ChangeLog contains some references to code contributors without >> SVN core access, e.g. > ... >> In fact, all should have been added here: >> https://trac.osgeo.org/grass/browser/grass/trunk/contributors.csv >> but that file didn't get updated lately. > > I have spent 1-2 hours on this now and updated the right file: > https://trac.osgeo.org/grass/browser/grass/trunk/contributors_extra.csv > > to also reflect the last 5 years of contributions from people without > SVN write access. > This list of contributors should be considered by the CRO as part of > the voting group. > > Please let us know if a name is still missing there. Adam Laza? for reference see e.g. https://lists.osgeo.org/pipermail/grass-commit/2016-August/039939.html Log: d.barscale: various GSoC improvments, author Adam Laza, merge from trunk r68529, r68570, r68947, r69005, r69006 - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Comment-regarding-PSC-election-tp5278038p5278874.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
