Things not being in Debian repos should be reported to Debian.
Greg, in that instance, no. QGIS maintains its own .deb repositories to
provide new QGIS versions on older Debian/Ubuntu releases:
https://qgis.org/resources/installation-guide/#debianubuntu
--
http://www.spatialys.com
My software
For operational uses, I would say the latter is the better. For
regression test purposes, some tests might perhaps need
tweaking/skipping depending on the GDAL version. CI uses GDAL 3.4.1 for
QT5 testing and 3.7.3 for QT6 testing.
> Background/motivation for asking: I have tried compiling dif
I've reported the issue to the OGC GeoPackage specification issue
tracker: https://github.com/opengeospatial/geopackage/issues/683
Le 22/07/2024 à 15:57, Even Rouault via QGIS-Developer a écrit :
Benjamin,
Explicit casts like "(CAST(SUM(D.QAI) as INTEGER) as n_qai" did not
s
Benjamin,
Explicit casts like "(CAST(SUM(D.QAI) as INTEGER) as n_qai" did not
solve my problem.
Yeah, I recently came across a similar issue, and the finding is that it
is related to the SQLite version. Such casts apparently work since
SQLite 3.42. So if your QGIS build uses an older SQLit
à 08:56, Even Rouault via QGIS-Developer a écrit :
Hi,
Both formats are compliant with the WKT specifications.
Are they? I may have missed something in the Simple Features spec, but
looking at https://portal.ogc.org/files/?artifact_id=25355 , I can't
see where it would allo
Hi,
Both formats are compliant with the WKT specifications.
Are they? I may have missed something in the Simple Features spec, but
looking at https://portal.ogc.org/files/?artifact_id=25355 , I can't see
where it would allow the form {geometryTypeName}Z without a space
between {geometryType
Hi,
The procedure at
https://github.com/qgis/QGIS/blob/master/INSTALL.md#39-building-different-branches
is more for developers to create feature branches and submit pull requests
To just built the release-3_36 branch,
Assuming that "origin" is your remote pointing to
https://github.com/qgis
details about what is failing?
It took some time to find the VERBOSE=1 option, but even with verbose
output I don't understand what is going on. Is it
On Thu, Feb 29, 2024 at 8:52 AM Matthias Kuhn wrote:
On Wed, Feb 28, 2024 at 7:45 PM Even Rouault via QGIS-Developer
Thomas,
Le 28/02/2024 à 19:33, Thomas Larsen Wessel via QGIS-Developer a écrit :
I have successfully built QGIS and GDAL (3.7.2) separately. Now I want
to build QGIS against this GDAL. This is what I tried:
git clone g...@github.com:qgis/QGIS.git
cd QGIS
mkdir build
cd build
GDAL_DIR=/home/vel
I'm not sure if that explains the family of bugs seen, but as those
settings are a *integer* index in the list returned by
QgsVectorFileWriter::supportedFormatExtensions() or
QgsRasterFileWriter::supportedFormatExtensions() , they depend both on
the QGIS list of known formats which may evolve o
Le 10/02/2024 à 00:07, Nyall Dawson via QGIS-Developer a écrit :
Hey list,
What does everyone think about us backporting the python/PyQt6/
directory from master to the 3.34 branch? I'm thinking we could do
this as "orphan"/unused files, with the intention that it would make
backporting to th
Le 09/02/2024 à 00:45, John Lindsay via QGIS-Developer a écrit :
Hello,
I believe that I've solved my earlier issue with my QGIS plugin, which
previously relied on a pip package. In order to avoid this dependency,
I decided to include the Whitebox Workflows wheel in with my plugin.
Unfortunat
I’m not sure if I would want this marketplace being hosted by QGIS
itself and being access through the current Plugin Manager. I prefer
the idea of QGIS being clearly free… but at the same time maybe it’s
not that bad if there is a mix of free and paid plugin at the same
place, as long as it’
Hi Nyall,
It would seem tricky that qgis.org both offers/promotes a gratis & FOSS
"market place" (the current official plugin repository), and a paid one.
That could be conceived, but if qgis.org would promote in some way the
paid market place, this would create some expectation on the quali
ST_GeomFromText('POINT(-179.5 0)', 4326, 'axis-order=long-lat'));
Le 28/01/2024 à 19:04, Even Rouault via QGIS-Developer a écrit :
Richard,
what I don't understand is how you manage to create with ogr2ogr a
table without explicit SRS with features whose coordi
But, my point: why can QGIS apparently show attributes, while not
showing a geom.. Apparently the features were fully retrieved.
When displaying the attribute table, QGIS doesn't apply a spatial
filter. Whereas when displaying features on the canvas, it does. And as
I found out, something's
onsequence, it seems safer to disable spatial filtering on layers with
geographic coordinates with MySQL...
That's just what I've done in https://github.com/OSGeo/gdal/pull/9152 .
Hopefully that will fix those issues with geometries not appearing.
Obviously performance will not be op
Richard,
There's something weird with your installation. According to
https://salsa.debian.org/qt-kde-team/extras/qwt/-/blob/debian/master/src/qwt_plot_layout.h?ref_type=heads#L84,
this should be
|constQRectF& plotRect, Options options = Options());|
According to
https://packages.debian.org
Le 23/01/2024 à 20:43, Richard Duivenvoorde a écrit :
Ah, oo :-)
I can reproduce now in the docker!
After seeing
src/core/providers/ogr/qgsogrprovider.cpp:3236 : (crs) [0ms] no
spatial reference found
in the debug info of that other db, I thought to try to load the data
WITHOUT telling it
I'll try to debug the current db, and I've asked the people to create
a test db (which hopefully then has the same issue :-) )
I'm not familiar with MySQL but I guess there must be some dump &
restore commands that could be used to exactly replicate a setup where
the bug triggers?
--
h
Richard,
I've failed to reproduce. Here's my testing procedure:
docker run --name gdal-mysql1 -e MYSQL_ROOT_PASSWORD=passwd -e
"MYSQL_ROOT_HOST=%" -p 33060:3306 -d mysql:8.0.34 mysqld
--default-authentication-plugin=mysql_native_password
docker exec gdal-mysql1 sh -c "echo 'CREATE DATABASE tes
Rhea,
I've just unsubscribed you (from the admin interface)
Even
Le 16/01/2024 à 18:17, Rhea via QGIS-Developer a écrit :
Hello,
I’ve been trying to unsubscribe its been months now and it’s not working, i
keep on receiving emails as if im still part of the list.
I followed this link : https
Rhea,
*
- Proposition would be a feature that allows users to limit Python
console functionality based on their needs.
If you have in mind to limit the set of functionality available in the
Python console, that's not technically doable, at least with the CPython
interpreter. All you
/blob/master/.docker/qgis3-qt5-build-deps.dockerfile
- Fedora 38 for QG6 builds:
https://github.com/qgis/QGIS/blob/master/.docker/qgis3-qt6-build-deps.dockerfile
On Mon, Jun 19, 2023 at 2:34 PM Even Rouault
wrote:
Building recent QGIS versions on 20.04 is going to be quite a lot
of
Building recent QGIS versions on 20.04 is going to be quite a lot of
pain since you'll need indeed to have a qt 5.15 build, and all the other
auxiliary QT based dependencies build against it.
I'd suggest you update to 22.04 at least. Or if you don't want to do
development but can live with rel
Le 27/03/2023 à 10:06, Alessandro Pasotti via QGIS-Developer a écrit :
Hi,
QGIS is using the GDAL/OGR library to read the shapefiles.
which uses shapelib
On Mon, Mar 27, 2023 at 9:51 AM 余 绍健 via QGIS-Developer
wrote:
Dear All,
Sorry to interrupt, I'm newer to QGIS, whe I use QIGS, I fin
Hi,
I guess one point of improvement is to really implement a policy that
was discussed in the past, that is that after let's say half the total
period of support of the LTR only "critical" bugfixes are allowed into
it, with critical being for example defined as:
- fix a regression introduce
Dereferencing a null dataProvider() seems to me to be a recurrent class
of (crashing) bugs (I've for sure fixed such issues several times)
My idea is probably a bit silly, but what about
https://gist.github.com/rouault/ed533d30738bda806ebeaa47f0877e2c ?
Basically:
- deprecate dataProvider()
Hi,
just to avoid other people losing a couple hours like me... If you
update to latest master on Debian/Ubuntu, and after rebuild, you get a
cryptic error like the following when importing qgis_gui:
# PYTHONPATH=output/python QGIS_PREFIX_PATH=output python3 -c "from
qgis._gui import *"
Tra
> Very cool project, Even! (Why not "Cloud-Optimized" though? 😉 )
The term is heavily loaded and quite vague. SOZip doesn't make something
cloud unfriendly magically cloud friendly. If you need to seek at 100
different locations in a (uncompressed) file, you'll need to also seek
at 100 locatio
Le 09/01/2023 à 16:54, Richard Duivenvoorde a écrit :
Hi Even,
Cool!
Out of curiosity: I thought sqlite/geopackage was already relatively
'skinny' packed? Am I wrong?
Well, SQLite does some packing of integer or floating-point values, but
nothing on strings or blobs (which means no compressi
Sujet : [gdal-dev] Announcing SOZip: Seek-Optimized profile for the
.zip format
Date : Mon, 9 Jan 2023 15:19:07 +0100
De :Even Rouault
Pour : gdal-...@lists.osgeo.org
Hi,
It is my pleasure to announce (
https://github.com/sozip/sozip-spec/blob/master/blog/01-announcement.md
mized .deb
packaging.
The goal is to structure and promote knowledge on this topic to
attract packager in addition to developers.
And then we would also create packaging process documentation for
Windows Store.
Regards,
Julien M
Le 23/11/2022 à 10:41, Even Rouault via QGIS-Developer a écrit
Hi Harrissou,
"q" should do it, as the diff is displayed with the "less" utility, and
it's the shortcut to exit from it
Even
Le 16/12/2022 à 06:18, Delaz J via QGIS-Developer a écrit :
Hi,
Whenever I run prepare_commit.sh and there are changes, I fail to find
how to get back to the command
Would it be too crazy to shrink down some offending name to prevent
error when switching to more recent branches? I can submit a PR if needed.
Seems like a good idea. You'll likely have to change references to that
file in the test suite.
--
http://www.spatialys.com
My software is free, bu
- There is a requirement for every library in the package to be "UWP
compatible".
At that time, libpq (postgresql) didn't have that, so I stopped.
It's hard to say how many other packages will also need special
attention. [1]
Interesting. I know that people have contributed in the past fix
Le 17/10/2022 à 12:36, Raymond Nijssen a écrit :
Thank you Even. And that will always be available in QGIS? Without any
extra (gdal) installations?
yes, I think so. This is needed by the GDAL processing tools, which
AFAIK are availalable out-of-the box in the standalone Windows installer
-
You can just use
from osgeo import ogr
from osgeo import gdal
from osgeo import osr
That will work with any GDAL version of the last 15 years or so.
Le 17/10/2022 à 10:52, Raymond Nijssen via QGIS-Developer a écrit :
Dear developers,
What is the best way to import ogr, gdal and osr in my pyqg
Le 24/06/2022 à 02:29, Alexandre Neto via QGIS-Developer a écrit :
I am testing the GDAL tools on QGIS 3.22.8 on Windows. When running
gdal2xyz with a single band raster I am getting the following error:
C:\Users\testing_user>gdal2xyz.bat -b 1
C:/Users/testing_user/Desktop/gdal_commands_test/
Use sysprof or just run under a debugger and interrupt regularly should
help you spot in which method(s) most time is spent
Le 20/06/2022 à 18:48, David Marteau via QGIS-Developer a écrit :
I used the following test:
readflags = Qgis.ProjectReadFlags() readflags |=
Qgis.ProjectReadFlag.Trust
9441== by 0x4011B89: call_init.part.0 (dl-init.c:72)
==49441== by 0x4011C90: call_init (dl-init.c:30)
==49441== by 0x4011C90: _dl_init (dl-init.c:119)
==49441== by 0x4001139: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so)
==49441==
==49441==
==49441== HEAP SUMMARY:
==49441== in use at
Alessandro,
the truth (and sometimes issues) is in projinfo:
$ projinfo -s EPSG:4258 -t EPSG:4326
Candidate operations found: 1
-
Operation No. 1:
EPSG:1149, ETRS89 to WGS 84 (1), 1.0 m, Europe - onshore and offshore:
Albania; Andorra; Austria; Belgium; Bosn
I meant "Pedro", sorry for the typo.
Le 27/11/2021 à 20:38, Even Rouault a écrit :
Petro,
I've queued https://github.com/OSGeo/gdal/pull/4908 which will "fix"
that particular case (more precisely anything based on ETRS89). I'm
not super satisfied with this, an
Petro,
I've queued https://github.com/OSGeo/gdal/pull/4908 which will "fix"
that particular case (more precisely anything based on ETRS89). I'm not
super satisfied with this, and I believe there's no miracle solution for
all potential use cases. What GDAL returns in both 2.4.0 and 3.4.0 is
ac
Hi,
Probably a topic that can raise passions and on which I'm moderately
legitimate to speak, but shouldn't we seriously consider leveraging the
Conda / Conda-Forge (https://conda-forge.org/) ecosystem for QGIS
packaging, especially on the Windows and Mac platforms ? QGIS depends on
a lot of
Andreas
Several things to check:
- Is your GDAL build a clean one ? That is is it from a fresh build
directory, or are you rebuilding in a directory where a previous build
was done. If the later, make sure to "make clean" before rebuilding
- Is your GDAL build using your custom GEOS one ? Ot
SQLite, which is the underneath database engine for GeoPackage, doesn't
support ILIKE. The SQLite LIKE operator is actually case insensitive for
ASCII characters. See paragraph 5 "The LIKE, GLOB, REGEXP, and MATCH
operators" of https://www.sqlite.org/lang_expr.html
Le 28/07/2021 à 21:43, C Ham
Le 15/07/2021 à 22:30, Nyall Dawson a écrit :
On Fri, 16 Jul 2021, 4:52 am Andrea Giudiceandrea,
mailto:andreaer...@libero.it>> wrote:
> Isn't this limitation ultimately that GDAL isn't reading the
encoding
> correctly? (Or perhaps it's a limitation in the underlying freexl
Le 15/07/2021 à 21:51, Andrea Giudiceandrea a écrit :
Il 15/07/2021 20:51, Andrea Giudiceandrea ha scritto:
Instead, QGIS imports correctly XLSX files as UTF-8 encoded, while
XLS files are wrongly imported as "system" encoded, even selecting
UTF-8 [3] encoding in the Data Source Manager vector
By design, only speaking about behaviour of the GDAL utilities themselves:
- gdal_translate -a_nodata just modifies the nodata metadata, and
doesn't alter pixel values
- gdalwarp [-srcnodata xxx] -dstnodata yyy modifies the nodata metadata
and pixel values
Le 09/07/2021 à 01:02, Alexandre N
Hi Alessandro,
Isn't it just the bump of version numbers after the release and stale
.so.3.19.* files in output/lib ? (but that caused for me crashes for the
qgis application)
Even
Le 23/06/2021 à 19:36, Alessandro Pasotti a écrit :
Hi,
I really don't know what I have changed but since yes
Jeferson,
yes, you can sell plugins, but you'll have to distribute the source code
of it, or make a written offer to have access to it, to your customers
under the GPL v2+ license of QGIS (which mean they could also
potentially redistribute the source code freely, in all meaning of the
word,
| Also I wonder if it would be possible to work with the GPKG developers
to provide better timezone support there as well.
This is more about finding how to convince the GeoPackage spec
maintainers that it is worth adding it than a technical one. I guess
they wouldn't want to break compatibili
but the question I have is whether a vector layer were saved to
something like a GPKG would the timezone even be preserved?
Short answer: not by default
Longer answer:
- see https://github.com/opengeospatial/geopackage/issues/530
- and https://github.com/OSGeo/gdal/issues/3423#issuecomment
Andreas,
if you've built yourself PROJ on a system that has older proj versions, I'd
suppose that one of the QGIS dependency links against that older proj (might
be spatialite for example), and at runtime you get a clash between it and
7.2.x
Check the output of:
ldd /home/an/dev/QGIS/build/out
On mardi 19 janvier 2021 09:55:46 CET Jorge Gustavo Rocha wrote:
> Hi,
>
> Just an additional comment. The GDALAutoCreateWarpedVRTEx is there, as
> far as I can see.
>
> nm -g libqgis_core.so.3.16.3 | grep GDALAutoCreateWarpedVRTEx
> U GDALAutoCreateWarpedVRTEx
>
> But if the sy
On jeudi 7 janvier 2021 18:18:03 CET Vincent Picavet (ml) wrote:
> Hi,
>
> On 07/01/2021 10:43, Nyall Dawson wrote:
> > On Thu, 7 Jan 2021 at 19:13, Topi Tjukanov wrote:
> [..]
>
> >> So if this really is a requirement, should this be enforced somehow and
> >> checked when plugins are accepted t
> QGIS might not be affected by this since we don't have more than 5
> concurrent builds.
That's not my understanding. The 1, 2 or 5 concurrent builds plans are paying
plans if you look at https://travis-ci.com/organizations/qgis/plan .
The free plan of QGIS is subject to the 10,000 credits syste
Hi,
I was pointed to
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
If my understanding is correct (which I'm not completely sure given all the
subtelties), QGIS builds will now have a initial credit of 1000 minutes of
build time (so only 17 hours), and then we'd have to beg for mo
Of potential interest. "Develop a logical model for GeoPackage so that future
implementations can be separated from the current requirement to use SQLite."
is intriguing
-- Forwarded Message --
Subject: [TC-Announce] OGC Geopackage Standards Working Group updates its
Charter;
On mardi 20 octobre 2020 16:12:56 CEST Pedro Venâncio wrote:
> Hi Joaquim Luís,
>
> This is an IPMA NetCDF, it was working before the update.
>
> And I think it is in fact a HDF5 library version problem:
> > gdalinfo AROME_OPER_001_FC_SP_PT2_025_RH_2-HTGL_2020102000.nc
>
> Warning 1: Recode from
> Wow, great! So now Tim's screencast has directgly lead to a bunch of
> improvements from GDAL up :D
For clarity I didn't turn on automatically PRAGMA synchronous = OFF for
existing databases.
For current GDAL version, this can be done by setting the
OGR_SQLITE_SYNCHRONOUS configuration option
On dimanche 18 octobre 2020 15:35:11 CEST Nyall Dawson wrote:
> On Sat, 17 Oct 2020 at 20:02, Even Rouault
wrote:
> > Hi Nyall,
> >
> > > But I can't explain this. In both cases the resultant gpkg has a
> > > spatial index. Does anyone know why one of th
Hi Nyall,
> But I can't explain this. In both cases the resultant gpkg has a
> spatial index. Does anyone know why one of the methods is so much
> slower than the other? (And ultimately, can we fix
> QgsVectorLayerExporter so it uses the same fast approach!)
Candidate fix and explanations at:
htt
On jeudi 15 octobre 2020 17:48:30 CEST Matthias Kuhn wrote:
> If there is a managed database where there has been a conscious decision to
> have an integer id column (postgres case) and workflows are built around
> this: filling the id on insert, building foreign keys against it etc, that
> works j
> The way I see it, fid can be seen very similarly to rowid or shapefile
> fids. A semi-stable unique identifier. Just - and that's the big difference
> - those are not part of the data hence the system can transparently deal
> with duplicates and can fill holes once in a while (shp -> repack, sqli
> I think this is a great idea -- we could retain any compliant fid
> values without change, but as soon as we hit a duplicate fid or
> non-integer fid value then we discard it and generate a new one.
>
> What do you think Even?
Are you talking about the addFeatures() method of the provider ?
Th
> Well -- here's an example file:
> https://github.com/qgis/QGIS/blob/master/python/plugins/processing/tests/tes
> tdata/dissolve_polys.gml
>
> Not sure how that file was created in the first place, but I've seen
> many like it!
Ah ok, this is a GML2 file, which reports indeed a 'fid' field (comi
Hi Nyall,
> - The type constraint on the fid column makes it really hard to
> translate datasets with an existing, non-numeric "fid" column into
> geopackage. Eg. GML files often have a textual fid string, and
> attempting to convert these to gpkg results in a string of errors
> about string value
Andreas,
> Can QGIS 2.18 be built against GDAL 3.x?
Hum, I guess it would build, although definitely not a vetted combination. I
wouldn't expect
datum transformations to work very well, since QGIS would be dependent on
towgs84
coming in PROJ.4 strings, and GDAL 3 / PROJ >= 6 will not populate
d actually.
When things go bad you can add a suppression
// cppcheck-suppress {name_of_cppcheck_diagnostic}
Or we can disable a category in scripts/cppcheck.sh if it is too unreliable
Even
>
>
> On Tue, Sep 29, 2020 at 12:11 PM Even Rouault
>
> wrote:
> > On mardi 29 s
On mardi 29 septembre 2020 11:55:40 CEST Alessandro Pasotti wrote:
> Looks like cppcheck is not smart enough...
Yeah, it hardly understands C++ (it doesn't need to be able to fully compile a
file to analyze it,
if I remember correctly)
>
> const double factor { std::pow( 10, - mPrecisionSpinBo
Hi,
I want to report about the outcome of
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/172
"Use of FileGeodatabase spatial index in OpenFileGDB driver"
This work has been successfully completed into GDAL master (for upcoming GDAL
3.2) per
https://github.com/OSGeo/gdal/pull/2771 , a
> E.g. GDAL has a flag if a
> datetime is UTC or "not utc/unknown", and that's it.
Small precision: it also has support for explicit timezones
(like UTC+0200)
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
QGIS-Developer
On mardi 28 juillet 2020 17:06:05 CEST Andreas Neumann wrote:
> Thanks for sharing this discussion.
>
> So when you load an old project in QGIS master, the average method would
> be replaced with bilinear now?
>
> Is "bilinear" the closest method to the previous "average"?
This is just a label c
Hi Sandro,
I hope this emails finds you, and you are doing well. We had a few exchanges in
private over
past months about a next Spatialite release, but I'm still unclear on when a
next release will
materialize, hence this public call, with the Spatialite list, and GDAL and
QGIS communities
On mardi 30 juin 2020 14:20:50 CEST Rizky Maulana Nugraha wrote:
> Hi Olivier,
>
> Maybe this helps. You can run build in debug mode in travis. I usually just
> make a private repo with a minimum script to run that said tests. Then
you
> can ssh into the build.
Slightly more convenient is to use
Julien,
> I was looking to create an empty GPKG layer and try the solution Even
> provide, but it creates an invalid file.
>
> fields=QgsFields()
> fields.append(QgsField("note", QVariant.Double))
> QgsVectorFileWriter.create("/tmp/test.gpkg", fields,
> QgsWkbTypes.MultiLineString, QgsProject.ins
On mercredi 24 juin 2020 11:53:37 CEST Peter Petrik wrote:
> Hi,
>
> As building on iOS already works (
> https://github.com/lutraconsulting/input-sdk/tree/master/ios), I imagine it
> would be possible to run another architecture build for MacOS with a
> similar approach. It is in Apple's interes
On mardi 23 juin 2020 15:34:58 CEST Raymond Nijssen wrote:
> My python plugin should create a table without geometry in a gpkg to
> store some additional (meta) info about the layers. I could use python
> bindings for sqlite of course, but the plugin users might not have that
> installed.
>
> What
Matthias,
thanks for the analysis. There are however a few unexpected results.
1) I'd expect gpkg pyramid_JPEG and COG_JPEG to have very similar sizes, even
COG_JPEG
being potentially slightly smaller.
And I'd also expect COG_JPEG to be slighly faster (but with less confidence
that my
stateme
> After some Q&A, it appeared that he had opened the shapefile
from a ZIP...
Not addressing your general concern, but upgrading to GDAL 3.1.0
will fix that particular point: update of .shp.zip is now supported.
(performance will probably not be rocketting if the .shp.zip is too
big)
Even
--
On vendredi 5 juin 2020 21:44:22 CEST Denis Rouzaud wrote:
> Hi all,
>
> After digging a bit more, it seems that the cache invalidation is not
> working on the WFS layer.
>
> If I call emitDataChanged on any of its layers dependencies, or call
> emitDataChanged on this layer or even call triggerR
> Yes, I already thought of that, too. Can the extend be derrived
from a
> gsb-file? Otherwise I have to estimate.
Command line with "gdalinfo Minden.gsb" and look at Corner
Coordinates
Or just open the gsb file in QGIS as a raster and look at the
properties.
Even
--
Spatialys - Geospatial p
On vendredi 5 juin 2020 11:13:09 CEST Thomas Schüttenberg wrote:
> Hi all!
>
> Because I better should not roll out QGIS with the afore mentioned premanent
> ballpark-warning in place, I investigatetd further and stumbled across an
> "allowFallback"-setting:
>
> By placing a default datum transfo
On mardi 2 juin 2020 15:58:38 CEST Olivier Dalang wrote:
> Hi !
>
> About WAL related issues :
>
> I just tried to reproduce the original issue that lead to using WAL on
> local files (https://github.com/qgis/QGIS/issues/23283) but could not
> reproduce it (recent master, Windows 10). Does the is
> No transform is available between EPSG:3763 - ETRS89 / Portugal TM06 and
> Unknown CRS: GEOGCRS["unknown",DATUM["unknown",ELLIPSOID["GRS 1….
> proj_create_operations: cannot build geodeticCRS 4326: SQLite error on
> SELECT name, ellipsoid_auth_name, ellipsoid_code, prime_meridian_auth_name,
> pri
Andreas,
> I am struggling with libspatialite. What libspatialite versions are you
> guys using? I am trying to compile libspatialite-4.3.0a, but it
> complains about not finding "proj_api.h" (although this file is
> available at /usr/local/include). I tried both with proj-6.3.2 and
> proj-7.0.1.
On samedi 9 mai 2020 08:54:06 CEST Matthias Kuhn wrote:
> Hi Richard,
>
> On 5/8/20 5:24 PM, Richard Duivenvoorde wrote:
> > About Tobias' flatgeobuf: instead of a shp/gpkg file alternative, would
> > this not be a very good candidate to store our intermediate processing
> > steps in (which was sh
> > *The requirement for a single geometry column per table
> >
> >I just don't see a good reason to forbid that
> >
> >Possible mitigation: a) alter the standard. b) ignore the standard
> >
> > and patch the ogr implementation.
>
> I don't think the Geopackage OGC SWG would be keen
> * The fid requirement
>
>I sometimes want my features to be identified by uuids or others.
> They also tend to accumulate if derived datasets are created (through
> processing etc). If I need some pseudo stable primary key there is a
> rowid builtin into sqlite, we don't need a second one.
>
Richard,
>
> Probably not important, but I get the following output when running my
> build:
>
> $ ninja install
> [0/1] Re-running CMake...
> -- QGIS version: 3.13.0 Master (31300)
> ...
> -- Found Proj: /usr/lib/x86_64-linux-gnu/libproj.so version 7 (7.0.0)
> ...
> -- Using PROJ 6 srs database
On jeudi 9 avril 2020 21:30:02 CEST Martin Dobias wrote:
> Hi Vincent
>
> On Thu, Apr 9, 2020, 18:32 Vincent Picavet (ml)
>
> wrote:
> > Hi all, PSC,
> >
> > Olaf Schmidt-Wishhöfer from KDE project has made a statement yesterday
> > about a
> > really concerning situation regarding the OpenSour
On vendredi 20 mars 2020 19:26:03 CET Jeremy Palmer wrote:
> > On Fri, 20. Mar 2020 at 08:12:35 +0100, Andreas Neumann wrote:
> > > Isn't that potentially a quite large amount of data? Most QGIS users
> >
> > that I
> >
> > > know mainly work in one country or region and only need one gridshift
>
> For example, is it possible to compromise QGIS Desktop via a
> opening/connecting to a compromised shapefile/Geopackage/web-service/CSV
> etc etc? I have no idea, but it'd definitely be a useful thing to
> investigate.
For file formats, part of the security/insecurity would fall on GDAL (and
un
Nadia,
Thanks for investigating QGIS server security. However, I would expect a
vulnerability report to go a bit beyond than just using a generic security
scanner that can have false positives, especially here as all components
involved are open source so it is possible to look at the code, instru
On lundi 27 janvier 2020 17:35:22 CET Paolo Cavallini wrote:
> Thanks Even. As I read it, this essentially means we are more or less
> forced to use the latest version, not the LTS (or to stick to an older
> one). This could mean more bugs.
QGIS sources aren't bound to a particular QT version. Cur
Hi,
Just read this:
https://www.phoronix.com/scan.php?page=news_item&px=Qt-Going-More-Commercial
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: ht
Regarding
> prohibit the use of QGIS to the fossil-fuels industry.
and
> ...may I suggest to add GLOBAL PEACE & WAR issues to this QGIS
> discussion on environmental questions ?
That's not a good idea IHMO. Don't mix licensing & ethics. Free software
licenses explicitly don't discriminate agai
GDAL 3.0.3 has just been released.
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
Unsubscri
1 - 100 of 429 matches
Mail list logo