[QGIS-Developer] phasing out OSGeo4W QGIS/GRASS 32bit

2020-05-15 Thread Helmut Kudrnovsky 
Hi,

in the GRASS community, we're thinking about to phase out winGRASS 32bit
versions in 2020, see [1].

in [2] Upgrade Qt version to latest 5.12.x LTR, I saw following comment:


The current idea is to switch to 5.14 and use the occasion to upgrade
compilers and drop 32bit (according to the latest qgis survey only 7% of the
participants still use it).


related:
https://www.bleepingcomputer.com/news/microsoft/rip-microsoft-to-drop-support-for-windows-10-on-32-bit-systems/

"Microsoft to drop support for Windows 10 on 32-bit systems:

Microsoft has stated that future versions of Windows 10, starting with the
May 2020 Update, will no longer be available as 32-bit builds on new OEM
computers."

all in all a good moment to phase out OSGeo4W 32bit :-)

any schedule to drop 32bit QGIS on windows by the QGIS community/devs?

I think a joint announcement about dropping 32bit by both communities
(GRASS/QGIS) whould be good.

any ideas?

[1] https://lists.osgeo.org/pipermail/grass-psc/2020-January/002094.html
[2] https://trac.osgeo.org/osgeo4w/ticket/627



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] WinGRASS build up (WIP)

2019-11-06 Thread Helmut Kudrnovsky 
>next daily builds (32/64bit) should be built against GDAL3/PROJ6.

daily build 78:
 
https://wingrass.fsv.cvut.cz/grass78/x86_64/logs/log-r9c8923eb9-9/package.log

##

[...]
checking for location of External PROJ includes... /c/OSGeo4W64/include
checking for proj.h... yes
checking External PROJ major version... 6
checking External PROJ minor version... 2
checking External PROJ patch version... 1
found PROJ version 6.2.1
using new PROJ version 5+ API
checking for location of External PROJ library... 
/usr/src/grass78/mswindows/osgeo4w/lib
checking for proj_pj_info in -lproj... yes
checking for location of External PROJ data files... /c/OSGeo4W64/share/proj
checking for /c/OSGeo4W64/share/proj/epsg... no
configure: warning: *** Unable to locate PROJ data files.
[...]
GDAL support:   yes

##

daily build 79:

https://wingrass.fsv.cvut.cz/grass79/x86_64/logs/log-r39af5f541-9/package.log

##

[...]
checking for location of External PROJ includes... /c/OSGeo4W64/include
checking for proj.h... yes
checking External PROJ major version... 6
checking External PROJ minor version... 2
checking External PROJ patch version... 1
found PROJ version 6.2.1
using new PROJ version 5+ API
checking for location of External PROJ library... 
/usr/src/grass79/mswindows/osgeo4w/lib
checking for proj_pj_info in -lproj... yes
checking for location of External PROJ data files... /c/OSGeo4W64/share/proj
checking for /c/OSGeo4W64/share/proj/epsg... no
configure: warning: *** Unable to locate PROJ data files.
[...]
GDAL support:   yes

##

daily builds with proj6/gdal3 in OSGeo4W looks good so far.

regards
Helmut
 


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] WinGRASS build up (WIP)

2019-11-05 Thread Helmut Kudrnovsky 
>> I could do a test compilation with OSGeo4W testing/experimental mode and issue a
>>
>> grass-7.8.1RC1-2.tar.bz2
>>
>> with test in setup.hint.
>
>Thanks.
 

now locally switched to gdal3/proj6 for compiling winGRASS, see

 

###

 


C:\>gdalinfo --version
GDAL 3.0.2, released 2019/10/28

C:\>cs2cs --version
Rel. 6.2.1, November 1st, 2019

 

###

GRASS is now configured for:  x86_64-w64-mingw32

  Source directory:   /usr/src/rc_nexgen/grass-7.8.1RC1
  Build directory:    /usr/src/rc_nexgen/grass-7.8.1RC1
  Installation directory: ${prefix}/grass78
  Startup script in directory:/c/OSGeo4W64/bin
  C compiler: gcc -g -O2
  C++ compiler:   c++ -g -O2
  Building shared libraries:  yes
  OpenGL platform:    Windows

  MacOSX application: no
  MacOSX architectures:   
  MacOSX SDK:     

  BLAS support:   no
  BZIP2 support:  yes
  C++ support:    yes
  Cairo support:  yes
  DWG support:    no
  FFTW support:   yes
  FreeType support:   yes
  GDAL support:   yes
  GEOS support:   yes
  LAPACK support: no
  Large File support (LFS):   yes
  libLAS support: yes
  MySQL support:  no
  NetCDF support: no
  NLS support:    yes
  ODBC support:   yes
  OGR support:    yes
  OpenCL support: no
  OpenGL support: yes
  OpenMP support: no
  PDAL support:   no
  PNG support:    yes
  POSIX thread support:   no
  PostgreSQL support: yes
  Readline support:   no
  Regex support:  yes
  SQLite support: yes
  TIFF support:   yes
  X11 support:    no
  Zstandard support:  yes

  using new PROJ 5+ API

 

###

GRASS GIS 7.8.1RC1 exported compilation log
--
Started compilation: Tue Nov  5 22:20:43 CET 2019
--
Errors in:
No errors detected.
--
Finished compilation: Tue Nov  5 23:04:48 CET 2019

 

###

System Info     
GRASS Version: 7.8.1RC1     
Code revision: exported     
Build date: 2019-11-05  
Build platform: x86_64-w64-mingw32  
GDAL: 3.0.2 <=    
PROJ: 6.2.1 <= 
GEOS: 3.8.0     
SQLite: 3.29.0  
Python: 3.7.0   
wxPython: 4.0.3     
Platform: Windows-10-10.0.18362-SP0 (OSGeo4W)

###

 

will promote it now as testing to OSGeo4W 64 bit

 

regards

Helmut


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] WinGRASS build up (WIP)

2019-11-05 Thread Helmut Kudrnovsky 
Hi Jürgen,

>Or just build GRASS with the "test" packages, upload it and then we can remove
>all the "experimental" tags.

just checked OSGeo4W, to be sure:

OSGeo4W normal mode

GDAL 2.4.1-1
PROJ 5.2.0-1
GEOS 3.8.0-1

OSGeo4W testing/experimental mode, update would be

GDAL 2.4.1-1 => GDAL 3.0.2-1
PROJ 5.2.0-1 => PROJ 6.2.1-1
GEOS 3.8.0-1

I could do a test compilation with OSGeo4W testing/experimental mode and issue a

grass-7.8.1RC1-2.tar.bz2

with test in setup.hint.

not sure how ready Martin's build environment is to switch also to build addons 
?!

regards
Helmut
 
 

Gesendet: Dienstag, 05. November 2019 um 18:56 Uhr
Von: "Jürgen E. Fischer"

Betreff: Re: Re: WinGRASS build up (WIP)
Hi Helmut,

On Tue, 05. Nov 2019 at 18:30:18 +0100, Helmut Kudrnovsky wrote:
> >Any idea when GRASS will be updated with the new dependencies?
>
> see https://github.com/OSGeo/grass/pull/136#issuecomment-547497328

> "Sure it is still GDAL2"

> is OSGeo4W still default in gdal2/proj5? is gdal3/proj6 still in OSGeo4W 
> experimental/testing?

I went ahead an did all what is proposed there and now you can build GRASS with
GDAL3 and PROJ6 using the "experimental" packages. Once that's done we can
flip the switch and take all the "experimental" packages live - they are only
waiting for GRASS.


> in #136, environment is pointing to gdal-dev proj-dev, which I assume is 
> gdal3/proj6, right?

No, GDAL master (3.1 2b) and PROJ master (7.0 2b). And #136 is for master
(ie. grass-daily)

#137 was for the release branch and was merged.


> GRASS is in a RC cycle for GRASS 7.8.1: RC1

With #118 merged - so it should already work with GDAL3 and PROJ6.


> a possible workflow may be (?):

> (1) update/adapt #136 to reflect a default gdal3/proj6 in OSGeo4W
> (2) apply updated PR to issue a GRASS 7.8.1 RC2
> (3) switch OSGeo4W to a default gdal3/proj6
> (4) binary release GRASS 7.8.1 RC2 in OSGeo4W

Or just build GRASS with the "test" packages, upload it and then we can remove
all the "experimental" tags.


Jürgen

--
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50
Software Engineer D-26506 Norden https://www.norbit.de[https://www.norbit.de]
QGIS release manager (PSC) Germany IRC: jef on FreeNode
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/[https://www.norbit.de/83/]
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] WinGRASS build up (WIP)

2019-11-05 Thread Helmut Kudrnovsky 
>Any idea when GRASS will be updated with the new dependencies?

see https://github.com/OSGeo/grass/pull/136#issuecomment-547497328

"Sure it is still GDAL2"

is OSGeo4W still default in gdal2/proj5? is gdal3/proj6 still in OSGeo4W 
experimental/testing?

in #136, environment is pointing to gdal-dev proj-dev, which I assume is 
gdal3/proj6, right?

GRASS is in a RC cycle for GRASS 7.8.1: RC1

a possible workflow may be (?):

(1) update/adapt #136 to reflect a default gdal3/proj6 in OSGeo4W
(2) apply updated PR to issue a GRASS 7.8.1 RC2
(3) switch OSGeo4W to a default gdal3/proj6
(4) binary release GRASS 7.8.1 RC2 in OSGeo4W

@Martin: any opinion?

Kind regards
Helmut


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] WinGRASS build up (WIP)

2019-11-04 Thread Helmut Kudrnovsky 
Hi Jürgen,

just updated my OSGeo4W in normal mode (not tick Exp), QGIS, GRASS 7.8.0, I'm 
getting an error that gdal300.dll and proj6.2.x.dlll is missing.


regards
Helmut
 
 

Gesendet: Montag, 04. November 2019 um 18:39 Uhr
Von: "Jürgen E. Fischer" 
An: "Martin Landa" 
Cc: grass-u...@lists.osgeo.org, qgis-developer@lists.osgeo.org, 
osgeo4w-...@lists.osgeo.org, "Helmut Kudrnovsky" 
Betreff: Re: WinGRASS build up (WIP)
Hi Martin,

I added "experimental" packages to OSGeo4W (ie. only available if you tick Exp
in the OSGeo4W installer):

- PROJ 6.2.1
- GDAL 3.0.2
- liblwgeom 3.0.0
- OGDI 4.1.0
- Rebuilds of QGIS 3.10.0, QGIS 3.4.13 and spatialite 4.3.0a against the above
packages
- Backward compatibility packages gdal204dll and proj5dll that carry the 
original
DLLs from PROJ 5.2.0 and GDAL 2.4.1

The only missing bit is GRASS built against new GDAL and PROJ. Once that's is
available I can remove the "experimental" tag.


Jürgen

--
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50
Software Engineer D-26506 Norden https://www.norbit.de
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/[https://www.norbit.de/83/]
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] GRASS GIS (trunk) and python 3 - testing welcome

2019-01-27 Thread Helmut Kudrnovsky 
Dear OSGeo community,

the GRASS GIS dev team is working on a python 3-support/transition [1] of the 
source code in trunk [2].
 
winGRASS GIS 7.7svn daily builds with python 3 are already available as 
standalone installers [3] or in OSGeo4W [4]; see:

System Info 
GRASS Version: 7.7.svn  
GRASS SVN revision: r74011  
Build date: 2019-01-25  
Build platform: x86_64-w64-mingw32  
GDAL: 2.4.0 
PROJ.4: 5.2.0   
GEOS: 3.7.0 
SQLite: 3.26.0  
Python: 3.7.0  <==  
wxPython: 4.0.3 
Platform: Windows-10-10.0.17763-SP0 (OSGeo4W)  

In [5] there are hints how to test it in e.g. Linux.

As the GRASS GIS transition to python 3 covers changes in many lines of code, a 
broader testing by the community is very welcome.

Problems and bugs can be reported in the GRASS GIS trac [6].
 
Thanks and kind regards
Helmut

[1] https://trac.osgeo.org/grass/wiki/Python3Support
[2] https://trac.osgeo.org/grass/browser/grass/trunk
[3] https://grass.osgeo.org/download/software/ms-windows/
[4] https://trac.osgeo.org/osgeo4w/
[5] https://trac.osgeo.org/grass/wiki/Python3Support#Linux
[6] https://trac.osgeo.org/grass
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] GSoC 2019 - Call for mentors and ideas

2019-01-25 Thread Helmut Kudrnovsky 
Dear OSGeo community,

It is time for *GSoC* [1] this year, so this is our starting information to get 
involved!

If you are willing to act as a mentor [2], fill in this form:

< https://goo.gl/forms/njL27YLWBVensZ3m1 >

If you want to participate proposing ideas, you just need 
to send us (admins:  ) the URL for your project's
ideas page.

Remember that every idea should indicate:

• A title
• A description
• 2 mentors 
• A test for the students to submit to your evaluation. The test aims at 
evaluating if the student is capable for the project, so please design the test 
having in mind the skills required to complete the project.

Time is short, we need to collect all URLs by Feb 4. Here the timeline [3].

Thanks and please forward to your project community.

Your OSGeo GSoC admins

[1] https://summerofcode.withgoogle.com/
[2] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019_Administrative
[3] https://summerofcode.withgoogle.com/how-it-works/#timeline
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] [Qgis-user] New Features in Shape Tools 3.2.0

2018-10-01 Thread Helmut Kudrnovsky 
>I'm struggling to work out where the difference lies between the code
>paths. Do you mind sharing the values from the st state struct when
>G_ellipsoid_polygon_area is called for this polygon?
>
>Nyall 

delivered by Markus Metz, GRASS dev:

st->AE: 40408299984661.4
st->QA: 0.00446291999342754
st->QB: 2.6340714427e-05
st->QC: 1.71432450253425e-07
st->QbarA: -1.00448998025995
st->QbarB: 0.0015057373196404
st->QbarC: -5.48062628444059e-06
st->QbarD: 2.44903500362035e-08
st->Qp: 1.00448998025995
st->E: 510065621153775

precision: %.15g

by adding a debug message in GRASS: in lib/gis/area_poly1.c add debug
messages in G_begin_ellipsoid_polygon_area().





-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] [Qgis-user] New Features in Shape Tools 3.2.0

2018-10-01 Thread Helmut Kudrnovsky 
Helmut Kudrnovsky wrote
>>[...]
>>Caris LOTS: 14.737 km^2
>>ArcMap: 14.727,446 km^2
>>MapInfo:14.727,352 km^2
>>GeoMedia:   14.726,443 km^2
>>Planimeter: 14.722,522 km^2
>>QGIS 3.2:   14.652,181 km^2
>>QGIS 2.8:   14.652,181 km^2
>>[...]
>>My suspicion is that the geodesic algorithm used by QGIS (and apparently
> GRASS) is to blame here.
> 
> a quick check in GRASS 7.7.svn shows :-)
> 
> |m2|km2|
> |14718097678,673|14.718,097679|
> 
> 
> 
> -
> best regards
> Helmut
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> ___
> QGIS-Developer mailing list

> QGIS-Developer@.osgeo

> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

forwarding from the GRASS GIS dev ML:
[https://lists.osgeo.org/pipermail/grass-dev/2018-October/090080.html]

--
On Tue, Sep 25, 2018 at 7:38 PM Helmut Kudrnovsky wrote:
>
> fyi see
>
https://lists.osgeo.org/pipermail/qgis-developer/2018-September/054644.html
>
> with GRASS mentioned
> --
> Kristian Evers:
>
> Right, here are the calculated areas as returned by a number of different
> GIS applications and the planimeter app of GeographicLib for reference:
>
> Caris LOTS: 14.737 km^2
> ArcMap: 14.727,446 km^2
> MapInfo:14.727,352 km^2
> GeoMedia:   14.726,443 km^2
> Planimeter: 14.722,522 km^2
> QGIS 3.2:   14.652,181 km^2
> QGIS 2.8:   14.652,181 km^2

adding to the confusion:

I used the geographiclib API as included in PROJ 5.2.0 following the
example for geod_polygonarea() in geodesic.h and get
geographiclib: 14,737.935 km^2
quite different from
Planimeter: 14,722.522 km^2

GRASS native gives 14,718.097679
as also reported by Helmut and Stefan

Markus M
--



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] [Qgis-user] New Features in Shape Tools 3.2.0

2018-09-25 Thread Helmut Kudrnovsky 
>[...]
>Caris LOTS: 14.737 km^2
>ArcMap: 14.727,446 km^2
>MapInfo:14.727,352 km^2
>GeoMedia:   14.726,443 km^2
>Planimeter: 14.722,522 km^2
>QGIS 3.2:   14.652,181 km^2
>QGIS 2.8:   14.652,181 km^2
>[...]
>My suspicion is that the geodesic algorithm used by QGIS (and apparently
GRASS) is to blame here.

a quick check in GRASS 7.7.svn shows :-)

|m2|km2|
|14718097678,673|14.718,097679|



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

2018-02-06 Thread Helmut Kudrnovsky 
pcav wrote
> Il 05/02/2018 22:03, Helmut Kudrnovsky ha scritto:
>> and see here for a follow up in the GRASS community:
>> 
>> http://osgeo-org.1560.x6.nabble.com/Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352828.html
>> http://osgeo-org.1560.x6.nabble.com/Re-GRASS-user-Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352836.html
> 
> Thank you Helmut. Following our PSC meeting, I'll start an open
> discussion with all parties involved. Looking forward for your input.
> I assumed GRASS-dev was the list to contact, but you sent it on
> GRASS-users, any special reason for this?
> All the best.
> -- 
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
> ___
> QGIS-Developer mailing list

> QGIS-Developer@.osgeo

> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

And on the dev side, some ideas and discussions are floating around:

e.g.

https://lists.osgeo.org/pipermail/grass-dev/2018-February/087388.html



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] GSoC idea: improve QGIS-GRASS GIS algs provider

2018-02-06 Thread Helmut Kudrnovsky 
As a follow-up of the long discussion how to proceed with alg providers in
QGIS, have a look at:

https://trac.osgeo.org/grass/wiki/GSoC/2018#ImproveGRASSintegrationinQGIS3

It should be seen as an starting point to collect ideas, and to sharpen the
technical interface and requirements for such an Integration of external alg
providers.

And it should be also understood as a starting contribution of the GRASS
community for a deeper proactively inter-project communication and
collaboration.

Feel free to to improve and extend the ideas proposal.





-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

2018-02-06 Thread Helmut Kudrnovsky 
Hi Paolo,


pcav wrote
> Il 05/02/2018 22:03, Helmut Kudrnovsky ha scritto:
>> and see here for a follow up in the GRASS community:
>> 
>> http://osgeo-org.1560.x6.nabble.com/Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352828.html
>> http://osgeo-org.1560.x6.nabble.com/Re-GRASS-user-Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352836.html
> 
> Thank you Helmut. Following our PSC meeting, I'll start an open
> discussion with all parties involved. Looking forward for your input.
> I assumed GRASS-dev was the list to contact, but you sent it on
> GRASS-users, any special reason for this?
> All the best.
> -- 
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
> ___
> QGIS-Developer mailing list

> QGIS-Developer@.osgeo

> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

I sent it to GRASS users as it seems to me to be more a community issue than
a dev issue.

Thinking about/hearing to your user base helps you to improve decisions on
the dev side.

see 

https://trac.osgeo.org/grass/wiki/GSoC/2018#ImproveGRASSintegrationinQGIS3

as a starting point to a possible closer OSGeo inter-project communication
and collaboration.

Being an OSGeo GSoC/GCI admin now for some time, such opportunities or
similar to improve inter-project collaboration seem to be really under-used
at the moment. 

I'll start a new thread about the GSoC idea to attract new interested
people.






-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

2018-02-05 Thread Helmut Kudrnovsky 
rashadkm wrote
> Hello all,
> 
> Here is a PR to allow integration of otb smoothly. tests are all passing,
> commits are squashed and ready to review.
> https://github.com/qgis/QGIS/pull/6272
> I did a small fix to control visibility of parameter from provider.
> Addition of specific parameter class for OTB is not included in this PR.
> 
> Thanks for feedback
> 
> On Mon, Feb 5, 2018 at 12:20 PM, Helmut Kudrnovsky 

> hellik@

>  wrote:
> 
>> >Otherwise if we don't care and just want to enable others to have QGIS
>> >intgration, they'll have to adopt the plugins.  That might work better
>> if
>> there
>> >is real interest.  But I think they usally prefer their tools to be used
>> in
>> >their own environment and don't care that much about whether it works in
>> QGIS
>> or not.  Is there solid interest of the SAGA or GRASS team to adopt
>> the
>  >providers?  Otherwise I guess they'll sooner or later will die.
>>
>> quickly screened the GRASS MLs, I can't find any entry that the GRASS
>> community was ever asked if there could be e.g. a shared attempt for an
>> automatization to create/maintain the plugin code.
>>
>> Looking at the new OSGeo website:
>>
>> *Desktop Applications*
>>
>> -QGIS Desktop
>> -GRASS GIS
>>
>> *Geospatial Libraries*
>>
>> -Orfeo ToolBox
>> -GDAL/OGR
>>
>> *Meta CRS Initiative*
>>
>> -PROJ4
>>
>> Most of the software mentioned in this thread are projects under the
>> common
>> umbrella of OSGeo.
>>
>> An option may be to ask that OSGeo plays a more proactive role in helping
>> to
>> coordinate and supporting (technically/financally/...) such inter-project
>> challenges.
>>
>> I will forward a short summary of this thread to the GRASS community.

and see here for a follow up in the GRASS community:

http://osgeo-org.1560.x6.nabble.com/Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352828.html
http://osgeo-org.1560.x6.nabble.com/Re-GRASS-user-Keeping-GRASS-OTB-algorithm-in-qgis-processing-td5352836.html




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Keeping OTB algorithm in qgis processing

2018-02-05 Thread Helmut Kudrnovsky 
>Otherwise if we don't care and just want to enable others to have QGIS
>intgration, they'll have to adopt the plugins.  That might work better if
there
>is real interest.  But I think they usally prefer their tools to be used in
>their own environment and don't care that much about whether it works in
QGIS
providers?  Otherwise I guess they'll sooner or later will die. 

quickly screened the GRASS MLs, I can't find any entry that the GRASS
community was ever asked if there could be e.g. a shared attempt for an
automatization to create/maintain the plugin code.

Looking at the new OSGeo website:

*Desktop Applications*

-QGIS Desktop
-GRASS GIS

*Geospatial Libraries*

-Orfeo ToolBox
-GDAL/OGR

*Meta CRS Initiative*

-PROJ4

Most of the software mentioned in this thread are projects under the common
umbrella of OSGeo.

An option may be to ask that OSGeo plays a more proactive role in helping to
coordinate and supporting (technically/financally/...) such inter-project
challenges.

I will forward a short summary of this thread to the GRASS community.



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] QGIS and GRASS 7.0.0

2015-02-23 Thread Helmut Kudrnovsky 
Paolo Cavallini wrote
 Il 23/02/2015 00:06, Pedro Venâncio ha scritto:
 
 QGIS GRASS plugin (qgis-plugin-grass) still depends on the 6.4.4, so it
 will no longer be available for those who upgrade to GRASS 7.0.0.
 
 GRASS 6.4 in Processing has 168 algorithms, GRASS 7 has 153, are a few
 less, but it will be easier to solve.
 
 So how can the issue of GRASS plugin be overcome with the GRASS 7?
 
 Ola Pedro,
 this will require a reasonable amount of work. I have raised the issue
 several times; sadly it seems nobody is willing to invest the necessary
 resources on this.
 BTW, would you mind giving us a list of the missing modules in
 Processing? AFAIK these should be only obsolete and useless ones, but if
 there is some genuinely missing we should be able to fix this rather
 easily.
 Thanks.
 
 -- 
 Paolo Cavallini - www.faunalia.eu
 QGIS  PostGIS courses: http://www.faunalia.eu/training.html
 *New course* QGIS for naturalists:
 http://www.faunalia.eu/en/nat_course.html
 ___
 Qgis-developer mailing list

 Qgis-developer@.osgeo

 http://lists.osgeo.org/mailman/listinfo/qgis-developer

the grass 7 command list in qgis processing should be uptodate.

see:

https://github.com/qgis/QGIS/commit/b7dcd67f3eb2e330742c2dd30f035ea6c31a9973




-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/QGIS-and-GRASS-7-0-0-tp5189299p5189554.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Re: GRASS regions

2012-05-03 Thread Helmut Kudrnovsky 
see http://lists.osgeo.org/pipermail/grass-dev/2012-May/058487.html

[GRASS-dev] Re: [Qgis-developer] GRASS regions [grass topology inside
PostGIS2.0]

again FYI from the qgis-dev-ml:

http://lists.osgeo.org/pipermail/qgis-developer/2012-May/019894.html

On Fri, Apr 27, 2012 at 02:36:41PM +0200, Patrick S. wrote:

 @strk: Do you know of projects/options to implement the grass topology
 inside PostGIS2.0?

Markus Neteler mentioned that Martin Landa was thinking about it, but I'm
not aware of any progress. I'd love to hear from them.

--strk; 

  ,--o-. 
  |   __/  |Delivering high quality PostGIS 2.0 !
  |  / 2.0 |http://strk.keybit.net - http://vizzuality.com
  `-o--'


-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.n6.nabble.com/GRASS-regions-tp4931222p4950277.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer