Helmut Kudrnovsky wrote
>>Not that I know how to fix that, but what needs to be done?
>
> have look into
>
> 32bit issues:
>
> https://trac.osgeo.org/osgeo4w/ticket/429
> https://trac.osgeo.org/osgeo4w/ticket/539
>
> 64bit issues:
>
> https://trac.osgeo
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
Helmut Kudrnovsky wrote
> deactivated now lidar modules in winGRASS 32bit and 64bit by:
>
> [GRASS-SVN] r71920 - grass/trunk/mswindows/osgeo4w svn_grass at
> osgeo.org
> [GRASS-SVN] r71921 - grass/branches/releasebranch_7_4/mswindows/osgeo4w
> svn_grass at osgeo.org
&g
>I think the latter course of action is better in the short term. Howard,
Would this affect other software?
the GRASS lidar tools in QGIS; maybe also other sw.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
Martin Landa wrote
> Hi,
>
>> - build environment reverts back to the LASzip 2.2.0 version to use
>> libLAS
>
> yes, we can downgrade version in building environment, and also in
> packaging environment (for standalone installer). But osgeo4w will
> download latest version, and the modules will
regarding the lidar errors, have look into
/mswindows/OSGeo4W/package.sh
155 if [ "$MINGW_POSTFIX" = "64" ]; then
156 conf_host=x86_64-w64-mingw32
157 # see https://trac.osgeo.org/osgeo4w/ticket/539#ticket
158 # LAS support
[https://lists.osgeo.org/pipermail/grass-dev/2017-December/086838.html]
> Hi,
>
> I've updated to the EPSG v9.2 database.
>
> The relevant tickets/commits are:
> * libgeotiff: https://trac.osgeo.org/geotiff/changeset/2802
> * GDAL: https://trac.osgeo.org/gdal/ticket/7125
> * proj.4:
fyi
http://lists.maptools.org/pipermail/proj/2017-November/007849.html
All,
I think the current development cycle is coming to an end and a new release
should be made. It's been more than a year since that least release of
PROJ.4. In that period of time the library has improved
>it seems that some vector commands (e.g. v.buffer) doesn't work with
>v.external'ed vectors.
ok, in the settings, following option can be set/unset:
"For vector layers, use v.external (faster) instead of v.in.ogr"
unsetting this option, also vector commands seems to work.
-
best
>that this build uses GDAL from OSGeo4W,
yes it uses OSGeo4W GDAL
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
it seems there is an issue with winGRASS:
32 bit:
https://wingrass.fsv.cvut.cz/grass73/x86/logs/log-r71641-1/error.log
GRASS GIS 7.3.svn r71641 compilation log
--
Started compilation: Tue Nov 7 21:30:33 2017
--
Errors in:
Markus Neteler wrote
> On Sun, Nov 5, 2017 at 1:53 PM, Markus Neteler
> neteler@
> wrote:
>> Update: it is going on well!
>> https://github.com/qgis/QGIS/pull/5426
>>
>> An open wish is this enhancement ticket (r.mapcalculator script):
>> https://trac.osgeo.org/grass/ticket/3431
>
> AFAIK it
Andy Wickert-2 wrote
> Hello GRASS developers,
>
> The "six" python package, required by Matplotlib, seems to be missing on
> the Windows side. As a result, all packages requiring it are throwing
> errors. For example, as seen at
> http://wingrass.fsv.cvut.cz/grass72/x86/addons/latest/logs/:
>
>
Andy Wickert-2 wrote
> How about tkinter on Win64?
>
> *ImportError: No module named Tkinter*
which addon?
https://wingrass.fsv.cvut.cz/grass73/x86_64/addons/grass-7.3.svn/logs/v.faultdirections.log
v.faultdirections builds on 64 bit
-
best regards
Helmut
--
Sent from:
Helmut Kudrnovsky wrote
> Andy Wickert-2 wrote
>> How about tkinter on Win64?
>>
>> *ImportError: No module named Tkinter*
>
> which addon?
>
> https://wingrass.fsv.cvut.cz/grass73/x86_64/addons/grass-7.3.svn/logs/v.faultdirections.log
>
> v.f
>But there is some underlying package problem...
it seems six is in the winGRASS 64bit build environment, but not in the
winGRASS 32bit build environment.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
Helmut Kudrnovsky wrote
> fyi
> http://lists.maptools.org/pipermail/proj/2017-November/007849.html
>
> All,
>
> I think the current development cycle is coming to an end and a new
> release
> should be made. It's been more than a year since that least release of
Helmut Kudrnovsky wrote
> it seems there is an issue with winGRASS:
>
> 32 bit:
>
> https://wingrass.fsv.cvut.cz/grass73/x86/logs/log-r71641-1/error.log
>
> GRASS GIS 7.3.svn r71641 compilation log
> --
> Started compi
hi,
tested here a little bit with winGRASS7.2.2 and trunk.
test case:
- winGRASS in win10
- system locale: german
- switching in winGRASS from system locale (german) to en
- wxgui uses now en, only some buttons (e.g. in the startup wizzard: help,
quit) are still in the system locale
see
Markus Metz-3 wrote
> On Wed, Nov 15, 2017 at 1:36 PM, Helmut Kudrnovsky
> hellik@
> wrote:
>>
>> Background of the question in subject: the GRASS algs in upcoming QGIS3
> are
>> working with v.external linked data.
>>
>> I've seen some m
Background of the question in subject: the GRASS algs in upcoming QGIS3 are
working with v.external linked data.
I've seen some modules doesn't work with such kind of data.
Is there maybe a list already available?
-
best regards
Helmut
--
Sent from:
Markus Neteler wrote
> On Sun, Oct 22, 2017 at 4:13 PM, Markus Neteler
> neteler@
> wrote:
>> On Sun, Oct 22, 2017 at 1:00 PM, Helmut Kudrnovsky
> hellik@
> wrote:
>>> Markus Neteler wrote
>>>> On Oct 22, 2017 10:45 AM, "Jürgen E. Fischer
>Is there any instruction how to test it in windows?
according to
https://github.com/qgis/QGIS/pull/5426#issuecomment-342620619
it will be merged soon, thus testing will be easier.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
Markus Neteler wrote
> Hi,
>
> (subject renamed for clarity, original thread:
> part 1:
> https://lists.osgeo.org/pipermail/grass-dev/2017-October/thread.html#86395
> part 2:
> https://lists.osgeo.org/pipermail/grass-dev/2017-December/086738.html
> )
after little testing, I succeed to compile
>all what would be needed is to include zstd into the OSGeo4W >tree. will
open
>a ticket there.
for the record:
https://lists.osgeo.org/pipermail/osgeo4w-dev/2017-December/003453.html
thanks to Jürgen F. zstd is now included in OSGeo4W, now the changes in the
GRASS source/winGRASS compiling
Jerry Huang wrote
> Hello,
>
> I was attempting to download and install GRASS GIS (grass72_release) using
> the following link: https://trac.osgeo.org/grass/wiki/CompileOnWindows
>
> Following the steps, I get an error from running:
>
> OSGEO4W_POSTFIX=64 ./mswindows/osgeo4w/package.sh
>
>
Martin Landa wrote
> Hi,
>
> 2017-12-03 5:09 GMT+01:00 Jerry Huang
> jhuang37050@
> :
>> I was attempting to download and install GRASS GIS (grass72_release)
>> using
>> the following link: https://trac.osgeo.org/grass/wiki/CompileOnWindows
>
> to be precise you are not installing GRASS but
>Not that I know how to fix that, but what needs to be done?
have look into
32bit issues:
https://trac.osgeo.org/osgeo4w/ticket/429
https://trac.osgeo.org/osgeo4w/ticket/539
64bit issues:
https://trac.osgeo.org/osgeo4w/ticket/550
the liblas [1] tools and laszip in OSGeo4W are broken.
what
looking at
https://wingrass.fsv.cvut.cz/grass75/x86_64/logs/log-r71915-25/error.log
Started compilation: Sat Dec 9 21:35:30 2017
--
Errors in:
/c/msys64/usr/src/grass_trunk/raster/r.in.lidar
/c/msys64/usr/src/grass_trunk/raster3d/r3.in.lidar
/c/msys64/usr/src/grass_trunk/vector/v.out.lidar
Helmut Kudrnovsky wrote
> Helmut Kudrnovsky wrote
>>>all what would be needed is to include zstd into the OSGeo4W >tree. will
>> open
>>>a ticket there.
>>
>> for the record:
>>
>> https://lists.osgeo.org/pipermail/osgeo4w-dev/2017-Decem
-
best regards
Helmut
--
Sent from: 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
Helmut Kudrnovsky wrote
>>all what would be needed is to include zstd into the OSGeo4W >tree. will
> open
>>a ticket there.
>
> for the record:
>
> https://lists.osgeo.org/pipermail/osgeo4w-dev/2017-December/003453.html
>
> thanks to Jürgen F. zstd is now
Martin Landa wrote
> Hi,
>
> 2017-12-09 10:48 GMT+01:00
> svn_grass@
> :
>> -requires: liblas avce00 gpsbabel gs gdal-python matplotlib msvcrt iconv
>> libtiff gdal proj freetype-mingw pdcurses zlib fftw libpng wxpython
>> python-numpy python-pil pyopengl cairo psycopg2 rbatch
>> +requires:
>BTW, zstd-bin contains only zstd.exe and is also not needed.
I prefer to keep it as a tool available to handle such compressed data;
also zip/bzip/... as tools are included in winGRASS.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
Martin Landa wrote
> 2017-12-09 12:03 GMT+01:00 Helmut Kudrnovsky
> hellik@
> :
>> oh right. it should not be needed, but added to the instruction in the
>> wiki.
>> I'll change it.
>
> thanks, Ma
changed in svn and wiki.
-
best regards
Helmut
--
Se
Helmut Kudrnovsky wrote
> looking at
>
> https://wingrass.fsv.cvut.cz/grass75/x86_64/logs/log-r71915-25/error.log
>
> Started compilation: Sat Dec 9 21:35:30 2017
> --
> Errors in:
> /c/msys64/usr/src/grass_trunk/raster/r.in.lidar
> /c/msys64/usr/src/grass_trun
-
best regards
Helmut
--
Sent from: 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
Helmut Kudrnovsky wrote
>>Re: bugfix. I could also change the name to "Jaeger". Let me know what
>>you prefer.
>
> any chance for the bugfix? winGRASS will be still broken until the fix.
>
> I'm in favor of:
>
> """
> # -*- coding: utf-
Markus Neteler wrote
> On Oct 22, 2017 10:45 AM, "Jürgen E. Fischer"
> jef@
> wrote:
>>
>> Hi Markus,
>>
>> On Sun, 22. Oct 2017 at 09:37:02 +0200, Markus Neteler wrote:
>> > Does anyone know the current state of GRASS GIS support in QGIS3?
>>
>> GRASS support is still completely disabled in
have a look into
https://lists.osgeo.org/pipermail/gdal-dev/2018-May/048552.html
for interesting new proj(4)/GDAL development
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing
NikosAlexandris wrote
> Dears,
>
> before creating the HPC related Wiki,
>
> I would like to ask for your advise on hard-linking raster maps files.
>
> Soeren suggested this as a tip, I understand to save time and space.
> Hard-linking was also mentioned inside the JEODPP (JRC) team at some
>
Markus Neteler wrote
> On Tue, May 15, 2018 at 11:46 AM, Martin Landa
> landa.martin@
> wrote:
>> Hi Markus,
> ...
>> it's two weeks from RC1, I would go ahead with RC2. Any objections?
>> Martin
>
> Yes, fine for me. I can tag it tomorrow night.
what are the main fixes to go from RC1 to
>but after creating thousands of raster maps with ZSTD >compression on
different systems,
tested zstd on Windows for some time now, no problems so far.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
> I hope there is enough people interested in this feature to test it on
Windows.
I can do the testing in winGRASS.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
>...
>ERROR: Extension not found
addons for winGRASS are only compiled once a day, you have to try it
tomorrow again.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
>> for installing system wide in windows administrator rights are needed.
maybe
>> some possible source of troubles.
>
>The .libPaths(Sys.getenv('R_LIBS_USER')) call should set the
>installation directory to the user's. But maybe this is not guaranteed
>to be defined which wouldn't make it a good
>>Here is a summary of some ideas from the recent discussion on >the list and
in our lab:
>https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup
"Scariness of and bad associations with terminal window/command line on
Windows (but consistency and most people seem to ignore it anyway)"
>3) Is there any blocking issue?
> Ctypes are not fully compatible with the Python3 even if they are
>compiling without any issues. Discussed witb mentors about the >next
>steps and how to deal with ctypes.
ctypes seems not to be actively maintained anymore. Are there any
alternatives?
Hi Moritz,
Moritz Lennert wrote
> Hi everyone,
>
> I have a vague memory that someone has coded this before, but cannot
> find it anywhere, but before I code it myself I wanted to know if my
> vague memory actually was right: I need a module that takes a
> qualitative raster map (e.g. land
Hi Anna,
>ctypes is standard Python package, ctypesgen is what is not much maintained
yes I meant ctypesgen.
> although there are forks with some Python3 changes Sanjeet was using.
> There are alternatives to ctypes >such as cffi, Pietro did some initial
> work. However given the fact that
Anna Petrášová wrote
> Hi,
>
> I can't add and comment to a ticket, specifically this one:
> https://trac.osgeo.org/grass/ticket/3556 (I wanted to close it)
> It's something wrong with permissions, although I am logged in. Is
> anybody having the same problem, or it's just me?
>
> Thank you,
>
looking into winGRASS build logs:
https://wingrass.fsv.cvut.cz/grass73/x86_64/logs/log-r71566-385/error.log
https://wingrass.fsv.cvut.cz/grass73/x86_64/logs/log-r71567-385/error.log
recent r.plane commits seems to break winGRASS builds:
GRASS GIS 7.3.svn r71567 compilation log
>v.clip and v.profile are IMHO important functionality for 7.4.0.
+1 for these 2 addons
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
>Re: bugfix. I could also change the name to "Jaeger". Let me know what
>you prefer.
any chance for the bugfix? winGRASS will be still broken until the fix.
I'm in favor of:
"""
# -*- coding: utf-8 -*-
"""
-
best regards
Helmut
--
Sent from:
hi,
it seems that wingrass-daily is not updated on http://download.osgeo.org.
comparing:
https://wingrass.fsv.cvut.cz/grass73/x86_64/osgeo4w/
[latest entry:]
grass-daily-7.3.svn-r71600-393.tar.bz2 28-Oct-2017 07:19 59M
with:
Neev Mistry wrote
> Dear GRASS GIS developers, I am Neev Mistry (Eric1234), a student
> participating in the 2017 Google Code-In. I have been having some trouble
> with compiling and installing GRASS GIS on Windows. I have followed the
> instructions on
hi,
just tested compiling GRASS on windows; compilation works fine with the
instruction in:
https://trac.osgeo.org/grass/wiki/CompileOnWindows
but I've found in one of the last steps of installing following issue:
grass75svn.bat is copied to
C:\OSGeo4W64\bin\grass75svn.bat
the content is:
Martin Landa wrote
> Hi,
>
> 2018-01-06 21:27 GMT+01:00 Helmut Kudrnovsky
> hellik@
> :
>> SET OSGEO4W_ROOT=@osgeo4w@ <=
>
> [...]
>
>> SET OSGEO4W_ROOT=C:\OSGeo4W64
>> [...]
>> --
>>
>> it seems @osg
-
best regards
Helmut
--
Sent from: 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
Neev Mistry wrote
> Dear GRASS GIS developers, I am Neev Mistry (Eric1234), a student
> participating in the 2017 Google Code-In. I have been having some trouble
> with compiling and installing GRASS GIS on Windows. I have followed the
> instructions on
>> SET OSGEO4W_ROOT=@osgeo4w@
>>
>
>the process is dedicated for creating osgeo4w package.
ok
>Anyway, created package must contain original bat file.
ok
>we could fix the local installation process (after the osgeo package
>is created).
if it's possible, yes.
otherwise we have to extend
Markus Neteler wrote
> Am 25.01.2018 6:37 nachm. schrieb "Martin Landa"
> landa.martin@
> :
>
> Hi,
>
> 2018-01-25 17:52 GMT+01:00 Markus Neteler
> neteler@
> :
>>> what about backporting changes in i.atcorr? Ma
>>
>> There are quite a lot, and still ongoing...
>
> probably @MarkusM will
See http://lists.maptools.org/pipermail/proj/2018-February/007966.html
5.0.0 Release Notes
---
This version of PROJ introduces some significant extensions and
improvements to (primarily) the geodetic functionality of the system.
The main driver for introducing the new
>I don't know how difficult it would be to create such algorithm
>descriptions automagically.
for a better overview:
processing module description:
https://github.com/qgis/QGIS/tree/9fb386ac60f5e3155294b712ed064ad97eba3226/python/plugins/processing/algs/grass7/description
and related python
Von: "Moritz Lennert"
>I don't know how difficult it would be to create such algorithm
>descriptions automagically.
https://github.com/qgis/QGIS/search?p=1=processing+grass==%E2%9C%93
AFAIU there are some general python scripts to provide it in processing:
e.g.
Anna Petrášová wrote
> Hi,
>
> I ran into a weird problem with KML with 3D line, v.import failed when
> reprojecting it:
>
> WARNING: pj_transform() failed: latitude or longitude exceeded limits
>
> This happened with GRASS 7.4.0 64bit (GDAL 2.2.3) on Windows 10, on my
> Ubuntu with latest
Helmut Kudrnovsky wrote
> trying
>
> ogr2ogr -f KML ogr2ogr_flight.kml attachment-0001.kml
> Warning 1: Layer name 'Flight 1' adjusted to 'Flight_1' for XML validity.
> Warning 1: The output driver does not natively support DateTime type for
> field timestamp. Miscon
pcav wrote
> Il 08/02/2018 15:49, Nikos Alexandris ha scritto:
>> * Moritz Lennert
> mlennert@.worldonline
> [2018-02-08 15:20:14
>> +0100]:
>>
>>> On 08/02/18 15:08, Nikos Alexandris wrote:
I guess, there are numerous cases like this one. What would,
effectively, mean a removal of
Martin Landa wrote
> Hi,
>
> 2018-02-06 23:12 GMT+01:00 Helmut Kudrnovsky
> hellik@
> :
>> this is part of QGIS success and this question has also to be answered by
>> the QGIS community.
>>
>> This may be an indication that OSGeo's inter-project co
Hi Paolo,
pcav wrote
> Hi all,
> following the discussion on qgis-dev ML:
> https://lists.osgeo.org/pipermail/qgis-developer/2018-January/051701.html
> it has been proposed to remove all external providers (namely OTB,
> already removed, GRASS, and SAGA) from Processing in QGIS2 (GDAL will
>
Markus Neteler wrote
> On Mon, Feb 12, 2018 at 5:37 PM, Michael Barton
> Michael.Barton@
> wrote:
>> It’s $100 per year for a developer account. I have an account. But
>> perhaps we should open a GRASS account for this. Any thoughts on this?
>
> This would probably make sense. Or, OSGeo on
Markus Neteler wrote
> On Mon, Feb 12, 2018 at 5:37 PM, Michael Barton
> Michael.Barton@
> wrote:
>> It’s $100 per year for a developer account. I have an account. But
>> perhaps we should open a GRASS account for this. Any thoughts on this?
>
> This would probably make sense. Or, OSGeo on
Yann Chemin wrote
> Hi
>
>
> I am teaching grass at uni this week following the grass starter tutorial
> (grass promo svn)
>
> On windows, r.mapcalc does not process double if statements an multiple
> cases of || && in a single expression. Also the expression quotes are
> remove by
>We used the tutorial in grass=promo/tuorials/grassstarter, the script at the
end essentially, running on >Spearfish dataset.
hopefully found the right cmds (easier would be posting directly the
commands here).
workflow here in winGRASS7.4.0:
r.buffer input=streams@PERMANENT output=bstreams500
>r.mapcalc expression=if(case1,if(case2,Val2True,Val2False),Val1False))
>
>This expression will fail, note that the lack of quote is intentional, as
it is a requirement to run simpler >r.mapcalc statements in WinGRASS.
when, in winGRASS, I copy from r.mapcalc:
r.mapcalc expression="rbstreams500
>I conducted a GRASS GIS course this week and we found some bugs on WinGRASS:
the subject of this report is _(WinGRASS)_ and _aconda 7.5dev on Mac_
which winGRASS version have you used? 7.4.0? 7.5dev? another version?
-
best regards
Helmut
--
Sent from:
>We had a mix of installations on Windows:
>1 - QGIS standalone with GRASS7.2.2. (GRASS could also be run standalone it
seems)
>2 - WinGRASS 7.4.0. mostly direct install, but maybe some from OSGEO4W too.
>3 - WinGRASS7.5svn nightly
there shouldn't be much difference in behaviour
>We tried to use
>*wxGUI console:
>r.mapcalc expression=s_sl = if( rbstreams500@yann == 1, if( slope@PERMANENT
><= 5, 2, 5 ), 0 )
>(Tue Feb 20 13:30:06 2018) Command finished (0 sec)
I put quoted r.mapcalc term into the wxGUI; but it seems the quotes are
stripped in the wxGUI output window. mmm
-
If anyone interested
https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018#future-of-processing-providers
there you can find the info about the discussion meeting regarding Future of
QGIS processing/external alg providers
Proposed schedule: 23/02 10:30 -
Luca Delucchi wrote
> Il 22 feb 2018 7:27 PM, "Helmut Kudrnovsky"
> hellik@
> ha scritto:
>
> If anyone interested
>
> https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018#
> future-of-processing-providers
>
> there you can find the inf
Helmut Kudrnovsky wrote
> hi,
>
> fresh svn up and make clean, any idea why compilations may fail:
>
> --
> Started compilation: Fr 23. Feb 16:55:33 CET 2018
> --
> Errors in:
> /home/bugs/dev/cpp/grass7_trunk/raster/r.s
hi,
fresh svn up and make clean, any idea why compilations may fail:
--
Started compilation: Fr 23. Feb 16:55:33 CET 2018
--
Errors in:
/home/bugs/dev/cpp/grass7_trunk/raster/r.sunmask
/home/bugs/dev/cpp/grass7_trunk/raster/r.support
--
In case of
Hi,
according to [1] it seems a new proj.4 version, now called PROJ 5.0.0, will
be out in the beginning of March.
anyone already tried to compile GRASS with PROJ 5.0.0 RC?
[1] http://lists.maptools.org/pipermail/proj/2018-February/007990.html
-
best regards
Helmut
--
Sent from:
hi,
in [1], I've updated the instructions to compile GRASS on windows platforms.
compilation steps based upon the both frameworks OSGeo4W and MSYS2 are
straightforward; the list of mentioned dependencies are up-to-date.
producing VC libraries using dumpbin command is one of the
See
https://lists.osgeo.org/pipermail/grass-web/2018-August/004876.html
https://lists.osgeo.org/pipermail/grass-dev/2018-August/089232.html
https://wingrass.fsv.cvut.cz/grass75/x86_64/
it seems there are issues in the winGRASS build/compilation.
anything we could do?
-
best regards
>I read here [1] that the addons manual pages are updated daily but regarding
i.sentinel.mask the link refers >to the old version of the manual while
i.sentinel.preproc still doesn't appear.
last update of this site: Sat Jul 21 20:45:20 UTC 2018
@Martin and/or @Markus: could be the update
Martin Landa wrote
> winGRASS builds including addons are back. Ma
thanks for the fix
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
Hi Roberta,
>The title of the project is "GRASS GIS module for Sentinel-2 cloud >and
shadow detection". It adds new tools for the processing of >Sentinel 2
images to GRASS GIS software (Organization: OSGeo).
Thanks for the nice addon!
Does your addon also work with already atmospheric
>So addons are off line for the moment?
What about a svn checkout of the addon svn repo and installing it from the
local source?
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev
Roberta,
>Obviously, it would be easier for me to use the existing addon
(i.sentinel.download) but I struggled quite a >ot to avoid pandas and other
dependencies ;-). I do not know if it makes sense to add it now in order to
>integrate a module that already exists and that users can use
just installed standalone WinGRASS-7.5.svn-r72999-198-Setup-x86_64.exe
after installation, WinGRASS-7.5.svn doesn't start cause of a missing
zstd.dll
maybe the winGRASS-OSGeo4W packaging environment is missing this dll?
-
best regards
Helmut
--
Sent from:
>fixed, Ma
thanks for fixing.
trying to open https://wingrass.fsv.cvut.cz/grass75/x86_64 in
firefox/chrome/edge, it can't be accessed cause of an invalid cert, e.g.
error code: DLG_FLAGS_SEC_CERT_DATE_INVALID
-
best regards
Helmut
--
Sent from:
>error code: DLG_FLAGS_SEC_CERT_DATE_INVALID
firefox reports:
error code: SEC_ERROR_EXPIRED_CERTIFICATE
it seems the certificate of the server expired at 17 July 2018
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
dressik wrote
> Hello, I need to do GRASS anaglyph to school. Which version
> has d.anaglyph please? I have GRASS 7.4.1, i installed 6.4.0; 6.4.1RC1;
> 6.3.0 and none has d.anaglyph.
it's a GRASS 6 addon:
http://grasswiki.osgeo.org/wiki/AddOns/GRASS_6#d.anaglyph
-
best regards
Helmut
--
> > Deprecated since version 2.7: The optparse module is deprecated and
will not
>> be developed further; development will continue with the argparse
module.
>
>Can you add optparse package? It's weird, it should be part of standard
Python library:
Martin Landa wrote
> Hi,
>
> út 4. 9. 2018 v 16:22 odesílatel Jürgen E. Fischer
> jef@
> napsal:
>> Also added a wxpython transitional package that depends on python-wx.
>> msys-grass and in turn grass6 still depend on it.
>
> I would prefer to avoid any transitional packages if possible. I
>So far it seems to be that the Python virtual env works and, alternatively,
changing PATH (perhaps >together with creating a symlink) should work too.
Also those who needed to workaround that they distro >has python -> python3
symlink don't need to do the workaround anymore. Finally, we could
>would like to participate in GSoC 2017.
happy 2018 ;-)
>Do you have some other ideas what I should do?
Have a look into the students basic recommendations:
https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students
-
best regards
Helmut
--
Sent from:
Aasheesh Tiwari wrote
> -- Forwarded message -
> From: Aasheesh Tiwari
> aasheesht50@
>
> Date: Tue, 20 Feb 2018 at 9:48 PM
> Subject: GSoC Guidance
> To:
> grass-dev@.osgeo
>
>
>
> Dear all,
> I am Aasheesh Tiwari from India. Currently, I am pursuing Masters in
>
fyi
https://github.com/OSGeo/proj.4/milestones?direction=asc=due_date=open
-
5.0.1
Due by April 1, 2018 Last updated 4 days ago
Bug fixes.
5.1.0
Due by June 1, 2018 Last updated 4 days ago
New API revisions in response to actual use Bug fixes Security patches
701 - 800 of 1003 matches
Mail list logo
