A follow up as a fix has been found in sip 6.6 hg tip.
Please see
https://www.riverbankcomputing.com/pipermail/pyqt/2022-May/044641.html for
more info.
Donovan
On Wed., May 4, 2022, 20:28 Sebastiaan Couwenberg via QGIS-Developer, <
qgis-developer@lists.osgeo.org> wrote:
> On 5/4/22 23:52, Sau
On Tue, Sep 29, 2020 at 10:41:17AM -0300, José de Paula Rodrigues via
QGIS-Developer wrote:
> Hi all,
>
> I've tried running some test cases locally against PostgreSQL 12 and
> PostGIS 3.0.0 ~ 3.0.2. These tests are consistently failing here,
> whereas they run successfully on Travis. Attached ar
Hi Andreas
I have seen this and looked into that some time ago. If I remember
correctly, sometimes the indexing algorithm when constructing the octree
decides to merge the more detailed "bucket" of points into the parent
"bucket" (that has bigger spacing), resulting in this kind of artifacts
where
Hi,
I followed the following instructions and managed to build on Windows:
https://gist.github.com/troopa81/b43f96c20fdde2778ecdeaf8cf87684e
But you can also try with this if you are comfortable with github
actions yaml :
https://github.com/jef-n/OSGeo4W/blob/workflows/.github/workflows/qgis-de
Hi,
QGIS builds fine again - thanks to your hints and help from ldd /
valgrind.
Turned out to be a self-compile pdal (I know, more self-compiled stuff)
that linked to an old geotiff which linked to an old proj. Replacing the
old geotiff with as self-compile geotiff library fixed the issue.
Yes. I guess I have to dig with ldd through all the libraries and see
which one is linking to the old proj version. There is more
self-compiled stuff on my system.
Anyway - I will find the culprit with ldd and valgrind.
Thanks for your help!
Andreas
On 2021-09-03 16:51, Even Rouault wrote:
The Valgrind output is actually interesting:
see
==49441== by 0x150193E6: ??? (in
/usr/lib/x86_64-linux-gnu/libproj.so.15.3.1)
[...]
==49441== by 0x9C3FDC6: ??? (in /usr/local/lib/libproj.so.22.1.0)
So you're linking to 2 PROJ versions. That would have been my first bet,
but you didn
Hi Even,
Thank you for your reply.
I checked with the ldd about gdal/geos/proj - and they all seem to link
to the self-compiled versions in /usr/local/lib
gdal:
xxx@t480:~/dev/QGIS/build$ ldd /usr/local/lib/libgdal.so.29
linux-vdso.so.1 (0x7fffb930d000)
libcrypto.so.1.1 =>
Thanks Regis and Andeas ☺
The big sed on the filesystem could work on .qgs files, but what about .qgz
files ? ☺
Regards
Jacky Volpes
Développeur python
HR-Team pour la Société du Canal de Provence
Direction des Systèmes d’Information
Tél. 04 42 66 70 34
Le Tholonet - CS 70064 - 13182 Aix-en-Pr
Hi,
In our efforts to improve cartographic quality, I'd also like to
discuss, if we could somehow improve the quality of the line-pattern
fills, and/or the antialiasing quality of the qt renderer.
A very small change in angle can change the quality of a line-pattern
fill in QGIS pretty or ver
10 matches
Mail list logo
