Re: [Qgis-developer] Processing GUI integration

[Paolo Cavallini]

Hi Nyall,

Il 30/03/2017 21:42, Nyall Dawson ha scritto:
>> get rid of the Processing menu altogether:
> 
> I'm a -1 on this. I like the idea of integrating processing more
> strongly in the ui, but I think there's a strong need for a processing
> menu.

agreed in principle; currently however the menu is pretty useless,
replicating things available elsewhere, and adding history that as
Victor said could be better integrated in the panel.
what more flesh could we add here?

> There just isn't anywhere else that this stuff belongs in
> naturally, unless we add an "analysis" menu, and then it's effectively
> just a menu rename...

in this case it would be more of a Task menu, according to the vision of
Victor as exposed in his enlightening talk in Girona last year.

> I'd like to see a toolbar icon added for opening/closing this panel.

ì1

> Agreed. I'm hoping to get a chance in the near future to port
> QtCreator's locator bar to QGIS. It's a really nice implementation,
> where 3rd party plugins can hook in search providers and everything
> happens in background threads. If we added something like this we
> could integrate some native search providers like a layer search (am I
> the only one who often struggles to find layers in the layer tree in a
> complex project??) and processing algorithm search.
> 
> Then plugins can take over and add address searching facilities using
> the various online facilities, native db searches, layer catalog
> searches, etc...

that would be great.

Thanks to all for comments.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
___
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] Concave polygins

[Paolo Cavallini]

Hi Nyall,

Il 30/03/2017 21:35, Nyall Dawson ha scritto:
> For reference, which ones did you try? I think this is something
> useful that we need to investigate getting into master, either via
> importing one of the existing plugins and adapting to processing or
> via a c++ implementation exposed via processing.

I have tried:
* PostGIS ST_ConcaveHull
* QGIS Concave Hull in Processing
* Concave hull (k-nearest-neighbors) from plugin Concave Hull (this
works differently, and has the useful option of creating multiple hulls
based on a field)
Thanks.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
___
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 2.18 on OSX

[Paolo Cavallini]

Il 30 marzo 2017 18:27:07 GMT+00:00, William Kyngesburye 
 ha scritto:
>I recently upgraded my system, it messed up my dev environment a bit
>and I need to straighten that out.
>
>> On Mar 30, 2017, at 3:45 AM, Etienne Trimaille
> wrote:
>> 
>> Hi Mats,
>> 
>> You can open the file with a text editor : 
>>
>/Applications/QGIS.app/Contents/Resources/python/plugins/processing/algs/saga/SagaUtils.py
>> 
>> on line 75, instead of: 
>> if not os.path.isdir(folder):
>> 
>> replace with: 
>> if folder and not os.path.isdir(folder):
>> 
>> In some other words, just add "folder and" between the "if" and
>"os.path"
>> 
>> William, do you think you will provide a release?
>> 
>> 
>> 
>> 2017-03-30 8:46 GMT+02:00 Mats Lindegarth
>:
>> Thanks Etienne!
>> I realize this forum is for developers and I am just a simple user. I
>do not
>> quite understand how to "apply this patch manually in the
>> file :
>>
>/Applications/QGIS.app/Contents/Resources/python/plugins/processing/algs/saga/SagaUtils.py".
>> Do I paste something in the Python console or in the Terminal or
>what.
>> Apologies for my ignorance and thanks for your efforts! If it is too
>> complicated I guess I'll have to wait for the next release. /Mats
>> 
>> 
>> 
>> --
>> View this message in context:
>http://osgeo-org.1560.x6.nabble.com/QGIS-2-18-on-OSX-tp5311966p5314899.html
>> Sent from the QGIS - Developer mailing list archive at Nabble.com.
>> ___
>> 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 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

Thanks William for the update, and for your work.
All the best.
-- 
Sent from mobile. Sorry for being short___
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] Processing GUI integration

[Nyall Dawson]

> get rid of the Processing menu altogether:

I'm a -1 on this. I like the idea of integrating processing more
strongly in the ui, but I think there's a strong need for a processing
menu. There just isn't anywhere else that this stuff belongs in
naturally, unless we add an "analysis" menu, and then it's effectively
just a menu rename...

On 30 March 2017 at 19:37, Victor Olaya  wrote:
> I think that if the only way to show the toolbox is going to be
> enabling it in the "Panel" menu, that is going to be very confusing...

I'd like to see a toolbar icon added for opening/closing this panel.

> The commander, we should get rid of it...

Agreed. I'm hoping to get a chance in the near future to port
QtCreator's locator bar to QGIS. It's a really nice implementation,
where 3rd party plugins can hook in search providers and everything
happens in background threads. If we added something like this we
could integrate some native search providers like a layer search (am I
the only one who often struggles to find layers in the layer tree in a
complex project??) and processing algorithm search.

Then plugins can take over and add address searching facilities using
the various online facilities, native db searches, layer catalog
searches, etc...

Nyall
___
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] Concave polygins

[Nyall Dawson]

On 31 March 2017 at 03:37, Paolo Cavallini  wrote:
> Hi all,
> I was looking for a convex polygon tool, and to my surprise I did not
> found one that behaves as I (and I presume many others) expect: to me
> the parameter to choose is the max length of the segment, whereas the
> existing tools seem to allow the choice of the proportion of convex
> polygon covered.
> Am I missing something, or is this a real limitation of our tools?
> All the best.

Hi Paolo,

For reference, which ones did you try? I think this is something
useful that we need to investigate getting into master, either via
importing one of the existing plugins and adapting to processing or
via a c++ implementation exposed via processing.

Nyall
___
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-psc] bug tracker cleanup

[Tim Sutton]

Hi

> On 28 Mar 2017, at 1:49 PM, Matthias Kuhn  wrote:
> 
> Hi all
> 
> 
> On 3/28/17 8:38 AM, Paolo Cavallini wrote:
>> Hi Giovanni,
>> 
>> Il 27/03/2017 12:02, Giovanni Manghi ha scritto:
>> 
>>> this thread didn't get the traction I was hooping for, is this a
>>> indication that is a general opinion that all the fixing effort should
>>> be focused on qgis3 and not also on the next LTR?
>> agreed, I'm also surprised (the list seems less reactive on several
>> subjects lately), and thanks for your perseverance in tracking this
>> important issue.
> 
> Would there be resources around to sponsor regular bugfixes instead of
> only the ones before normal releases?
> I think we should call on larger organizations to provide resources so
> this can be taken care of. After all it's for organizations that LTR exists.

Do you mean like a monthly effort to dedicate some funds for bug fixing? I'd 
certainly like to see us heading that way, and even better where QGIS.org hires 
full time bug fixers / developers to work only for the good of the general 
project and not to serve a specific client. Andreas can speak better to the 
ability to do anything right now - but I suspect we might need to wait till 
next year if we want to budget for more substantial (e.g. monthly) paid bug 
fixing rounds.

Regards

Tim


> 
>> 
 it makes sense to me. how many do you think are important to fix?
 how many affect 2.18 only, not 3?
>>> 
>>> during my cleanup a couple of weeks ago I clearly separated the
>>> regressions affecting only master/qgis3 and the ones only affecting
>>> 2.18.*. In the second case I tried to my best to also try clearly
>>> separate the ones we know since more or less long time and the ones
>>> that have appeared after 2.14.
>>> 
>>> The following list is a sample of important things (to me) that have
>>> regressed in 2.18 since 2.14:
>>> 
>>> 16242 QGIS 2.18.4 saves always with absolute paths
>>> 15961 Escaping out of Dialog causes QGIS to crash
>>> 15803 2.18: Move Selection to Top not working in attribute table
>>> 15976 Attribute table: rows are switching when adding attributes
>>> 16302 Quick calculation bar causes QGIS crash when updating fields with 
>>> aliases
>>> 16186 Broken Processing/GRASS tools under Windows > this is a
>>> packaging issue and not a Processing one
>>> 15868 Frequent errors in DB Manager: `pyqtSignal must be bound to a
>>> QObject, not 'PGVectorTable'`
>>> 16295 DB Manager: error importing data into GPKG connections
>>> 16296 Cannot use anymore d&d to import a layer from Spatialite in PostGIS
>>> 16297 (macOS) layers imported into a Spatialite Database with DB
>>> manager are not recognized as spatial tables
>>> 15741 PostGIS issue when using 'Merge selected features' tool
>>> (Geometry type does not match column type) > this is very bad as
>>> causes data loss
>>> 15974 Rows of the attribute table seem to be duplicated when saving
>>> edits in a shapefile
> Thanks for the list, Giovanni.
>>> * the platform version is very old (2010), can we try upgrade it? If
>>> someome provides me with a copy of the db I would give it a go on a
>>> testbench
>>> * remove all the projects others than "QGIS Application" from
>>> http://hub.qgis.org/projects 
>> it makes sense, but in spipte of our efforts, many plugins still rely on
>> this, and I do not think it's a good move just to shut them down
> 
> Do we have a plan for the signup process for redmine?
> I think the decision to stick to redmine was made under the assumption
> that one no longer needs to obtain a shared secret during this process.
>>> * close all tickets that were last updated/commented more than... 2/3/4 
>>> years?
>> not sure about this: if they still make sense, I'd prefer to keep them.
>> e.g. the second oldest is still valid, and helps us remembering about a
>> real issue:
>> http://hub.qgis.org/issues/167 
>> I understand keeping the list short is a major advantage, but removing
>> issues like this is not an advantage for the project IMHO.
> What about all that have been in "feedback" state for more than 1 year?
> That should filter out issues like 167.
> 
> Matthias
>> 
>> All the best.
> 
> 
> ___
> 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 
> 
—










Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

Kartoza is a merger between Linfiniti and Afrispatial

_

Re: [Qgis-developer] automatic sip files generation

[Matthias Kuhn]

Hi

On 3/30/17 8:31 PM, Tim Sutton wrote:
> Hi
>
>> On 30 Mar 2017, at 5:08 PM, Matthias Kuhn > > wrote:
>>
>> Hi Denis,
>>
>> Thanks a lot for finishing this.
>>
>> I am really excited and expect less troubles on the sip front in the
>> long-term.
>>
>> Tim, actually the generated python code now includes python DocStrings,
>> so it should be much easier to inspect an appropriate python
>> documentation directly with `help(QgsVectorLayer)` etc.
>>
>> And to automatically generate an up-to-date python documentation.
>
> This is really great! I guess the next step would be to see if we can
> use autodoc to generate python documentation on the python libs. If
> that works it will go a long way towards bump starting the Python API
> work that Wes and Francisco were going to work on under a small QGIS
> funded project. The project never got out the starting gates because
> we could not come up with an elegant build system.
Having more people improve on this system will be very welcome, there
are plenty of nice little bells and whistles to add!

>
> Might I suggest that we do our python documentation in a sphinx
> friendly way? So for example where you did:
>
> @versionadded 3.0
> in 
> https://github.com/qgis/QGIS/pull/4318/files#diff-356d7cb762f7b9dfa4526f102450a9aaR41
>
> it would become
>
> ..versionadded:: 3.0
>
> See http://www.sphinx-doc.org/en/stable/markup/para.html
>
> Since we are in green fields with python docstrings here it would be
> nice to have everything clean and neat and pythonic out the gate. Or
> are there some restrictions in the sippy annotations that require you
> to use a certain docstring style?
These doc strings are generated from the C++ doc strings. But since they
are a pretty simple syntax, it shouldn't be hard to improve sipify.pl to
also convert a set of doxygen tags to their pythonic equivalent. We
might want to unify the doxygen style as well within this process.

Cheers
Matthias
> Regards
>
> Tim
>
>>
>> Cheers
>> Matthias
>>
>> On 03/30/2017 05:02 PM, Denis Rouzaud wrote:
>>>
>>>
>>> Le jeu. 30 mars 2017 à 16:56, Tim Sutton >> 
>>> > a écrit :
>>>
>>>Hi
>>>
On 30 Mar 2017, at 3:18 PM, Denis Rouzaud
 mailto:denis.rouz...@gmail.com>
> wrote:

Dear all,

I'd like to raise the attention on a new workflow I just merged to
automatically generate SIP files using the header as source only.

A PR is pending for the documentation, but you can read it here

 https://github.com/3nids/QGIS-Documentation/blob/6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/codingstandards.rst#sip-bindings
(waiting to be merged).

For the moment, only 3 files are generated (qgsattributes,
qgsfeature and qgsvectorlayer). One can starts adding new files to
the process by adapting their header and removing them from
python/auto_sip.blacklist.
>>>
>>>This is really great! A couple of questions:
>>>
>>>1) the blacklist implies that any new .h files added to the source
>>>tree will automatically have sip bindings generated unless you
>>>explicitly blacklist them?
>>>
>>>
>>> As soon as you add the include in python/core/core.sip (or gui,
>>> analysis), the SIP is considered as automatically generated from header
>>> except if you blacklist it.
>>>
>>>
>>>2) are you thinking to maintain the sip files in Git still or remove
>>>the from revision in favour of having them as build time artifacts
>>>only? I ask this because I often direct people to use the sip files
>>>as a reference guide for the python API if they want to dig under
>>>the hood a bit more.
>>>
>>>
>>> The goal is to remove the SIP files and have them created on build time.
>>> But:
>>> 1) I except a few errors in the script to arise (so better to have an
>>> easy access to the SIP files)
>>> 2) it needs to reach a significant point of ported headers.
>>>
>>> So, in a somehow close or far future, yes they'll be removed from source
>>> (hence no blacklist anymore only manual files such as
>>> core/conversions.sip).
>>>
>>>
>>> ___
>>> 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 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
>
> —
>
>
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Project chair:* QGIS.org 
>
> Visit http://kartoza.com 

[Qgis-developer] Uncertainty Visualization GSOC

[Sven Christ]

My name is Sven from South Africa. I finished my masters' degree last year
and developed a QGIS plugin for uncertainty visualization and accuracy
assessment of continuous raster datasets such as DEMs. It is function but
has some bugs still and there are also some functions I would like to add
to it. I am currently busy with my PhD proposal and am wondering if this
would be a good project to propose to the summer of code.
___
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] automatic sip files generation

[Tim Sutton]

Hi

> On 30 Mar 2017, at 5:08 PM, Matthias Kuhn  wrote:
> 
> Hi Denis,
> 
> Thanks a lot for finishing this.
> 
> I am really excited and expect less troubles on the sip front in the
> long-term.
> 
> Tim, actually the generated python code now includes python DocStrings,
> so it should be much easier to inspect an appropriate python
> documentation directly with `help(QgsVectorLayer)` etc.
> 
> And to automatically generate an up-to-date python documentation.

This is really great! I guess the next step would be to see if we can use 
autodoc to generate python documentation on the python libs. If that works it 
will go a long way towards bump starting the Python API work that Wes and 
Francisco were going to work on under a small QGIS funded project. The project 
never got out the starting gates because we could not come up with an elegant 
build system.

Might I suggest that we do our python documentation in a sphinx friendly way? 
So for example where you did:

@versionadded 3.0 in 
https://github.com/qgis/QGIS/pull/4318/files#diff-356d7cb762f7b9dfa4526f102450a9aaR41

it would become

..versionadded:: 3.0

See http://www.sphinx-doc.org/en/stable/markup/para.html

Since we are in green fields with python docstrings here it would be nice to 
have everything clean and neat and pythonic out the gate. Or are there some 
restrictions in the sippy annotations that require you to use a certain 
docstring style?

Regards

Tim

> 
> Cheers
> Matthias
> 
> On 03/30/2017 05:02 PM, Denis Rouzaud wrote:
>> 
>> 
>> Le jeu. 30 mars 2017 à 16:56, Tim Sutton > 
>> >> a écrit :
>> 
>>Hi
>> 
>>>On 30 Mar 2017, at 3:18 PM, Denis Rouzaud >> 
>>>>> wrote:
>>> 
>>>Dear all,
>>> 
>>>I'd like to raise the attention on a new workflow I just merged to
>>>automatically generate SIP files using the header as source only.
>>> 
>>>A PR is pending for the documentation, but you can read it here
>>>
>>> https://github.com/3nids/QGIS-Documentation/blob/6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/codingstandards.rst#sip-bindings
>>>(waiting to be merged).
>>> 
>>>For the moment, only 3 files are generated (qgsattributes,
>>>qgsfeature and qgsvectorlayer). One can starts adding new files to
>>>the process by adapting their header and removing them from
>>>python/auto_sip.blacklist.
>> 
>>This is really great! A couple of questions:
>> 
>>1) the blacklist implies that any new .h files added to the source
>>tree will automatically have sip bindings generated unless you
>>explicitly blacklist them?
>> 
>> 
>> As soon as you add the include in python/core/core.sip (or gui,
>> analysis), the SIP is considered as automatically generated from header
>> except if you blacklist it.
>> 
>> 
>>2) are you thinking to maintain the sip files in Git still or remove
>>the from revision in favour of having them as build time artifacts
>>only? I ask this because I often direct people to use the sip files
>>as a reference guide for the python API if they want to dig under
>>the hood a bit more.
>> 
>> 
>> The goal is to remove the SIP files and have them created on build time.
>> But:
>> 1) I except a few errors in the script to arise (so better to have an
>> easy access to the SIP files)
>> 2) it needs to reach a significant point of ported headers.
>> 
>> So, in a somehow close or far future, yes they'll be removed from source
>> (hence no blacklist anymore only manual files such as core/conversions.sip).
>> 
>> 
>> ___
>> 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 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 
> 
—










Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

Kartoza is a merger between Linfiniti and Afrispatial

___
Qgis-developer mailing list
Qgis-developer@li

Re: [Qgis-developer] QGIS 2.18 on OSX

[William Kyngesburye]

I recently upgraded my system, it messed up my dev environment a bit and I need 
to straighten that out.

> On Mar 30, 2017, at 3:45 AM, Etienne Trimaille  
> wrote:
> 
> Hi Mats,
> 
> You can open the file with a text editor : 
> /Applications/QGIS.app/Contents/Resources/python/plugins/processing/algs/saga/SagaUtils.py
> 
> on line 75, instead of: 
> if not os.path.isdir(folder):
> 
> replace with: 
> if folder and not os.path.isdir(folder):
> 
> In some other words, just add "folder and" between the "if" and "os.path"
> 
> William, do you think you will provide a release?
> 
> 
> 
> 2017-03-30 8:46 GMT+02:00 Mats Lindegarth :
> Thanks Etienne!
> I realize this forum is for developers and I am just a simple user. I do not
> quite understand how to "apply this patch manually in the
> file :
> /Applications/QGIS.app/Contents/Resources/python/plugins/processing/algs/saga/SagaUtils.py".
> Do I paste something in the Python console or in the Terminal or what.
> Apologies for my ignorance and thanks for your efforts! If it is too
> complicated I guess I'll have to wait for the next release. /Mats
> 
> 
> 
> --
> View this message in context: 
> http://osgeo-org.1560.x6.nabble.com/QGIS-2-18-on-OSX-tp5311966p5314899.html
> Sent from the QGIS - Developer mailing list archive at Nabble.com.
> ___
> 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 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] Concave polygins

[Paolo Cavallini]

Hi all,
I was looking for a convex polygon tool, and to my surprise I did not
found one that behaves as I (and I presume many others) expect: to me
the parameter to choose is the max length of the segment, whereas the
existing tools seem to allow the choice of the proportion of convex
polygon covered.
Am I missing something, or is this a real limitation of our tools?
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&geo=IT&q=qgis,arcgis
___
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] Processing UI looks strange

[matteo]

HI devs,

I just compiled QGIS and I still have these problems with Processing.

Besides Tim and Frank, nobody else have strange and not usable
Processing UIs?

Thanks!

Best

Matteo
___
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] automatic sip files generation

[Alessandro Pasotti]

On Thu, Mar 30, 2017 at 5:26 PM, Alessandro Pasotti 
wrote:

> On Thu, Mar 30, 2017 at 5:02 PM, Denis Rouzaud 
> wrote:
>
>>
>>
>> Le jeu. 30 mars 2017 à 16:56, Tim Sutton  a écrit :
>>
>>> Hi
>>>
>>> On 30 Mar 2017, at 3:18 PM, Denis Rouzaud 
>>> wrote:
>>>
>>> Dear all,
>>>
>>> I'd like to raise the attention on a new workflow I just merged to
>>> automatically generate SIP files using the header as source only.
>>>
>>> A PR is pending for the documentation, but you can read it here
>>> https://github.com/3nids/QGIS-Documentation/blob/6e3a9fb6f98
>>> a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/c
>>> odingstandards.rst#sip-bindings
>>> (waiting to be merged).
>>>
>>> For the moment, only 3 files are generated (qgsattributes, qgsfeature
>>> and qgsvectorlayer). One can starts adding new files to the process by
>>> adapting their header and removing them from python/auto_sip.blacklist.
>>>
>>>
>>> This is really great! A couple of questions:
>>>
>>> 1) the blacklist implies that any new .h files added to the source tree
>>> will automatically have sip bindings generated unless you explicitly
>>> blacklist them?
>>>
>>
>> As soon as you add the include in python/core/core.sip (or gui,
>> analysis), the SIP is considered as automatically generated from header
>> except if you blacklist it.
>>
>>
>>> 2) are you thinking to maintain the sip files in Git still or remove the
>>> from revision in favour of having them as build time artifacts only? I ask
>>> this because I often direct people to use the sip files as a reference
>>> guide for the python API if they want to dig under the hood a bit more.
>>>
>>
>> The goal is to remove the SIP files and have them created on build time.
>>
>>
> I surely missed something: how can you deal with annotations?
>
>
>
Oh, now I see the docs:

https://patch-diff.githubusercontent.com/raw/qgis/QGIS-Documentation/pull/1788.diff

Smart solution indeed!

Thanks!

-- 
Alessandro Pasotti
w3:   www.itopen.it
___
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] automatic sip files generation

[Alessandro Pasotti]

On Thu, Mar 30, 2017 at 5:02 PM, Denis Rouzaud 
wrote:

>
>
> Le jeu. 30 mars 2017 à 16:56, Tim Sutton  a écrit :
>
>> Hi
>>
>> On 30 Mar 2017, at 3:18 PM, Denis Rouzaud 
>> wrote:
>>
>> Dear all,
>>
>> I'd like to raise the attention on a new workflow I just merged to
>> automatically generate SIP files using the header as source only.
>>
>> A PR is pending for the documentation, but you can read it here
>> https://github.com/3nids/QGIS-Documentation/blob/
>> 6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/
>> codingstandards.rst#sip-bindings
>> (waiting to be merged).
>>
>> For the moment, only 3 files are generated (qgsattributes, qgsfeature and
>> qgsvectorlayer). One can starts adding new files to the process by adapting
>> their header and removing them from python/auto_sip.blacklist.
>>
>>
>> This is really great! A couple of questions:
>>
>> 1) the blacklist implies that any new .h files added to the source tree
>> will automatically have sip bindings generated unless you explicitly
>> blacklist them?
>>
>
> As soon as you add the include in python/core/core.sip (or gui, analysis),
> the SIP is considered as automatically generated from header except if you
> blacklist it.
>
>
>> 2) are you thinking to maintain the sip files in Git still or remove the
>> from revision in favour of having them as build time artifacts only? I ask
>> this because I often direct people to use the sip files as a reference
>> guide for the python API if they want to dig under the hood a bit more.
>>
>
> The goal is to remove the SIP files and have them created on build time.
>
>
I surely missed something: how can you deal with annotations?


-- 
Alessandro Pasotti
w3:   www.itopen.it
___
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] automatic sip files generation

[Matthias Kuhn]

Hi Denis,

Thanks a lot for finishing this.

I am really excited and expect less troubles on the sip front in the
long-term.

Tim, actually the generated python code now includes python DocStrings,
so it should be much easier to inspect an appropriate python
documentation directly with `help(QgsVectorLayer)` etc.

And to automatically generate an up-to-date python documentation.

Cheers
Matthias

On 03/30/2017 05:02 PM, Denis Rouzaud wrote:
> 
> 
> Le jeu. 30 mars 2017 à 16:56, Tim Sutton  > a écrit :
> 
> Hi
> 
>> On 30 Mar 2017, at 3:18 PM, Denis Rouzaud > > wrote:
>>
>> Dear all,
>>
>> I'd like to raise the attention on a new workflow I just merged to
>> automatically generate SIP files using the header as source only.
>>
>> A PR is pending for the documentation, but you can read it here
>> 
>> https://github.com/3nids/QGIS-Documentation/blob/6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/codingstandards.rst#sip-bindings
>> (waiting to be merged).
>>
>> For the moment, only 3 files are generated (qgsattributes,
>> qgsfeature and qgsvectorlayer). One can starts adding new files to
>> the process by adapting their header and removing them from
>> python/auto_sip.blacklist.
> 
> This is really great! A couple of questions:
> 
> 1) the blacklist implies that any new .h files added to the source
> tree will automatically have sip bindings generated unless you
> explicitly blacklist them?
> 
> 
> As soon as you add the include in python/core/core.sip (or gui,
> analysis), the SIP is considered as automatically generated from header
> except if you blacklist it.
>  
> 
> 2) are you thinking to maintain the sip files in Git still or remove
> the from revision in favour of having them as build time artifacts
> only? I ask this because I often direct people to use the sip files
> as a reference guide for the python API if they want to dig under
> the hood a bit more.
> 
> 
> The goal is to remove the SIP files and have them created on build time.
> But:
> 1) I except a few errors in the script to arise (so better to have an
> easy access to the SIP files)
> 2) it needs to reach a significant point of ported headers.
>  
> So, in a somehow close or far future, yes they'll be removed from source
> (hence no blacklist anymore only manual files such as core/conversions.sip).
> 
> 
> ___
> 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 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] automatic sip files generation

[Tim Sutton]

Hi


> On 30 Mar 2017, at 5:02 PM, Denis Rouzaud  wrote:
> 
> 
> 
> Le jeu. 30 mars 2017 à 16:56, Tim Sutton  > a écrit :
> Hi
> 
>> On 30 Mar 2017, at 3:18 PM, Denis Rouzaud > > wrote:
>> 
>> Dear all,
>> 
>> I'd like to raise the attention on a new workflow I just merged to 
>> automatically generate SIP files using the header as source only.
>> 
>> A PR is pending for the documentation, but you can read it here
>> https://github.com/3nids/QGIS-Documentation/blob/6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/codingstandards.rst#sip-bindings
>>  
>> 
>> (waiting to be merged).
>> 
>> For the moment, only 3 files are generated (qgsattributes, qgsfeature and 
>> qgsvectorlayer). One can starts adding new files to the process by adapting 
>> their header and removing them from python/auto_sip.blacklist.
> 
> This is really great! A couple of questions:
> 
> 1) the blacklist implies that any new .h files added to the source tree will 
> automatically have sip bindings generated unless you explicitly blacklist 
> them?
> 
> As soon as you add the include in python/core/core.sip (or gui, analysis), 
> the SIP is considered as automatically generated from header except if you 
> blacklist it.
>  
> 2) are you thinking to maintain the sip files in Git still or remove the from 
> revision in favour of having them as build time artifacts only? I ask this 
> because I often direct people to use the sip files as a reference guide for 
> the python API if they want to dig under the hood a bit more.
> 
> The goal is to remove the SIP files and have them created on build time.
> But:
> 1) I except a few errors in the script to arise (so better to have an easy 
> access to the SIP files)
> 2) it needs to reach a significant point of ported headers.
>  
> So, in a somehow close or far future, yes they'll be removed from source 
> (hence no blacklist anymore only manual files such as core/conversions.sip).


Ok thanks for the clarifications!

Regards

Tim


> 

—










Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

Kartoza is a merger between Linfiniti and Afrispatial

___
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] automatic sip files generation

[Denis Rouzaud]

Le jeu. 30 mars 2017 à 16:56, Tim Sutton  a écrit :

> Hi
>
> On 30 Mar 2017, at 3:18 PM, Denis Rouzaud  wrote:
>
> Dear all,
>
> I'd like to raise the attention on a new workflow I just merged to
> automatically generate SIP files using the header as source only.
>
> A PR is pending for the documentation, but you can read it here
>
> https://github.com/3nids/QGIS-Documentation/blob/6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/codingstandards.rst#sip-bindings
> (waiting to be merged).
>
> For the moment, only 3 files are generated (qgsattributes, qgsfeature and
> qgsvectorlayer). One can starts adding new files to the process by adapting
> their header and removing them from python/auto_sip.blacklist.
>
>
> This is really great! A couple of questions:
>
> 1) the blacklist implies that any new .h files added to the source tree
> will automatically have sip bindings generated unless you explicitly
> blacklist them?
>

As soon as you add the include in python/core/core.sip (or gui, analysis),
the SIP is considered as automatically generated from header except if you
blacklist it.


> 2) are you thinking to maintain the sip files in Git still or remove the
> from revision in favour of having them as build time artifacts only? I ask
> this because I often direct people to use the sip files as a reference
> guide for the python API if they want to dig under the hood a bit more.
>

The goal is to remove the SIP files and have them created on build time.
But:
1) I except a few errors in the script to arise (so better to have an easy
access to the SIP files)
2) it needs to reach a significant point of ported headers.

So, in a somehow close or far future, yes they'll be removed from source
(hence no blacklist anymore only manual files such as core/conversions.sip).
___
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] automatic sip files generation

[Tim Sutton]

Hi

> On 30 Mar 2017, at 3:18 PM, Denis Rouzaud  wrote:
> 
> Dear all,
> 
> I'd like to raise the attention on a new workflow I just merged to 
> automatically generate SIP files using the header as source only.
> 
> A PR is pending for the documentation, but you can read it here
> https://github.com/3nids/QGIS-Documentation/blob/6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/codingstandards.rst#sip-bindings
>  
> 
> (waiting to be merged).
> 
> For the moment, only 3 files are generated (qgsattributes, qgsfeature and 
> qgsvectorlayer). One can starts adding new files to the process by adapting 
> their header and removing them from python/auto_sip.blacklist.

This is really great! A couple of questions:

1) the blacklist implies that any new .h files added to the source tree will 
automatically have sip bindings generated unless you explicitly blacklist them?
2) are you thinking to maintain the sip files in Git still or remove the from 
revision in favour of having them as build time artifacts only? I ask this 
because I often direct people to use the sip files as a reference guide for the 
python API if they want to dig under the hood a bit more.

Regards

Tim

> 
> Best wishes,
> 
> Denis
> 
> ___
> 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

—










Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

Kartoza is a merger between Linfiniti and Afrispatial

___
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] Plugin [65] Mask approval notification.

[noreply]

Plugin Mask approval by pcav.
The plugin version "[65] Mask 1.7" is now approved
Link: http://plugins.qgis.org/plugins/mask/
___
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] using gdal_arrays in QGIS 2.99

[Idan Miara]

Hello,

I am trying to read a raster using gdal's ReadAsArray() method in python
3.6. I am using the gdal library provided in Qgis' 2.99 weekly release
(QGIS-OSGeo4W-2.99.0-9-Setup-x86_64.exe).

this sample script:

import gdal
x = gdal.Open(r'D:/Map Samples/1/DTM/n29w098d5dtm.tif')  #valid tif
y = x.ReadAsArray()
print(y)


produces this error:

Traceback (most recent call last):
  File
"C:\PROGRA~1\QGIS2~1.99\apps\Python36\lib\site-packages\osgeo\gdal_array.py",
line 16, in swig_import_helper
fp, pathname, description = imp.find_module('_gdal_array',
[dirname(__file__)])
  File "C:\PROGRA~1\QGIS2~1.99\apps\Python36\lib\imp.py", line 296, in
find_module
raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_gdal_array'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\PROGRA~1\QGIS2~1.99\apps\Python36\lib\code.py", line 91, in
runcode
exec(code, self.locals)
  File "", line 1, in 
  File "", line 3, in 
  File
"C:\PROGRA~1\QGIS2~1.99\apps\Python36\lib\site-packages\osgeo\gdal.py",
line 1817, in ReadAsArray
from . import gdalnumeric
  File "C:/PROGRA~1/QGIS2~1.99/apps/qgis-dev/./python\qgis\utils.py", line
647, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File
"C:\PROGRA~1\QGIS2~1.99\apps\Python36\lib\site-packages\osgeo\gdalnumeric.py",
line 1, in 
from osgeo.gdal_array import *
  File "C:/PROGRA~1/QGIS2~1.99/apps/qgis-dev/./python\qgis\utils.py", line
647, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
  File
"C:\PROGRA~1\QGIS2~1.99\apps\Python36\lib\site-packages\osgeo\gdal_array.py",
line 26, in 
_gdal_array = swig_import_helper()
  File
"C:\PROGRA~1\QGIS2~1.99\apps\Python36\lib\site-packages\osgeo\gdal_array.py",
line 18, in swig_import_helper
import _gdal_array
  File "C:/PROGRA~1/QGIS2~1.99/apps/qgis-dev/./python\qgis\utils.py", line
647, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
ModuleNotFoundError: No module named '_gdal_array'


What can i do to use gdal's readAsArray method in my code?
Thank you.
___
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] Plugin [740] qgis2web approval notification.

[noreply]

Plugin qgis2web approval by pcav.
The plugin version "[740] qgis2web 2.0.0" is now approved
Link: http://plugins.qgis.org/plugins/qgis2web/
___
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] Plugin [749] Thin greyscale image to skeleton approval notification.

[noreply]

Plugin Thin greyscale image to skeleton approval by pcav.
The plugin version "[749] Thin greyscale image to skeleton 0.3" is now approved
Link: http://plugins.qgis.org/plugins/ThinGreyscale/
___
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] Plugin [730] Line direction histogram approval notification.

[noreply]

Plugin Line direction histogram approval by pcav.
The plugin version "[730] Line direction histogram 1.5" is now approved
Link: http://plugins.qgis.org/plugins/LineDirectionHistogram/
___
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] Plugin [740] qgis2web approval notification.

[noreply]

Plugin qgis2web approval by pcav.
The plugin version "[740] qgis2web 2.14.0" is now approved
Link: http://plugins.qgis.org/plugins/qgis2web/
___
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] automatic sip files generation

[Denis Rouzaud]

Dear all,

I'd like to raise the attention on a new workflow I just merged to
automatically generate SIP files using the header as source only.

A PR is pending for the documentation, but you can read it here
https://github.com/3nids/QGIS-Documentation/blob/6e3a9fb6f98a2869aef27c01b7ab70eb0a4c7556/source/docs/developers_guide/codingstandards.rst#sip-bindings
(waiting to be merged).

For the moment, only 3 files are generated (qgsattributes, qgsfeature and
qgsvectorlayer). One can starts adding new files to the process by adapting
their header and removing them from python/auto_sip.blacklist.

Best wishes,

Denis
___
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 in Ubuntu 16.04

[Bernd Vogelgesang]

yep,
thanx for the fast fix!

Cheers
Bernd

Am 30.03.2017, 09:28 Uhr, schrieb roy roy :


It's already fixed, i'm sticking with Ubuntu then.

Thanks to maintainers for the great work!!



QGIS and GRASS GIS installed on Ubuntu, the

QGIS packages with "ubuntugis" dependencies are now broken:

http://hub.qgis.org/issues/16386

"Yesterday, UbuntuGIS got a GDAL 2.1.3 update, so QGIS need to be  
rebuilt

against that version."

Is it possible for QGIS to be rebuilt with the updated libraries?

I know QGIS is rebuild every month but will it be now?

You guys want to force me to use windows, you have to admit that! :-)

given that I (of course) appreciate the effort of maintainers,

thanks, Roy.
___
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 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



--
Bernd Vogelgesang
Siedlerstraße 2
91083 Baiersdorf/Igelsdorf
Tel: 09133-825374
___
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] Fwd: Re: QGIS 3D processing

[Andreas Plesch]

Let me share a side conversation here, with permission.


-- Forwarded message --
From: "Andreas Plesch" 
Date: Mar 29, 2017 2:40 PM
Subject: Re: QGIS 3D processing
To: "Hillers Heather" 

Hello Heather,

thank you for your interest and offer to participate in the development of
3d capabilities in QGis. You may have looked up my proof of concept github
project https://github.com/andreasplesch/QGIS-X3D-Processing which will
give you a good sense of where my interest is. Please feel free to submit
issues (or PRs!) there.

I encourage you to give the processing scripts and models a try, and then
perhaps fork the project and see if you can modify some of the python
scripts or just create a new processing model. For example it would be
straightforward to add automatic reprojection of the DEM to WGS84
geographic coordinates in a model. That could be good first mini-project.

I plan on slow, deliberate development emphasizing robustness and doing one
thing well before adding features. Any help is of course very welcome.
Would you be able to contribute under an open source license ?

The processing framework allows for very modular development which may be
helpful for adding or customizing functionality.

I took the liberty to extract your list of requirements here and offer some
responses:

1) Load 3d shapefiles  or database stored shapes (we use Oracle)  and DEMs
and have a very easy to use and navigate 3d viewer

Here the idea would be to use qgis as an abstraction layer and just use the
qgis vector and raster layer API. I did this for DEMs. How large in terms
of data size are the DEMs you need to view and navigate ? For large scenes
it will be necessary to use a LOD or tile based concept which is also
possible.
What kind of 3d vector data do you have ? The QGIS2Threejs plugin has some
good ideas for representing points and polylines. TINs have a direct
equivalent in X3D and would be also very doable.
Currently, the idea is to use a web browser as viewer and interface which
has a lot of advantages. With QT5 and Qgis3 it may be possible to couple a
html/js webkit viewer more tightly with Qgis3.

2) Get x, y, z from clicked points and nearest neighbor vertices to the
clicked points.

x3dom has built in picking. Nearest neighbor (snapping) should also be
possible but probably outside of QGis using js on the web client.

3) Allow editing of z coordinate of vertices in a 3d shapefile or other
vector

Editing is another category altogether which I am not targeting at this
point. The way I can see editing Z values is by using the 2d map Qgis
interface and attribute editing capabilities and have an automatically
updating 3d display of the adjustments. Editing directly in 3d will require
a lot more development. The GEarthview plugin allows for digitizing in
Google Earth.

4) Get 3d distance along a line or polygon boundary between 2 vertices.

Following and measuring a line in 3d should be pretty easy outside of the
3d display just as a regular plugin. There may well be existing
functionality.

5) Pin coordinates, feature ids, vertex ids of selected feature vertices in
order to query distances between them or for editing.

Not sure but does this collapse to labelling individual vertices so they
are easy to find/identify with other tools?

Hope this helps,

Andreas

On Wed, Mar 29, 2017 at 3:10 AM, Hillers Heather <
heather.hill...@erftverband.de> wrote:

>
>
>
>
> Hello,
>
>
>
> My users are increasingly interested in visualizing and querying 3D
> Shapefiles and DEMs in QGIS.  We want to apply this to groundwater
> modelling and monitoring as well as profiling river beds.  I would be
> interested in working on this project and I am certain I can get permission
> to allocate some of my work time to it.  At the moment I do a lot of pyqgis
> development.  I haven’t done any QGIS C++ development, although I am
> familiar with the qgis source code and I have done C++ programming in the
> distant past.  I am working on a 3D sidecar plugin this week, so I’ve got
> the qgis 3d api stuck up my nose at the moment anyway.
>
>
>
> Grüße,
>
>
>
> Heather
>
>
>
> Heather Hillers
> Bereich: Personal und Verwaltung
> Abteilung: Informationstechnologie
> Erftverband, *Am Erftverband 6*, D 50126 Bergheim
> Fon: +49 2271 88 1548 <+49%202271%20881548> , Fax: +49 2271 88 1210
> <+49%202271%20881210>
>
> Für die Programmierung von Navigationsgeräten empfehlen wir noch für
> einige Zeit die Eingabe Paffendorfer Weg 42 zu verwenden.
>
> Erftverband: Wasserwirtschaft für unsere Region - mit zertifiziertem
> Qualitäts-, Umwelt- und technischem Sicherheitsmanagement.
>
>
> [image: http://intranet/disclaimer/disclaimer.jpg]
>



-- 
Andreas Plesch
39 Barbara Rd.
Waltham, MA 02453
___
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] Georeferencer icons in QGIS 3

[Paolo Cavallini]

Hi all,
I noticed in qgis 3 the icons from georeferencer are much bigger than
the ones in the main menus: do they have to be replaced with new ones?
Another very minor issue, I'm afraid ;)
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&geo=IT&q=qgis,arcgis
___
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 2.18 on OSX

[Mats Lindegarth]

Thanks Etienne!
I believe that this fixed my problem!/Mats



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/QGIS-2-18-on-OSX-tp5311966p5314934.html
Sent from the QGIS - Developer mailing list archive at Nabble.com.
___
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] Processing GUI integration

[Victor Olaya]

I think that if the only way to show the toolbox is going to be
enabling it in the "Panel" menu, that is going to be very confusing...

The history can be integrated with the QGIS log maybe

The commander, we should get rid of it...

2017-03-30 9:05 GMT+02:00 Paolo Cavallini :
> Hi all,
> now that Processing has appropriately moved its options to the Options
> menu, I wonder if it wouldn't it be better to move also other entries,
> and get rid of the Processing menu altogether:
> * the Processing panel can be (de)activated from the Panels menu
> * Results as well
> * the graphical modeller can be started from inside the Processing panel
>
> Menus to be moved are therefore:
> * History
> * Command line (unsure about this one, it could be a panel as well).
> This would clean up the interface, and make Processing more integrated;
> opinions?
>
> Thanks.
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
> ___
> 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 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 2.18 on OSX

[Etienne Trimaille]

Hi Mats,

You can open the file with a text editor :
/Applications/QGIS.app/Contents/Resources/python/
plugins/processing/algs/saga/SagaUtils.py

on line 75, instead of:
if not os.path.isdir(folder):

replace with:
if folder and not os.path.isdir(folder):

In some other words, just add "folder and" between the "if" and "os.path"

William, do you think you will provide a release?



2017-03-30 8:46 GMT+02:00 Mats Lindegarth :

> Thanks Etienne!
> I realize this forum is for developers and I am just a simple user. I do
> not
> quite understand how to "apply this patch manually in the
> file :
> /Applications/QGIS.app/Contents/Resources/python/
> plugins/processing/algs/saga/SagaUtils.py".
> Do I paste something in the Python console or in the Terminal or what.
> Apologies for my ignorance and thanks for your efforts! If it is too
> complicated I guess I'll have to wait for the next release. /Mats
>
>
>
> --
> View this message in context: http://osgeo-org.1560.x6.
> nabble.com/QGIS-2-18-on-OSX-tp5311966p5314899.html
> Sent from the QGIS - Developer mailing list archive at Nabble.com.
> ___
> 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 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] Processing menu dropdowns

[Neumann, Andreas]

Hi Paolo, 

While I agree with you that in most cases the same layer wouldn't be
chosen twice as input layers, I am not sure if your proposal is worth
the effort. 

In >90% of the cases the user will have to change the input layer anyway
- so what is the gain? 

Better to let the user consciously choose the correct parameters than
doing any wild guesses of what may be, by chance, the right choice in
some cases. 

I think we have other, more pressing issues to fix besides this minor
issue. 

Andreas 

On 2017-03-30 09:36, Paolo Cavallini wrote:

> Hi all,
> in Processing, the interface prefills the dropdowns for the choice of
> input layers with the active layer. When >1 layer has to be chosen (e.g.
> for Difference) the same layer is selected twice. Of course Processing
> cannot know which other layer to select, but it's almost certain that
> nobody wants the same layer twice. I'd suggest therefore to put as a
> default the topmost layer, excluding the active one.
> Thanks.

  ___
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] Processing menu dropdowns

[Paolo Cavallini]

Hi all,
in Processing, the interface prefills the dropdowns for the choice of
input layers with the active layer. When >1 layer has to be chosen (e.g.
for Difference) the same layer is selected twice. Of course Processing
cannot know which other layer to select, but it's almost certain that
nobody wants the same layer twice. I'd suggest therefore to put as a
default the topmost layer, excluding the active one.
Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
___
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 in Ubuntu 16.04

[roy roy]

It's already fixed, i'm sticking with Ubuntu then.

Thanks to maintainers for the great work!!


> QGIS and GRASS GIS installed on Ubuntu, the
>
> QGIS packages with "ubuntugis" dependencies are now broken:
>
> http://hub.qgis.org/issues/16386
>
> "Yesterday, UbuntuGIS got a GDAL 2.1.3 update, so QGIS need to be rebuilt
> against that version."
>
> Is it possible for QGIS to be rebuilt with the updated libraries?
>
> I know QGIS is rebuild every month but will it be now?
>
> You guys want to force me to use windows, you have to admit that! :-)
>
> given that I (of course) appreciate the effort of maintainers,
>
> thanks, Roy.
> ___
> 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 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] Processing GUI integration

[Paolo Cavallini]

Hi all,
now that Processing has appropriately moved its options to the Options
menu, I wonder if it wouldn't it be better to move also other entries,
and get rid of the Processing menu altogether:
* the Processing panel can be (de)activated from the Panels menu
* Results as well
* the graphical modeller can be started from inside the Processing panel

Menus to be moved are therefore:
* History
* Command line (unsure about this one, it could be a panel as well).
This would clean up the interface, and make Processing more integrated;
opinions?

Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
___
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