Re: [GRASS-dev] [GRASS GIS] #3870: add missing depencencies into winGRASS

2019-07-16 Thread GRASS GIS
: fixed | Keywords: CPU: All| Platform: MSWindows +- Changes (by hellik): * status: new => closed * resolution: => fixed -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3870#comment:4> GRAS

Re: [GRASS-dev] [GRASS GIS] #3870: add missing depencencies into winGRASS

2019-07-16 Thread GRASS GIS
cc2 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3870#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3870: add missing depencencies into winGRASS

2019-07-15 Thread GRASS GIS
/OSGeo/grass/pull/53 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3870#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-15 Thread GRASS GIS
of "Cannot parse interface for module" errors without and with this PR. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:10> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org h

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-15 Thread GRASS GIS
. Please try it. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:9> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3870: add missing depencencies into winGRASS

2019-07-15 Thread GRASS GIS
cre-1.dll both missing dlls are in my msys2 build environment; copying these into C:\OSGeo4W64\apps\grass\grass77\bin solves the problem. will open a ticket and hopefully my first PR :-) }}} missing dlls libgraphite2.dll and libpcre-1.dll have to be added to winGRASS. -- Ticket URL: <htt

Re: [GRASS-dev] [GRASS GIS] #3861: winGRASS master (git) - g.proj not found at startup

2019-07-15 Thread GRASS GIS
ss/ticket/3861#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3861: winGRASS master (git) - g.proj not found at startup

2019-07-15 Thread GRASS GIS
sue seems to be fixed; closing the ticket. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3861#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-14 Thread GRASS GIS
se try this: https://github.com/OSGeo/grass/pull/52 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:8> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-13 Thread GRASS GIS
to 7.6 (bfb7e0a511ea62391a02fb7904f8b3902ecbc450) and 7.4 (29fc4ae1019d639719af206637e47b57b1b5f785) -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-13 Thread GRASS GIS
|Version: svn-trunk Resolution: | Keywords: CPU: Unspecified | Platform: Unspecified --+- Changes (by martinl): * milestone: => 7.4.5 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:6> GRASS G

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-13 Thread GRASS GIS
: <https://trac.osgeo.org/grass/ticket/3867#comment:5> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3861: winGRASS master (git) - g.proj not found at startup

2019-07-12 Thread GRASS GIS
ass/ticket/3861#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-10 Thread GRASS GIS
Try running with LC_ALL=lv_LV Python 2.7.16 wxpython-3.0.2.0 wxGTK-3.0.4 Gentoo ~AMD64 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-09 Thread GRASS GIS
you have installed? It happens during loading info about installed addons. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osg

Re: [GRASS-dev] [GRASS GIS] #3869: v.import add missing v.in.ogr options

2019-07-09 Thread GRASS GIS
and gdal 3+ in future releases of GRASS GIS. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3869#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3869: v.import add missing v.in.ogr options

2019-07-09 Thread GRASS GIS
useful option to use in gdal_doo to have a better support for GML files. I think it is important to have this capability also in v.import for example -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3869#comment:2> GRASS GIS <https://

Re: [GRASS-dev] [GRASS GIS] #3869: v.import add missing v.in.ogr options

2019-07-09 Thread GRASS GIS
69#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-09 Thread GRASS GIS
cmd, det=decode(cmderr)))) UnicodeEncodeError: 'ascii' codec can't encode characters in position 1-2: ordinal not in range(128) }}} -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3869: v.import add missing v.in.ogr options

2019-07-09 Thread GRASS GIS
), the missing options have not been added for some reasons or could I work on it? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3869> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lis

[GRASS-dev] [GRASS GIS] #3868: v.in.wfs support only version 1.0.0

2019-07-09 Thread GRASS GIS
%3AEnvironmentalMonitoringFacility=100' output=wfs_test }}} - improve v.in.wfs using an external library like owslib (this probably require a new dependencies) - improve v.in.wfs as it is now, but it is really difficult to maintain -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3868> GRASS GIS <https://grass.

Re: [GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-08 Thread GRASS GIS
and I wonder why do you get that error at all. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/li

[GRASS-dev] [GRASS GIS] #3867: menudata.py: global name 'error_handler' is not defined

2019-07-08 Thread GRASS GIS
files. " NameError: global name 'error_handler' is not defined }}} -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3867> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3866: i.spec.unmix: endmember pixels do not sum up to 100%

2019-07-05 Thread GRASS GIS
is important for a defined analysis (while i.pysptools.unmix apparently always auto-generates the endmembers which are not necessarily the best or those the user wants). I suspect a bug in i.spec.unmix (maybe just a scaling issue internally?). -- Ticket URL: <https://trac.osgeo.org/grass/ti

Re: [GRASS-dev] [GRASS GIS] #3865: i.spec.unmix: map writeout broken

2019-07-05 Thread GRASS GIS
occurs and maps are now written out. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3865#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3865: i.spec.unmix: map writeout broken

2019-07-05 Thread GRASS GIS
. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3865#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3865: i.spec.unmix: map writeout broken

2019-07-05 Thread GRASS GIS
tps://trac.osgeo.org/grass/ticket/3865#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3865: i.spec.unmix: map writeout broken

2019-07-04 Thread GRASS GIS
: | Keywords: i.spec.unmix CPU: x86-64 | Platform: Unspecified --+-- Changes (by neteler): * Attachment "spectrum.txt" added. Input data for i.spec.unmix (endmember table) -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3865>

[GRASS-dev] [GRASS GIS] #3865: i.spec.unmix: map writeout broken

2019-07-04 Thread GRASS GIS
ter function usage is not correct? I have attached the input matrix of endmembers for easy testing. Ideas welcome! -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3865> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing

Re: [GRASS-dev] [GRASS GIS] #3863: epsg file missing in GRASS 7.6.1 stable

2019-07-03 Thread GRASS GIS
URL: <https://trac.osgeo.org/grass/ticket/3863#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3864: r.in.pdal - add option of first/mid/last return

2019-07-02 Thread GRASS GIS
, last) -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3864> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3863: epsg file missing in GRASS 7.6.1 stable

2019-07-02 Thread GRASS GIS
Lite3 database file: https://proj.org/news.html#id41 I wonder why the bundle was built with an incompatible proj-6 libary -- it that going to break a lot of GRASS functionality other than the missing epsg file? Should I close the bug as it is apparently not a bug? -- Ticket URL: <https://

Re: [GRASS-dev] [GRASS GIS] #3863: epsg file missing in GRASS 7.6.1 stable

2019-07-02 Thread GRASS GIS
o longer has an epsg file. GRASS 7.6 is not compatible with proj-6+, please rebuild with proj-5.x. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3863#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing lis

[GRASS-dev] [GRASS GIS] #3863: epsg file missing in GRASS 7.6.1 stable

2019-07-01 Thread GRASS GIS
. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3863> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3862: winGRASS on appveyor

2019-06-21 Thread GRASS GIS
are e.g. MSYS2 and MinGW-w64. these 2 environments are actually used to build winGRASS. in [https://github.com/OSGeo/gdal/blob/master/appveyor.yml#L78 GDAL's appveyor script] an example how dependencies may be handled. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3862> GRASS GIS

[GRASS-dev] [GRASS GIS] #3861: winGRASS master (git) - g.proj not found at startup

2019-06-21 Thread GRASS GIS
NITS unit : Meter units : Meters meters : 1 }}} in summary, wxGUI fails to start in winGRASS master. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3861> GRASS GIS <https://grass.osgeo.org> _

Re: [GRASS-dev] [GRASS GIS] #1421: scalability of r.terraflow

2019-06-12 Thread GRASS GIS
say this is a feature, so we should not backport this. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1421#comment:19> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/m

Re: [GRASS-dev] [GRASS GIS] #1421: scalability of r.terraflow

2019-06-12 Thread GRASS GIS
fixed => * milestone: 7.0.0 => 7.8.0 Comment: Backporting candidate when tested properly? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1421#comment:18> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-d

Re: [GRASS-dev] [GRASS GIS] #1421: scalability of r.terraflow

2019-06-12 Thread GRASS GIS
tps://trac.osgeo.org/grass/ticket/1421#comment:17> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1421: scalability of r.terraflow

2019-06-12 Thread GRASS GIS
before I get back. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1421#comment:16> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1421: scalability of r.terraflow

2019-06-12 Thread GRASS GIS
ectory If they should be applied, pls open an updated PR at https://github.com/OSGeo/grass/pulls -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1421#comment:15> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lis

Re: [GRASS-dev] [GRASS GIS] #1421: scalability of r.terraflow

2019-06-12 Thread GRASS GIS
? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1421#comment:14> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-11 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: reopened Priority: normal | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: reopened Priority: normal | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: reopened Priority: normal | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: reopened Priority: normal | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: reopened Priority: normal | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

Re: [GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-10 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL +- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified

[GRASS-dev] [GRASS GIS] #3860: GRASS GIS producing different slope than GDAL

2019-06-09 Thread GRASS GIS
#3860: GRASS GIS producing different slope than GDAL ---+- Reporter: mazingaro | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.6.2 Component: Raster |Version: unspecified Keywords

Re: [GRASS-dev] [GRASS GIS] #3854: r.stream.extract does not support fully qualified map names

2019-06-03 Thread GRASS GIS
<https://trac.osgeo.org/grass/ticket/3854#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3832: Add environment variable to create all temp-files at a user-defined location (outside the mapsets)

2019-06-03 Thread GRASS GIS
implemented only for vector library (GRASS_VECTOR_TMPDIR_MAPSET), see also related discussion, https://lists.osgeo.org/pipermail/grass-dev/2015-June/075220.html -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3832#comment:3> GRASS GIS <https://grass.

Re: [GRASS-dev] [GRASS GIS] #3859: r.out.gdal: Add notes about bigtiff and example with BIGTIFF=YES (or similar) to manual (was: r.out.gdal: Do not fail with big tiffs if user does not provide BIGTIFF

2019-06-03 Thread GRASS GIS
ken. Changed into a documentation ticket (that I could fix myself). -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3859#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://

Re: [GRASS-dev] [GRASS GIS] #3859: r.out.gdal: Do not fail with big tiffs if user does not provide BIGTIFF=YES creatopt

2019-06-03 Thread GRASS GIS
ot all (Geo)Tiff drivers support BIGTIFF. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3859#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3859: r.out.gdal: Do not fail with big tiffs if user does not provide BIGTIFF=YES creatopt

2019-06-03 Thread GRASS GIS
/IF_SAFER by default when exporting GeoTiff or if it could compute the required creation option from region size, number of bands and data type... -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3859> GRASS GIS <https://grass.osgeo.org> _

Re: [GRASS-dev] [GRASS GIS] #3832: Add environment variable to create all temp-files at a user-defined location (outside the mapsets)

2019-06-03 Thread GRASS GIS
/grass/ticket/3857#comment:4 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3832#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3777: vector digitizer crashes with python 3

2019-06-02 Thread GRASS GIS
plying to [comment:7 martinl]: > See https://github.com/OSGeo/grass/pull/13 Thanks! It works as expected now, closing. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3777#comment:8> GRASS GIS <https://grass.osgeo.org> ___ grass-dev m

Re: [GRASS-dev] [GRASS GIS] #3857: r.mapcalc unable to rename null and cell files

2019-06-02 Thread GRASS GIS
/grass/ticket/3857#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3858: r.mapcalc - Add warning when the same map is used both as an input and an output

2019-06-01 Thread GRASS GIS
tion might be to check inputs and outputs beforehand and add a warning for Linux and an error message for MS Windows. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3858> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list gra

Re: [GRASS-dev] [GRASS GIS] #3857: r.mapcalc unable to rename null and cell files

2019-06-01 Thread GRASS GIS
issue is on Windows' side. I am therefore closing this ticket and will open a new one regarding that input/output check suggested by Wenzeslaus. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3857#comment:3> GRASS GIS <https://grass.osgeo.org> ___

Re: [GRASS-dev] [GRASS GIS] #3857: r.mapcalc unable to rename null and cell files

2019-05-31 Thread GRASS GIS
: | Keywords: r.mapcalc CPU: x86-64 | Platform: MSWindows 7 --+- Comment (by hellik): Replying to [ticket:3857 Hygsson]: > **Note:** This works on Ubuntu without any problems. > > While using GRASS GIS 7.6.1 on 64-bit

Re: [GRASS-dev] [GRASS GIS] #3857: r.mapcalc unable to rename null and cell files

2019-05-31 Thread GRASS GIS
nd, having this feature (`a = a + 1`) seems reasonable (but supporting it is more complex). -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3857#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev

[GRASS-dev] [GRASS GIS] #3857: r.mapcalc unable to rename null and cell files

2019-05-31 Thread GRASS GIS
: unspecified Keywords: r.mapcalc|CPU: x86-64 Platform: MSWindows 7 | -+- **Note:** This works on Ubuntu without any problems. While using GRASS GIS 7.6.1 on 64-bit Windows 7, I encountered a problem with r.mapcalc. For a simple stochastic

Re: [GRASS-dev] [GRASS GIS] #3856: implement svn keyword substitution

2019-05-30 Thread GRASS GIS
Resolution: | Keywords: git, svn keywords CPU: Unspecified | Platform: Unspecified --+--- Changes (by martinl): * milestone: 7.8.0 => 7.6.2 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3856#comment:2&

[GRASS-dev] [GRASS GIS] #3856: implement svn keyword substitution

2019-05-30 Thread GRASS GIS
URL: <https://trac.osgeo.org/grass/ticket/3856> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3856: implement svn keyword substitution

2019-05-30 Thread GRASS GIS
ment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3855: update WinGRASS standalone installer to use GRASS_VERSION_GIT variable

2019-05-30 Thread GRASS GIS
o/grass/pull/9 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3855> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3852: PyGRASS GridModule silently ignores when module has no output defined

2019-05-30 Thread GRASS GIS
Ticket URL: <https://trac.osgeo.org/grass/ticket/3852#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3854: r.stream.extract does not support fully qualified map names

2019-05-28 Thread GRASS GIS
Resolution: | Keywords: r.stream.extract CPU: All | Platform: All -+-- Comment (by mmetz): Fixed in master, relbr76, and relbr74. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3854#comment:1> GRASS GIS

[GRASS-dev] [GRASS GIS] #3854: r.stream.extract does not support fully qualified map names

2019-05-27 Thread GRASS GIS
because it uses [https://github.com/OSGeo/grass/blob/master/raster/r.stream.extract/main.c#L172 G_find_raster] instead of [https://github.com/OSGeo/grass/blob/master/raster/r.stream.extract/main.c#L248 G_find_raster2] ? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3854> GRASS GIS

Re: [GRASS-dev] [GRASS GIS] #3771: Run tests on Travis

2019-05-26 Thread GRASS GIS
/grass77 --grasssrc ./ \ --grassdata $HOME/Documents/grassdata/ }}} completes with Python 3, but not with Python 2 (Unicode error) -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3771#comment:24> GRASS GIS <https://grass.osgeo.org> _

[GRASS-dev] [GRASS GIS] #3853: "make changelog" fails in clean source code copy

2019-05-26 Thread GRASS GIS
latform.make'. Stop. }}} The target "changelog" itself is defined in include/Make/Docs.make There is, however, another Makefile dependency which I cannot find - any ideas? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3853> GRASS GIS <https://grass.osgeo.org> ___

Re: [GRASS-dev] [GRASS GIS] #3851: r.out.mpeg always fails because the output file name is empty

2019-05-24 Thread GRASS GIS
commit/78e9da1af300035ab1dbe4135ab79d1068aadd58 https://github.com/OSGeo/grass/commit/2340b9dc9612535a6f249557a6175c98128a7451 https://github.com/OSGeo/grass/commit/3ab95ff7a1781317dcca969c13cfe4fc6cb024df -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3851#comment:2> GRASS GIS <https://

Re: [GRASS-dev] [GRASS GIS] #3852: PyGRASS GridModule silently ignores when module has no output defined

2019-05-24 Thread GRASS GIS
org/grass/ticket/3852#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3852: PyGRASS GridModule silently ignores when module has no output defined

2019-05-24 Thread GRASS GIS
% [] }}} -> no raster map created. The !GridModule should fail at least when no output option is defined. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3852> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing

Re: [GRASS-dev] [GRASS GIS] #3771: Run tests on Travis

2019-05-23 Thread GRASS GIS
ass/ticket/3771#comment:23> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3825: Fix tests stalling with Python 3

2019-05-23 Thread GRASS GIS
ot all 100% successful) under both Python 2 and 3. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3825#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3835: v.distance returns a 'Syntax error' when used from python

2019-05-23 Thread GRASS GIS
5#comment:5> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3846: r.contour started producing broken/segmented contour lines since 7.4

2019-05-23 Thread GRASS GIS
846#comment:6> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3846: r.contour started producing broken/segmented contour lines since 7.4

2019-05-23 Thread GRASS GIS
milestone: => 7.6.2 Comment: Closing as fixed. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3846#comment:5> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3777: vector digitizer crashes with python 3

2019-05-22 Thread GRASS GIS
tps://trac.osgeo.org/grass/ticket/3777#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3849: Do we need to clear the screen when entering/exiting GRASS?

2019-05-22 Thread GRASS GIS
ithub.com/OSGeo/grass/pull/12 PR12] has been merged, closing. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3849#comment:5> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo

Re: [GRASS-dev] [GRASS GIS] #3851: r.out.mpeg always fails because the output file name is empty

2019-05-22 Thread GRASS GIS
/pulls We recently mirated to !GitHub for the code management and we could handle your contribution much easier. Thanks! -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3851#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev

Re: [GRASS-dev] [GRASS GIS] #3851: r.out.mpeg always fails because the output file name is empty

2019-05-22 Thread GRASS GIS
rac.osgeo.org/grass/ticket/3851> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3851: r.out.mpeg always fails because the output file name is empty

2019-05-22 Thread GRASS GIS
-- Ticket URL: <https://trac.osgeo.org/grass/ticket/3851> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3850: r.out.mpeg always fails because the output file name is empty

2019-05-22 Thread GRASS GIS
@@ parse_command(viewopts, vfiles, , ); +/* output file */ +strcpy(outfile, out->answer); + r_out = 0; if (conv->answer) r_out = 1; -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3850> GRASS GIS <https://grass.osgeo.org> __

Re: [GRASS-dev] [GRASS GIS] #3849: Do we need to clear the screen when entering/exiting GRASS?

2019-05-22 Thread GRASS GIS
. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3849#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3849: Do we need to clear the screen when entering/exiting GRASS?

2019-05-21 Thread GRASS GIS
or will you welcome not clearing? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3849#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3849: Do we need to clear the screen when entering/exiting GRASS?

2019-05-20 Thread GRASS GIS
discussed. [https://github.com/OSGeo/grass/pull/12 PR12] is a new one that only removes the clear screen stuff. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3849#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailin

Re: [GRASS-dev] [GRASS GIS] #3846: r.contour started producing broken/segmented contour lines since 7.4

2019-05-20 Thread GRASS GIS
796197.58953) > > I can confirm the missing segments, the previous fix to prevent contours from tracing back on themselves was not working. Working on it... r.contour has been fixed in master, relbr76, and relbr74. -- Ticket URL: <https://trac.osgeo.org/grass/tic

Re: [GRASS-dev] [GRASS GIS] #3849: Do we need to clear the screen when entering/exiting GRASS?

2019-05-19 Thread GRASS GIS
ive mode", without `--exec`) 3. Bunch of messages is printed (//Starting GRASS GIS...// etc.). (even with `--exec`) Here we focus on the clearing only. In #2639 I compared behavior to Python and R in case when standard input is provided. As for interactive use, Python (`python`), R (`R`

<    5   6   7   8   9   10   11   12   13   14   >