Re: [QGIS-Developer] Run processing model on selected features only

[Matthias Kuhn]

Hi Nyall


On 12/13/17 11:20 PM, Nyall Dawson wrote:
> On 12 December 2017 at 00:10, Andreas Neumann  wrote:
>> Thanks for the information. Unfortunately I cannot use "Feature Source" as
>> an input in my model.
>>
>> Matthias told me that I have to use "Vector layer" as an input, because my
>> model relies on certain features that aren't available on "feature source"
>> inputs. I need to use refactor fields in a model with expressions support
>> for relation_aggregates and represent_value (which requires information on
>> widget configuration).
>>
> Hi Andreas,
>
> Thanks for your feedback while testing the new processing modeler...
> it's very valuable information!
>
>> I also find it quite confusing that the inputs come with zero documentation.
>> I think for probably 99% of the users who are not devs it isn't obvious when
>> to use which input. Could we introduce a very simple tooltip that explains
>> with 1 or 2 sentences what the input implies - esp. for the "Vector layer"
>> vs. "Feature Source" vs. "Layer field" ?
> I need to improve how this is exposed in the modeler, but the
> difference between "Feature sources" and "vector layers" is that
> feature sources are used wherever *features* from a layer are being
> processed, vs "vector layer" parameters which are for processes which
> alter the whole layer (e.g changing its style, adding a field in
> place, deleting/renaming it, etc)
>
> Accordingly, all algorithms which edit features should be made to work
> fully with "feature sources". In this case, we need to fix the
> refactor fields algorithm to handle the relation/represent value use
> cases somehow. But the proper solution here isn't to require a vector
> layer parameter.

When relations are involved, there needs to be a vector layer around to
work with these as far as I can see.
If this vector layer is promoted from a feature source parameter or
provided as vector layer input is a different question (I can live with
both).

For a really nice UX, the expressions in the algorithms would be
analyzed for if they require only attributes/geometries or other layer
specific information and complain if they get an input that's
incompatible with their expectations. But that's quite a bit of work for
probably not so many use cases so I wouldn't put that on high priority.

>
> (Note that ALL algorithms which use feature source parameters will
> happily accept a vector layer parameter and operate on the all the
> features in that layer... but that's just done to make the modeler as
> flexible as possible).
>
> I plan on renaming "Feature Source" -> "Vector layer features" in the
> modeler to help clarify this (also "layer field" -> "vector layer
> field"), and I'll add some tooltips too. (also sort that list)

That sounds good to me, +1

Matthias

>
>> Is there any chance this checkbox could also be introduced for "Vector
>> layer" inputs? Should I open an issue?
> Based on the above - no. Vector Layer parameters operate on a whole
> layer... so what would a "selected features" checkbox mean for an
> algorithm like "rename layer"? Or for setting layer styles? It's just
> opening up a can of worms
>
> Another (related) question. I've been thinking model input UI should
> be reworked. My proposal:
> - remove the list of input types
> - change it to a dock with a list of inputs present in the current
> model, with an "add" (and remove) button to add new inputs to the
> model (at which point the input type selection will be asked)
> - add up/down reordering controls for inputs (supported in the backed,
> but in the frontend there's no way to set the ordering. Which is a
> pain for making end-user usable models)
>
> Thoughts?
>
> Nyall
>
>
>> On 2017-12-11 15:01, Mathieu Pellerin wrote:
>>
>> The global use only selected features option is gone (yay) in favor of a
>> checkbox which can be activated on a per-use basis. I believe iterating
>> through selected features only requires a vector source input.
>>
>> On Dec 11, 2017 20:57, "Andreas Neumann"  wrote:
>>> Hi,
>>>
>>> In QGIS master (version 3), with a Vector Layer input, I am failing to
>>> find the option to run a processing model only on the selected features.
>>>
>>> Can you please help me find the setting? I looked in the "Options" -->
>>> "Settings" --> "Processing" or watched out for a checkbox in the "Run model
>>> dialog" - but both did not show an option to restrict on selected features
>>> only.
>>>
>>> Thanks for a hint,
>>>
>>> Andreas
>>>
>>>
>>> ___
>>> 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
>> 

Re: [QGIS-Developer] QGIS 3D: looking below the terrain model

[Andreas Neumann]

Hi Nyall, 

nice that we agree on both ;-) 

I will start collecting a wish-list on 3D and we can do a crowd funding
to address selected issues. Or we could do another QGIS grant on 3D
improvements. 

Andreas 

On 2017-12-13 23:06, Nyall Dawson wrote:

> On 14 December 2017 at 00:31, Andreas Neumann  wrote:
> 
>> However, one issue I have is that the terrain rendering disappears when I
>> look below the terrain model surface - which isn't so nice for a caver or
>> geologist. Is this also an issue about culling? Would it be possible to
>> enable the rendering of the backside of the terrain surface?
> 
> I agree that this is desirable. Geotechs will also very quickly be
> demanding this feature in order to visualise boreholes correctly!
> 
>> The other issue I have is that tilting is somehow locked at the horizon. I
>> can look down on the terrain and then rotate the whole model until I look
>> sideway into the model, but than the rotation is blocked. I cannot rotate
>> any further so that my camera gets below the surface and that I could move
>> below the surface and look up towards the terrain. I guess this makes a lot
>> of sense for people who do not need to explore things below the terrain
>> surface, but for geologists or cavers, it would be great if this
>> rotation/tilting blocking could be disabled somehow.
> 
> I'd suggest this should be an option in the 3d view configuration. I
> agree it's a valid use case, but for most users it may be unwanted.
> 
> 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 3D: navigation questions

[Andreas Neumann]

forwarding this to the list as well.

Too early in the morning to properly use an e-mail client ;-)


On 14.12.2017 06:48, Andreas Neumann wrote:

Hi Nyall,

Thanks for your replies!


On 13.12.2017 23:08, Nyall Dawson wrote:
On 14 December 2017 at 00:25, Andreas Neumann  
wrote:

Hi,

I think I heard several people stating that the navigation in QGIS 
3D is too
fast. Nyall has a PR to slow down navigation when holding the 
Ctrl-key -

which unfortunately hadn't been merged to master yet.

I'll update based on Martin's comments, just gotta find some time...


Thanks for merging. Currently compiling ...



To me the question is: when the majority of users think that 
navigation is

too fast, shouldn't the default already be slower?

I think so too :)


@Martin - can we do that?




Other navigation issues I have:

* I did not find a way to lower or raise the altitude of the 
"camera" while
staying it the same positions and not changing all the viewing 
angles (like
taking the helicopter up and down at the same position). Is there a 
hidden

shortcut for that?
Not that I can find, but we need this too. Maybe page up/page down 
could work?


Page up/Page down would be awesome for this purpose. Just need to make 
sure that the steps aren't too large (like it is currently with the 
arrow keys)




I also think we need a way to modify the camera rotation without
altering its position. See https://issues.qgis.org/issues/17653


Right - that is exactly what I would need as well!
Is there any documentation somewhere about how the navigation should 
work? I
read something about support for keyboard (arrow keys) - but if I 
use the
arrow keys, only the main 2D canvas is panned, not the 3D view. Also 
the

Shift key, which should be used according to
https://www.lutraconsulting.co.uk/blog/2017/10/16/buildings-in-qgis3d/ 
has

no effect on my machine - maybe another KDE/Plasma issue?

I believe this is a bug on all platforms when the canvas is docked.
Try undocking it.




Confirmed. Undocking the 3d widgets brings back the arrow keys. So it 
really is a bug with the docked state of the 3D widget. Is there an 
issue reported on it already?


Thanks,
Andreas


___
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] Improving usability of "Project Home" in browser?

[Mathieu Pellerin]

Sorry all, just ignore this message. Human broken, not the machine, once
again.

That'll teach me to write emails prior to intake of caffeine.

On Thu, Dec 14, 2017 at 9:09 AM, Mathieu Pellerin 
wrote:

> I find the project home node brilliant, but I've not used it so far (the
> way I structure my data isn't compatible with this concept).
>
> That said, testing it this morning, the behavior was not was I was
> expecting. IMHO, this node should essentially act as a symlink, and
> maintain the sub-directory structure.
>
> On Thu, Dec 14, 2017 at 7:43 AM, Nathan Woodrow 
> wrote:
>
>> .. listen to layers loaded on the project, pull the source from the
>> layer, resolve folder...
>>
>> Maybe I'm missing something here
>>
>> On Thu, Dec 14, 2017 at 10:41 AM, Nyall Dawson 
>> wrote:
>>
>>> On 14 December 2017 at 10:38, Nathan Woodrow 
>>> wrote:
>>> >> I'm guessing you mean "scan all folders used in the project file". If
>>> >> so, good idea! Unfortunately non-trivial... but something we
>>> >> could/should do as a future enhancement to the Project Home item.
>>> >
>>> >
>>> > Isn't project home only set after the project is loaded?  So we will
>>> know
>>> > the folders used as the project loads...
>>> >
>>>
>>> How so? Am I missing something obvious?
>>>
>>> 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
>>
>
>
___
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] Notification of QGIS releases

[Jeremy Palmer]

Thanks for the support.

> And there is
>
> https://version.qgis.org/version.txt

This is good. But can we get a platform release feed? From my understanding
windows and MacOSX releases take time to package from the time the tag is
released. Or another option is just a mail list.


> >
> > https://twitter.com/JuergenEFischer

For me this is too ad-hoc to provide to a production IT team to monitor.

> >
> > and https://github.com/qgis/QGIS/commits/release-2_18 (watch out for
> > Release xx messages).

Again this doesn't mean a binary is released for a specific platform - Just
that code is ready for packaging

Thanks,
Jeremy
___
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] Improving usability of "Project Home" in browser?

[Mathieu Pellerin]

I find the project home node brilliant, but I've not used it so far (the
way I structure my data isn't compatible with this concept).

That said, testing it this morning, the behavior was not was I was
expecting. IMHO, this node should essentially act as a symlink, and
maintain the sub-directory structure.

On Thu, Dec 14, 2017 at 7:43 AM, Nathan Woodrow  wrote:

> .. listen to layers loaded on the project, pull the source from the layer,
> resolve folder...
>
> Maybe I'm missing something here
>
> On Thu, Dec 14, 2017 at 10:41 AM, Nyall Dawson 
> wrote:
>
>> On 14 December 2017 at 10:38, Nathan Woodrow  wrote:
>> >> I'm guessing you mean "scan all folders used in the project file". If
>> >> so, good idea! Unfortunately non-trivial... but something we
>> >> could/should do as a future enhancement to the Project Home item.
>> >
>> >
>> > Isn't project home only set after the project is loaded?  So we will
>> know
>> > the folders used as the project loads...
>> >
>>
>> How so? Am I missing something obvious?
>>
>> 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
>
___
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] Improving usability of "Project Home" in browser?

[Randal Hale]

When I set up a project I have a base folder (PROJECT) with subfolders 
like: scripts, data, pdf, temp, qgs


Could I right click that folder and set it as HOME. Hence that becomes 
the default workspace for that session.


Pro:

 * Everything references home - like geoproccessing scripts etc. I open
   up a tool/script/whatever and it starts there.

Con:

 * I might change the name of the project and something breaks
 * not everyone loves storing a project in one folder structure
 * Slow QGIS at start (?)

Randy



On 12/13/2017 07:22 PM, Nyall Dawson wrote:

Hey all,

I'm seeking ideas on how we can improve the usefulness of the "Project
Home" item in the browser panel.

Currently, this item is shown after opening a project, and consists of
a directory item showing the contents of the same folder in which the
.qgs project file is stored.

I really like the idea of this Project Home item, but I can't make use
of it because at none of my current workplaces are the .qgs project
files stored in the root directory of a project. A more common
structure is something like:

project_001\
project_001\incoming_data\
project_001\reports
project_001\outgoing
project_001\data
project_001\projects\my_qgis_file.qgs

In this case the shortcut to the .qgs folder doesn't help - because
none of the interesting stuff is located there. I suspect this isn't
an uncommon scenario, and that a lot of workplaces don't store .qgs
files in the root directory of projects.

Has anyone got any ideas of how we could improve the Project Home item
to meet this scenario? Best I can come up with is to add a new setting
(booo) in Project Properties to manually set the project home
folder...

(Note - In an ideal world, ALL file open/save dialogs would have a
shortcut to this project home folder available too. It's possible in
Windows (see e.g.
http://www.pbjzone.com/images/VS2010_open_dialog.png) - but not
exposed via Qt (yet) )

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


--
Randal Hale
rjh...@northrivergeographic.com
https://www.northrivergeographic.com
(423)653-3611

___
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] What changed on Travis?

[Denis Rouzaud]

Hi,

I think that the dependency docker image got updated with latest gdal
version (possibly other libs as well) due to Qt Script removal (which
updated the Dockerfile,  hence the image).

Denis

Le mer. 13 déc. 2017 à 18:47, Even Rouault  a
écrit :

> On jeudi 14 décembre 2017 08:25:31 CET Nyall Dawson wrote:
>
> > Hi all,
>
> >
>
> > Anyone know what changed on Travis yesterday? All of a sudden we're
>
> > seeing a shapefile test failing with no changes which account for
>
> > this.
>
>
>
> Nyall,
>
>
>
> I have had today issues on Travis GDAL too (new warnings popping up
> whereas the code was unchanged), and finally tracked that down to an
> upgrade of the Trusty image from clang 3.9 to clang 5.0
>
> But in the QGIS case, this is weird since according to the cmake report it
> seems to use a clang 3.8 in both cases (probably coming from the docker
> image)
>
>
>
> But this seems definitely correlated with the change of the Travis image
> since the last good build (
> https://api.travis-ci.org/v3/job/315460942/log.txt ) is with the old
> image (with clang 3.9), and the first bad one
>
> ( https://api.travis-ci.org/v3/job/315604790/log.txt ) is with the new
> image (with clang 5.0)
>
>
>
> I see they've pubished a blog post about the change:
>
> https://blog.travis-ci.com/2017-12-12-new-trusty-images-q4-launch
>
> and the updated packages:
>
> https://docs.travis-ci.com/user/build-environment-updates/2017-12-12/
>
>
>
> Even
>
>
>
> --
>
> Spatialys - Geospatial professional services
>
> http://www.spatialys.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] Improving usability of "Project Home" in browser?

[Nathan Woodrow]

.. listen to layers loaded on the project, pull the source from the layer,
resolve folder...

Maybe I'm missing something here

On Thu, Dec 14, 2017 at 10:41 AM, Nyall Dawson 
wrote:

> On 14 December 2017 at 10:38, Nathan Woodrow  wrote:
> >> I'm guessing you mean "scan all folders used in the project file". If
> >> so, good idea! Unfortunately non-trivial... but something we
> >> could/should do as a future enhancement to the Project Home item.
> >
> >
> > Isn't project home only set after the project is loaded?  So we will know
> > the folders used as the project loads...
> >
>
> How so? Am I missing something obvious?
>
> 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] Improving usability of "Project Home" in browser?

[Nyall Dawson]

On 14 December 2017 at 10:38, Nathan Woodrow  wrote:
>> I'm guessing you mean "scan all folders used in the project file". If
>> so, good idea! Unfortunately non-trivial... but something we
>> could/should do as a future enhancement to the Project Home item.
>
>
> Isn't project home only set after the project is loaded?  So we will know
> the folders used as the project loads...
>

How so? Am I missing something obvious?

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] Improving usability of "Project Home" in browser?

[Nathan Woodrow]

>
> I'm guessing you mean "scan all folders used in the project file". If
> so, good idea! Unfortunately non-trivial... but something we
> could/should do as a future enhancement to the Project Home item.


Isn't project home only set after the project is loaded?  So we will know
the folders used as the project loads...

On Thu, Dec 14, 2017 at 10:34 AM, Nyall Dawson 
wrote:

> On 14 December 2017 at 10:26, Nathan Woodrow  wrote:
> > One option might be to scan all folders used in the profile file and add
> > each one to the project home folder so you have quick access to all
> folders
> > that are currently used.
> >
>
> I'm guessing you mean "scan all folders used in the project file". If
> so, good idea! Unfortunately non-trivial... but something we
> could/should do as a future enhancement to the Project Home item.
>
> I also don't think it fully addresses my use case, since it would only
> show utilised folders. So e.g. if I get new data and place it in a new
> folder under "incoming", it won't be shown there.
>
> 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] Improving usability of "Project Home" in browser?

[Nyall Dawson]

On 14 December 2017 at 10:26, Nathan Woodrow  wrote:
> One option might be to scan all folders used in the profile file and add
> each one to the project home folder so you have quick access to all folders
> that are currently used.
>

I'm guessing you mean "scan all folders used in the project file". If
so, good idea! Unfortunately non-trivial... but something we
could/should do as a future enhancement to the Project Home item.

I also don't think it fully addresses my use case, since it would only
show utilised folders. So e.g. if I get new data and place it in a new
folder under "incoming", it won't be shown there.

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] Improving usability of "Project Home" in browser?

[Nathan Woodrow]

One option might be to scan all folders used in the profile file and add
each one to the project home folder so you have quick access to all folders
that are currently used.

- Nathan

On Thu, Dec 14, 2017 at 10:22 AM, Nyall Dawson 
wrote:

> Hey all,
>
> I'm seeking ideas on how we can improve the usefulness of the "Project
> Home" item in the browser panel.
>
> Currently, this item is shown after opening a project, and consists of
> a directory item showing the contents of the same folder in which the
> .qgs project file is stored.
>
> I really like the idea of this Project Home item, but I can't make use
> of it because at none of my current workplaces are the .qgs project
> files stored in the root directory of a project. A more common
> structure is something like:
>
> project_001\
> project_001\incoming_data\
> project_001\reports
> project_001\outgoing
> project_001\data
> project_001\projects\my_qgis_file.qgs
>
> In this case the shortcut to the .qgs folder doesn't help - because
> none of the interesting stuff is located there. I suspect this isn't
> an uncommon scenario, and that a lot of workplaces don't store .qgs
> files in the root directory of projects.
>
> Has anyone got any ideas of how we could improve the Project Home item
> to meet this scenario? Best I can come up with is to add a new setting
> (booo) in Project Properties to manually set the project home
> folder...
>
> (Note - In an ideal world, ALL file open/save dialogs would have a
> shortcut to this project home folder available too. It's possible in
> Windows (see e.g.
> http://www.pbjzone.com/images/VS2010_open_dialog.png) - but not
> exposed via Qt (yet) )
>
> 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
___
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] Improving usability of "Project Home" in browser?

[Nyall Dawson]

Hey all,

I'm seeking ideas on how we can improve the usefulness of the "Project
Home" item in the browser panel.

Currently, this item is shown after opening a project, and consists of
a directory item showing the contents of the same folder in which the
.qgs project file is stored.

I really like the idea of this Project Home item, but I can't make use
of it because at none of my current workplaces are the .qgs project
files stored in the root directory of a project. A more common
structure is something like:

project_001\
project_001\incoming_data\
project_001\reports
project_001\outgoing
project_001\data
project_001\projects\my_qgis_file.qgs

In this case the shortcut to the .qgs folder doesn't help - because
none of the interesting stuff is located there. I suspect this isn't
an uncommon scenario, and that a lot of workplaces don't store .qgs
files in the root directory of projects.

Has anyone got any ideas of how we could improve the Project Home item
to meet this scenario? Best I can come up with is to add a new setting
(booo) in Project Properties to manually set the project home
folder...

(Note - In an ideal world, ALL file open/save dialogs would have a
shortcut to this project home folder available too. It's possible in
Windows (see e.g.
http://www.pbjzone.com/images/VS2010_open_dialog.png) - but not
exposed via Qt (yet) )

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] What changed on Travis?

[Even Rouault]

On jeudi 14 décembre 2017 08:25:31 CET Nyall Dawson wrote:
> Hi all,
> 
> Anyone know what changed on Travis yesterday? All of a sudden we're
> seeing a shapefile test failing with no changes which account for
> this.

Nyall,

I have had today issues on Travis GDAL too (new warnings popping up whereas the 
code was 
unchanged), and finally tracked that down to an upgrade of the Trusty image 
from clang 3.9 
to clang 5.0
But in the QGIS case, this is weird since according to the cmake report it 
seems to use a clang 
3.8 in both cases (probably coming from the docker image)

But this seems definitely correlated with the change of the Travis image since 
the last good 
build ( https://api.travis-ci.org/v3/job/315460942/log.txt ) is with the old 
image (with clang 
3.9), and the first bad one 
( https://api.travis-ci.org/v3/job/315604790/log.txt ) is with the new image 
(with clang 5.0)

I see they've pubished a blog post about the change:
https://blog.travis-ci.com/2017-12-12-new-trusty-images-q4-launch
and the updated packages:
https://docs.travis-ci.com/user/build-environment-updates/2017-12-12/

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.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] What changed on Travis?

[Nyall Dawson]

Hi all,

Anyone know what changed on Travis yesterday? All of a sudden we're
seeing a shapefile test failing with no changes which account for
this.

Was there a GDAL library update applied?

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] Run processing model on selected features only

[Nyall Dawson]

On 12 December 2017 at 00:10, Andreas Neumann  wrote:
> Thanks for the information. Unfortunately I cannot use "Feature Source" as
> an input in my model.
>
> Matthias told me that I have to use "Vector layer" as an input, because my
> model relies on certain features that aren't available on "feature source"
> inputs. I need to use refactor fields in a model with expressions support
> for relation_aggregates and represent_value (which requires information on
> widget configuration).
>

Hi Andreas,

Thanks for your feedback while testing the new processing modeler...
it's very valuable information!

> I also find it quite confusing that the inputs come with zero documentation.
> I think for probably 99% of the users who are not devs it isn't obvious when
> to use which input. Could we introduce a very simple tooltip that explains
> with 1 or 2 sentences what the input implies - esp. for the "Vector layer"
> vs. "Feature Source" vs. "Layer field" ?

I need to improve how this is exposed in the modeler, but the
difference between "Feature sources" and "vector layers" is that
feature sources are used wherever *features* from a layer are being
processed, vs "vector layer" parameters which are for processes which
alter the whole layer (e.g changing its style, adding a field in
place, deleting/renaming it, etc)

Accordingly, all algorithms which edit features should be made to work
fully with "feature sources". In this case, we need to fix the
refactor fields algorithm to handle the relation/represent value use
cases somehow. But the proper solution here isn't to require a vector
layer parameter.

(Note that ALL algorithms which use feature source parameters will
happily accept a vector layer parameter and operate on the all the
features in that layer... but that's just done to make the modeler as
flexible as possible).

I plan on renaming "Feature Source" -> "Vector layer features" in the
modeler to help clarify this (also "layer field" -> "vector layer
field"), and I'll add some tooltips too. (also sort that list)

> Is there any chance this checkbox could also be introduced for "Vector
> layer" inputs? Should I open an issue?

Based on the above - no. Vector Layer parameters operate on a whole
layer... so what would a "selected features" checkbox mean for an
algorithm like "rename layer"? Or for setting layer styles? It's just
opening up a can of worms

Another (related) question. I've been thinking model input UI should
be reworked. My proposal:
- remove the list of input types
- change it to a dock with a list of inputs present in the current
model, with an "add" (and remove) button to add new inputs to the
model (at which point the input type selection will be asked)
- add up/down reordering controls for inputs (supported in the backed,
but in the frontend there's no way to set the ordering. Which is a
pain for making end-user usable models)

Thoughts?

Nyall


>
> On 2017-12-11 15:01, Mathieu Pellerin wrote:
>
> The global use only selected features option is gone (yay) in favor of a
> checkbox which can be activated on a per-use basis. I believe iterating
> through selected features only requires a vector source input.
>
> On Dec 11, 2017 20:57, "Andreas Neumann"  wrote:
>>
>> Hi,
>>
>> In QGIS master (version 3), with a Vector Layer input, I am failing to
>> find the option to run a processing model only on the selected features.
>>
>> Can you please help me find the setting? I looked in the "Options" -->
>> "Settings" --> "Processing" or watched out for a checkbox in the "Run model
>> dialog" - but both did not show an option to restrict on selected features
>> only.
>>
>> Thanks for a hint,
>>
>> Andreas
>>
>>
>> ___
>> 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 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 3D: navigation questions

[Nyall Dawson]

On 14 December 2017 at 00:25, Andreas Neumann  wrote:
> Hi,
>
> I think I heard several people stating that the navigation in QGIS 3D is too
> fast. Nyall has a PR to slow down navigation when holding the Ctrl-key -
> which unfortunately hadn't been merged to master yet.

I'll update based on Martin's comments, just gotta find some time...

> To me the question is: when the majority of users think that navigation is
> too fast, shouldn't the default already be slower?

I think so too :)

> Other navigation issues I have:
>
> * I did not find a way to lower or raise the altitude of the "camera" while
> staying it the same positions and not changing all the viewing angles (like
> taking the helicopter up and down at the same position). Is there a hidden
> shortcut for that?

Not that I can find, but we need this too. Maybe page up/page down could work?

I also think we need a way to modify the camera rotation without
altering its position. See https://issues.qgis.org/issues/17653

> Is there any documentation somewhere about how the navigation should work? I
> read something about support for keyboard (arrow keys) - but if I use the
> arrow keys, only the main 2D canvas is panned, not the 3D view. Also the
> Shift key, which should be used according to
> https://www.lutraconsulting.co.uk/blog/2017/10/16/buildings-in-qgis3d/ has
> no effect on my machine - maybe another KDE/Plasma issue?

I believe this is a bug on all platforms when the canvas is docked.
Try undocking it.

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 3D: looking below the terrain model

[Nyall Dawson]

On 14 December 2017 at 00:31, Andreas Neumann  wrote:

> However, one issue I have is that the terrain rendering disappears when I
> look below the terrain model surface - which isn't so nice for a caver or
> geologist. Is this also an issue about culling? Would it be possible to
> enable the rendering of the backside of the terrain surface?

I agree that this is desirable. Geotechs will also very quickly be
demanding this feature in order to visualise boreholes correctly!

> The other issue I have is that tilting is somehow locked at the horizon. I
> can look down on the terrain and then rotate the whole model until I look
> sideway into the model, but than the rotation is blocked. I cannot rotate
> any further so that my camera gets below the surface and that I could move
> below the surface and look up towards the terrain. I guess this makes a lot
> of sense for people who do not need to explore things below the terrain
> surface, but for geologists or cavers, it would be great if this
> rotation/tilting blocking could be disabled somehow.

I'd suggest this should be an option in the 3d view configuration. I
agree it's a valid use case, but for most users it may be unwanted.

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

[QGIS-Developer] Plugin [1373] ZEB Toolbox approval notification.

[noreply]

Plugin ZEB Toolbox approval by pcav.
The plugin version "[1373] ZEB Toolbox 0.1" is now approved
Link: http://plugins.qgis.org/plugins/ZebToolbox/
___
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 [1335] Otoklim approval notification.

[noreply]

Plugin Otoklim approval by pcav.
The plugin version "[1335] Otoklim 0.1.2 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/Otoklim/
___
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] QGIS 3D: looking below the terrain model

[Andreas Neumann]

Hi,

Being a caver, I have a lot of underground data. Thanks to the support 
from Martin I got them to load correctly as 3D polygondata.


However, one issue I have is that the terrain rendering disappears when 
I look below the terrain model surface - which isn't so nice for a caver 
or geologist. Is this also an issue about culling? Would it be possible 
to enable the rendering of the backside of the terrain surface?


The other issue I have is that tilting is somehow locked at the horizon. 
I can look down on the terrain and then rotate the whole model until I 
look sideway into the model, but than the rotation is blocked. I cannot 
rotate any further so that my camera gets below the surface and that I 
could move below the surface and look up towards the terrain. I guess 
this makes a lot of sense for people who do not need to explore things 
below the terrain surface, but for geologists or cavers, it would be 
great if this rotation/tilting blocking could be disabled somehow.


Thanks,

Andreas

___
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] QGIS 3D: navigation questions

[Andreas Neumann]

Hi,

I think I heard several people stating that the navigation in QGIS 3D is 
too fast. Nyall has a PR to slow down navigation when holding the 
Ctrl-key - which unfortunately hadn't been merged to master yet.


To me the question is: when the majority of users think that navigation 
is too fast, shouldn't the default already be slower?


Other navigation issues I have:

* I did not find a way to lower or raise the altitude of the "camera" 
while staying it the same positions and not changing all the viewing 
angles (like taking the helicopter up and down at the same position). Is 
there a hidden shortcut for that?


* When rotating the whole model (middle mouse button) - how can I 
determine the rotation point? What is the rule for rotating the whole model?


Is there any documentation somewhere about how the navigation should 
work? I read something about support for keyboard (arrow keys) - but if 
I use the arrow keys, only the main 2D canvas is panned, not the 3D 
view. Also the Shift key, which should be used according to 
https://www.lutraconsulting.co.uk/blog/2017/10/16/buildings-in-qgis3d/ 
has no effect on my machine - maybe another KDE/Plasma issue?


Thanks for your reply.

Andreas




___
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 nightly - snap shortcut

[Borys Jurgiel]

Ah, found it! I'm changing it in the PL translation from S to P (so Shift+Alt
+P will also work), unless you have a better idea.

Please note nightly builds don't contain the recent translations, so it won't 
be effective before the release. Or...

@Werner, what about:
1. pulling recent string changes to Transifex (there are tons of them I guess)
2. pushing translations to master, so we all can enjoy and test them early.

Borys
___
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-community-team] WhiteboxTools geospatial data analysis engine

[Paolo Cavallini]

Thanks John,
adding your toolbox to Processing seems a very good idea, and it should
be a reasonable task. One thing that would speed up and facilitate the
adoption, at least for Linux users, would be to have proper offical
packages for it. I'd be interested in helping with the Debian packaging.
All the best, and thanks for sharing.

Il 12/12/2017 19:36, John Lindsay ha scritto:
> Hello QGISers,
> 
> /Please note, I intended to submit the following to the Developers mail
> group, but I think that access to that site is restricted. Hopefully
> someone on the core development team will read this./
> 
> I am the lead developer of an open-source GIS called Whitebox GAT
> . I frequently get
> requests from users who want to access Whitebox GAT's plugin tools from
> outside of the software and to incorporate these tools into other
> geospatial projects. Admittedly, this has never been very easy in the
> past, in large part owing to the fact that Whitebox GAT was largely
> developed using Java, but also due to the architecture of the project. I
> have recently started to port Whitebox GAT's many tools into a
> stand-alone command-line application called WhiteboxTools
> . This
> small library already contains about 250 tools for processing raster and
> LiDAR data sets (Whitebox GAT has about 450 tools--much work remains). I
> have developed WhiteboxTools using the Rust programming language, a
> low-level systems language that is efficient and safe (without use of
> garbage collection). The project uses a permissive MIT open-source
> license. I'm not sure if there is any interest in incorporating any or
> all of the tools contained in WhiteboxTools as a toolbox in QGIS, but I
> thought that I would make you aware of the possibility. I welcome any
> feedback or questions you may have.
> 
> As an aside, thank you for all of your efforts. I am well aware of the
> monumental efforts that your team must have made to make QGIS what it is
> today. Well done!
> 
> Best regards,
> 
> John Lindsay, PhD
> 
> Room 346, Hutt Building,
> 
> Department of Geography,
> 
> The University of Guelph,
> 
> E-mail: jlind...@uoguelph.ca
> 
> Phone: (519) 824-4120 ext. 56074
> 
> Web: http://www.uoguelph.ca/geography/faculty/lindsay-john
> 
> Research page: http://www.uoguelph.ca/~hydrogeo/
> 
> Whitebox GAT: http://www.uoguelph.ca/~hydrogeo/Whitebox/index.html
> 
> 
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as 
> documentation, translation etc..
> qgis-community-t...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
> 


-- 
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@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] Build problems of master (GDAL related)

[Andreas Neumann]

Hi Strk,

Thanks a lot. It helped!

Andreas


On 13.12.2017 10:40, Sandro Santilli wrote:

On Wed, Dec 13, 2017 at 10:26:37AM +0100, Andreas Neumann wrote:


../src/core/qgsvectorfilewriter.cpp:126:43: error:
‘GDAL_DCAP_FEATURE_STYLES’ was not declared in this scope

...


I use GDAL SVN (latest version): GDAL 2.3.0dev, released 2017/99/99

Any idea what could be done to fix my compile issues?

I've had the same problem yesterday, make sure to drop any gdal header
from older releases and re-install a clean GDAL from current trunk.

--strk;


___
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] Build problems of master (GDAL related)

[Nyall Dawson]

On 13 December 2017 at 19:26, Andreas Neumann  wrote:

> I use GDAL SVN (latest version): GDAL 2.3.0dev, released 2017/99/99
>
> Any idea what could be done to fix my compile issues?
>

Just to expand on Sandro's answer: I've been implementing some changes
in upstream GDAL to allow us to remove some hardcoded format handling
in QGIS. These changes have been merged in gdal dev and will be
included in 2.3, but in meantime they have also been utilised in qgis
code for gdal >= 2.3 builds.

So basically you need to update to a newer svn build which includes
these latest changes (or use a stable gdal build, which will also
work, and just fall back to the hardcoded format handling).

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] Build problems of master (GDAL related)

[Richard Duivenvoorde]

Hi Andreas,

yesterday on IRC strk had the same problem:

http://irclogs.geoapt.com/qgis/%23qgis.2017-12-12.log

something with different selfbuild GDAL's?

Regards,

Richard Duivenvoorde


On 13-12-17 10:26, Andreas Neumann wrote:
> Hi,
> 
> I tried to build latest QGIS master but run into - probably - GDAL issues:
> 
> ---
> 
> 47/4075] Generating qgsversion.h, qgsversion.inc
> Files "/home/an/dev/QGIS/build/qgsversion.h.temp" to
> "/home/an/dev/QGIS/build/qgsversion.h" are different.
> [104/4075] Building CXX object
> src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o
> FAILED: src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o
> /usr/lib/ccache/c++  -DENABLE_TESTS -DQGISDEBUG=1 -DQT_CONCURRENT_LIB
> -DQT_CORE_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB
> -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_POSITIONING_LIB
> -DQT_PRINTSUPPORT_LIB -DQT_SQL_LIB -DQT_SVG_LIB -DQT_WEBKITWIDGETS_LIB
> -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB
> -DTEST_DATA_DIR=\"/home/an/dev/QGIS/tests/testdata\" -DWITH_BINDINGS
> -DWITH_QTWEBKIT -D_HAVE_PTHREAD_ -D_TTY_POSIX_ -Dqgis_core_EXPORTS -I.
> -I../src/core -Isrc/core -I../src/core/3d -I../src/core/annotations
> -I../src/core/auth -I../src/core/composer -I../src/core/dxf
> -I../src/core/effects -I../src/core/expression
> -I../src/core/fieldformatter -I../src/core/geometry -I../src/core/geocms
> -I../src/core/geocms/geonode -I../src/core/layertree
> -I../src/core/layout -I../src/core/locator -I../src/core/metadata
> -I../src/core/pal -I../src/core/processing
> -I../src/core/processing/models -I../src/core/providers
> -I../src/core/providers/memory -I../src/core/raster
> -I../src/core/renderer -I../src/core/scalebar -I../src/core/symbology
> -I../src/core/gps/qextserialport -isystem /usr/include/x86_64-linux-gnu
> -isystem /usr/include/spatialindex -isystem /usr/local/include -isystem
> /usr/include/QtCrypto -isystem /usr/include/qt5keychain -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtPositioning -Wall -Wextra
> -Wno-long-long -Wformat-security -Wno-strict-aliasing -g -fPIC
> -fvisibility=hidden   -fPIC -std=gnu++11 -MD -MT
> src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o -MF
> src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o.d -o
> src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o -c
> ../src/core/qgsvectorfilewriter.cpp
> ../src/core/qgsvectorfilewriter.cpp: In static member function ‘static
> bool QgsVectorFileWriter::supportsFeatureStyles(const QString&)’:
> ../src/core/qgsvectorfilewriter.cpp:126:43: error:
> ‘GDAL_DCAP_FEATURE_STYLES’ was not declared in this scope
>    return CSLFetchBoolean( driverMetadata, GDAL_DCAP_FEATURE_STYLES,
> false );
> ^~~~
> ../src/core/qgsvectorfilewriter.cpp:126:43: note: suggested alternative:
> ‘GDAL_DCAP_DEFAULT_FIELDS’
>    return CSLFetchBoolean( driverMetadata, GDAL_DCAP_FEATURE_STYLES,
> false );
> ^~~~
> GDAL_DCAP_DEFAULT_FIELDS
> [113/4075] Building CXX object
> src/core/CMakeFiles/qgis_core.dir/composer/qgscomposition.cpp.o
> ninja: build stopped: subcommand failed.
> 
> 
> 
> I use GDAL SVN (latest version): GDAL 2.3.0dev, released 2017/99/99
> 
> Any idea what could be done to fix my compile issues?
> 
> Thanks a lot,
> 
> Andreas
> 
> ___
> 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] Build problems of master (GDAL related)

[Andreas Neumann]

Hi,

I tried to build latest QGIS master but run into - probably - GDAL issues:

---

47/4075] Generating qgsversion.h, qgsversion.inc
Files "/home/an/dev/QGIS/build/qgsversion.h.temp" to 
"/home/an/dev/QGIS/build/qgsversion.h" are different.
[104/4075] Building CXX object 
src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o

FAILED: src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o
/usr/lib/ccache/c++  -DENABLE_TESTS -DQGISDEBUG=1 -DQT_CONCURRENT_LIB 
-DQT_CORE_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_POSITIONING_LIB 
-DQT_PRINTSUPPORT_LIB -DQT_SQL_LIB -DQT_SVG_LIB -DQT_WEBKITWIDGETS_LIB 
-DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB 
-DTEST_DATA_DIR=\"/home/an/dev/QGIS/tests/testdata\" -DWITH_BINDINGS 
-DWITH_QTWEBKIT -D_HAVE_PTHREAD_ -D_TTY_POSIX_ -Dqgis_core_EXPORTS -I. 
-I../src/core -Isrc/core -I../src/core/3d -I../src/core/annotations 
-I../src/core/auth -I../src/core/composer -I../src/core/dxf 
-I../src/core/effects -I../src/core/expression 
-I../src/core/fieldformatter -I../src/core/geometry -I../src/core/geocms 
-I../src/core/geocms/geonode -I../src/core/layertree 
-I../src/core/layout -I../src/core/locator -I../src/core/metadata 
-I../src/core/pal -I../src/core/processing 
-I../src/core/processing/models -I../src/core/providers 
-I../src/core/providers/memory -I../src/core/raster 
-I../src/core/renderer -I../src/core/scalebar -I../src/core/symbology 
-I../src/core/gps/qextserialport -isystem /usr/include/x86_64-linux-gnu 
-isystem /usr/include/spatialindex -isystem /usr/local/include -isystem 
/usr/include/QtCrypto -isystem /usr/include/qt5keychain -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtPositioning -Wall -Wextra 
-Wno-long-long -Wformat-security -Wno-strict-aliasing -g -fPIC 
-fvisibility=hidden   -fPIC -std=gnu++11 -MD -MT 
src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o -MF 
src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o.d -o 
src/core/CMakeFiles/qgis_core.dir/qgsvectorfilewriter.cpp.o -c 
../src/core/qgsvectorfilewriter.cpp
../src/core/qgsvectorfilewriter.cpp: In static member function ‘static 
bool QgsVectorFileWriter::supportsFeatureStyles(const QString&)’:
../src/core/qgsvectorfilewriter.cpp:126:43: error: 
‘GDAL_DCAP_FEATURE_STYLES’ was not declared in this scope
   return CSLFetchBoolean( driverMetadata, GDAL_DCAP_FEATURE_STYLES, 
false );

^~~~
../src/core/qgsvectorfilewriter.cpp:126:43: note: suggested alternative: 
‘GDAL_DCAP_DEFAULT_FIELDS’
   return CSLFetchBoolean( driverMetadata, GDAL_DCAP_FEATURE_STYLES, 
false );

^~~~
GDAL_DCAP_DEFAULT_FIELDS
[113/4075] Building CXX object 
src/core/CMakeFiles/qgis_core.dir/composer/qgscomposition.cpp.o

ninja: build stopped: subcommand failed.



I use GDAL SVN (latest version): GDAL 2.3.0dev, released 2017/99/99

Any idea what could be done to fix my compile issues?

Thanks a lot,

Andreas

___
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 nightly - snap shortcut

[Borys Jurgiel]

> Hi Sławomir,
> 
> you can override the default QGIS keyboard shortcuts, see:
> 
> https://docs.qgis.org/testing/en/docs/user_manual/introduction/qgis_configur
> ation.html#keyboard-shortcuts
> 
> Note that with me the shortcut is a simple capital S.
> 
> I do not think we can make everybody happy with the chosen shortcuts :-)

It seems to be a bit more complicated...

Usually we can translate shortcuts in the PL translation, but this one seems 
to be generated automagically by QT - I can't find any place in the code where 
it could be defined. 

Does anybody know how it's being generated? Probably we should define it 
explicitly so we can translate it.

Borys

PS. As Richard said, it's listed as simple "s", so you can't use it when 
you're in any text edit widget. It seems the Shift+Alt+S is an alias for such 
situations - with inverted priority, what causes the problem. So the only fast 
fix is to change it to e.g. "p".
___
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 nightly - snap shortcut

[Slawomir Bienias]

Hi, thanks!

Yes, I know I can change default shortcut. But the problem is not the
shortcut - it is ok and it is great to turn on/off snap by shortcut. 

I see the problem, because this shortcut works when I'm editing attributes
in the dialog box after create a feature in text field. Is there any chance
to "repair" this?

In attribute table and expression fields "Ś" works fine.


Regards, 
Sławomir Bienias



--
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 nightly - snap shortcut

[Richard Duivenvoorde]

On 13-12-17 09:03, Slawomir Bienias wrote:
> Hello,
> 
> I have noticed, that snap default shortcut (Shift+Alt+S) works when I'm
> editing attributes. 
> 
> It is problem with Polish letter "Ś", because if you want to write "Ś" you
> have to combine keys Shift+Alt+S... and then you turn the snapping function
> on...
> 
> My test was on virtual machine with Ubuntu 17.10 and nightly snapshot form
> debian repo.
> 
> 
> Best regards,
> Sławomir

Hi Sławomir,

you can override the default QGIS keyboard shortcuts, see:

https://docs.qgis.org/testing/en/docs/user_manual/introduction/qgis_configuration.html#keyboard-shortcuts

Note that with me the shortcut is a simple capital S.

I do not think we can make everybody happy with the chosen shortcuts :-)


Regards,

Richard Duivenvoorde
___
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] QGIS nightly - snap shortcut

[Slawomir Bienias]

Hello,

I have noticed, that snap default shortcut (Shift+Alt+S) works when I'm
editing attributes. 

It is problem with Polish letter "Ś", because if you want to write "Ś" you
have to combine keys Shift+Alt+S... and then you turn the snapping function
on...

My test was on virtual machine with Ubuntu 17.10 and nightly snapshot form
debian repo.


Best regards,
Sławomir



--
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