Re: [Qgis-user] Labeling: Allow HTML Formatting, text-size and map units

2024-05-16 Thread Nyall Dawson via QGIS-User
On Thu, 16 May 2024 at 23:51, chris hermansen via QGIS-User
 wrote:
>
> Thomas and list,
>
> On Thu, May 16, 2024, 06:39 Thomas Schüttenberg  wrote:
>>
>> Hi Chris,
>>
>> yes I tried that. Any css-unit I could think of as well as em, % and 
>> code-words (large). But only pt resulted in a visible change on the canvas.

We're a little constrained by the subset of css which the Qt library
supports. See https://doc.qt.io/qt-6/richtext-html-subset.html#css-properties

Unfortunately Qt CSS only supports font sizes in pt or px, not %. This
could be an enhancement which the QGIS project considers sponsoring in
Qt in future -- I can certainly see the limitation for a use case like
you describe!

Nyall


>>
>> Not sure if it is just not implemented or if it is a bug.
>
>
> So ... works but  doesn't... That seems to be 
> surprising behaviour.
>
> I can get that CSS style directives might not work the way one might hope 
> (that often happens to me in other circumstances...)
>
> This is tempting me to experiment. Thanks for that!
>
>>
>> Thomas
>>
>> > chris hermansen  hat am 15.05.2024 21:00 CEST 
>> > geschrieben:
>> >
>> >
>> > Thomas and list,
>> >
>> >
>> > On Wed, May 15, 2024 at 7:20 AM Thomas Schüttenberg via QGIS-User 
>> >  wrote:
>> > > Ha!
>> > >  I found an other way around to do the trick, suitable for my use case 
>> > > at least:
>> > >
>> > >  1) increasing the (overall) text size setting on the text tab by 2/3
>> > >  2) putting only the attributes/text strings of the second and following 
>> > > lines between ... tags, which renders them about 2/3 smaler, 
>> > > i.e. same as before.
>> > >
>> > >  The (reverse) result is a multi line label with the first line 
>> > > emphazised by its larger size! ;-)
>> > >
>> > >  "Bezeichnung" || 'D ' || round("Deckelhohe",2) || 
>> > > 'S ' || round( "Sohlhohe" ,2) || ''
>> > >
>> > In your first note you mentioned:
>> >
>> > > But only pt (points) seams to work as the unit in this place, which 
>> > > gives a fixed size throughout all scales and does not respect the 
>> > > behavior of the map units with maximum scale setting.
>> >
>> > I suppose you tried style="font-size: 75%;" and maybe style="font-size: 
>> > 0.75em;", and they did not work?
>> >
>> > I wonder if, besides ..., you might have tried 
>> > ...?
>> > --
>> >
>> > Chris Hermansen · clhermansen "at" gmail "dot" com
>> >
>> > C'est ma façon de parler.
>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Search through folders and combine SHP files

2024-05-09 Thread Nyall Dawson via QGIS-User
On Fri, 10 May 2024 at 09:06, Tony Shepherd (FarmMaps NZ) via QGIS-User <
qgis-user@lists.osgeo.org> wrote:

> Hi
>
>
>
> I have loads, literally thousands, of SHP, GPKG, TAB files located in
> loads of different folders and sub-folders.
>
>
>
> Is there a plugin that will trawl through a set of folders, copy say just
> the polygons from each file into a new file, and populate a field with say
> the filename and folder the polygon(s) came from?
>
>
>
> Essentially combining a heap of files into one with some metadata about
> where the data came from?
>
>
>
> Why?  I have files from clients dating back about 20 years.  Clients sell
> properties.  Properties get subdivided.  New clients come and see us, and
> often we don’t realise we have GIS info on file for that property from many
> years ago, usually under a different name.  It would be handy to see a
> polygon on the screen and easily go back to some old GIS data.
>
>
>
> Maybe I am missing an easy tool to do this, but I can’t see anything
> obvious.
>

You could use the "Merge Vector Layers" tool from the Processing toolbox,
that does everything you want. The trickiest bit would be getting a master
list of ALL your shapefiles/etc you want to combine and passing this to the
tool. It's not going to be easy from the GUI itself, as that only allows
you to add files from a single folder at once.

I'd run the tool on the files from a single folder, then checkout the
processing history dialog and copy the python command which corresponds to
what you just did. You could then adapt this command to pass a complete
list of all the files you want to combine. (It's quite straightforward in
Python to build a list of files which recursively match a file pattern --
see eg https://stackoverflow.com/a/2186565 )

Hope that helps!
Nyall


>
>
>
>
> Cheers
>
> Tony
>
>
>
>
> --
>
> *Tony Shepherd*
>
> *  GeoSpatial Manager @ FarmMaps NZ & Photographer @ Shepherd Photos*
>
>
>
> *Phone* *–* 027 435 6193  | *Website – *shepherdphotos.co.nz
>
> *Email** – Maps* t...@farmmaps.nz  |  *Email – Photos*
> t...@shepherdphotos.co.nz
>
> *Facebook* TonyShepherdPhotos
> 
>
>
>
>
>
> [image: FM_logo1_small (Custom)]
>
>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] QGIS 3.36.1 Installation

2024-04-15 Thread Nyall Dawson via QGIS-User
On Tue, 16 Apr 2024 at 03:56, Pham, Ty via QGIS-User
 wrote:
>
> Hello Team,
>
>
>
> I am trying to onboard 3.36.1 here at JPMorgan and our internal packaging 
> team receives the below error when launching shortcut.
>
>
>
>
>
> Is it possible to disable this so that it does NOT prompt install of Open 
> Sans font?

There's a fix queued for the next round of patch releases -- you'll
need to wait for these.

Nyall
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] adding offset to QgsSvgMarkerSymbolLayer using pyqgis

2024-01-25 Thread Nyall Dawson via QGIS-User
On Thu, 25 Jan 2024, 7:04 pm Bernhard Seckinger via QGIS-User, <
qgis-user@lists.osgeo.org> wrote:

> Hi,
>
> I wrote a plugin which changes the symbology of a layer using SVG-images.
> Almost everything works but I need to add an offset to the SVG-image and
> did
> not find a way to set it from pyqgis.
>
> That's what I'm doing currently (rule is a rule from a
> QgsRuleBasedRenderer):
>
> icon = os.path.dirname(__file__) + 'a.svg';
> marker = QgsSvgMarkerSymbolLayer(icon)
> marker.setAngle(100) # setting the angle works
> # marker.setOffset(5,5) # this doesn't work (there is no setOffset method)
>

setOffset exists, but requires a QPointF argument. See
https://qgis.org/pyqgis/master/core/QgsMarkerSymbolLayer.html#qgis.core.QgsMarkerSymbolLayer.setOffset

Nyall


rule.symbol().changeSymbolLayer(0,marker)
>
> Any ideas?
>
> Thanks, Bernhard
>
> --
> Bernhard Seckinger 
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] QGIS Qt6 Wayland ongoing status

2024-01-18 Thread Nyall Dawson via QGIS-User
> Thanks very much for this detailed authoritative explanation, Nyall.  I
have a couple of specific comments below...

>  It's disappointing to read this as there's clearly a disconnect between
what e.g. QGIS developers are experiencing and what Fedora, Gentoo and
maybe others are saying about Qt5 and Wayland.  For example, this on the
Gentoo Wiki here https://wiki.gentoo.org/wiki/Wayland

That gentoo page is fairly optimistic in that it's considering wayland
support "complete" just because it works for common use cases.

>> For Qt an additional package called dev-qt/qtwayland is required. In the
Qt Wiki it says: "QtWayland is a Qt 5 module that wraps the functionality
of Wayland. QtWayland is separated into a client and server side. The
client side is the wayland platform plugin, and provides a way to run Qt
applications as Wayland clients. The server side is the QtCompositor API,
and allows users to write their own Wayland compositors."

This is definitely incorrect. Qt5 on wayland, regardless of whether or not
QtWayland is in play, will still be broken. It will "kind of" work in some
circumstances, but eg docks/toolbars are broken and will NEVER work
correctly under this setup.

> And this on Fedora here
https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
>
>> Qt Wayland plugin has been available for a long time, but it hasn't been
in condition where it could be enabled by default. With Qt 5.12 the state
of the Wayland plugin is much better and it's becoming more and more
reliable.

"becoming more reliable" does not equate to "reliable" 藍

>  It now supports all the needed protocols and has been enabled by default
for non-Gnome Wayland sessions. With Qt Wayland on Gnome Wayland session we
need to support CSD, it's actually the only way how decorations are going
to work in Qt apps right now. Qt Wayland implements basic decorations,
which really doesn't match Gnome Adwaita theme, therefore there are new CSD
being implemented as part of QGnomePlatform.
>>
>> To make Qt applications run natively on Wayland we need to modify Qt 5,
specifically qt5-qtbase module, where we allow the Wayland plugin to be
used also for Gnome sessions. The new decorations from QGnomePlatform will
be used automatically once they are fully implemented and updated in Fedora.
>
> (the above dated 2019!!!)

Right, but that's all focusing on a very narrow topic -- getting client
side decorations working under wayland and allowing Qt applications to
open. Once again, trying to use anything but a very simple single window /
"hello world" type application will quickly run into breakage. That
particular page is written from a "running Qt apps on Wayland under gnome"
viewpoint, and isn't trying to consider the lower lying topics about
getting full functionality for any qt app (on any platform) working under
Wayland.

>>
>> Read about the sorry state of it here:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/247
>
>
> An exceptionally informative pull request.  I was particularly struck by
this comment:
>
>>  Of course you could argue that all of these applications should be
rewritten from the ground up, but especially in science this is not
feasible - people will use X11 indefinitely rather than going to Wayland
with a much degraded user experience.
>
>
> Maybe it's just me, but I have to think that the lack of a placement
protocol (when X, Windows and OSX all support this) is a design mis-feature
in Wayland, rather than a decision taken to guide the architecture of
future desktop applications...

I should have linked to the original posting relating to this (couldn't
find it yesterday). Here's the full gory details:
https://blog.tenstral.net/2024/01/wayland-really-breaks-things-just-for-now.html


Nyall



>
>>
>> So yeah, not a happy situation. At least on the QGIS side we're making
progress toward Qt 6 compatibility, and that's all we can really do from
our end.
>
>
> Well as always, extreme thank-yous to all QGIS developers.  And again the
information you provide here is very valuable at least to me, so thanks
again for taking the time to write this!
>>
>>
>> Nyall
>
>
> [previous stuff deleted]
>
>
> --
> Chris Hermansen · clhermansen "at" gmail "dot" com
>
> C'est ma façon de parler.
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] QGIS Qt6 Wayland ongoing status

2024-01-17 Thread Nyall Dawson via QGIS-User
On Thu, 18 Jan 2024 at 13:56, chris hermansen via QGIS-User <
qgis-user@lists.osgeo.org> wrote:
>
> Adam and list,
>
> On Wed, Jan 17, 2024 at 5:34 PM Adam Nielsen 
wrote:
>>
>> > I have been trying to find a mostly definitive and mostly up-to-date
>> > conversation about the status of QGIS, Qt6 and Wayland and I'm not
having
>> > any luck.
>>
>> What's the underlying need for this information?

... gather round folks, for a truly sorry tale! Here's the definitive(*)
situation regarding QGIS and wayland.

- Qt 5 based applications do NOT work well under any wayland environment.
There's fundamental broken functionality, and its functionality which QGIS
requires. A good example is trying to drag a toolbar or dock panel --
you'll instantly "break" the application with non functional empty windows.
- This particular issue HAS been fixed in very recent Qt versions. Read all
about it here:
https://blog.david-redondo.de/kde/wayland/qt/2023/08/08/xdg-toplevel-drag.html
. BUT... this fix ONLY works if the desktop environment supports the fix.
So you'll also need a very recent KDE release for this to work. Gnome, in
typical Gnome fashion, have shown no interest in helping out other toolkits
and implementing this new Wayland protocol and so Qt applications (even
those built with Qt 6.6+) will still be broken. There's little hope on the
horizon that Gnome will change their ways, so you'll also need to move to
KDE and put Gnome in the past. 路
- So let's say you're running KDE, on a distro with a very recent Qt
version. You'll still need a QGIS build based on Qt 6. That's a heavy work
in progress at the moment. We're all ACTIVELY working toward that, but it's
still some time away. You CAN build master versions and get a mostly
working QGIS Qt6 build, so long as you don't require any Python support,
that is!
- Ok, now lets assume you're on KDE, have recent Qt 6 library, have built
QGIS master with Qt6 support and don't need python/plugins. Yay! Will
everything work on Wayland? Well, not quite!.. There's still going to be
broken functionality (such as the color picker not working outside of the
QGIS application). There's also STILL fundamental missing bits in Wayland
itself, such as proper restoring of Window locations. Every time QGIS opens
a new dialog it'll just be thrown on some random screen at some random
location. There's still no real progress toward that being fixed. Read
about the sorry state of it here:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/247

So yeah, not a happy situation. At least on the QGIS side we're making
progress toward Qt 6 compatibility, and that's all we can really do from
our end.

Nyall




>
>
> I don't know if you have recently run QGIS on a Wayland desktop, but
there is a stern message strongly suggesting reverting to X.
>
> So as we seem to be marching away from X and ever forward to Wayland, I
would like to start planning ahead a bit, and I would especially like to
find some real information, as opposed to "I think this (but I really don't
know)", or even worse, the people who can see a bright future for (let's
say) Wayland-only desktops and aren't worried about the bumps on the road
getting there.
>
> Fortunately it seems Ubuntu 24.04 will continue to support X
https://discourse.ubuntu.com/t/ubuntu-desktop-24-04-lts-roadmap-highlights/41032
so in my case at least I know I can drop back to X if / as necessary for
the immediate future.
>>
>>
>> > There is some stuff on GitHub but it seems to be at least a year or two
>> > old, talking about Qt6.0 and I gather we are at Qt6.6 by now.  Plus
endless
>> > short conversations in places like Reddit that throw off more heat than
>> > light.
>>
>> Updating to a new Qt version is likely going to be a lot of work, so I
>> imagine nobody is that keen on starting until there's really no choice.
>
>
> As it happens, a search for qt6 in the QGIS repo on GitHub shows work
being done on qt6, apparently for QGIS 4.  So maybe someone has started
already?  I wonder how that's going?
>>
>>
>> > Does anyone have any suggestions as to where to keep informed on this
>> > topic?  Because it seems like Wayland is coming whether we want it or
not...
>>
>> Wayland has been around for many years at this point, and is already the
>> default on some Linux distributions, which have no problem running
>> QGIS.  There is so much legacy code that they are always going to have
>> compatibility modules to keep non-Wayland programs usable.  I wouldn't
>> worry about any programs suddenly breaking due to Wayland.
>
>
> While I appreciate your attempts to reassure me, this isn't helping.
>
> I'm aware from firsthand experience that Wayland has been around for many
years at this point.  I have even used it on and off.  In fact it's my
daily driver on my laptop.
>
> My concern is learning how QGIS development might converge - or not -
with a Wayland-only future, since it seems several important Linux distros
are leaning away from supporting X to 

Re: [Qgis-user] Canvas larger than viewport is rendered/drawn for vector layers, but not for raster layers

2023-12-11 Thread Nyall Dawson via QGIS-User
On Thu, 16 Nov 2023, 2:40 am Thomas Larsen Wessel via QGIS-User, <
qgis-user@lists.osgeo.org> wrote:

> This screen capture demonstrates much better than words:
> https://imgur.com/5LSEsiY.
>
> Is there any way I can make it prerender the raster data as well?
>
> What I have already tried:
> * setting almost infinite cache size
> * all the relevant QGIS options/settings I could find
> * both local (gpkg) and remote WMS raster data
> * both Windows and Linux
> * QGIS 3.22 and 3.30
> * different CRS for layer
>
> Some of my tests did make the rendering speed up, but no matter what it
> always renders the raster data only for the canvas inside the view port,
> and does not render anything outside of the view port, whereas vector data
> is always rendered for an area that extends outside the view port.
>

There's a few parts to the logic defining whether a layer will be included
in the outside-visible-extent preview:

- WMS layers are **never** included. This is by design, to reduce
unnecessary server load
- when a layer is drawn the time taken to render it is recorded. If this
time exceeds a certain threshold, then the layer is marked as too expensive
to render in these optional out-of-canvas areas.

(You can check the new renderer profile option available in the F12
debugging tools panel in 3.34 for more detailed information about layer
render times)

Nyall



> Sincerely, Thomas
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Accessing iface from jupyter to create map from QGIS

2023-12-06 Thread Nyall Dawson via QGIS-User
On Thu, 7 Dec 2023 at 13:13, noshin prachi via QGIS-User <
qgis-user@lists.osgeo.org> wrote:

> Thank you Adam for your response. I have imported iface from from
> qgis.utils import iface. I am working in qgis environment.   It is my
> first work with qgis and I am finding it difficult to understand. Can you
> please share where I am going wrong? Is there any other way to activate a
> layer from multiple layers and create a map?  I have google street map ,
> shape file and dfsu file in these layers which are required to be added in
> the map.
>

iface is ONLY available when you're running the QGIS desktop application.
It contains methods for interacting with the parts of the desktop
application, which have no meaning when run from elsewhere (such as in a
notebook). In this situation you should avoid iface and use only the
classes from qgis.core instead.

Hope that helps!
Nyall



>
> On Wed, 6 Dec 2023 at 18:10, Adam Nielsen via QGIS-User <
> qgis-user@lists.osgeo.org> wrote:
>
>> > While trying to activate with iface.setactivelayer I am facing an error.
>>
>> The error is complaining that iface is None.  Your code doesn't show
>> what value you assigned to this variable - where did you set iface and
>> what value did you set it to?  I think you forgot to set it and that is
>> why you are getting this error.
>>
>> Cheers,
>> Adam.
>> ___
>> QGIS-User mailing list
>> QGIS-User@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Reselect Features

2023-11-16 Thread Nyall Dawson via QGIS-User
On Fri, 17 Nov 2023 at 12:48, Michael Edward McNeil via QGIS-User <
qgis-user@lists.osgeo.org> wrote:

>
> This is the moment when it would be exceedingly nice if one could just
> pull down Edit > Select > Reselect Features and thereby get back to the
> last previous selected set of features as they existed just prior to the
> last keystroke/click entered.
>
> But that command appears to do nothing.
>

Reselect only works if you've previously "cleared" a selection. If you're
*changing* the selection, then reselect won't do anything.

I think what you're ultimately asking for is a undo/redo history for
selections Which is a GOOD idea! 

Nyall


>
> (Thanks again for your response!)
>
> Best,
> Michael McNeil
>
>
> > On Nov 16, 2023, at 16:33, Andrea Giudiceandrea via QGIS-User <
> qgis-user@lists.osgeo.org> wrote:
> >
> > 
> >>
> >> Michael Edward McNeil memcneil02 at gmail.com
> >> Thu Nov 16 16:04:37 PST 2023
> >
> >> Why doesn't the Edit > Select > Reselect Features command work?
> >
> > Hi Michael,
> > it seems to me the command works as expected [1], at least using QGIS
> 3.28 on Windows.
> >
> > May you provide a detailed list of steps that lead to such command to
> not work properly?
> >
> > Best regards.
> >
> > Andrea
> >
> > [1]
> https://docs.qgis.org/3.28/en/docs/user_manual/introduction/general_tools.html#selecting-manually-on-the-map-canvas
> > ___
> > QGIS-User mailing list
> > QGIS-User@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


[Qgis-user] QEP: Authentication system updates

2023-11-15 Thread Nyall Dawson via QGIS-User
Hi lists,

I've created a new QGIS enhancement proposal at
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/278
concerning changes to the inbuilt authentication system / secure storage
support in QGIS.

By its nature, the authentication framework needs to be secure and any
changes to the authentication logic need careful consideration.

Comments and discussion on the github ticket linked above are encouraged!

Kind regards,
Nyall
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Removal of overlap geometries within the same layer - merge to largest neighbor polygon

2023-07-25 Thread Nyall Dawson via QGIS-User
On Tue, 25 July 2023, 8:02 pm Andreas Neumann via QGIS-User, <
qgis-user@lists.osgeo.org> wrote:

> Hi,
>
> A friend of mine has a dirty input data set with lots of overlapping
> geometries (within the same layer) and asked me if there is a tool within
> QGIS to automatically remove the overlaps and assign the overlapping area
> to the neighbor polygon with the largest area.
>
> The solution was surprisingly hard to find, although I am pretty sure
> there are multiple combinations of algorithms that would solve the problem.
> Here is the solution I came up with: 
> https://github.com/qgis-ch/overlap_removal/tree/main
> - perhaps you have better ideas - more elegant solutions?
>
> Wouldn't it be great if QGIS had a processing tool to solve this overlap
> cleaning within the same layer "out of the box" without having to use a
> graphical model or a more or less complicated sequence of algorithms in the
> processing toolbox? Apparently, ArcGIS has such a tool ...
>
> Saga and GRASS also might have such tools - but I couldn't get the SAGA
> based QGIS plugin "Dissect and dissolve overlaps" (
> https://plugins.qgis.org/plugins/dissect_dissolve_overlaps).
>
> The same problem exists for automatically filling small gaps in the
> polygon data set ...
>

The recently introduced geos tools for coverage layer cleaning and
simplification seem like a good fit here! See eg
https://lin-ear-th-inking.blogspot.com/2022/08/validating-polygonal-coverages-in-jts.html?m=1

These tools would ideally be exposed through the qgis processing toolbox.

Nyall

Andreas
>
>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Possible bug?

2023-07-23 Thread Nyall Dawson via QGIS-User
On Sun, 23 July 2023, 5:39 pm Richard Duivenvoorde via QGIS-User, <
qgis-user@lists.osgeo.org> wrote:

> Hi Roxo,
>
> You are right, I can confirm this with a very recent build of QGIS:
>
> - with extension we ask for confirmation of overwriting
> - without extension we silently overwrite an old file
>

It's actually an operating system (well, gtk library) issue. The same thing
happens in other apps too on that same platform.

Nyall


> Please file an issue (https://github.com/qgis/QGIS/issues), this seems
> easily fixable.
> See
> https://qgis.org/en/site/getinvolved/development/bugreporting.html#bugs-features-and-issues
>
> Regards,
>
> Richard Duivenvoorde
>
> On 7/22/23 20:21, Fernando M. Roxo da Motta via QGIS-User wrote:
> >
> >
> >Hi all,
> >
> >Today I was exporting some QGis projects as PNG images
> > (project>import/export>export map to image).   At certain point I made
> > a mistake and repeated the name of the previous map, and QGis happily
> > overwrote the previous image, without asking before.  I tried to repeat
> > the action giving the full name of the file (map10.png) and QGis asked
> > for confirmation.The difference was that the first time I gave jjust
> > a name, without the "extension" .png.
> >
> >It seems that even if QGis will give the default "extension" to the
> > filename, it does not verify the prior existence of the file after it
> > attach the "extension".
> >
> >This was in a QGis 3.26.0 on Linux Xubuntu 20.04.   I know that both
> > the QGis and system are kind of old, but if this "feature" is present
> > in current versions it can be cumbersome.
> >
> >
> >
> >Roxo
> >
>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Color Picker Only Partially Opens

2023-07-12 Thread Nyall Dawson via QGIS-User
On Wed, 12 July 2023, 6:24 pm Alexandru Munteanu via QGIS-User, <
qgis-user@lists.osgeo.org> wrote:

> Hi,
> I can confirm the issue. It's the same with me. I have to click two times
> for the color selector to show entirely. I'm using 3.28 version. I have two
> monitors of the same resolution and make. On my laptop is the same.
>

Is this reproducible on versions 3.30 or later? A fix was added in 3.30
which should address this.

Nyall


> Alexandru
>
>
> On Wed, Jul 12, 2023, 10:45 Frank Broniewski via QGIS-User <
> qgis-user@lists.osgeo.org> wrote:
>
>> Hi Tim,
>>
>>
>>
>> I cannot replicate the issue on my Windows 11 machine (OSGeo4W Installer
>> w QGIS 3.28), but I have all kinds of scaling / UI issues when using mixed
>> DPI screens. I.e. when using my Laptops HiRes Screen and attach a normal
>> FullHD-Monitor, things can get all wonky … do you have by any chance this
>> kind of setup?
>>
>>
>>
>> *Von:* QGIS-User  *Im Auftrag von *Tim
>> Malloy via QGIS-User
>> *Gesendet:* Dienstag, 11. Juli 2023 21:06
>> *An:* qgis-user@lists.osgeo.org
>> *Betreff:* [Qgis-user] FW: Color Picker Only Partially Opens
>>
>>
>>
>> Greetings QGIS Users,
>>
>>
>>
>> I have a long-standing issue with the color picker dialog box in QGIS –
>> all versions (running on Windows 11, but issue has been encountered on
>> various Windows versions) and I’m wondering if there is a setting or some
>> other fix to resolve this.  The issue is that when I click on the down
>> arrow on the color settings dialog in the Layer Styling panel the color
>> picker dialog box only partially opens (image on the left).  I have to
>> click twice more to close and then reopen the color picker dialog box to
>> get it to fully open (image on the right).  This happens the first time I
>> attempt to open the dialog box after performing another function.  If I
>> remain in the same layer and test other colors the dialog will open fully
>> with one click.   This seems minor but when I’m setting up colors for lots
>> of new layers or matching colors to those of other features within a
>> project, where the “Pick Color” function is really handy, it gets pretty
>> tedious.  I suspect this is a Windows issue but any thoughts about the
>> issue and how to resolve it would be appreciated.
>>
>>
>>
>> Tim
>>
>>
>>
>> [image: A screenshot of a computer Description automatically generated]
>> [image: A screenshot of a computer Description automatically generated]
>>
>>
>>
>> Tim Malloy
>>
>> 402 Park Drive
>>
>> t...@tgmalloy.com
>>
>>
>>
>>
>> ___
>> QGIS-User mailing list
>> QGIS-User@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] [QGIS-Developer] Call of testing of nightlies on hi-dpi displays

2023-05-29 Thread Nyall Dawson via QGIS-User
On Mon, 29 May 2023 at 19:23, Richard Duivenvoorde  wrote:
>
> Hi Nyall,
>
> Happy to do some testing, I do have a (dual boot) laptop/tablet with 
> 3000x2000 screen (that's high-dpi, yes?), but in Gnome I set the Display 
> 'Scale' on 200% to have proper applications (an to me readable text :-) ).
>
> Is there some test plan/idea's?

There's a few things in particular we need to identify:

- Widgets which are now showing as pixelated. Basically just hunt
through the UI looking for things which look pixelated! This might be
icons, graphics, or even just the drawing of the widget itself. You'll
spot them immediately, as they clearly stand out. But there's a LOT of
different dialogs/tabs/widgets/pages/... in QGIS and it will take some
time to hunt through them all.
- Icons/images which look the wrong size. Eg the marker symbols shown
in the layer tree right now are incorrectly sized and will be half the
size of the actual symbol shown on the map. That's a known regression,
but there's likely others like this hiding around the place.
- Text which is the wrong size. If something has a hard-coded sizing
it's possible that we'll get fonts scaled badly, so if you spot any
text which noticably looks incorrectly sized vs other UI elements then
that's also something we need to fix.

> Is my setup something you want to test (200%), or is is preferred to use the 
> 100% scale?

This is EXACTLY the kind of setup we need testing on! If the display
scaling is set to 100% (in Windows, or Linux), then you'll see no
difference between the old approach vs new. The new logic only kicks
in when display scaling is present.

> I'm not sure what is supposed to be the 'normal' way of scaling (like what 
> does a mac do)?

Things should just look perfect, regardless of whether or not display
scaling is active :)

Nyall

> Or is it more to try to see if the icons/widgets scale up/down when fidling 
> with scale (or what it is called in Windows)?
>
> Regards,
>
> Richard Duivenvoorde
>
> On 5/29/23 06:01, Nyall Dawson via QGIS-Developer wrote:
> > Hi lists,
> >
> > For the upcoming QGIS 3.32 release a change has been made in how QGIS
> > handles high dpi (and retina) displays. This should ultimately make
> > QGIS behave MUCH better on these displays, but there's likely some
> > short-term fallout and regressions caused by the change.
> >
> > If you've access to a high-dpi display, please test out the nightly
> > releases and file bug reports on github for any regressions you spot
> > -- in particular we are looking for widgets and places where the QGIS
> > interface is now looking pixelated or where the scale / sizes of
> > objects are incorrect.
> >
> > (Currently there's known regressions for the icons shown in the layer
> > tree panel, and for pixelated icons in the style manager dialog.)
> >
> > Thanks in advance!
> > Nyall
> > ___
> > QGIS-Developer mailing list
> > qgis-develo...@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


[Qgis-user] Call of testing of nightlies on hi-dpi displays

2023-05-28 Thread Nyall Dawson via QGIS-User
Hi lists,

For the upcoming QGIS 3.32 release a change has been made in how QGIS
handles high dpi (and retina) displays. This should ultimately make
QGIS behave MUCH better on these displays, but there's likely some
short-term fallout and regressions caused by the change.

If you've access to a high-dpi display, please test out the nightly
releases and file bug reports on github for any regressions you spot
-- in particular we are looking for widgets and places where the QGIS
interface is now looking pixelated or where the scale / sizes of
objects are incorrect.

(Currently there's known regressions for the icons shown in the layer
tree panel, and for pixelated icons in the style manager dialog.)

Thanks in advance!
Nyall
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


[Qgis-user] PSA: Don't update to Gnome 44!

2023-04-27 Thread Nyall Dawson via QGIS-User
Hi lists,

Just a quick PSA: If you're using QGIS (or any Qt based app), I recommend
avoiding an upgrade to any gnome 44 based distribution for now.

You'll get hit with this nasty bug:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2715 which breaks drag and
drop functionality in all Qt applications. And in the process, basically
makes QGIS unusable... 

You've been warned!

Nyall
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Placing random points

2023-03-23 Thread Nyall Dawson via QGIS-User
On Thu, 23 Mar 2023 at 19:20, Thomas Sebastien via QGIS-User
 wrote:
>
> Dear QGIS users,
>
> I’m trying to place a small number of points, n, randomly in a large number 
> of polygons, N. But, the Vector>Research Tools> Random points in polygons 
> tool only lets me place a minimum of 1 random point in each of the N 
> polygons, i.e N points when I only need n. Do you know a way I can go about 
> this?

How about dissolving the polygons into a single feature and then
placing the desired random number of points inside this dissolved
feature?

Nyall

>
> Thanks,
>
> Sebastien
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Problems with transformation including height values

2023-03-21 Thread Nyall Dawson via QGIS-User
On Tue, 21 Mar 2023, 8:21 pm Richard McDonnell, 
wrote:

> Hi,
>
> Just to add to what Nyall said.
>
> See link below, which suggests a way using OGR to carry out the process
> you require.
>
>
>
>
> https://gis.stackexchange.com/questions/324848/transform-datum-csv-csv-using-ogr2ogr
>
>
>
> It suggests you preform your horizontal transformation first, this can be
> done in QGIS, then carry out the Vertical Transformation. This can be done
> in command line, if you are on windows, the best option is to use the *OSGeo4w
> Shell*, as all the needed environmental settings are applied.
>
> I hope the above helps.
>
>
>
> Maybe there is an opportunity to have QGIS preform Vertical translations,
> even if these are a separate step? It’s something that would be useful for
> both Raster and Vector Data.
>

It's definitely on the radar -- especially for transformation of point
clouds. It's just a very involved task with a high degree of complexity,
and will need funding to happen.

Nyall

Regards,
>
>
> Richard
>
>
>
>
>
>
>
> ——
> Richard McDonnell MSc GIS, FME Certified Professional
> *FRM Data Management*
>
> ——
> Oifig na nOibreacha Poiblí
> Office of Public Works
>
> Sráid Jonathan Swift, Baile Átha Troim, Co na Mí, C15 NX36
> Jonathan Swift Street, Trim, Co Meath, C15 NX36
> ——
> M +353 87 688 5964 T +353 46 942 2409
> https://gov.ie/opw
>
> ——
> To send me files larger than 30MB, please use the link below
> https://filetransfer.opw.ie/filedrop/richard.mcdonn...@opw.ie
>
> Email Disclaimer:
> https://www.gov.ie/en/organisation-information/439daf-email-disclaimer/
>
> ——
> MSc GIS, FME Certified Professional
>
> ——
> Oifig na nOibreacha Poiblí
> Office of Public Works
>
> Sráid Jonathan Swift, Baile Átha Troim, Co na Mí, C15 NX36
> Jonathan Swift Street, Trim, Co Meath, C15 NX36
> ——
> M +353 87 688 5964 T +353 46 942 2409
> https://https://gov.ie/opw <https://www.opw.ie>
>
> ——
> Email Disclaimer:
> https://www.gov.ie/en/organisation-information/439daf-email-disclaimer/
> <https://www.opw.ie/en/disclaimer/>
>
> *From:* QGIS-User  *On Behalf Of *Nyall
> Dawson via QGIS-User
> *Sent:* 21 March 2023 10:14
> *To:* Bo Victor Thomsen 
> *Cc:* qgis-user 
> *Subject:* Re: [Qgis-user] Problems with transformation including height
> values
>
>
>
>
>
> On Tue, 21 Mar 2023, 8:06 pm Bo Victor Thomsen via QGIS-User, <
> qgis-user@lists.osgeo.org> wrote:
>
> Hi list -
>
> I have a problem with transforming a csv file containing x,y *and *z
> values from EPSG:4326 to EPSG:7416, i.e I want to transform the height
> value from LongLat/ WGS84 ellipsoid height to UTM32/Etrs89 with vertical
> reference DVR90.
>
> The file look like this:
>
>
> *== data.csv, EPSG:4326 id: col1, x: col3, y: col2, z: col4 == *
> a;55.0;12.0;42.0
> b;55.05;12.0;43.0
> c;55.10;12.0;44.0
> d;55.15;12.0;45.0
> e;55.20;12.0;46.0
> *===*
>
> *Step 1*: I import the file into QGIS using the Data Source Manager -->
> "Delimited Text" and define the projection to be EPSG:4326 *and* to
> include z values. This works and the points are shown on my map where I
> expect them to be (Somewhere in the middle of Zealand, Denmark)
>
> *Step 2*: I export the layer as a geojson file using "Export" --> "Save
> features as.." from the layer manager and choose EPSG:7416 (UTM32/ETRS89
> with DVR90 as vertical reference. And to include z-values
>
> The resulting file looks like this:
>
>
> *== data.geojson, EPSG:7416 == *{
> "type": "FeatureCollection",
> "name": "data",
> "crs": { "type": "name", "properties": { "name":
> "urn:ogc:def:crs:EPSG::4979" } },
> "features": [
> { "type": "Feature", "properties": { "field_1": "a", "field_2": 55.0,
> "field_3": 12.0, "field_4": 42.0 }, "geometry": { "type": "Point",
> "coordinates": [ 12.0, 55.0, 42.0 ] } },
> { "type": "Feature", "properties": { "field_1": "b", "field_2": 55.05,
> "field_3": 12.0, "field_4": 43.0 }, "geometry": { "type": "Point",
> "coordinates": [ 12.0, 55.05, 43.0 ] } },
> { "type": "Feature", "properties": { "field_1": "c", "field_2": 55.1,
> "field_3": 12.0, "field_4": 44.0 }, "geometry": { "ty

Re: [Qgis-user] Problems with transformation including height values

2023-03-21 Thread Nyall Dawson via QGIS-User
On Tue, 21 Mar 2023, 8:06 pm Bo Victor Thomsen via QGIS-User, <
qgis-user@lists.osgeo.org> wrote:

> Hi list -
>
> I have a problem with transforming a csv file containing x,y *and *z
> values from EPSG:4326 to EPSG:7416, i.e I want to transform the height
> value from LongLat/ WGS84 ellipsoid height to UTM32/Etrs89 with vertical
> reference DVR90.
>
> The file look like this:
>
> *== data.csv, EPSG:4326 id: col1, x: col3, y: col2, z: col4 ==*
> a;55.0;12.0;42.0
> b;55.05;12.0;43.0
> c;55.10;12.0;44.0
> d;55.15;12.0;45.0
> e;55.20;12.0;46.0
> *===*
>
> *Step 1*: I import the file into QGIS using the Data Source Manager -->
> "Delimited Text" and define the projection to be EPSG:4326 *and* to
> include z values. This works and the points are shown on my map where I
> expect them to be (Somewhere in the middle of Zealand, Denmark)
>
> *Step 2*: I export the layer as a geojson file using "Export" --> "Save
> features as.." from the layer manager and choose EPSG:7416 (UTM32/ETRS89
> with DVR90 as vertical reference. And to include z-values
>
> The resulting file looks like this:
>
> *== data.geojson, EPSG:7416 ==*
> {
> "type": "FeatureCollection",
> "name": "data",
> "crs": { "type": "name", "properties": { "name":
> "urn:ogc:def:crs:EPSG::4979" } },
> "features": [
> { "type": "Feature", "properties": { "field_1": "a", "field_2": 55.0,
> "field_3": 12.0, "field_4": 42.0 }, "geometry": { "type": "Point",
> "coordinates": [ 12.0, 55.0, 42.0 ] } },
> { "type": "Feature", "properties": { "field_1": "b", "field_2": 55.05,
> "field_3": 12.0, "field_4": 43.0 }, "geometry": { "type": "Point",
> "coordinates": [ 12.0, 55.05, 43.0 ] } },
> { "type": "Feature", "properties": { "field_1": "c", "field_2": 55.1,
> "field_3": 12.0, "field_4": 44.0 }, "geometry": { "type": "Point",
> "coordinates": [ 12.0, 55.1, 44.0 ] } },
> { "type": "Feature", "properties": { "field_1": "d", "field_2": 55.15,
> "field_3": 12.0, "field_4": 45.0 }, "geometry": { "type": "Point",
> "coordinates": [ 12.0, 55.15, 45.0 ] } },
> { "type": "Feature", "properties": { "field_1": "e", "field_2": 55.2,
> "field_3": 12.0, "field_4": 46.0 }, "geometry": { "type": "Point",
> "coordinates": [ 12.0, 55.2, 46.0 ] } }
> ]
> }
> *===*
>
> The new file is shown in my map exactly on top of the original point
> layer, meaning the horizontal projection is accurate. However, my z
> coordinates are not reprojected to the new vertical reference. All the
> z-values are exactly the same as the values in the .csv - file.
>
> After some digging through Google and other places, I discover that
> EPSG:4326 *doesn't* have a z component. Surprise ! You have to use
> EPSG:4979, which is the same as EPSG:4326 with ellipsoid height.
>
> But, *after *repeating *step 1*, *but* using EPSG:4979 as CRS during
> import, and subsequently repeating *step 2*, I get the exact same result:
> No transformation of height values.
>
> So, what is not working ? Am I doing something wrong ?? Or is QGIS
> incapable of transforming z values ???
>

The second -- qgis currently doesn't handle vertical crs at all. My
recommendation is to use gdal utilities to do a transform respecting
vertical datums.

Nyall

>
> --
> Med venlig hilsen / Best regards
>
> Bo Victor Thomsen
>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Export to ESRI File Geodatabase

2023-01-17 Thread Nyall Dawson via QGIS-User
On Wed, 18 Jan 2023 at 07:04, Even Rouault via QGIS-User
 wrote:
>
> Randal,
>
> Support for the OpenFileGDB driver in the Save As dialog only dates back
> to a few days ago per https://github.com/qgis/QGIS/pull/51397 , so
> you'll have to wait for 3.28.3

Just to clarify -- the missing bit in 3.28 was that FileGeodatabase
wasn't showing in the layer right-click menus.
It should still be possible to export to GDB in 3.28 without that fix.
From the browser panel, you can create a new empty Geodatabase by
right-clicking on a folder, and then drag and drop layers directly
into that GDB to import them!

Nyall


>
> What you must see with the driver being interminently available is that
> some of your installations might have the FileGDB driver (not
> OpenFileGDB) that relies on the ESRI closed source SDK.
>
> Even
>
> Le 17/01/2023 à 21:56, Randal Hale via QGIS-User a écrit :
> > I don't think this is just me - BUT - I wanted to check before filing
> > a bug report. This is all with QGIS 3.28.2 On Windows 10 and using
> > GDAL 3.6.1
> >
> > I was checking on a problem and had used Network Installer to install
> > QGIS - I had File Geodatabase as a choice for Export (Right Click on
> > Layer -> Export As ->pick  ESRI File Geodatabase).
> >
> > I installed QGIS using the Stand Alone installer (after removing QGIS
> > Network Install) and didn't have ESRI File Geodatabase as a choice on
> > export Features. This is confirmed by another user using the
> > standalone installer.
> >
> > I removed QGIS and Reinstalled using the Network Installer and didn't
> > have ESRI File Geodatabase as a choice (but I did before).
> >
> > So it seems like I'm missing something - I've been digging through
> > options and creating new profiles but I can't make the ERI File
> > Geodatabase consistently appear or disappear. Is there something else
> > I should try?
> >
> > Randy
> >
> >
> --
> http://www.spatialys.com
> My software is free, but my time generally not.
>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Unable to open some LISTdata open data ESRI File Geodatabases

2022-12-15 Thread Nyall Dawson via QGIS-User
On Fri, 16 Dec 2022 at 09:18, Even Rouault via QGIS-User
 wrote:
>
> Hi Peter,
>
> yes I confirm this dataset is a raster gdb. I can sort-of open it with
> my QGIS + GDAL master build using the OpenFileGDB driver, but you'll see
> the raster tables in a raw unusable way. For example layers like
> fras_blk_NCH_ES_WATER_LOGGING_HAZARD which contains the tiles as
> compressed data in a BLOB column.
>
> You could try the https://github.com/r-barnes/ArcRasterRescue utility to
> convert into GeoTIFF

FWIW, I've had more luck with the fork at
https://github.com/justinfisk/ArcRasterRescue

Nyall

>
> You could also kindly or not kindly suggest your administration to not
> use proprietary formats for open data whereas thereare so many open
> alternatives, like GeoTIFF...
>
> Small "advertizing": for those interesting, there's a funding
> opportunity to develop a GDAL open source raster driver to be able to
> read filegdb rasters that QGIS could use to open directly such files.
> Contact me off-list if interested.
>
> Even
>
> Le 15/12/2022 à 23:49, JOLLY, Peter via QGIS-User a écrit :
> > Hello
> >
> > I've downloaded some  datasets from the LISTdata open data repository 
> > (https://listdata.thelist.tas.gov.au/opendata/index.html) -  which is a 
> > great service.
> > However, I can't open any datasets that are solely an ESRI File 
> > Geodatabase, e.g. 
> > https://listdata.thelist.tas.gov.au/opendata/data/NCH_ES_WATER_LOGGING_HAZARD_STATEWIDE.zip
> >  (279 MB)
> > Maybe these are raster gdb datasets? How can I tell if that is the case?
> > Is there any way the open a raster gdb other than with ESRI software?
> >
> > I can open gdb files in QGIS from LISTdata that are included as part of a 
> > set with shapefile and MapInfo tab files (e.g. in the "Tasmanian Irrigation 
> > Irrigation District" dataset). I'm guessing that is because these are 
> > vector gdb files?
> >
> > I'm running QGIS 3.10.6 ltr on Windows 10 64-bit (yes I know it's not the 
> > latest ltr, but it was the most recent "portable" build I have been able to 
> > find and run successfully).
> >
> > Thanks
> > Peter
> > Tasmania, Australia
> >
> > ___
> > QGIS-User mailing list
> > QGIS-User@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
> --
> http://www.spatialys.com
> My software is free, but my time generally not.
>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Georeferencer Problem

2022-12-07 Thread Nyall Dawson via QGIS-User
On Thu, 8 Dec 2022 at 09:53, Grant Boxer via QGIS-User
 wrote:
>
> I am having issues with the georeferencer. When I register an image the 
> process does not recognise the CRS entered into the settings window. It 
> returns the layer with an invalid projection. When I try to change the 
> projection in the new layer it creates this error.
>
>
>
> Has anyone else had this problem? See output below, Any thoughts?


That error is coming from the "enmapboxplugin" plugin. Try removing
that plugin and re-testing.

Nyall

>
>
>
> Regards Grant Boxer, Perth WA
>
>
>
> An error has occurred while executing Python code:
>
> RuntimeError: The JPEG driver does not support update access to existing 
> datasets.
>
> Traceback (most recent call last):
>   File 
> "C:\Users/boxer/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\qgispluginsupport\qps\layerconfigwidgets\gdalmetadata.py",
>  line 1218, in apply
> ds = gdalDataset(self.mapLayer(), gdal.GA_Update)
>   File 
> "C:\Users/boxer/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\qgispluginsupport\qps\utils.py",
>  line 829, in gdalDataset
> return gdalDataset(dataset.source(), eAccess=eAccess)
>   File 
> "C:\Users/boxer/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\enmapbox\qgispluginsupport\qps\utils.py",
>  line 833, in gdalDataset
> ds = gdal.Open(dataset, eAccess)
>   File "C:\OSGeo4W\apps\Python39\lib\site-packages\osgeo\gdal.py", line 4708, 
> in Open
> return _gdal.Open(*args)
> RuntimeError: The JPEG driver does not support update access to existing 
> datasets.
>
>
> Python version: 3.9.5 (tags/v3.9.5:0a7dcbd, May  3 2021, 17:27:52) [MSC 
> v.1928 64 bit (AMD64)]
> QGIS version: 3.28.1-Firenze Firenze, fde3b8fbb8
>
> Python Path:
>
> · C:/OSGeo4W/apps/qgis/./python
>
> · 
> C:/Users/boxer/AppData/Roaming/QGIS/QGIS3\profiles\default/python
>
> · 
> C:/Users/boxer/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins
>
> · C:/OSGeo4W/apps/qgis/./python/plugins
>
> · C:\OSGeo4W\bin\python39.zip
>
> · C:\OSGeo4W\apps\Python39\DLLs
>
> · C:\OSGeo4W\apps\Python39\lib
>
> · C:\OSGeo4W\bin
>
> · 
> C:\Users\boxer\AppData\Roaming\Python\Python39\site-packages
>
> · C:\OSGeo4W\apps\Python39
>
> · C:\OSGeo4W\apps\Python39\lib\site-packages
>
> · C:\OSGeo4W\apps\Python39\lib\site-packages\win32
>
> · C:\OSGeo4W\apps\Python39\lib\site-packages\win32\lib
>
> · C:\OSGeo4W\apps\Python39\lib\site-packages\Pythonwin
>
> · 
> C:/Users/boxer/AppData/Roaming/QGIS/QGIS3\profiles\default/python
>
> · 
> C:\Users/boxer/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin\site-packages
>
> · 
> C:\Users/boxer/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\enmapboxplugin
>
> · 
> C:\Users\boxer\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\enmapboxplugin\enmapbox\site-packages
>
> · 
> C:\Users\boxer\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\enmapboxplugin\enmapbox\apps
>
> · 
> C:\Users\boxer\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\enmapboxplugin\enmapbox\coreapps
>
> · 
> C:\Users\boxer\AppData\Roaming\QGIS\QGIS3\profiles\default\python\plugins\enmapboxplugin\enmapbox\eo4qapps
>
> .
>
>
>
>
>
> ___
> QGIS-User mailing list
> QGIS-User@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
QGIS-User mailing list
QGIS-User@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] New crowdfunding campaign: point clouds and 3D improvements in QGIS

2022-09-27 Thread Nyall Dawson via Qgis-user
On Tue, 27 Sept 2022 at 16:40, Saber Razmjooei
 wrote:
>
> Hi Andreas,
>
> Many thanks for your email.
> @Nyall Dawson can comment on that, but I think it should be possible to add 
> SVG format too as an option to export elevation profiles to.

The issue with including SVG export is the time-old limitation in Qt
regarding SVG exports when clipping paths are present. We use clipping
paths heavily in the elevation plots, so if we exported these to SVG
then the clipping would be ignored and the results would be an
unusable mess.

(I'll revisit this when the issue is resolved in Qt, as the actual
QGIS part of SVG exports is trivial)

Nyall




>
> Kind regards
> Saber
>
>
> On Tue, 27 Sept 2022 at 08:25, Andreas Neumann  wrote:
>>
>> Hi Saber,
>>
>> Very good. Hopefully it will be another successful campaign.
>>
>> A question on the export of the profile: CSV and DXF is mentioned. Wouldn't 
>> it also make sense to add SVG export, so the profile could be exported to 
>> Inkscape/Illustrator? I know, it is already possible to export a layout to 
>> SVG (and with the new enhancement, the profile can then be part of a 
>> layout), but it would be convenient, being able to export to SVG without 
>> having to create a layout first. Not sure, how much effort this would mean?
>>
>> I will help to spread the word!
>>
>> Andreas
>>
>> On Mon, 26 Sept 2022 at 17:43, Saber Razmjooei via Qgis-user 
>>  wrote:
>>>
>>> Dear all,
>>>
>>> As you know, in the past couple of years, we (Lutra, North Road and 
>>> https://hobu.co/) added support point clouds and developed several new 3D 
>>> features to QGIS (e.g. Profile tool).
>>>
>>> For the next round of crowdfunding, after feedback by several user groups 
>>> and organizations, we decided to bring processing of point clouds to QGIS. 
>>> In addition, there will be several enhancements to the profile tool and 3D 
>>> maps. For more information, see:
>>> https://www.lutraconsulting.co.uk/crowdfunding/pointcloud-processing-qgis/
>>>
>>> Your help is needed to make this happen. Please support our crowdfunding 
>>> campaign by filling out the pledge form. If you are from a larger 
>>> organisation and require extra information to contribute to the campaign, 
>>> please contact me.
>>>
>>> Kind regards
>>> Saber
>>>
>>> --
>>> Saber Razmjooei
>>> www.lutraconsulting.co.uk
>>>
>>> ___
>>> Qgis-user mailing list
>>> Qgis-user@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>>
>>
>> --
>>
>> --
>> Andreas Neumann
>> QGIS.ORG board member (treasurer)
>
>
>
> --
> Saber Razmjooei
> www.lutraconsulting.co.uk
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Event loop in QGIS3

2022-08-16 Thread Nyall Dawson via Qgis-user
On Wed, 17 Aug 2022 at 06:54, Tudorache, Marian via Qgis-user
 wrote:
>
> Hi Chris,
>
>
>
> I read that article and based on it I found out that I need to put 
> processEvents() and I understand the logic in this.
>
>
>
> Someone said:
>
> In more recent QGIS versions the Python console no longer triggers this event 
> loop, as it's often quite dangerous to execute the loop in the middle of 
> other running code.
>
>
>
> It seems somehow QGIS 2.18 was designed to send automatically updates to the 
> GUIs when a loop is running and this capability was eliminated in QGIS 3

That's correct -- there was a forced processEvents in QGIS 2 after
printing anything, but that directly lead to crashes in some
circumstances. processEvents is a potentially very dangerous call, so
now the responsibility is on end users/developers to make sure it's
safe to call after a print.

Nyall



>
> Anyway, thank you for your answer.
>
>
>
> Marian
>
>
>
> From: chris hermansen 
> Sent: August 16, 2022 4:40 PM
> To: Tudorache, Marian 
> Cc: qgis-user@lists.osgeo.org
> Subject: [EXT] Re: [Qgis-user] Event loop in QGIS3
>
>
>
> Marian and list, On Tue, Aug 16, 2022 at 12: 02 PM Tudorache, Marian via 
> Qgis-user  wrote: Hello community,   A while 
> ago I sent a question about a problem with QMessageBox and message bar does 
> not get updated
>
> Marian and list,
>
>
>
> On Tue, Aug 16, 2022 at 12:02 PM Tudorache, Marian via Qgis-user 
>  wrote:
>
> Hello community,
>
>
>
> A while ago I sent a question about a problem with QMessageBox and message 
> bar does not get updated during a long process.
>
> In my example I create a script like this.
>
>
>
> from qgis.PyQt import QtWidgets
>
> message = "Wait to open the airspace project..."
>
> msg = QtWidgets.QMessageBox()
>
> msg.setText(message)
>
> msg.show()
>
> qgis.utils.iface.messageBar().pushMessage("Wait", message)
>
>
>
>
>
> for i in range(1000):
>
> print(i)
>
> qgis.utils.iface.messageBar().pushMessage("Done", "The process is done")
>
> msg.setText("The process is done")
>
> msg.show()
>
> qgis.utils.iface.messageBar().pushMessage("Done", "The process is done"))
>
>
>
>
>
> When I run the scrip in QGIS 2.18 the QMessageBox displays first the message 
> "Wait to open the airspace project...". The same message is pushed to 
> messageBar.
>
> Then during the loop it displays the variable i.
>
> At the end of the loop the QMessageBox displays the message "The process is 
> done" which is also pushed to the messageBar.
>
>
>
> When I run the same scrip on QGIS 3 the QMessageBox is empty. The message 
> "Wait to open the airspace project..." is not displayed by QMessageBox nor by 
> messageBar.
>
> The print inside the loop displays the I and when the loop is done the 
> QMessageBox displays the message "The process is done".
>
> The messageBar displays also the message "The process is done". And after a 
> while it displays the initial message "Wait to open the airspace project..."
>
>
>
> I modified the scrip by adding QApplication.processEvents() inside the loop 
> and now everything is fine.
>
> It seems QGIS3 no longer triggers this event loop and I have to do this 
> explicitly by calling processEvents from QApplication.
>
>
>
> Why QGIS 3 needs to call QApplication.processEvents() and QGIS 2 does not 
> need?
>
>
>
>
>
> Marian, did you read this article?
>
>
>
> https://doc.qt.io/qt-5/qcoreapplication.html#details
>
>
>
> There you will see this:
>
>
>
> The event loop is started with a call to exec(). Long-running operations can 
> call processEvents() to keep the application responsive.
>
>
>
> In your case, your "long-running operation" is your for loop.  And it is not 
> QGIS3 that has the responsibility to trigger processEvents() but your own 
> long-running operation, at least the way I'm reading this.
>
>
>
> As to why QGIS 2 did not need this, I don't know.
>
>
> --
>
> Chris Hermansen · clhermansen "at" gmail "dot" com
>
> C'est ma façon de parler.
>
>
> 
>
> This electronic message, as well as any transmitted files included in the 
> electronic message, may contain privileged or confidential information and is 
> intended solely for the use of the individual(s) or entity to which it is 
> addressed. If you have received this electronic message in error please 
> notify the sender immediately and delete the electronic message. Any 
> unauthorized copying, disclosure or distribution of the electronic message is 
> strictly forbidden. NAV CANADA accepts no liability for any damage caused by 
> any virus and/or other malicious code transmitted by this electronic 
> communication.
>
> Le présent message électronique et tout fichier qui peut y être joint peuvent 
> contenir des renseignements privilégiés ou confidentiels destinés à l’usage 
> exclusif des personnes ou des organismes à qui ils s’adressent. Si vous avez 
> reçu ce message électronique par erreur, veuillez en informer l’expéditeur 
> immédiatement et supprimez le. Toute 

Re: [Qgis-user] Convert huge shapefile to small size

2022-07-28 Thread Nyall Dawson via Qgis-user
On Fri, 29 Jul 2022 at 06:22, Madry, Scott via Qgis-user
 wrote:
>
> Thanks Chris, but I do think that this is a topic is worth considering by the 
> QGIS community, beyond the limitations of the archaeic shapefile format. We 
> are moving into an era of very big data, both raster and vector, and QGIS 
> should be able to meet this challenge. This will require some foresight and 
> planning, thus my raising the issue. Or not...

In truth QGIS is already well prepared for handling massive datasets.
(E.g. you'll see in recent versions how well it handles mammoth point
cloud formats!). Sure, there's further improvements which can be made,
but they're evolutionary rather than revolutionary!

Nyall


>
> Best,
>
> Scott
>
> On Jul 28, 2022, at 4:05 PM, chris hermansen  wrote:
>
> Scott and list,
>
> With respect I think this conversation is moving off the point, which was 
> related to a 5gb shapefile
>
> https://en.m.wikipedia.org/wiki/Shapefile
>
> Which is beyond the design limits of the Shapefile standards and perhaps 
> therefore the source of the problem that the OP has.
>
> Notably not a limitation of QGIS
>
> On Thu, Jul 28, 2022, 10:45 Madry, Scott via Qgis-user 
>  wrote:
>>
>> Dear colleagues,
>>
>> As we move more into the world of big data, IOE, data mining, and data 
>> analytics, dealing with larger and larger data sets will become required, 
>> and, eventually, the norm.
>>
>> GRASS GIS has made very good progress in this regard, optimizing the code to 
>> run on massively parallel computer architectures, with very good effect:
>>
>> https://grasswiki.osgeo.org/wiki/Supercomputing
>>
>> Perhaps it is time for QGIS to consider this in its future development 
>> plans? We will certainly be needing this in the future.
>>
>> And thanks to all the team who keep the QGIS train running, I am constantly 
>> amazed at the energy, effort, and availability of people to the broader 
>> community.
>>
>> Scott
>>
>> Scott Madry, Ph.D.
>> Research Associate Professor of Archaeology
>> The University of North Carolina at Chapel Hill
>>
>> Tel 1-919-448-4493
>> Email:mad...@email.unc.edu
>> https://scottmadry.web.unc.edu
>> Skype:   scott madry
>>
>>
>>
>> On Jul 28, 2022, at 10:14 AM, jhubbslist--- via Qgis-user 
>>  wrote:
>>
>> Past a point, trying to run a GIS app with very large data structures just 
>> doesn't work well. If you really need all the information you're carrying 
>> around for your analysis or whatever, you may need to reach for different 
>> tools or use the tools you have differently.
>>
>> I assume it's not so much the >5GiB of disk space that's the issue and that 
>> you've maxxed out the CPU, graphics, and disk I/O rate as much as is 
>> practical so mostly it's a matter of how long it takes maps etc. to paint 
>> onscreen. It may help you to move the heavy-lift onto PostgreSQL/PostGIS 
>> where you can make use of spatial indexing. Or, you can craft your 
>> operations the way you want them in QGIS but do the actual work with e.g. 
>> GDAL calls in Python. I spoke with someone a couple weeks ago whose 
>> particular GIS process worked better in GRASS than in QGIS, so that's 
>> something you might look into as well.
>>
>> On 7/28/22 7:52 AM, krishna Ayyala via Qgis-user wrote:
>>
>> dbf file itself is 5.1GB. Rest all other files are less than 500MB. It is 
>> the number of records which is huge. It has about 117,2100 points.
>>
>> On Thu, Jul 28, 2022 at 12:02 AM Bernd Vogelgesang via Qgis-user 
>>  wrote:
>>>
>>> how big is the dbf file of that shape? Maybe you can also drop some
>>> attributes.
>>>
>>> Am 28.07.22 um 03:46 schrieb krishna Ayyala via Qgis-user:
>>> > Hello,
>>> > I have a shapefile of 5GB in size. Is it possible to convert this
>>> > shapefile to a smaller size file? It can be any format, not
>>> > necessarily a shapefile. But, preferably a vector format. I tried to
>>> > convert it into tiles, but that didn't work as it was losing the
>>> > resolution. I am looking to convert this 5GB size file to about 500MB.
>>> >
>>> > Regards.
>>> >
>>> > ___
>>> > Qgis-user mailing list
>>> > Qgis-user@lists.osgeo.org
>>> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>> ___
>>> Qgis-user mailing list
>>> Qgis-user@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>>
>> ___
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>>
>> ___
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: 

Re: [Qgis-user] [QGIS-Developer] A good task for someone wanting to get involved -- update CPT ramps

2022-07-19 Thread Nyall Dawson via Qgis-user
On Wed, 20 Jul 2022 at 09:50,  wrote:
>
> Here is a pull request for the requested changes:
> https://github.com/qgis/QGIS/pull/49423

Wow -- that was fast!! :D

Nyall

>
> --
> James
>
> -Original Message-
> From: QGIS-Developer  On Behalf Of
> Nyall Dawson via QGIS-Developer
> Sent: Tuesday, July 19, 2022 4:36 PM
> To: qgis-developer ; qgis-user
> 
> Subject: [QGIS-Developer] A good task for someone wanting to get involved --
> update CPT ramps
>
> Hi all,
>
> Here's an idea for a good task for someone wanting to get involved in QGIS
> contributions which doesn't require any c++/python.
>
> Currently we package a subset of the CPT ramps archive in QGIS, which you
> can see here
> https://github.com/qgis/QGIS/tree/master/resources/cpt-city-qgis-min
>
> It's missing a lot of the ramps present in the current version of the CPT
> archive from http://soliton.vm.bytemark.co.uk/pub/cpt-city/ . Some of these
> are because the licenses won't permit bundling with QGIS (e.g. the ESRI
> sets), but others are just missing because we haven't updated our subset in
> a loong time. (E.g. compare the subset present in QGIS
> https://github.com/qgis/QGIS/tree/master/resources/cpt-city-qgis-min/gmt
> from the GMT set vs
> http://soliton.vm.bytemark.co.uk/pub/cpt-city/gmt/index.html )
>
> It would be great to update our subset and re-sync it with the upstream
> collection. We're missing a lot of nice ramps we could be bundling by
> default :)
>
> I'm happy to mentor this task if someone wants to give it a shot...
>
> Nyall
> ___
> QGIS-Developer mailing list
> qgis-develo...@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


[Qgis-user] A good task for someone wanting to get involved -- update CPT ramps

2022-07-19 Thread Nyall Dawson via Qgis-user
Hi all,

Here's an idea for a good task for someone wanting to get involved in
QGIS contributions which doesn't require any c++/python.

Currently we package a subset of the CPT ramps archive in QGIS, which
you can see here
https://github.com/qgis/QGIS/tree/master/resources/cpt-city-qgis-min

It's missing a lot of the ramps present in the current version of the
CPT archive from http://soliton.vm.bytemark.co.uk/pub/cpt-city/ . Some
of these are because the licenses won't permit bundling with QGIS
(e.g. the ESRI sets), but others are just missing because we haven't
updated our subset in a loong time. (E.g. compare the subset
present in QGIS
https://github.com/qgis/QGIS/tree/master/resources/cpt-city-qgis-min/gmt
from the GMT set vs
http://soliton.vm.bytemark.co.uk/pub/cpt-city/gmt/index.html )

It would be great to update our subset and re-sync it with the
upstream collection. We're missing a lot of nice ramps we could be
bundling by default :)

I'm happy to mentor this task if someone wants to give it a shot...

Nyall
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Qgis 3.22.8 Error messages displayed in the GUI

2022-07-11 Thread Nyall Dawson via Qgis-user
On Mon, 11 Jul 2022 at 21:40, Piet via Qgis-user
 wrote:
>
> Dear List,
>
> I used a selfcompiled Qgis, build with 'Debug-Option' set in ccmake.
>
> Now there's a small red window in the main window which displayed 
> errors/warning.
>
> In my case "Qt: QXcbConnection: XCB error: 3 (BadWindow), sequence: 65154, 
> resource id: 11286601, major code: 40 (TranslateCoords), minor code: 0",
>
> which seems to be a known QT-Bug.
>
> Can I turn of this error window?

This particular one is now filtered out for 3.26+, as it's not
reflective of a bug in QGIS.

The others still remain, as they likely ARE indicative of something
which needs fixing in QGIS. If you encounter them, you should open
tickets for each so that the underlying cause can be identified.

Nyall

>
> Because it's upset me a bit and I can see the warnings in a console as well.
>
> Thank you for any hint!
>
> Kind regards
>
> Piet
>
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


[Qgis-user] QEP: Layout Legends - Rework handling of initial layer set and synchronization

2022-05-29 Thread Nyall Dawson via Qgis-user
Hi all,

Please see https://github.com/qgis/QGIS-Enhancement-Proposals/issues/253
for a newly submitted QGIS enhancement proposal regarding the initial
content and layer synchronization of legends in print layouts.

Comments/suggestions/feedback is welcome (and encouraged!) on the page
linked above!

Nyall
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


[Qgis-user] QGIS 3.26 Elevation profile/cross section tool deep dive - live today

2022-05-12 Thread Nyall Dawson via Qgis-user
Hi all,

Later today (May 13), at 19:30 AEST (GMT+10) / 11:30 CEST I'll be
doing an in-depth live exploration of all the new elevation
profile/cross section functionality coming in QGIS 3.26. Tim Sutton
will be joining me, so it's guaranteed to be an educational &
entertaining session!

You can tune in live here https://youtu.be/AknJjNPystU (a recording
will also be made available after the event).

Regards,
Nyall
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] QGIS 3.24 Ubuntu

2022-04-21 Thread Nyall Dawson via Qgis-user
On Fri, 22 Apr 2022 at 06:03, Angeles Raphaël Saul via Qgis-user
 wrote:
>
> Dear QGIS community,
>
> I have two questions : Do you know how to install easily pcraster on ubuntu ? 
> How can I uninstall the latest version of QGIS 3.24 and get an older version 
> of QGIS on ubuntu ?
>
>
> Situation : I am a recent ubuntu user and I need to install pcraster for 
> advanced watershed calculations. Apparently it is possible to install it 
> using anaconda-navigator, so I first needed to install anaconda using this 
> tutorial : 
> https://gisunchained.wordpress.com/2019/05/29/using-qgis-from-conda/. But 
> once QGIS 3.18.3 installed and opened, any plugin utilization do not work at 
> all. For example, applying strahler order tool from SAGA on a DEM does not 
> work. Every time, the python error is :
>
>
> WARNINGTraceback (most recent call last):
>
> File 
> "/home/raphael/anaconda3/envs/demonstration/share/qgis/python/plugins/processing/gui/AlgorithmDialog.py",
>  line 194, in runAlgorithm
>
> self.cancelButton().setEnabled(self.algorithm().flags() & 
> QgsProcessingAlgorithm.FlagCanCancel)
>
> TypeError: setEnabled(self, bool): argument 1 has unexpected type 'Flags'

This is (unfortunately) expected -- Python 3.9 broke some API
compatibility, so the older QGIS 3.18 release ISN'T compatible with
the newer Python version. As you've concluded, the solution is
updating to a newer, supported QGIS version.

Nyall


>
>
> Thus I tried to install QGIS 3.24 via this link 
> https://www.qgis.org/en/site/forusers/alldownloads.html#debian-ubuntu to see 
> if the problem can be resolved with a more recent version. The problem is 
> that this tutorial is not for a conda environment, so now I want to uninstall 
> 3.24 to go to an older and more stable version and I don't know how to do it. 
> If I install and uninstall QGIS, the version 3.24 still appears. Moreover, I 
> still don't have pcraster installed and operational which I need the most.
>
> Thank you in advance for your precious answer and have a good night!
>
> Raphaël
>
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Help with scales in print layouts for geographic CRS

2022-04-06 Thread Nyall Dawson via Qgis-user
On Thu, 7 Apr 2022 at 10:26, Greg Troxel  wrote:
>
>
> Nyall Dawson  writes:
>
> > In all cases (projected OR geographic) the scalebar logic is:
> >
> > 1. Create a horizontal line across the width of the layout map
> > 2. Calculate the length of that line using great circle/ellipsoidal
> > calculations, based on the project's ellipsoid settings.
> > 3. Compare the length of the ellipsoidal line vs the map width to
> > calculate the corresponding scale
>
> That is a very straightforward approach with easy-to-understand
> semantics.
>
> > So qgis scalebar calculations are ALWAYS based on great
> > circle/ellipsoidal lengths*.
>
> And more precisely, a true geodesic between two points varying in x and
> with constant y in the layout CRS.  For north-up (at least ish)
> projections, that means a line of constant latitude.
>
> For a lat/lon CRS in the layout, at mid latitudes, it's going to mean
> that the scale in the y axis is smaller by about 110km/70km; a square in
> lat/lon is taller than it is wide (and plus it's not a square, but
> that's less obvious).  Equivalently, a square on the ground has a larger
> difference in longitude than it does in latitude.  Or maybe I have that
> backward, but using lat/lon in a layout does not preserve shapes.
>
> This is what I was trying to get at: a single concept of scale is really
> only valid for a projection that has the same scale in x and y.  Which I
> think is true iff the projection is conformal.  And it's only truly
> valid if the scale doesn't change over the layout, which is probably
> ~never exactly true, but many projections aim to have it remain close
> enough to be treated as constant (e.g. UTM).
>
> Which is a long way of getting around to "if you are using lat/lon as
> the axes in your layout, either you are doing something odd on purpose
> or you probably should rethink your approach."  If you really do mean
> it, I would find the explanation of why interesting.

All correct, indeed!

I've been thinking about introducing a new warning when exporting
layouts, which would look something like this:

1. For each scale bar, look at the referenced map
2. Measure the scale using multiple lines, each across the
top/middle/bottom horizontally and left/center/right vertically
3. Compare these scale values, and if any differ by more than XXX %
then show a warning to the user. Something like "The scale for map 1
varies from 1: to 1:y across different parts of the map.
Consider using an alternative form of representing the map scale (such
as a grid overlay), as the scale bar may be misleading for this map."

What do you think?

Nyall


>
> > * Unless the project itself is set to not use ellipsoidal calculations
> > and only use planar calculations, in the project properties dialog
>
> Presumably those calculations are in the project CRS's xy space, and
> would typically (when used sensibly) be grid distance in UTM, some State
> Plane Coordinate System, or similar.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Help with scales in print layouts for geographic CRS

2022-04-06 Thread Nyall Dawson via Qgis-user
On Wed, 6 Apr 2022 at 09:34, Greg Troxel via Qgis-user
 wrote:
>
> Jorge Gustavo Rocha via Qgis-user  writes:
>
> > I need you help to understand how scale works with geographic
> > coordinate systems.


In all cases (projected OR geographic) the scalebar logic is:

1. Create a horizontal line across the width of the layout map
2. Calculate the length of that line using great circle/ellipsoidal
calculations, based on the project's ellipsoid settings.
3. Compare the length of the ellipsoidal line vs the map width to
calculate the corresponding scale

So qgis scalebar calculations are ALWAYS based on great
circle/ellipsoidal lengths*.

Nyall

* Unless the project itself is set to not use ellipsoidal calculations
and only use planar calculations, in the project properties dialog
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user