Hi Kurt,
Il 10/03/2018 03:08, Kurt Stine ha scritto:
> I am trying to port QGIS to Windows RT Desktop (Windows on ARM). I have
> everything set up and running, until I get to cmake. Cmake fails to
> build when it reaches spatialite.
>
> This is what the cmake error file
> shows: https://hastebin
Hello,
I am trying to port QGIS to Windows RT Desktop (Windows on ARM). I have
everything set up and running, until I get to cmake. Cmake fails to build when
it reaches spatialite.
This is what the cmake error file shows: https://hastebin.com/woherijadi.tex
I have tried manually replacing
On 9 March 2018 at 22:24, Richard Duivenvoorde wrote:
> On 09-03-18 12:38, Andrew Brooks wrote:
>> Hi
>>
>> The docs state
>>Qwt >= 5.0 & (< 6.1 with internal QwtPolar)
>> Can you be more explicit about exactly which version of Qwt (and
>> QwtPolar) to use?
>>
>> Most versions of Qwt don't bui
On 9 March 2018 at 19:39, Kristian Evers wrote:
> All,
>
> Just to follow up on this, since I am the one to blame for this error to show
> up.
Kristian -- just to add my 2c here, there's absolutely NO-ONE who can
blame you for this mistake, please do not beat yourself up over this!
I'm sure ther
XML and JSON formats do not adhere to the simple feature model of GDAL/OGR
that is reminiscent of a flat file or a relational table. And GDAL is one
of the base pillars for QGIS.
These are more similar to other storage models, say hierarchical or graphs,
so they enable a complex data structure that
Hi
I encountered this same error trying to compile and package QGIS 3.0 within
the "conda-forge" community channel of the Anaconda Python distribution, but
only when using GCC 4.8 (4.8.5, specifically). Pretty sure I have to stick
with GCC 4.8 for now within this build environment, but I did not e
On 03/09/2018 07:04 PM, Richard Duivenvoorde wrote:
> ps README.md still talking about ./configure in "Building on Unix/Linux"
> while apparently it is not there anymore?
It's there after you run autogen.sh.
___
QGIS-Developer mailing list
QGIS-Developer
On 09-03-18 16:30, Even Rouault wrote:
>
> I don't think the removal of "+nadgrids=@null" is a "universal"
> workaround. It only works when the other SRS has no +towgs84 or
> +nadgrids clause itself, which isn't the case of EPSG:28992. Basically
> if you transform between EPSG:28992 and WebMercat
Plugin Beeline approval by pcav.
The plugin version "[1424] Beeline 0.1" is now approved
Link: http://plugins.qgis.org/plugins/Beeline/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgi
Plugin Beeline approval by pcav.
The plugin version "[1424] Beeline 0.2.0" is now approved
Link: http://plugins.qgis.org/plugins/Beeline/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/q
Well, you might just be right since I could not get some of the packages
working off of brew (due to installation issues, or unavailability). Some
of them were build from source (e.g., SIP), which might be causing the
issue that you are talking about.
And no, I have not been using Remi's formula.
The challenge with KML imports is that its free form nature makes it
difficult to conform to a table. I have large KMLs with nested folder
structures. I find that these large KMLs crash QGIS if I try to import the
entire thing and then each point gets rendered as a separate layer.
It wouldn't be h
Hi Giovanni,
GetFeatures can output GML with a different format.
What is sure is that GeoJSON spec doesn't leave any choice, unless we go
for a proprietary output format allowing another SRS.
I'll keep that in mind when testing OGC compliancy for WFS. We are working
on that currently to evaluate
This discussion is going a bit off-topic, but I think the problem could be
in your Homebrew installation. If someone changes the reference to qt from
qt4 to qt5 may cause some issue (I call it a mess, but I am biased, I had a
very bad time with these issue – thanks to Larry did fix them). Maybe you
Hello Carlo,
Would you advice building Qt5 from source then, rather than using brew?
Thanks
On Fri, Mar 9, 2018 at 11:13 AM, Carlo A. Bertelli (Charta s.r.l.) <
carlo.berte...@gmail.com> wrote:
> Hello,
> I suggest to remind that using Homebrew carries in another issue. The
> maintainers decide
Hello,
I suggest to remind that using Homebrew carries in another issue. The
maintainers decided to force everyone to use Qt5 as Qt4 is deprecated by Qt
developers. Everything that was called qt5-something should become
qt-something, so everyone who uses Qt4 had to make formulas called
qt4-somethin
On vendredi 9 mars 2018 12:19:09 CET Richard Duivenvoorde wrote:
> Hi All,
>
> I second that: not blaming anybody here. This happens in the real world.
>
> My point was that I think as QGIS we can 'hide' this issue by not using
> 5.0.0 'yet' in the osgeo4w package.
>
> I will happily use/test wh
Plugin NNJoin approval by pcav.
The plugin version "[597] NNJoin 3.0.5" is now approved
Link: http://plugins.qgis.org/plugins/NNJoin/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-
On vendredi 9 mars 2018 11:38:17 CET Even Rouault wrote:
> Kristian
>
> your are certainly not too blame at à personal level. this is the kind of
> this that happen inevitably given a certain amount of changes . i'm
> surprised that the GDAL autotest suite did not catch this but the cause is
> li
Timur,
I am having similar issues in Linux openSUSE Leap 42.3. As far as I
understand there are issues and conflict between versions of PyQT and SIP.
It is not a QGIS problem. It would be nice to sort it out in any case.
/H.
On Thu, Mar 8, 2018 at 4:10 PM, Timur Girgin wrote:
> Hello everyone,
Hi René-Luc,
> Le 01/03/2018 à 12:52, Giovanni Manghi a écrit :
>> Hi all,
>> now that 2.18 is LTR I guess that many have also updated their QGIS
>> Server installation to this release. Problem is that I see a few
>> issues in 2.18 and would like to have gsome feedback from others.
>>
>> *) slow
Hi all,
>> It will be great to have the possibility to allow nullptr in the map
>> combobox.
>> Nyall, do you have an idea how to enhance QgsComposerItemComboBox
>> introdiuced by
>> https://github.com/qgis/QGIS/commit/1b4bd47076103e931e642c9c2b6a363f14b20a45
>> ?
>> Issue already exists: https://
On 09.03.2018 14:51, Luigi Pirelli wrote:
I was answering you to prepare a PR... and you just did it
https://github.com/qgis/QGIS/pull/6566
This is the best way to proceed, tnx
No, that PR is not about this issue. I did not create a PR for this
because I don't know how to fix this. I assume bu
I was answering you to prepare a PR... and you just did it
https://github.com/qgis/QGIS/pull/6566
This is the best way to proceed, tnx
"don't ask what the QGIS dev community can do for you, but what you
can do for all"
Luigi Pirelli
Thanks Kristian.
This experience shows us how today in the world of mapping "services"
(remote mapping engines like QGIS, MapServer, PostGIS, GRASS GIS,..)
rely on this unfortunate projection (thanks Google ha), where end-users
of the services really have no access to the remote server's PROJ
On 09-03-18 12:38, Andrew Brooks wrote:
> Hi
>
> The docs state
> Qwt >= 5.0 & (< 6.1 with internal QwtPolar)
> Can you be more explicit about exactly which version of Qwt (and
> QwtPolar) to use?
>
> Most versions of Qwt don't build with Qt-5.
> QwtPolar doesn't seem to build at all.
>
> Any
Hi
The docs state
Qwt >= 5.0 & (< 6.1 with internal QwtPolar)
Can you be more explicit about exactly which version of Qwt (and QwtPolar)
to use?
Most versions of Qwt don't build with Qt-5.
QwtPolar doesn't seem to build at all.
Any advice regarding building Qwt? Thanks!
_
Il 09/03/2018 12:27, Sebastiaan Couwenberg ha scritto:
> FWIW, proj (5.0.0-3~exp1) available in Debian experimental contains a
> patch with the cherry-picked commit that fixes this issue. [0]
Thanks Bas!
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/trainin
Hi,
Two strings in python/plugins/processing/algs/gdal/buildvrt.py do not
translate because pylupdate5 puts them into wrong context
(ParameterVrtDestination should be in buildvrt).
That's because in buildvrt.py ParameterVrtDestination class is defined
within buildvrt. Perhaps pylupdate5 simp
On 03/09/2018 12:19 PM, Richard Duivenvoorde wrote:
> I will happily use/test whatever is available in Debian sid :-)
FWIW, proj (5.0.0-3~exp1) available in Debian experimental contains a
patch with the cherry-picked commit that fixes this issue. [0]
It also contains a patch with the changes fro
Am Fr, 9.03.2018, 12:19 schrieb Richard Duivenvoorde:
>
> My point was that I think as QGIS we can 'hide' this issue by
> not using 5.0.0 'yet' in the osgeo4w package.
Hehe, proj is hiding itself, since 493 is still shown in "about" ;)
___
QGIS-Develope
Hi All,
I second that: not blaming anybody here. This happens in the real world.
My point was that I think as QGIS we can 'hide' this issue by not using
5.0.0 'yet' in the osgeo4w package.
I will happily use/test whatever is available in Debian sid :-)
Also tried Kristian's fix.
For QGIS user
Sorry for rewinding the thread to where it started.
Provided that users can benefit from keeping the last stable release and an
LTR both installed, do you think that this is up to the specific platform
to handle this (OsGeo4W does it already) or a more general solution can be
provided?
The LTR will
Kristian
your are certainly not too blame at à personal level. this is the kind of this
that happen inevitably given a certain amount of changes . i'm surprised that
the GDAL autotest suite did not catch this but the cause is likely that the
GDAL c++ class that wraps proj has an optimisation w
Hello,
How can I disable authentication from qgis during build or runtime?
Whe opening settings -> options -> authentication, I have below message
"Authentication system is DISABLED:
QCA's OpenSSL plugin (qca-openssl) is missing.
"
I also have an "critical" message in messagbar every time qgis is
All,
Just to follow up on this, since I am the one to blame for this error to show
up.
Both by introducing it in the first place and by releasing 5.0.0 with this as a
known bug. The bug was introduced to fix a range of other potential issues.
Unfortunately the architecture in the old API of PROJ
Plugin Beeline approval by pcav.
The plugin version "[1352] Beeline 0.2.0" is now approved
Link: http://plugins.qgis.org/plugins/Beeline-master/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/lis
37 matches
Mail list logo
