Re: [GRASS-user] Best workflow

2016-06-27 Thread Paul Meems
Thanks Markus for your suggestion.

I first tried Stefan's suggestion of using a VRT-file.
I have 1300 tiff-files with a combined file size of 400GB. Creating the
VRT-file was no problem, but when I tried to import the VRT-file in GRASS7
using r.in.gdal GRASS crashes and dies.
Loading the same VRT-file in QGis did take some time to load but it worked.

So I think I need to set-up a GeoServer after all, just to get a small
portion of my height data to process in GRASS without worrying about
polygons that are partially on multiple tiff-files.

Of course I'm open to any other suggestion. As said I'm new to GRASS.




Paul

*Paul Meems *
Release manager, configuration manager
and forum moderator of MapWindow GIS.
www.mapwindow.org

Owner of MapWindow.nl - Support for
Dutch speaking users.
www.mapwindow.nl


Download the latest MapWinGIS mapping engine.


Download the latest MapWindow 5 open source desktop application.


2016-06-26 1:34 GMT+02:00 Markus Neteler :

> On Fri, Jun 24, 2016 at 12:44 PM, Blumentrath, Stefan
>  wrote:
> > Forgot to mention: pay attention to border effects in r.slope.aspect
> (see:
> > https://grass.osgeo.org/grass70/manuals/r.slope.aspect.html). So if your
> > tiles do not overlap, you might have to merge them...
>
> If you can define your tiles yourself, then you may use the "overlap"
> parameter to create tiles which overlap by 1 row/column:
>
> https://grass.osgeo.org/grass72/manuals/r.tile.html
>
> Markus
>
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] v.label utf8 possible?

2016-06-27 Thread Glynn Clements

Robert Kuszinger wrote:

> I'd like to create a label for a point vector map with point names to be
> utilized in map composer (ps.map).
> 
> Everything works except that I cannot use my UTF8 strings. They are
> rendered as latin1 as far as I can see.
> 
> Using d.vect strings are displayed correctly:
> 
> d.vect --quiet map=places@Duna where="type='village' OR type='town'"
> color=none fill_color=red width=1 icon=basic/circle attribute_column=name
> label_color=black label_size=9 font=LinBiolinum_R encoding=UTF-8
> 
> but there is no encoding option in v.label. I've found some links to
> v.label.sa which is not available in my Grass setup nor on the extension
> list.
> Grass version is:

AIUI, v.label simply sets the labels as byte strings. Their
interpretation is determined by the program which actually renders the
labels, either by an explicit call to D_encoding(), or from the
environment variable GRASS_ENCODING, or from the font's default
encoding from the fontcap file.

UTF-8 text should work with d.vect and d.labels if you use a FreeType
font (but not for a stroke font, which only provide glyphs for the
ASCII range). I wouldn't expect it to work with anything which
generates PostScript.

-- 
Glynn Clements 
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.landsat.toar and -n flag

2016-06-27 Thread Ken Mankoff
Hi Nikos,

On 2016-06-25 at 16:16, Nikos Alexandris  wrote:
> * Ken Mankoff  [2016-06-23 14:38:21 -0400]:
>>
>> Is there a way to only process 1 band with i.landsat.toar? It would
>> save some time.
>
> I don't think so.  But it would be nice to have it.

I've opened a feature request here: https://trac.osgeo.org/grass/ticket/3083

And submitted a patch that appears to work for me on the latest svn trunk. This 
is my first source code contribution to grass so I don't know if it meets 
standards and follows guidelines, but it does implement the functionality.

  -k.

___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Fwd: v.label utf8 possible?

2016-06-27 Thread Vaclav Petras
On Sun, Jun 26, 2016 at 7:38 AM, Robert Kuszinger 
wrote:

> As a workaround I've created a script and discovered that I could simulate
> the work done by ps.map with some handmade calculations.
> The result is not worse (visually in terms of generated code) than my
> beloved ps.map definition files. I have full control on display, raster,
> vector and other map gadgets (north, scalebar, etc). I use GRASS_RENDER_*
> variables, and all d.* commands. Cairo driver with BMP output is very fast.
> I put each map "layer" into a different BMP files with identicatal
> resolutions.
>

This sounds good. Perhaps you can share your work at some point. It would
be a good contribution to the discussion about the future of ps.map and d.
commands.


> The resolution is currently a given dpi (300-600) bitmap but I'd like to
> test the toolchain with svg output as well to keep vectors for best print
> process.
>

Please see:

https://trac.osgeo.org/grass/ticket/3033

Vaclav
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user