Glynn Clements wrote
> Helmut Kudrnovsky wrote:
>
>> >> anyone more insight, if %HOME% is needed in winGRASS?
>> >
>> >Done by Glynn in:
>> >https://trac.osgeo.org/grass/changeset/37873
>>
>> does GRASS need HOME to be de
Luca Delucchi wrote
> Hi devs,
>
> this morning I got a problem with v.select, I don't understand if is a
> bug or what... I repeated the procedure with north carolina dataset
>
> g.region vect=zipcodes -ap
>
> v.mkgrid map=zipcodes_grid box=1,1
>
> v.category zipcodes_grid opt=report
hi devs,
the subject question oroginates from
[GRASS-stats] GRASS can't find R packages from personal library on Windows
https://lists.osgeo.org/pipermail/grass-stats/2016-November/001690.html
technical background on winGRASS side:
%HOME% is defined in winGRASS by:
for trunk
Anna Petrášová wrote
> On Fri, Nov 18, 2016 at 9:14 AM, Helmut Kudrnovsky
> hellik@
> wrote:
>> hi devs,
>>
>> the subject question oroginates from
>>
>> [GRASS-stats] GRASS can't find R packages from personal library on
>> Windows
>> https://
as a follow up of:
https://lists.osgeo.org/pipermail/grass-dev/2016-November/083125.html
[snip]
>>> what happens if we don't set it in grass.py? I can't try now.
>>
>> tested in winGRASS7.0.5 by commenting out following line:
>>
>> # set HOME
>> #if windows and not os.getenv('HOME'):
>> #
pjzgeo wrote
> Hi list
>
> I'm developing some script in "grass gis", and I have some doubt that the
> documentation will not answer me (
> https://grass.osgeo.org/programming7/gis_8h.html)
>
> What is the diference betwen G_OPT_R_INPUT and G_OPT_R_MAP ?
>
> if I have a geoprocess has two
fyi (related to my mail to the PSC ML sometimes ago):
http://lists.osgeo.org/pipermail/postgis-devel/2016-October/025981.html
about postgis' possible transitions to OSGeo's GIT services.
-
best regards
Helmut
--
View this message in context:
Roger Bivand wrote
> With both Wayland and Xorg on the Gnome desktop, displaying elevation @
> nc_basic leads to high CPU usage and temperatures > 90C (also -text). This
> is on a fully updated laptop (Fedora 25 Workstation), GRASS 7.2RC2 built
> from source. A typical message under Wayland
Markus Neteler wrote
> On Sat, Dec 10, 2016 at 8:00 PM, Vaclav Petras
> wenzeslaus@
> wrote:
>>
>> On Sat, Dec 10, 2016 at 1:04 PM, Martin Landa
> landa.martin@
>
>> wrote:
>>>
>>> 2016-12-10 17:52 GMT+01:00 Helena Mitasova
> hmitaso@
> :
>>> > Regarding the release there is also a
Carlos Grohmann-2 wrote
> Thanks for testing it Anna.
>
> I commited some changes: EPSG code is not required in a projected location
> and null values are repected.
>
> Carlos
just have also a look at
https://wingrass.fsv.cvut.cz/grass73/x86_64/addons/grass-7.3.svn/logs/r.denoise.log
Moritz Lennert wrote
> On 06/12/16 23:42, Martin Landa wrote:
>> Hi,
>>
>> 2016-12-06 23:28 GMT+01:00 john polo
> jpolo@.usf
> :
>>> I downloaded GRASS 7.2 and installed. The download came from this link:
>>> https://grass.osgeo.org/news/65/15/GRASS-GIS-7-2-0RC2-released/
>>>
>>> As GRASS was
hi devs,
some days ago I've added in svn for all 7 branches an addition that
R-winGRASS-coupling works the same in OSGeo4W-winGRASS and standalone
winGRASS:
https://lists.osgeo.org/pipermail/grass-commit/2016-December/040953.html
Martin Landa wrote
> Hi,
>
> 2016-12-17 17:02 GMT+01:00 Helmut Kudrnovsky
> hellik@
> :
>> anyone any idea how to promote this also to the download server:
>>
>> http://download.osgeo.org/osgeo4w/x86_64/release/grass/grass-daily/setup.hint
>> http://downl
Helmut Kudrnovsky wrote
> another nice to have for winGRASS 7.2.0:
>
> https://trac.osgeo.org/osgeo4w/ticket/413#comment:29
>
> no blocker, just an OSGeo4W-packaging issue; if this is solved, the
> R-winGRASS-coupling-functionality will be the same in standalone winGRASS
>
>Thank you for rewriting this, here is couple of brief observations.
Additionally In
https://wingrass.fsv.cvut.cz/grass73/x86_64/addons/grass-7.3.svn/logs/r.denoise.log
[...]
ERROR: pyproj not found, install it first: pip install pyproj
maybe some kind of lazy importing of pyproj is needed that
Martin Landa wrote
> Hi,
>
> 2016-12-30 16:26 GMT+01:00 Markus Neteler
> neteler@
> :
>> Yes Windows binaries are missing (Martin is ill) but perhaps it is ok
>> to deliver them soon.
>
> I managed prepare Windows packages already yesterday evening, both
> standalone and osgeo4w packages are
Martin Landa wrote
> 2016-12-18 17:36 GMT+01:00 Helmut Kudrnovsky
> hellik@
> :
>> >So the next standalone installer should
>>>also include rbatch package.
>>
>> standalone has these R batchfiles already inside since ~2 years.
>
> Ok, so
Markus Neteler wrote
> On Sun, Dec 18, 2016 at 7:52 PM, Paulo van Breugel
>
> p.vanbreugel@
> wrote:
>> Hi Steven / devs
>>
>> The build status of r.randomforest shows it failed to build. From the log
>> file this seems to be because Pandas is not installed
>>
>> ...
>> ERROR: Pandas not
>So the next standalone installer should
>also include rbatch package.
standalone has these R batchfiles already inside since ~2 years.
-
best regards
Helmut
--
View this message in context:
Helmut Kudrnovsky wrote
>
> Markus Neteler wrote
>> On Sun, Dec 18, 2016 at 7:52 PM, Paulo van Breugel
>>
>> p.vanbreugel@
>> wrote:
>>> Hi Steven / devs
>>>
>>> The build status of r.randomforest shows it failed to build.
Markus Neteler wrote
> On Sun, Dec 18, 2016 at 9:17 PM, Helmut Kudrnovsky
> hellik@
> wrote:
>> Helmut Kudrnovsky wrote
> ...
>>> what about to do some kind of a lazy import and move panda and scikit to
>>> def main()?
>>>
>>> It isn't n
Markus Neteler wrote
> On Sun, Dec 18, 2016 at 9:39 PM, Anna Petrášová
> kratochanna@
> wrote:
>> On Sat, Dec 17, 2016 at 9:59 AM, Martin Landa
> landa.martin@
> wrote:
>>> Hi,
>>>
>>> 2016-12-10 20:00 GMT+01:00 Vaclav Petras
> wenzeslaus@
> :
Yes, that's it. Do you know
> I will move the import of pandas to a lazy import because
AFAIU also the Scikit imports should be done by a lazy import.
-
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/r-randomforest-built-status-tp5300348p5300387.html
Sent from the Grass -
pvanbosgeo wrote
> I am trying to write a script using pysal for point pattern analysis. From
> their manual, "PySAL contains a new file input-output API that should be
> used for all file IO operations" (
> pysal.readthedocs.io/en/latest/users/tutorials/fileio.html).
>
> Does anybody know or has
>However, I
>thought perhaps there is a more direct way to write a grass vector >layer
>to pysal format that people know of. If not, I'll use the
>grass-shapefile-pysal route.
no idea if pysal is able to read from pipe, if it's about point maybe it's
possible to feed the pipe by some
Martin Landa wrote
> Hi,
>
> 2017-03-27 21:39 GMT+02:00 Helmut Kudrnovsky
> hellik@
> :
>> G7A:v.clip - very easy to use and expected GIS functionality without
>> hassle
>> of complicated commmands :-)
>>
>> tested v.clip quite a lot in the last we
Markus Neteler wrote
> On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa
> landa.martin@
> wrote:
>> Hi all,
>>
>> based on roadmap published in ML [1] we are close to RC1. There are no
>> blockers registered [2], so it is seems that we can slowly start
>> preparing RC1. Any objections?
>>
>> Ma
Ondřej Pešek wrote
> Hello everyone,
>
> I am Ondrej Pesek, a student at CTU in Prague (studying master studies in
> geomatics) and I would like to participate in GSoC 2017.
>
> I am most interested in the SOS topic [1]. I will work during summer in
> NINA where I should work with istSOS, So I'm
Markus Neteler wrote
> On Mon, Mar 27, 2017 at 9:39 PM, Helmut Kudrnovsky
> hellik@
> wrote:
>> Markus Neteler wrote
>>> On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa
> ...
>>> Please (all) check
>>> https://trac.osgeo.org/grass/wiki/Grass7Planni
Dear OSGeo community, students,
* according to the Google Summer of Code 2017 Timeline [1]:*
April 3 16:00 UTC Student application deadline
application period will be closed very soon!!
* @Students: *
"Historically, the students with the best proposals reach out to the orgs early
>Or can / should I
>add this to the datum information files in $GISBASE/etc/proj/ogr_csv?
quite interesting as I don't have here $GISBASE/etc/proj/ogr_csv
from a fresh svn up and compilation
nada:~/dev/cpp/grass7_trunk/dist.x86_64-pc-linux-gnu/etc/proj$ ls -l
insgesamt 228
-rw-r--r-- 1 5725
database can be downloaded here:
http://www.eea.europa.eu/data-and-maps/data/biogeographical-regions-europe-3
ogrinfo -al -so BiogeoRegions2016.sqlite
INFO: Open of `BiogeoRegions2016.sqlite'
using driver `SQLite' successful.
Layer name: biogeoregions2016
Geometry: Multi Polygon
Helmut Kudrnovsky wrote
> it's a GUI regression.
>
> should I open a ticket?
ticket opened by https://trac.osgeo.org/grass/ticket/
nice number ;-)
-
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/How-to-import-from-a-s
Martin Landa wrote
> Hi,
>
> 2017-04-16 22:40 GMT+02:00 Helmut Kudrnovsky
> hellik@
> :
>> v.in.ogr -l input=BiogeoRegions2016.sqlite
>> biogeoregions2016
>
> [...]
>
>> Data source
>
> (format 'SQLite') contains 1 layers:
>> v.in.ogr
Martin Landa wrote
> Hi,
>
> 2017-04-16 22:40 GMT+02:00 Helmut Kudrnovsky
> hellik@
> :
>> v.in.ogr -l input=BiogeoRegions2016.sqlite
>> biogeoregions2016
>
> [...]
>
>> Data source
>
> (format 'SQLite') contains 1 layers:
>> v.in.ogr
Martin Landa wrote
> Hi,
>
> 2017-04-16 22:40 GMT+02:00 Helmut Kudrnovsky
> hellik@
> :
>> v.in.ogr -l input=BiogeoRegions2016.sqlite
>> biogeoregions2016
>
> [...]
>
>> Data source
>
> (format 'SQLite') contains 1 layers:
>> v.in.ogr
Markus Neteler wrote
> Hi devs,
>
> while thinking about a future GRASS GIS 8 version, I suggest that we
> plan when to release 7.4.0 later this year.
> We have already accumulated a series of tickets for 7.4.svn [1] and
> also numerous improvements which cannot be backported to 7.2.svn.
>
> The
(taken from the SOC ML)
Dear All,
at today, we have only 9 registered mentors, which I believe is not the
final number. If you are willing to mentor a student for Google Summer of
Code, here's what to do: add yourself here [1], clearly indicating the
*title* of the idea you are willing to
Tung Nguyen-2 wrote
> Hello GRASS dev,
>
> I'm using GRASS-GIS v6.4.3 (2013) on Linux Mint 17.3 Rosa but couldn't get
> the GUI to start. I have tried all solutions I could find to no avail.
> What
> I have done so far
> - Uninstall (purge) and reinstall python-wxversion, python-wxgtk2.8 then
>
stevenpawley wrote
> This seems to be an issue on windows that is related to r.tileset not
> r.terrain.texture. Infact on windows I can't get r.tileset to function at
> all on a windows system, but it works on linux:
>
> r.tileset sourceproj="+proj=tmerc +lat_0=0 +lon_0=-115 +k=0.9992
>
Moritz Lennert wrote
> On 16/08/17 00:48, Steven Pawley wrote:
>> This seems to be an issue on windows that is related to r.tileset not
>> r.terrain.texture. Infact on windows I can't get r.tileset to function
>> at all on a windows system, but it works on linux:
>>
>> r.tileset
>I have gone with your's and Moritz's suggestion and have completed
r.terrain.texture with the Iwahashi >and Pike nested-means terrain
classification method in the add-ons.
addon tested here with
System Info
GRASS version:
>(I also have three files representing color rules, and three category >files
that are applied to the 8, 12 or 16 terrain classification >results)
https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.euro.ecosystem/r.euro.ecosystem.py#L72
an example where I've embeded color and
just a fresh compiled
---
GRASS version: 7.3.svn
GRASS SVN revision: r71243
Build date: 2017-07-08
Build platform:
maybe related to
https://lists.osgeo.org/pipermail/grass-commit/2017-July/042140.html
-
Author: mmetz
Date: 2017-07-10 14:32:27 -0700 (Mon, 10 Jul 2017)
New Revision: 71255
Modified:
grass/trunk/raster/r.clump/clump.c
Log:
r.clump: fix arg type for time() fn
-
error log:
hi,
it seems the winGRASS 7-32bit nightly builds are broken since 16-Jun-2017
due to
checking for deflate in -lz... no
configure: error: *** Unable to locate zlib library.
-
best regards
Helmut
--
View this message in context:
Markus Metz-3 wrote
> On Fri, Jul 14, 2017 at 7:09 PM, Helmut Kudrnovsky
> hellik@
> wrote:
>>
>> maybe related to
>>
>> https://lists.osgeo.org/pipermail/grass-commit/2017-July/042140.html
>>
>> -
>> Author: mmetz
>> Date: 201
Markus Neteler wrote
> Hi,
>
> during the FOSS4G-Europe 2017 code sprint we decided to create a git
> repo the upcoming GRASS GIS web site (there is the long standing plan
> to get a new beautiful web site :-)
>
> To join, please register here - by using your OSGeo-ID:
>
>
>checking for cairo.h... yes
>Package cairo was not found in the pkg-config search path.
>Perhaps you should add the directory containing `cairo.pc'
>to the PKG_CONFIG_PATH environment variable
>No package 'cairo' found
>checking for location of cairo library..
Does the suggestion?
-
best
Fyi
https://lists.osgeo.org/pipermail/qgis-developer/2017-August/049586.html
Yes - it's a work in progress still. SAGA algs are being worked on in
https://github.com/qgis/QGIS/pull/5021, we need someone to step up and
port the GRASS ones. GDAL still has a few left to port (volunteers
welcome),
fyi
https://lists.osgeo.org/pipermail/pdal/2017-May/001245.html
-
All,
A note to let you know the GRASS team had a Google Summer of Code student
project accepted to enable the integration of PDAL capability in GRASS. The
student's name is Paul Schrum, and
Fyi
http://lists.maptools.org/pipermail/proj/2017-June/007697.html
AFAIU changes in GRASS code may be needed.
-
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Upcoming-proj4-releases-tp5325241.html
Sent from the Grass - Dev mailing list
Paul Schrum wrote
> I started off trying to build it in a directory under my home directory
> using the instructions here
> https://grasswiki.osgeo.org/wiki/Compile_and_Install_Ubuntu#Dependencies;,
> but I could not get it to build. The only part of those instructions that
> I was not following
Paul Schrum wrote
> Is there a way I can give myself privileges in my own usr/local to write
> to
> it and its subdirectories?
>
> In following the directions to build grass7_trunk, I put the source under
> /usr/local/src/grass7_trunk, and now everything I do which modifies
> anything must be
: 300: ./configure: Cannot fork
> ./configure: 300: ./configure: Cannot fork
>
> There is a lot more I could send but have not, including the last lines
> before it restarts at the top of the loop.
>
> Please let me know what more information to five you or what changes I
>
Paul Schrum wrote
> My GSoC mentor (Vashek) just now helped me work through this.
>
> I turns out that in my newbie confusion I was calling ./configure from
> ./configure, so it wasn't an endless loop, it was an endless recursion.
good to hear that's working now.
-
best regards
Helmut
--
>However, I may install a new blender in near future. As far as I know,
>it still comes with a separate Python installation.
>
>Any idea on how to avoid such interferences in the future?
no idea how blender handles its python installation.
AFAICT I have also a separate python installed and there
>C:\GRASS_GIS\etc\python\grass\script\task.py", line 35, in
>¦
AFAIU you're using winGRASS standalone installer. Correct? Which Version?
winGRASS standalone bundles its own python version.
>¦ from xml.parsers import expat # TODO: works for any Python?
>¦ File
temporary2017 wrote
> Hi!
>
> As a newbie to topographic analysis, I installed GRASS GIS 7.2.1 windows
> version (Win 7 Prof. 64, german) to do my first steps. However, I face
> some problems running it (probably bugs in GRASS GIS).
>
> In case this is the wrong mailing list please give me a
>If you do not know GDALs /vsizip and /vsiurl capabilities, I would recommend
having a look at this >blog-post from Even Rouault:
>
>http://erouault.blogspot.no/2012/05/new-gdal-virtual-file-system-to-read.html
>
>These GDAL features might be relevant for importing external data.
a small
hi
just started:
System Info
GRASS version: 7.3.svn
GRASS SVN revision: r71182M
Build date: 2017-06-13
hi,
just playing around with with running several GRASS modules in windows
bat-files.
example
test.bat with content:
REM --
@ECHO ON
g.region -p
v.in.region output=myreg2
v.db.addtable map=myreg2
v.db.addcolumn map=myreg2 columns="col1 inetger"
REM --
then copy the path to the
Helmut Kudrnovsky wrote
>>> v.db.addcolumn map=myreg2 columns="col1 inetger"
>>
>>typo in 'inetger'?
>
> oh :-)
>
>> how does it fail?
>
> if you have several python modules listed in the bat file, only the first
> one starts, the ot
Anna Petrášová wrote
> On Wed, Jun 14, 2017 at 8:20 AM, Helmut Kudrnovsky
> hellik@
> wrote:
>> hi
>>
>> just started:
>>
>> System Info
>> GRASS version: 7.3.svn
>> GRASS SVN revision: r71182M
>> Build date: 2017-06-13
>> Bui
Helmut Kudrnovsky wrote
>
> Helmut Kudrnovsky wrote
>>>> v.db.addcolumn map=myreg2 columns="col1 inetger"
>>>
>>>typo in 'inetger'?
>>
>> oh :-)
>>
>>> how does it fail?
>>
>> if you have several python m
>> v.db.addcolumn map=myreg2 columns="col1 inetger"
>
>typo in 'inetger'?
oh :-)
> how does it fail?
if you have several python modules listed in the bat file, only the first
one starts, the other aren't invoked.
the reason may be: in winGRASS the python scripts are invoked by bat-file
Markus Neteler wrote
> On Wed, Jun 14, 2017 at 3:36 PM, Helmut Kudrnovsky
> hellik@
> wrote:
>> Anna Petrášová wrote
>>> On Wed, Jun 14, 2017 at 8:20 AM, Helmut Kudrnovsky
>>
>>> hellik@
>>
>>> wrote:
>>>> hi
>>
CM Reddy wrote
> Hi All,
>
> We are new to Grass GIS and it's implementation. We have downloaded and
> compiled the Grass 7.2 version and trying to add new modules.
>
> We had already imported a vector map using v.in.ogr command. Imported
> map has nodes or points (four nodes) . We would like
CM Reddy wrote
> Hi All,
>
> We are new to Grass GIS and it's implementation. We have downloaded and
> compiled the Grass 7.2 version and trying to add new modules.
>
> We had already imported a vector map using v.in.ogr command. Imported
> map has nodes or points (four nodes) . We would like
incorrectly
set in the BAT file.
Application is up and running.
- Thanks
CM
On 02-10-2017 14:48, Helmut Kudrnovsky wrote:
> CM Reddy wrote
>> Hi Moritz
>>
>> I did the steps mentioned in the following and compiled the code
>> successfully on Windows 10 machine
>very good idea! we are accumulating things to discuss like
>
>- specs for GRASS GIS 8
>- what's missing for 7.4.0
>
>Outreach:
>- maybe run a survey to know who uses GRASS GIS
>- offer more GRASS GIS courses
>- more online material, use Sphinx
>- set up a new web site (asap) with responsive
fyi, in [1] an interesting comparison about coordinates conversions.
[1]
https://www.geomatys.com/wordpress/index.php/2017/09/20/proj-4-versus-apache-sis-an-accuracy-comparison/?lang=en
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
Martin Landa wrote
> Hi,
>
> 2017-08-30 23:35 GMT+02:00 Markus Neteler
> neteler@
> :
>> So, 7.2.2RC2 is out!
>>
>> https://trac.osgeo.org/grass/wiki/Release/7.2.2-News#ReleaseCandidate2RC2
>>
>> Please heavily test!
>
> tomorrow it will be 7 days since RC2 has been published. Any objection
>
Markus Neteler wrote
> On Sun, Sep 10, 2017 at 3:58 PM, Martin Landa
> landa.martin@
> wrote:
>> 2017-09-10 12:33 GMT+02:00 Markus Neteler
> neteler@
> :
>>> Given the amount of changes after RC2 I would suggest to have still an
>>> RC3 these days.
>>
>> OK, please go ahead. Ma
>
> I am
http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
CM Reddy wrote
> Hi Moritz
>
> I did the steps mentioned in the following and compiled the code
> successfully on Windows 10 machine.
>
> * https://trac.osgeo.org/grass/wiki/CompileOnWindows
>
> No errors in the error.log file. It created grass executable successfully.
>
> Found following
CM Reddy wrote
> Hi Moritz
>
> I did the steps mentioned in the following and compiled the code
> successfully on Windows 10 machine.
>
> * https://trac.osgeo.org/grass/wiki/CompileOnWindows
>
> No errors in the error.log file. It created grass executable successfully.
>
> Found following
Veronica Andreo wrote
> Ciao Lu,
>
> I signed in and will attend the meeting tonight through IRC chat. I had
> some ideas in mind:
>
> - Design the t-shirt for the next code-sprint
> - Add examples to xx manual pages
> - Make a promo video for GRASS GIS
> - Make new tutorial videos for GRASS GIS
phone.
>
> Cheers,
> Vero
>
>
> El 21 ago. 2017 6:54 p.m., "Helmut Kudrnovsky"
> hellik@
> escribió:
>
> hi,
>
> just found it in the manual:
>
> https://grass.osgeo.org/grass73/manuals/v.in.ogr.html
>
> in the command itself it's &quo
hi,
just found it in the manual:
https://grass.osgeo.org/grass73/manuals/v.in.ogr.html
in the command itself it's "columns"
v.in.ogr [-flc2tojrewi] input=string [layer=string[,string,...]]
[output=name] [spatial=xmin,ymin,xmax,ymax[,xmin,ymin,xmax,ymax,...]]
[where=sql_query] [min_area=float]
>I guess running any of the modules I cite in #3405 [1], such as
>i.segment, r.surf.idw, etc in a non-ascii Windows environment.
if de/german Windows environment counts, no problem by testing the modules
listed in #3405.
-
best regards
Helmut
--
View this message in context:
hi,
on the windows download site we have following standalone installers
available for download:
GRASS GIS 7.2.1 (current stable)
GRASS GIS 7.0.5 (old stable)
GRASS GIS 6.4.4 (very old stable)
GRASS GIS 7.3 (development, daily builds)
WinGRASS-6.4.4-1-Setup.exe was uploaded at 2014-06-25.
as
>and OSGeo4W (Expr area) are available for testing.
wanted to test it on a windows 32bit box with OSGeo4W, but the installer
can't find the RC2 binaries.
the binaries are there:
http://download.osgeo.org/osgeo4w/x86/release/grass/grass/
in
>Windows packages [1] and OSGeo4W (Expr area) are available for testing.
just a quick screening of our source and of the OSGeo4W MS runtimes:
--
32bit:
https://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_2/mswindows/GRASS-Installer.nsi.tmpl#L900
900
Martin Landa wrote
> 2017-09-02 8:27 GMT+02:00 Helmut Kudrnovsky
> hellik@
> :
>>>and OSGeo4W (Expr area) are available for testing.
>>
>> wanted to test it on a windows 32bit box with OSGeo4W, but the installer
>> can't find the RC2 binaries.
Martin Landa wrote
> Hi,
>
> 2017-09-02 10:35 GMT+02:00 Helmut Kudrnovsky
> hellik@
> :
>>> did you mark Expr radiobox ? Ma
>> No, because I want to see and to have control what will be installed.
>
> I do not understand. In order to install RC you *must
Martin Landa wrote
> 2017-09-02 12:13 GMT+02:00 Martin Landa
> landa.martin@
> :
>> as I wrote, to see RC versions (testing area packages) you need to go
>> to Advanced install and mark Expr mode. There is no other way. Ma
>
> Expr like Experimental. Ma
had to resize the window to find the
>> Please heavily test!
>
>Windows packages [1] and OSGeo4W (Expr area) are available for >testing.
Now tested :
winGRASS (standalone, OSGeo4W) 32bit/64bit
Debian stretch 64bit
no issue so far.
-
best regards
Helmut
--
Sent from:
Veronica Andreo wrote
> Hi Anna,
>
> thanks for your answer... I'll try to clarify as much as possible, though
> I'm also rather new in the matter. @Madi & @Helli, please correct me if
> I'm
> wrong
>
> 2017-10-04 19:41 GMT+02:00 Anna Petrášová
> kratochanna@
> :
>
>> Hi Vero,
>>
>> On Wed,
Veronica Andreo wrote
> Hey devs,
>
> As the subject reads: We need more mentors for Google Code-In :)
>
> GCI is a competition addressed to high-school students aged 13-17, as an
> introduction to the open source world. They are supposed to complete as
> much tasks as possible to win the
Anna Petrášová wrote
> Hi Vero,
>
> On Wed, Oct 4, 2017 at 11:24 AM, Veronica Andreo
> veroandreo@
> wrote:
>> Hey devs,
>>
>> As the subject reads: We need more mentors for Google Code-In :)
>>
>> GCI is a competition addressed to high-school students aged 13-17, as an
>> introduction to the
Hi,
with the upcoming GRASS 7.4.x, should we remove 'GRASS GIS 7.0.5 (old
stable)' from the winGRASS download section on the website?
there haven't been many fixes in 7.0.x in the last year. And users should
use the new technology instead of the old one ;-)
any opinion?
-
best
Martin Landa wrote
> Hi,
>
> 2017-11-13 8:23 GMT+01:00 Martin Landa
> landa.martin@
> :
>> please wait also for Windows daily binaries. It will take some time to
>> set it up too. Ma
>
> wingrass builds consolidated:
>
> * no daily builds for G70, only addons for last version 7.0.5
> * daily
Maris Nartiss wrote
> 2017-11-25 11:46 GMT+02:00 Helmut Kudrnovsky
> hellik@
> :
>> here a win 10 with german locale; setting preferences in GRASS to en,
>> then I
>> get:
>>
>> --
>> All attempts to enable English language have fail
here a win 10 with german locale; setting preferences in GRASS to en, then I
get:
--
All attempts to enable English language have failed. GRASS running with C
locale.
If you observe UnicodeError in Python, install en_US.UTF-8 locale and
restart GRASS.
-
what does this
Moritz Lennert wrote
> On 25/11/17 10:46, Helmut Kudrnovsky wrote:
>> here a win 10 with german locale; setting preferences in GRASS to en,
>> then I
>> get:
>>
>> --
>> All attempts to enable English language have failed. GRASS running with C
&g
looking into
https://wingrass.fsv.cvut.cz/grass75/x86_64/
last exe seems to be
WinGRASS-7.5.svn-r71875-17-Setup-x86_64.exe 2017-12-01 06:50159M
the build logs shows:
[DIR] log-r71875-17/ 2017-12-02 09:07-
[DIR] log-r71873-16/ 2017-11-30 07:40-
Under https://grass.osgeo.org/download/software/ms-windows/
section
*GRASS GIS 7.3 (development, daily builds)*
Provided by OSGeoREL at the CTU in Prague, Czech Republic
download (32bit) | download (64bit)
should be renamed to
*GRASS GIS 7.5 (development, daily builds)*
and the links
Markus Metz-3 wrote
> ZSTD compression has been added to trunk with r71889-92.
>
> ZSTD compression can be added with configure --with-zstd=yes or simpler
> configure --with-zstd
>
> In order to get some wider testing, ZSTD is now the default compression
> method in trunk if ZSTD is available.
>
CM Reddy wrote
> Hi All,
>
> I tried to install Grass source on Windows 10 using the following link.
>
>
> https://trac.osgeo.org/grass/wiki/CompileOnWindows
>
>
> Downloaded the GRASS source from development trunk using the following
> commands.
>
> cd /usr/src
> svn checkout
601 - 700 of 1003 matches
Mail list logo
