Re: [QGIS-Developer] Fwd: Question about a plugin. POC attached.

2023-04-15 Thread Giordano Cetti via QGIS-Developer
Dear Tim,

It seems that 99% of developers were asking themselves the same question
and hesitated to examine the code.

Regardless, I think it's already good to have shared this small proof of
concept with the community, demonstrating an integration between Django and
QGIS, especially considering that it has been implemented with a rather
robust certificate verification mechanism.

So, rest assured, my question does not hide an intention contrary to GPL
policy, but I remain curious to understand the boundary between a process
considered external and a process considered internal to QGIS, and
therefore subject to the same GPL license. If I ever present a project to a
client, I would like to be able to tell them that I applied a defense
mechanism (albeit simple, such as compilation) to prevent the leakage of
endpoints called by the REST APIs.

However, I think I have answered myself: after researching the issue
online, I found that calling QGSTask in a function is considered an
internal process to QGIS and thus subject to GPL. The subsequent question
that emerged and that I still cannot answer is: would it be acceptable if
only the run() function or a subsequent function were compiled, just enough
to close the REST parameters? There probably isn't a definitive answer;
could that portion of code be considered an extension of pycurl+certifi?
Maybe yes, maybe no. It matters little, I guess.

Thank you for the time you spent writing this request for clarification.

Best regards,


Giordano Cetti

CTO @ByCloudSRL

pec: bycl...@pec.it
giordano.ce...@bycloud.eu
https://bycloud.eu



Il giorno sab 15 apr 2023 alle 22:39 Tim Sutton  ha
scritto:

> Hi
>
> I havent looked at your code, but perhaps you could add to your original
> message an explanation of why you don't just distribute it as a py /
> uncompiled python source file?
>
> Regards
>
> Tim
>
> On Tue, Apr 11, 2023 at 6:48 PM Giordano Cetti via QGIS-Developer <
> qgis-developer@lists.osgeo.org> wrote:
>
>> Greetings to QGIS developers,
>>
>> I would greatly appreciate it if someone could check if the attached
>> plugin complies with the licenses compared to the imported modules.
>>
>> In this specific attached plugin, all the source code is open, but the
>> question is: what if it comes with the following file:
>> *'djangorest/include/djangorest_compiled.py'* really compiled as a .pyd
>> file? Would it violate the GPL license terms or is it just enough to be
>> considered as an acceptable external process?
>>
>> The .pyd will just import QgsTask from qgis.core and use a session_path
>> received as a text created by the open source part of the plugin
>> using QgsProcessingUtils.
>>
>> The attached one is a very simple plugin made for this demonstration, you
>> can click on the button, just type google.it, and it will download the
>> 404 page found ( because it appends some string that google doesn't serve
>> as content ). For user and password fields: just type anything, they are
>> not used in the POC but there's still a check active on fields population.
>> The only action the plugin will do is just a single pycurl GET request to
>> the address specified.
>>
>> Any advice will be appreciated.
>> Thanks
>>
>> *ATTACHMENT BLOCKED BY GOOGLE SCAN BECAUSE IT INCLUDES PYCURL AND CERTIFI
>> LIBRARY SO I SHARE USING GOOGLE DRIVE LINK. I TESTED IT ONLY ON QGIS 3.10*
>>
>> *https://drive.google.com/file/d/1qS7h3LaZ6BlBAW3AItEjM5swpDocHbue/view?usp=sharing
>> *
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> --
>
> --
> ​
>
> Tim Sutton
> Kartoza Co-Founder
> Visit http://kartoza.com to find out about open source:
>  * Desktop GIS programming services
>  * Geospatial web development
> * GIS Training
> * Consulting Services
> Tim is a member of the QGIS Project Steering Committee
>
> ---
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: Question about a plugin. POC attached.

2023-04-15 Thread Tim Sutton via QGIS-Developer
Hi

I havent looked at your code, but perhaps you could add to your original
message an explanation of why you don't just distribute it as a py /
uncompiled python source file?

Regards

Tim

On Tue, Apr 11, 2023 at 6:48 PM Giordano Cetti via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Greetings to QGIS developers,
>
> I would greatly appreciate it if someone could check if the attached
> plugin complies with the licenses compared to the imported modules.
>
> In this specific attached plugin, all the source code is open, but the
> question is: what if it comes with the following file:
> *'djangorest/include/djangorest_compiled.py'* really compiled as a .pyd
> file? Would it violate the GPL license terms or is it just enough to be
> considered as an acceptable external process?
>
> The .pyd will just import QgsTask from qgis.core and use a session_path
> received as a text created by the open source part of the plugin
> using QgsProcessingUtils.
>
> The attached one is a very simple plugin made for this demonstration, you
> can click on the button, just type google.it, and it will download the
> 404 page found ( because it appends some string that google doesn't serve
> as content ). For user and password fields: just type anything, they are
> not used in the POC but there's still a check active on fields population.
> The only action the plugin will do is just a single pycurl GET request to
> the address specified.
>
> Any advice will be appreciated.
> Thanks
>
> *ATTACHMENT BLOCKED BY GOOGLE SCAN BECAUSE IT INCLUDES PYCURL AND CERTIFI
> LIBRARY SO I SHARE USING GOOGLE DRIVE LINK. I TESTED IT ONLY ON QGIS 3.10*
>
> *https://drive.google.com/file/d/1qS7h3LaZ6BlBAW3AItEjM5swpDocHbue/view?usp=sharing
> *
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>


-- 
--
​

Tim Sutton
Kartoza Co-Founder
Visit http://kartoza.com to find out about open source:
 * Desktop GIS programming services
 * Geospatial web development
* GIS Training
* Consulting Services
Tim is a member of the QGIS Project Steering Committee
---
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [gdal-dev] Announcing SOZip: Seek-Optimized profile for the .zip format

2023-01-09 Thread Even Rouault via QGIS-Developer

> 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 locations in its SOZip compressed version (which is 
excruciatingly slow for a regular non-optimized ZIP). SOZip will shine 
most for local use cases, where this seeking in the underlying 
compressed stream is a cheap operation. For remote use, your mileage may 
vary.


--
http://www.spatialys.com
My software is free, but my time generally not.

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [gdal-dev] Announcing SOZip: Seek-Optimized profile for the .zip format

2023-01-09 Thread WhereGroup

Am 09.01.23 um 16:54 schrieb Richard Duivenvoorde via QGIS-Developer:


Anybody has experience with zipping "lrge zipped GeoPackages"? ;-) 
Is that useful? I just tested a 885MB mbtiles file (I know not 
geopackage...but still sqlite isnt't it?), and that ended up in 868MB. 


For *raster* GPKGs/MBTiles it won't do much. JPG and PNG tiles are 
already compressed and DEFLATE on top won't do anything interesting 
unless there is lots of identical tiles inside

For *vector* data it should offer considerable savings in most cases.

E. g.:

114M Address_25832_all.gpkg
16M Address_25832_all.gpkg.zip  # standard zip, not sozip

Or see https://github.com/sozip/sozip-examples for actual sozip examples.

Very cool project, Even! (Why not "Cloud-Optimized" though? ;) )

Cheers, Hannes

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [gdal-dev] Announcing SOZip: Seek-Optimized profile for the .zip format

2023-01-09 Thread Even Rouault via QGIS-Developer


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 compression o the WKB 
extended geometries of GeoPackage). You can get easily a 3x compression 
ratio when zipping GeoPackage vector files (of course depends a lot on 
what you put in them)


Anybody has experience with zipping "lrge zipped GeoPackages"? ;-) 
Is that useful? I just tested a 885MB mbtiles file (I know not 
geopackage...but still sqlite isnt't it?), and that ended up in 868MB.


I have successfully tested a ~30 GB uncompressed GeoPackage vector file 
compressed as ~10 GB as SOZip.


MBTiles holds PNG or JPEG tiles which are already compressed, so no 
surprise that the Deflate compression of ZIP doesn't help.




OR... are we talking about sets of geopackages?


The SOZip spec is all about laaarge-files-in-zip. Considerations of 
many-files-in-zip are not covered by it (they are orthogonal)



--
http://www.spatialys.com
My software is free, but my time generally not.

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [gdal-dev] Announcing SOZip: Seek-Optimized profile for the .zip format

2023-01-09 Thread Richard Duivenvoorde via QGIS-Developer

Hi Even,

Cool!

Out of curiosity: I thought sqlite/geopackage was already relatively 'skinny' 
packed? Am I wrong?

Anybody has experience with zipping "lrge zipped GeoPackages"? ;-) Is that 
useful? I just tested a 885MB mbtiles file (I know not geopackage...but still sqlite 
isnt't it?), and that ended up in 868MB.

OR... are we talking about sets of geopackages?

Regards,

Richard Duivenvoorde


On 1/9/23 16:42, Even Rouault via QGIS-Developer wrote:

Sorry for cross-posting, but very relevant topic for QGIS. To make it short, 
pending compressing .zip files in the SOZip way, it is possible to directly 
read lrge zipped GeoPackage files (or Shapefiles for nostalgic) from QGIS 
without prior decompression

Even

 Message transféré 
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 ) the 
initial release of the specification ( 
https://github.com/sozip/sozip-spec/blob/master/sozip_specification.md ) for 
the SOZip (Seek-Optimized Zip) profile to the ZIP file format, as well as its 
GDAL implementation.

What is SOZip ?
--

A Seek-Optimized ZIP file (SOZip) is a ZIP file that contains one or several 
Deflate-compressed files that are organized and annotated such that a 
SOZip-aware reader can perform very fast random access (seek) within a 
compressed file.

SOZip makes it possible to access large compressed files directly from a .zip 
file without prior decompression. It is not a new file format, but a profile of 
the existing ZIP format, done in a fully backward compatible way. ZIP readers 
that are non-SOZip aware can read a SOZip-enabled file normally and ignore the 
extended features that support efficient seek capability.

Use cases
--

The SOZip specification is intended to be general purpose / not domain 
specific. It was first developed to serve geospatial use cases, which commonly 
have large compressed files inside of ZIP archives. In particular, it makes it 
possible for users to read large GIS files using the Shapefile, GeoPackage or 
FlatGeobuf formats (which have no native provision for compression) compressed 
in .zip files without prior decompression.

Efficient random access and selective decompression are a requirement to 
provide acceptable performance in many usage scenarios: spatial index 
filtering, access to a feature by its identifier, etc.

Performance
--

SOZip is efficient:

* The overhead of using a file from a SOZip archive, compared to using it 
uncompressed, is of the order of 10% for common read operations.
* Generation of a SOZip file can be much faster than regular ZIP generation 
when using multithreading.
* SOZip files are typically only ~ 5% larger than regular ZIPs (dependent on 
content, and chunk size)

Have a look at benchmarking results: 
https://github.com/sozip/sozip-spec/blob/master/README.md#benchmarking

Other ZIP related specification
--

The SOZip GitHub organization also hosts the KeyValuePairs extra-field 
specification ( 
https://github.com/sozip/keyvaluepairs-spec/blob/master/zip_keyvalue_extra_field_specification.md
 ), to be able to encode arbitrary key-value pairs of metadata associated with 
a file within a ZIP. For example to store the Content-Type of a file.

How does this relate to GDAL ?
---

Pull request https://github.com/OSGeo/gdal/pull/7042 has been submitted with 
the following enhancements:

*  The /vsizip/ virtual file system uses the SOZip index to perform fast
     random access within a compressed SOZip-enabled file.

* The Shapefile and GPKG drivers can directly generate SOZip-enabled 
.shz/.shp.zip or .gpkg.zip files.

*  Addition of the CPLAddFileInZip() C function that can compress a file and add
     it to an new or existing ZIP file, and enable the SOZip optimization when 
relevant.

*  The existed VSIGetFileMetadata() method can be called on a filename of
     the form /vsizip/path/to/the/file.zip/path/inside/the/zip/file and
     with domain = "ZIP" to get information if a SOZip index is available for 
that file.

*  The sozip 
(https://github.com/rouault/gdal/blob/sozip/doc/source/programs/sozip.rst) new 
command line utility
     can be used to create a seek-optimized ZIP file, to append files to an 
existing ZIP file, list the
     contents of a ZIP file and display the SOZip optimization status or 
validate a SOZip file.

Best regards,

Even

--

http://www.spatialys.com
My software is free, but my time generally not.

___
gdal-dev mailing list
gdal-...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev


___
QGIS-Developer 

Re: [QGIS-Developer] Fwd: Dear develop team GIS (plugin)

2022-12-08 Thread Tim Sutton via QGIS-Developer
Hi Richard


I Cc'd in Admire. You can always ping me if there is anything in plugin
land that needs his attention.

Regards

Tim

On Wed, Dec 7, 2022 at 3:26 PM Richard Duivenvoorde via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi,
>
> I do not have an email address of NyakudayaE, but I asked the perion if it
> is OK like it is now:
>
> https://github.com/IFEERnD/Q5Pfes/issues/1
>
> (https://plugins.qgis.org/plugins/q5pfes/ has no public version yet)
>
> Regards,
>
> Richard Duivenvoorde
>
> On 12/7/22 03:33, Dương Phạm Quang wrote:
> > Dear Richard,
> > Thanks for your guidance, I tried deleting the old plugin and pushing
> the version with the new name but it's been more than 3 weeks now but I
> still haven't received a response or approval.
> > Can you please check in your account's upload plugin list "ifeernd".
> > Or you can give me the email channels email address so I can contact them
> > Thank you!*
> > *
> >
> >
> >
> > Vào Th 6, 28 thg 10, 2022 vào lúc 14:35 Richard Duivenvoorde <
> rdmaili...@duif.net > đã viết:
> >
> > Hi,
> >
> > I think you just have to remove the earlier version (or let me do
> the removal).
> >
> > And then upload the new version with the new name, which will then
> start with 1.2 as first version.
> >
> > Let me know if you want me to delete that version.
> >
> > (note: it is better to communicate via the email channels, then
> others also can help)
> >
> > Regards,
> >
> > Richard Duivenvoorde
> >
> > On 10/28/22 06:43, Dương Phạm Quang wrote:
> >  > thank for you support, our first version have been successful
> upload to QGIS Plugin. But we have a new decision to change our plugin
> name. Can you help us in this case?
> >  >
> >  > Vào Th 4, 19 thg 10, 2022 vào lúc 14:24 Richard Duivenvoorde <
> rdmaili...@duif.net   rdmaili...@duif.net >> đã viết:
> >  >
> >  > The author just sent me the github repo:
> >  > "Our link repo is: https://github.com/IFEERnD/v5Pfes <
> https://github.com/IFEERnD/v5Pfes>  https://github.com/IFEERnD/v5Pfes>>"
> >  >
> >  > @Pham Quang Duong am I right that this plugin is only in
> Vietnamees language?
> >  > Can you maybe provide some information (in english, in the
> README.txt (which is now empty)) about what the plugin is supposed to do,
> or maybe a little guide about how to test?
> >  > Most people approving the plugins are English
> speaking/reading ( or at least without knowledge of Vietnamees writing :-)
> ) , so without any guidance cannot tell what the plugin is doing, unless
> they deep dive into the code.
> >  >
> >  > Regards,
> >  >
> >  > Richard Duivenvoorde
> >  >
> >  > On 10/19/22 09:13, Werner Macho wrote:
> >  >  > Hi Richard,
> >  >  > I also searched for the user id "ifeernd" - and could
> not find it.
> >  >  > Maybe it is not a plugin and something
> completely different is meant?
> >  >  >
> >  >  > regards
> >  >  > werner
> >  >  >
> >  >  > On Wed, Oct 19, 2022 at 9:02 AM Richard Duivenvoorde via
> QGIS-Developer  qgis-developer@lists.osgeo.org>  >  qgis-developer@lists.osgeo.org 
>  >  >  >
> >  >  > Hi Devs,
> >  >  >
> >  >  > This mail was (accidently wrong) sent to the list
> owner of the dev list.
> >  >  >
> >  >  > Sender tells us a plugin was sent in 2 weeks ago.
> >  >  >
> >  >  > If I search for V5Pfes I only see 'None', if I search
> for Forest I see None again.
> >  >  >
> >  >  > Is there something wrong with the metadata of the
> plugin?
> >  >  > I think I normally see the name of the plugin, even
> when it is not approved?
> >  >  >
> >  >  > @Pham Quang Duong can you maybe sent the link of you
> repo?
> >  >  >
> >  >  > Regards,
> >  >  >
> >  >  > Richard Duivenvoorde
> >  >  >
> >  >  >
> >  >  >  Forwarded Message 
> >  >  > Subject:Dear develop team GIS
> >  >  > Date:   Tue, 18 Oct 2022 16:47:19 +0700
> >  >  > From:   Dương Phạm Quang    >     >  >  > To: qgis-developer-ow...@lists.osgeo.org  qgis-developer-ow...@lists.osgeo.org>  

Re: [QGIS-Developer] Fwd: Dear develop team GIS (plugin)

2022-12-07 Thread Richard Duivenvoorde via QGIS-Developer

Hi,

I do not have an email address of NyakudayaE, but I asked the perion if it is 
OK like it is now:

https://github.com/IFEERnD/Q5Pfes/issues/1

(https://plugins.qgis.org/plugins/q5pfes/ has no public version yet)

Regards,

Richard Duivenvoorde

On 12/7/22 03:33, Dương Phạm Quang wrote:

Dear Richard,
Thanks for your guidance, I tried deleting the old plugin and pushing the 
version with the new name but it's been more than 3 weeks now but I still 
haven't received a response or approval.
Can you please check in your account's upload plugin list "ifeernd".
Or you can give me the email channels email address so I can contact them
Thank you!*
*



Vào Th 6, 28 thg 10, 2022 vào lúc 14:35 Richard Duivenvoorde mailto:rdmaili...@duif.net>> đã viết:

Hi,

I think you just have to remove the earlier version (or let me do the 
removal).

And then upload the new version with the new name, which will then start 
with 1.2 as first version.

Let me know if you want me to delete that version.

(note: it is better to communicate via the email channels, then others also 
can help)

Regards,

Richard Duivenvoorde

On 10/28/22 06:43, Dương Phạm Quang wrote:
 > thank for you support, our first version have been successful upload to 
QGIS Plugin. But we have a new decision to change our plugin name. Can you help us 
in this case?
 >
 > Vào Th 4, 19 thg 10, 2022 vào lúc 14:24 Richard Duivenvoorde mailto:rdmaili...@duif.net> >> đã viết:
 >
 >     The author just sent me the github repo:
 >     "Our link repo is: https://github.com/IFEERnD/v5Pfes 
 >"
 >
 >     @Pham Quang Duong am I right that this plugin is only in Vietnamees 
language?
 >     Can you maybe provide some information (in english, in the 
README.txt (which is now empty)) about what the plugin is supposed to do, or maybe 
a little guide about how to test?
 >     Most people approving the plugins are English speaking/reading ( or 
at least without knowledge of Vietnamees writing :-) ) , so without any guidance 
cannot tell what the plugin is doing, unless they deep dive into the code.
 >
 >     Regards,
 >
 >     Richard Duivenvoorde
 >
 >     On 10/19/22 09:13, Werner Macho wrote:
 >      > Hi Richard,
 >      > I also searched for the user id "ifeernd" - and could not find it.
 >      > Maybe it is not a plugin and something completely different is 
meant?
 >      >
 >      > regards
 >      > werner
 >      >
 >      > On Wed, Oct 19, 2022 at 9:02 AM Richard Duivenvoorde via QGIS-Developer mailto:qgis-developer@lists.osgeo.org> >        >
 >      >     Hi Devs,
 >      >
 >      >     This mail was (accidently wrong) sent to the list owner of 
the dev list.
 >      >
 >      >     Sender tells us a plugin was sent in 2 weeks ago.
 >      >
 >      >     If I search for V5Pfes I only see 'None', if I search for 
Forest I see None again.
 >      >
 >      >     Is there something wrong with the metadata of the plugin?
 >      >     I think I normally see the name of the plugin, even when it 
is not approved?
 >      >
 >      >     @Pham Quang Duong can you maybe sent the link of you repo?
 >      >
 >      >     Regards,
 >      >
 >      >     Richard Duivenvoorde
 >      >
 >      >
 >      >      Forwarded Message 
 >      >     Subject:        Dear develop team GIS
 >      >     Date:   Tue, 18 Oct 2022 16:47:19 +0700
 >      >     From:   Dương Phạm Quang mailto:phamquangdu...@ifee.edu.vn> 
>        >     To: qgis-developer-ow...@lists.osgeo.org  
> 
 
>>
 >      >
 >      >
 >      >
 >      >     We are trying to release a tool to support the construction of V5Pfes 
Forest Environmental Services Payment Map on the QGIS platform called V5Pfes. The account we 
use has an id of "ifeernd".
 >      >     However, it has been more than 2 weeks since pushing the 
first 

Re: [QGIS-Developer] Fwd: Dear develop team GIS (plugin)

2022-10-19 Thread Richard Duivenvoorde via QGIS-Developer

The author just sent me the github repo:
"Our link repo is: https://github.com/IFEERnD/v5Pfes;

@Pham Quang Duong am I right that this plugin is only in Vietnamees language?
Can you maybe provide some information (in english, in the README.txt (which is 
now empty)) about what the plugin is supposed to do, or maybe a little guide 
about how to test?
Most people approving the plugins are English speaking/reading ( or at least 
without knowledge of Vietnamees writing :-) ) , so without any guidance cannot 
tell what the plugin is doing, unless they deep dive into the code.

Regards,

Richard Duivenvoorde

On 10/19/22 09:13, Werner Macho wrote:

Hi Richard,
I also searched for the user id "ifeernd" - and could not find it.
Maybe it is not a plugin and something completely different is meant?

regards
werner

On Wed, Oct 19, 2022 at 9:02 AM Richard Duivenvoorde via QGIS-Developer 
mailto:qgis-developer@lists.osgeo.org>> wrote:

Hi Devs,

This mail was (accidently wrong) sent to the list owner of the dev list.

Sender tells us a plugin was sent in 2 weeks ago.

If I search for V5Pfes I only see 'None', if I search for Forest I see None 
again.

Is there something wrong with the metadata of the plugin?
I think I normally see the name of the plugin, even when it is not approved?

@Pham Quang Duong can you maybe sent the link of you repo?

Regards,

Richard Duivenvoorde


 Forwarded Message 
Subject:        Dear develop team GIS
Date:   Tue, 18 Oct 2022 16:47:19 +0700
From:   Dương Phạm Quang mailto:phamquangdu...@ifee.edu.vn>>
To: qgis-developer-ow...@lists.osgeo.org 




We are trying to release a tool to support the construction of V5Pfes Forest 
Environmental Services Payment Map on the QGIS platform called V5Pfes. The account we use 
has an id of "ifeernd".
However, it has been more than 2 weeks since pushing the first version, but 
we still have not received a response to edit or approved version.
Please help me check it out and report back if there are any problems 
during our release


-- 
>


/Yours Sincerely,/
Pham Quang Duong

>Tell: +84 389799932

/phamquangdu...@ifee.edu.vn/  
>
*Department of Research and Development**Institute For Forest Ecology and 
Environment*/http://ifee.edu.vn  >/

>___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org 
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer 

Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer 




___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: Dear develop team GIS (plugin)

2022-10-19 Thread Werner Macho via QGIS-Developer
Hi Richard,
I also searched for the user id "ifeernd" - and could not find it.
Maybe it is not a plugin and something completely different is meant?

regards
werner

On Wed, Oct 19, 2022 at 9:02 AM Richard Duivenvoorde via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi Devs,
>
> This mail was (accidently wrong) sent to the list owner of the dev list.
>
> Sender tells us a plugin was sent in 2 weeks ago.
>
> If I search for V5Pfes I only see 'None', if I search for Forest I see
> None again.
>
> Is there something wrong with the metadata of the plugin?
> I think I normally see the name of the plugin, even when it is not
> approved?
>
> @Pham Quang Duong can you maybe sent the link of you repo?
>
> Regards,
>
> Richard Duivenvoorde
>
>
>  Forwarded Message 
> Subject:Dear develop team GIS
> Date:   Tue, 18 Oct 2022 16:47:19 +0700
> From:   Dương Phạm Quang 
> To: qgis-developer-ow...@lists.osgeo.org
>
>
>
> We are trying to release a tool to support the construction of V5Pfes
> Forest Environmental Services Payment Map on the QGIS platform called
> V5Pfes. The account we use has an id of "ifeernd".
> However, it has been more than 2 weeks since pushing the first version,
> but we still have not received a response to edit or approved version.
> Please help me check it out and report back if there are any problems
> during our release
>
>
> --
> 
>
> /Yours Sincerely,/
> Pham Quang Duong
>
> Tell: +84 389799932
>
> /phamquangdu...@ifee.edu.vn/ 
> *Department of Research and Development**Institute For Forest Ecology and
> Environment*/http://ifee.edu.vn /
>
>  >___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-25 Thread Régis Haubourg via QGIS-Developer
Nice, I'll work on this on the train back home on Saturday.
Fabiano did some magic css tricks only web developers know about . That
should be nice :)

Le jeu. 25 août 2022 à 10:00, Matthias Kuhn  a écrit :

> Hi
>
> On Thu, Aug 25, 2022 at 8:50 AM Richard Duivenvoorde via QGIS-Developer <
> qgis-developer@lists.osgeo.org> wrote:
>
>> On 8/24/22 16:23, Régis Haubourg via QGIS-Developer wrote:
>> > Do you have opinions on such a much ?
>> > (that would require to stress translators so that we don't brake
>> translations for a too long time for such an important landing page )
>>
>> No strong opinion,I just wanted to help someone, who complained that it
>> was not visible that we do not support Windows7 anymore...
>>
>> If you think the google strategy will work: go for it :-)
>>
>
> +1
>
>
>>
>> If you give me a hint when it is merged, I'll update the transifex
>> strings.
>> If you wait until the github-build/action is done, this will not be
>> necessary anymore (I think?)
>>
>
> That is already done and functional.
> Transifex will be updated within 2 hours. If it's not please ping me.
>
> Matthias
>
>
>>
>> Regards,
>>
>> Richard Duivenvoorde
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
> [image: https://qfield.org/get/] 
> QFIELD 2.0 IS HERE! - Hold the power of QGIS in your hand - learn more
>  - get it now
> 
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-25 Thread Matthias Kuhn via QGIS-Developer
Hi

On Thu, Aug 25, 2022 at 8:50 AM Richard Duivenvoorde via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> On 8/24/22 16:23, Régis Haubourg via QGIS-Developer wrote:
> > Do you have opinions on such a much ?
> > (that would require to stress translators so that we don't brake
> translations for a too long time for such an important landing page )
>
> No strong opinion,I just wanted to help someone, who complained that it
> was not visible that we do not support Windows7 anymore...
>
> If you think the google strategy will work: go for it :-)
>

+1


>
> If you give me a hint when it is merged, I'll update the transifex strings.
> If you wait until the github-build/action is done, this will not be
> necessary anymore (I think?)
>

That is already done and functional.
Transifex will be updated within 2 hours. If it's not please ping me.

Matthias


>
> Regards,
>
> Richard Duivenvoorde
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>

-- 
 

QFIELD 2.0 IS HERE! - Hold the power of QGIS in 
your hand - learn more 
 - get it now 


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-25 Thread Richard Duivenvoorde via QGIS-Developer

On 8/24/22 16:23, Régis Haubourg via QGIS-Developer wrote:

Do you have opinions on such a much ?
(that would require to stress translators so that we don't brake translations 
for a too long time for such an important landing page )


No strong opinion,I just wanted to help someone, who complained that it was not 
visible that we do not support Windows7 anymore...

If you think the google strategy will work: go for it :-)

If you give me a hint when it is merged, I'll update the transifex strings.
If you wait until the github-build/action is done, this will not be necessary 
anymore (I think?)

Regards,

Richard Duivenvoorde

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-24 Thread Régis Haubourg via QGIS-Developer
Hi guys,
in the same time during the sprint, we started to explore how to declutter
the main download page, which is being work in progress in PR
https://github.com/qgis/QGIS-Website/pull/1037

This would end up in removing all those warnings from the main page. As we
still need these informations, my thought was to add the standalone and
osgeo4w detailed specifications to the "all_download" page.  This way,
users wouldn't see them at first download, but at last it would be indexed
by google and they could find it.

Do you have opinions on such a much ?
(that would require to stress translators so that we don't brake
translations for a too long time for such an important landing page )

Best
Régis

Le mer. 24 août 2022 à 16:07, Jürgen E. Fischer via QGIS-Developer <
qgis-developer@lists.osgeo.org> a écrit :

> Hi Richard,
>
> On Wed, 24. Aug 2022 at 15:47:53 +0200, Richard Duivenvoorde via
> QGIS-Developer wrote:
> > On 8/24/22 15:09, Jürgen E. Fischer via QGIS-Developer wrote:
> > >
> https://github.com/qgis/QGIS-Website/commit/e37bbf2a530f9ad482331d211077e2d5104ad7fd
> > Ok, thanks. used it to add the following note (just below Download for
> Windows, as it is valid for ALL Windows installs):
> > NOTE: You will need Windows 8 or higher (as QGIS needs Python 3.9, and
> Windows 7 is not supported anymore by Python 3.9)
> > Hope this is fine/clear.
>
> LGTM
>
>
> Jürgen
>
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
> Software Engineer   D-26506 Norden
> https://www.norbit.de
> QGIS release manager (PSC)  Germany IRC: jef on Libera|OFTC
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-24 Thread Jürgen E . Fischer via QGIS-Developer
Hi Richard,

On Wed, 24. Aug 2022 at 15:47:53 +0200, Richard Duivenvoorde via QGIS-Developer 
wrote:
> On 8/24/22 15:09, Jürgen E. Fischer via QGIS-Developer wrote:
> > https://github.com/qgis/QGIS-Website/commit/e37bbf2a530f9ad482331d211077e2d5104ad7fd
> Ok, thanks. used it to add the following note (just below Download for 
> Windows, as it is valid for ALL Windows installs):
> NOTE: You will need Windows 8 or higher (as QGIS needs Python 3.9, and 
> Windows 7 is not supported anymore by Python 3.9)
> Hope this is fine/clear.

LGTM


Jürgen


-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  Germany IRC: jef on Libera|OFTC


signature.asc
Description: PGP signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-24 Thread Richard Duivenvoorde via QGIS-Developer

On 8/24/22 15:09, Jürgen E. Fischer via QGIS-Developer wrote:


https://github.com/qgis/QGIS-Website/commit/e37bbf2a530f9ad482331d211077e2d5104ad7fd


Ok, thanks. used it to add the following note (just below Download for Windows, 
as it is valid for ALL Windows installs):

NOTE: You will need Windows 8 or higher (as QGIS needs Python 3.9, and Windows 
7 is not supported anymore by Python 3.9)

Hope this is fine/clear.

Regards,

Richard Duivenvoorde___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-24 Thread Jürgen E . Fischer via QGIS-Developer
Hi Richard,

On Wed, 24. Aug 2022 at 14:58:29 +0200, Richard Duivenvoorde via QGIS-Developer 
wrote:
> On 8/24/22 14:46, Jürgen E. Fischer via QGIS-Developer wrote:
> > > It was unsupported since the introduction of osgeo4w v2 and there was a 
> > > (big
> > > fat red) warning for long - it has just been removed in the last couple of
> > > days.
> 
> Should we revive it (or update it with your info below)?
> Or was it discussed to remove it because Microsoft dropped it...
> (apparently people still use Win7)

> Could not find the commit...

https://github.com/qgis/QGIS-Website/commit/e37bbf2a530f9ad482331d211077e2d5104ad7fd


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  Germany IRC: jef on Libera|OFTC


signature.asc
Description: PGP signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-24 Thread Richard Duivenvoorde via QGIS-Developer

On 8/24/22 14:46, Jürgen E. Fischer via QGIS-Developer wrote:

It was unsupported since the introduction of osgeo4w v2 and there was a (big
fat red) warning for long - it has just been removed in the last couple of
days.


Should we revive it (or update it with your info below)?
Or was it discussed to remove it because Microsoft dropped it...
(apparently people still use Win7)

Could not find the commit...


And Windows >7 should still work.  Just Windows <=7 does not work anymore.

And support for Windows 7 (and/or 32bit) was not dropped during the period of
the previous LTR, but after it expired - that why osgeo4w v1 and v2 were
maintained in parallel for a while.


Ah, sorry did not now there ws something in between 7 and 10 :-)

Regards,

Richard
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-24 Thread Jürgen E . Fischer via QGIS-Developer
Hi Richard,

On Wed, 24. Aug 2022 at 14:36:46 +0200, Jürgen E. Fischer wrote:
> On Wed, 24. Aug 2022 at 11:58:48 +0200, Richard Duivenvoorde via 
> QGIS-Developer wrote:
> > See thread in user list...
> > Is Windows 7 indeed totally not supported anymore (for 3.22/LTR)?
> > If so we should indeed add a line that current installs are for >=Win10 
> > only?
 
> It was unsupported since the introduction of osgeo4w v2 and there was a (big
> fat red) warning for long - it has just been removed in the last couple of
> days.

And Windows >7 should still work.  Just Windows <=7 does not work anymore.

And support for Windows 7 (and/or 32bit) was not dropped during the period of
the previous LTR, but after it expired - that why osgeo4w v1 and v2 were
maintained in parallel for a while.


Jürgen 

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  Germany IRC: jef on Libera|OFTC


signature.asc
Description: PGP signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-24 Thread Jürgen E . Fischer via QGIS-Developer
Hi Richard,

On Wed, 24. Aug 2022 at 11:58:48 +0200, Richard Duivenvoorde via QGIS-Developer 
wrote:
> See thread in user list...
> Is Windows 7 indeed totally not supported anymore (for 3.22/LTR)?
> If so we should indeed add a line that current installs are for >=Win10 only?

It was unsupported since the introduction of osgeo4w v2 and there was a (big
fat red) warning for long - it has just been removed in the last couple of
days.


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  Germany IRC: jef on Libera|OFTC


signature.asc
Description: PGP signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Latest development version of QGIS as a .msi standalone installer ?

2022-08-24 Thread Luca Manganelli via QGIS-Developer
Il giorno mer 24 ago 2022 alle ore 11:58 Richard Duivenvoorde via
QGIS-Developer  ha scritto:
> See thread in user list...
>
> Is Windows 7 indeed totally not supported anymore (for 3.22/LTR)?
>
> If so we should indeed add a line that current installs are for >=Win10
only?

at least a warning. For us, QGIS without Python plugins is basically
useless.

-- 





Comune di Trento 

via Belenzani, 19 - 38122 Trento | C.F e P. IVA: 
00355870221

tel. +39 0461.884111 | www.comune.trento.it 
 


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: Compile Master with Debian Bullseye

2022-06-29 Thread Richard Duivenvoorde via QGIS-Developer

Hi Piet,

FYI: ccmake caches a lot apparently, so my way in such issues is often to remove the build 
directory, create it again, cd into it, and run "ccmake  
.." again (and then it often magically it finds stuff it earlier did not find...).

Keep on compiling :-)

Regards,

Richard Duivenvoorde


On 6/29/22 13:24, Piet via QGIS-Developer wrote:


Dear Johannes,

thank you very much for your kind answer!
Meanwhile I solved this issue.
I don't know why, but ccmake does not find the gdal library and I added the 
wrong library manually in the ccmake GUI.

After the change to the correct library the compilation works fine!

Kind regards

Piet
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: [Qgis-user] Editing a multipolygon object changes type from Multipolygon to Polygon

2022-04-02 Thread Bo Victor Thomsen via QGIS-Developer
I'll just add that  I have observed the same behaviour using a 
GeoPackage based layer. It was during a teaching session with 10-15 
students, so I can't remember exactly how and which editing tool that 
was the cause of the error.


Windows 10 / QGIS 3.22.3


Med venlig hilsen / Kind regards

Bo Victor Thomsen

Den 01-04-2022 kl. 17:38 skrev Jörg Höttges via QGIS-Developer:

Hi everyone,

I'm using QGIS 3.16 to 3.22. I created a table with multipolygon 
objects in a SpatiaLite database. When editing one of the polygons 
there appears a warning "Die Operation würden Geometrietyp ändern" 
("The operation would change geometry type") and saving of the 
changings failes.


Following are the objects before and after the modification:

before editing:
wkt_geom: MultiPolygon (((379698.836953434 
5709466.3700011175871, 379705.347671694 
5709460.9349959021807, 379703.797000204891 
5709459.0760035017729, 379697.347813735 
5709464.7740020861626, 379698.836953434 
5709466.3700011175871)))


after adding the point (379701.027186265 
5709464.5429959766865):
wkt_geom: Polygon ((379701.027186265 
5709464.5429959766865, 379705.347671694 
5709460.9349959021807, 379703.797000204891 
5709459.0760035017729, 379697.347813735 
5709464.7740020861626, 379698.836953434 
5709466.3700011175871, 379701.027186265 
5709464.5429959766865))


how can I make sure that the type does not change due to editing? The 
only idea i have is to remove or modify the geometry constraint in the 
Spatialite database table for the geometry column. The warning still 
appears but saving is successful.


Interesting fact: The problem didn't appear with QGIS 3.16.

Many thanks for your help!

Jörg Höttges

---
FH Aachen
University of Applied Sciences
Bayernallee 9
52066 Aachen | Germany
www.fh-aachen.de/menschen/hoettges



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe:https://lists.osgeo.org/mailman/listinfo/qgis-developer___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: Future of PDAL in Debian

2021-10-04 Thread Jürgen E . Fischer
Hi,

On Mon, 04. Oct 2021 at 08:06:56 +0200, Richard Duivenvoorde wrote:
> FYI, see below: anybody using PDAL and able to help packaging PDAL in Debian?

I think frankie just voluntered:

On Mon, 4 Oct 2021 09:34:21 +0200, Francesco P. Lovergine"  
wrote:
> On Mon, Oct 04, 2021 at 05:37:18AM +0200, Sebastiaan Couwenberg wrote:
> > PDAL 2.4 is going to require lazperf instead of laszip, this will hinder
> > adoption in Debian because lazperf is not packaged (yet).

> > I don't intend to package lazperf, getting laszip into Debian was far to
> > much effort already. If you care about LAZ support in PDAL, please help
> > to package and maintain lazperf in Debian.

> > Kind Regards,

> Annotated, due ASAP on my side along with new GDAL Perl support via FFI.

> -cheers


Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden  https://www.norbit.de


signature.asc
Description: PGP signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [QGIS-Developer] Fwd: Change values Temporal Controller Panel

2020-11-07 Thread Tim Sutton
Hi Richard

Note that your example contains a duplicate import:

QgsMapRendererCustomPainterJob,
QgsProject,
QgsMapRendererCustomPainterJob,

Regards


Tim

On Fri, Nov 6, 2020 at 3:42 PM Luiz Motta  wrote:

> Hi Richard,
>
> Your code was exactly what I needed.
>
> Thanks so much!
>
> Regards,
> Luiz Motta
>
>
>
> Em sex., 6 de nov. de 2020 às 11:08, Richard Duivenvoorde <
> rdmaili...@duif.net> escreveu:
>
>> Hi Luiz,
>>
>> We have fixed stuff to be able to use temporal stuff in pyqgis just
>> before 3.16
>>
>> I wrote some docs (with exampless) in the QGIS Documentation:
>>
>> https://github.com/qgis/QGIS-Documentation/pull/5521
>>
>> It still fails in Travis, but in this commit is example code:
>>
>>
>> https://github.com/qgis/QGIS-Documentation/blob/4ebc236d06a7ff2b6454ea5b8f94929b2b8423d0/docs/pyqgis_developer_cookbook/temporal_data.rst
>>
>> Hope this helps,
>>
>> Regards,
>>
>> Richard Duivenvoorde
>>
>>
>> On 11/6/20 2:47 PM, Luiz Motta wrote:
>> > Hi All,
>> >
>> >  I would like to change the values of the Temporal Controller Panel in
>> my plugin.
>> >
>> > How do I change the Range of datetimes and the values of step and unit
>> time using python?
>> >
>> >  Regards,
>> >  Luiz Motta
>> >
>> > ___
>> > QGIS-Developer mailing list
>> > QGIS-Developer@lists.osgeo.org
>> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> >
>>
>> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
--
​

Tim Sutton
Visit http://kartoza.com to find out about open source:
 * Desktop GIS programming services
 * Geospatial web development
* GIS Training
* Consulting Services
Tim is a member of the QGIS Project Steering Committee
---
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Using QgsWms* Classes From My Custom App

2020-10-27 Thread Alessandro Pasotti
No: those classes are not part of public API, symbols are not exported.


On Tue, Oct 27, 2020 at 11:35 AM Nedret Ozay  wrote:
>
> Hi there,
> I'm creating a custom cpp application using QGis framework. Nowadays I'm 
> trying to get a map from map server using WMS protocol.
> I've tried to use QgsWms* classes (QgsWmsCapabilitiesDownload etc.) in my 
> project but I came across with some linking problems. Is there any way to use 
> QgsWms* classes outside of the Qgis application? Any library including those 
> QgsWms* classes?
>
> Details can be found on the following issue:
>
> https://stackoverflow.com/questions/64523891/using-qgiswms-classes-in-my-standaone-cpp-application
>
> Thanks in advance.
>
> --
> Nedret ÖZAY
>
>
> --
> Nedret ÖZAY
>
>
> --
> Nedret ÖZAY
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: GPKG and FID -- can we fix this mess?

2020-10-15 Thread Even Rouault
> 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 ?

That would be a provider-level change I guess ? Why not, but I'm still puzzled 
why we need something in the GPKG case and not with PostgreSQL with a integer 
primary key.
One difference I see is that in the GPKG case, when creating features through 
the GUI, I can set a new feature to a fid value already taken, whereas if I 
try to do the same with a Postgres layer, the GUI prevents me from doing that. 
There must be some extra hint that the Postgres provider provides, and GPKG 
does not.
(I can even see that in the same edit session If I try to create 2 features 
with the same fid value with a Postgres layer, the GUI prevents me from doing 
that, so before trying any INSERT)

Hum, one difference I can see is that QgsOgrProvider::skipConstraintCheck() 
does not take into account providerProperty( EvaluateDefaultValues, false )  
whereas QgsPostgresProvider::skipConstraintCheck() does. And in the
QgsOgrProvider::skipConstraintCheck() case, for the fid column, the return of 
the method will be true ( mDefaultValues being equal to tr( "Autogenerate" ), 
so not empty )

Interestingly, putting the same implementation as the postgres provider makes 
GPKG behave as it for the scenarios presented above !
Let's see how CI likes that:
https://github.com/qgis/QGIS/pull/39388

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Plugin Development for accessing PostgresSQL Database in a QtableWidget in QT Designer

2020-09-07 Thread Richard Duivenvoorde
On 9/6/20 8:08 PM, SOHINI GOSWAMI wrote:
> Dear Developers,
> I would request to kindly help me with building a plugin using Qtablewidget 
> in QT designer. The table would retrieve a postgresql using a query 
> [Depending on the date of the date] . I have created the UI file in QT 
> designer but unable to fetch the data from the buttons click triggers in my 
> main python plugin file. It would be great if I could get a complete guide of 
> writing methods on onclick -buttons and retrive the data from Postgres 
> database.

Hi SOHINI GOSWAMI,

I think you really have to dive a little into PyQt coding.

It is hard to help without seeing what you already did. Do you maybe have your 
code on github/gitlab somewhere?

Maybe try to download some plugins and have a look into their code to get an 
idea what is needed to get a working QGIS Python plugin.

If you want to retrieve 'data' from a postgis plugin, you have to decide if you 
do that via QGIS (Features, if you can make that query into a filter) or 
directly from Postgres (you need to fetch table data yourself then using the 
psycopg2 module.

Regards,

Richard Duivenvoorde

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Compiling Problem QGis 3.12.1 on CentOS 7.6

2020-03-25 Thread Jorge Gustavo Rocha
Hi Victor,

Maybe yours qt5-qtbase-devel-5.9.7-2.el7.x86_64 is the same as mine
qtbase5-dev. I'm not on CentOS, sorry.

Your compiler is complaining about QIODevice. In my QT, QIODevice is
defined in qtbase5-dev package. I'm using QT 5.12 (not 5.9).

Try to find in your CentOS this QIODevice class.

Regards,

Jorge

On 25/03/20 11:06, Jorge Gustavo Rocha wrote:
> Hi Victor,
> 
> Have you qtbase5-dev package installed? I think it is missing in you
> system. Can you check, please?
> 
> Regards,
> 
> Jorge
> 
> On 25/03/20 10:33, Victor LOPES wrote:
>> Hello is someone can help with this case ?
>>
>> Vic
>>
>> Le 24/03/2020 à 17:42, piaff33z a écrit :
>>> Hello all, I need some help to compile and install last version of
>>> QGis 3.12.1 :-)
>>> Below my explanation about my last last blocking point.
>>>
>>> Context :
>>> My system is an CentOS Linux release 7.6.1810 (Core) on Linux
>>> 3.10.0-957.10.1.el7.x86_64 #1 SMP
>>>
>>> 
>>> Making tools
>>> -
>>> Provide by CentOS :
>>> gcc-c++-4.8.5-39.el7.x86_64
>>> libgcc-4.8.5-39.el7.x86_64
>>>
>>> Devtoolset installed if some products need to be compiled with more
>>> recent compiler :
>>> devtoolset-7-gcc-7.3.1-5.16.el7.x86_64
>>> gcc-4.8.5-39.el7.x86_64
>>> devtoolset-7-gcc-c++-7.3.1-5.16.el7.x86_64
>>>
>>> 
>>>
>>> I compiled successfully software below to have last versions
>>>
>>> lrwxrwxrwx. 1 root root    11 23 mars  15:15 gdal -> gdal-3.0.4/
>>> drwxr-xr-x. 7 root root  4096 23 mars  15:15 gdal-3.0.4
>>> lrwxrwxrwx. 1 root root    11 23 mars  15:52 grass -> grass-7.8.2
>>> drwxr-xr-x. 4 root root  4096 23 mars  15:57 grass-7.8.2
>>> lrwxrwxrwx. 1 root root    19 23 mars  17:11 libspatialite ->
>>> libspatialite-4.3.0
>>> drwxr-xr-x. 4 root root  4096 23 mars  17:11 libspatialite-4.3.0
>>> drwx--. 2 root root 16384 21 mars   2019 lost+found
>>> lrwxrwxrwx. 1 root root    10 23 mars  17:23 proj -> proj-4.9.3
>>> drwxr-xr-x. 6 root root  4096 23 mars  17:23 proj-4.9.3 ( I tried with
>>> proj-7.0.0 but is too recent for QGis 3.12.1 :-( )
>>> lrwxrwxrwx. 1 root root    11 23 mars  14:05 sqlite -> sqlite-3.32
>>> drwxr-xr-x. 6 root root  4096 23 mars  14:05 sqlite-3.32
>>>
>>> --
>>>
>>> Qt5 is provide by my distribution and I didn't try to compile it from
>>> source
>>>
>>> qca-qt5-2.1.3-3.el7.x86_64
>>> qt5-qttools-common-5.9.7-1.el7.noarch
>>> qt5-qtwebkit-devel-5.9.1-2.el7.x86_64
>>> qt5-qtwayland-devel-5.9.7-1.el7.x86_64
>>> qt5-qtbase-gui-5.9.7-2.el7.x86_64
>>> qt5-qtlocation-5.9.7-1.el7.x86_64
>>> python36-qt5-webkit-5.12.1-3.el7.x86_64
>>> qt5-qtgraphicaleffects-5.9.7-1.el7.x86_64
>>> qt5-qtquickcontrols2-devel-5.9.7-1.el7.x86_64
>>> qt5-qtstyleplugins-5.0.0-29.el7.x86_64
>>> qt5-qtbase-odbc-5.9.7-2.el7.x86_64
>>> qt5-qtserialport-5.9.7-1.el7.x86_64
>>> qt5-qtenginio-1.6.2-2.el7.x86_64
>>> qt5-qttools-devel-5.9.7-1.el7.x86_64
>>> qt5-qtaccountsservice-devel-0.1.1-3.el7.x86_64
>>> qt5-qtenginio-devel-1.6.2-2.el7.x86_64
>>> qca-qt5-gnupg-2.1.3-3.el7.x86_64
>>> qca-qt5-devel-2.1.3-3.el7.x86_64
>>> qt5-qtwebkit-5.9.1-2.el7.x86_64
>>> qt5-qttools-5.9.7-1.el7.x86_64
>>> qt5-qtimageformats-5.9.7-1.el7.x86_64
>>> qt5ct-0.35-2.el7.x86_64
>>> qt5-qtx11extras-5.9.7-1.el7.x86_64
>>> qt5-qtdeclarative-5.9.7-1.el7.x86_64
>>> qt5-qtmultimedia-5.9.7-1.el7.x86_64
>>> python36-qt5-5.12.1-3.el7.x86_64
>>> qt5-linguist-5.9.7-1.el7.x86_64
>>> qt5-qtconfiguration-0.3.0-3.el7.x86_64
>>> qt5-qt3d-5.9.7-1.el7.x86_64
>>> qt5-qtquick1-devel-5.7.1-2.2bc722agit.el7.x86_64
>>> qt5-qtwebchannel-devel-5.9.7-1.el7.x86_64
>>> qt5-qtdeclarative-static-5.9.7-1.el7.x86_64
>>> qca-qt5-pkcs11-2.1.3-3.el7.x86_64
>>> qca-qt5-nss-2.1.3-3.el7.x86_64
>>> qt5-rpm-macros-5.9.7-2.el7.noarch
>>> qt5-qtserialport-devel-5.9.7-1.el7.x86_64
>>> qt5-qttools-libs-help-5.9.7-1.el7.x86_64
>>> qt5-qtwebsockets-5.9.7-1.el7.x86_64
>>> qt5-qttools-libs-designercomponents-5.9.7-1.el7.x86_64
>>> qt5-qtscript-devel-5.9.7-1.el7.x86_64
>>> qt5-qtcanvas3d-5.9.7-1.el7.x86_64
>>> qt5-qdbusviewer-5.9.7-1.el7.x86_64
>>> qt5-qtbase-static-5.9.7-2.el7.x86_64
>>> qt5-qtsensors-devel-5.9.7-1.el7.x86_64
>>> qca-qt5-cyrus-sasl-2.1.3-3.el7.x86_64
>>> qt5-qtbase-devel-5.9.7-2.el7.x86_64
>>> qt5-qtsvg-devel-5.9.7-1.el7.x86_64
>>> qt5-qttools-libs-designer-5.9.7-1.el7.x86_64
>>> qt5-designer-5.9.7-1.el7.x86_64
>>> qt5-qtquick1-5.7.1-2.2bc722agit.el7.x86_64
>>> qt5-qtquickcontrols-5.9.7-1.el7.x86_64
>>> qt5-qtbase-mysql-5.9.7-2.el7.x86_64
>>> qt5-qtbase-postgresql-5.9.7-2.el7.x86_64
>>> qca-qt5-softstore-2.1.3-3.el7.x86_64
>>> qt5-qtbase-common-5.9.7-2.el7.noarch
>>> qt5-qtserialbus-5.9.7-1.el7.x86_64
>>> qt5-qtwebchannel-5.9.7-1.el7.x86_64
>>> python-qt5-rpm-macros-5.12.1-3.el7.noarch
>>> qt5-qtlocation-devel-5.9.7-1.el7.x86_64
>>> qt5-qtx11extras-devel-5.9.7-1.el7.x86_64
>>> qt5-qtxmlpatterns-devel-5.9.7-1.el7.x86_64
>>> qt5-qt3d-devel-5.9.7-1.el7.x86_64
>>> qt5-qtwebsockets-devel-5.9.7-1.el7.x86_64
>>> qca-qt5-gcrypt-2.1.3-3.el7.x86_64
>>> qt5-qtserialbus-devel-5.9.7-1.el7.x86_64
>>> 

Re: [QGIS-Developer] Fwd: Compiling Problem QGis 3.12.1 on CentOS 7.6

2020-03-25 Thread Jorge Gustavo Rocha
Hi Victor,

Have you qtbase5-dev package installed? I think it is missing in you
system. Can you check, please?

Regards,

Jorge

On 25/03/20 10:33, Victor LOPES wrote:
> Hello is someone can help with this case ?
> 
> Vic
> 
> Le 24/03/2020 à 17:42, piaff33z a écrit :
>> Hello all, I need some help to compile and install last version of
>> QGis 3.12.1 :-)
>> Below my explanation about my last last blocking point.
>>
>> Context :
>> My system is an CentOS Linux release 7.6.1810 (Core) on Linux
>> 3.10.0-957.10.1.el7.x86_64 #1 SMP
>>
>> 
>> Making tools
>> -
>> Provide by CentOS :
>> gcc-c++-4.8.5-39.el7.x86_64
>> libgcc-4.8.5-39.el7.x86_64
>>
>> Devtoolset installed if some products need to be compiled with more
>> recent compiler :
>> devtoolset-7-gcc-7.3.1-5.16.el7.x86_64
>> gcc-4.8.5-39.el7.x86_64
>> devtoolset-7-gcc-c++-7.3.1-5.16.el7.x86_64
>>
>> 
>>
>> I compiled successfully software below to have last versions
>>
>> lrwxrwxrwx. 1 root root    11 23 mars  15:15 gdal -> gdal-3.0.4/
>> drwxr-xr-x. 7 root root  4096 23 mars  15:15 gdal-3.0.4
>> lrwxrwxrwx. 1 root root    11 23 mars  15:52 grass -> grass-7.8.2
>> drwxr-xr-x. 4 root root  4096 23 mars  15:57 grass-7.8.2
>> lrwxrwxrwx. 1 root root    19 23 mars  17:11 libspatialite ->
>> libspatialite-4.3.0
>> drwxr-xr-x. 4 root root  4096 23 mars  17:11 libspatialite-4.3.0
>> drwx--. 2 root root 16384 21 mars   2019 lost+found
>> lrwxrwxrwx. 1 root root    10 23 mars  17:23 proj -> proj-4.9.3
>> drwxr-xr-x. 6 root root  4096 23 mars  17:23 proj-4.9.3 ( I tried with
>> proj-7.0.0 but is too recent for QGis 3.12.1 :-( )
>> lrwxrwxrwx. 1 root root    11 23 mars  14:05 sqlite -> sqlite-3.32
>> drwxr-xr-x. 6 root root  4096 23 mars  14:05 sqlite-3.32
>>
>> --
>>
>> Qt5 is provide by my distribution and I didn't try to compile it from
>> source
>>
>> qca-qt5-2.1.3-3.el7.x86_64
>> qt5-qttools-common-5.9.7-1.el7.noarch
>> qt5-qtwebkit-devel-5.9.1-2.el7.x86_64
>> qt5-qtwayland-devel-5.9.7-1.el7.x86_64
>> qt5-qtbase-gui-5.9.7-2.el7.x86_64
>> qt5-qtlocation-5.9.7-1.el7.x86_64
>> python36-qt5-webkit-5.12.1-3.el7.x86_64
>> qt5-qtgraphicaleffects-5.9.7-1.el7.x86_64
>> qt5-qtquickcontrols2-devel-5.9.7-1.el7.x86_64
>> qt5-qtstyleplugins-5.0.0-29.el7.x86_64
>> qt5-qtbase-odbc-5.9.7-2.el7.x86_64
>> qt5-qtserialport-5.9.7-1.el7.x86_64
>> qt5-qtenginio-1.6.2-2.el7.x86_64
>> qt5-qttools-devel-5.9.7-1.el7.x86_64
>> qt5-qtaccountsservice-devel-0.1.1-3.el7.x86_64
>> qt5-qtenginio-devel-1.6.2-2.el7.x86_64
>> qca-qt5-gnupg-2.1.3-3.el7.x86_64
>> qca-qt5-devel-2.1.3-3.el7.x86_64
>> qt5-qtwebkit-5.9.1-2.el7.x86_64
>> qt5-qttools-5.9.7-1.el7.x86_64
>> qt5-qtimageformats-5.9.7-1.el7.x86_64
>> qt5ct-0.35-2.el7.x86_64
>> qt5-qtx11extras-5.9.7-1.el7.x86_64
>> qt5-qtdeclarative-5.9.7-1.el7.x86_64
>> qt5-qtmultimedia-5.9.7-1.el7.x86_64
>> python36-qt5-5.12.1-3.el7.x86_64
>> qt5-linguist-5.9.7-1.el7.x86_64
>> qt5-qtconfiguration-0.3.0-3.el7.x86_64
>> qt5-qt3d-5.9.7-1.el7.x86_64
>> qt5-qtquick1-devel-5.7.1-2.2bc722agit.el7.x86_64
>> qt5-qtwebchannel-devel-5.9.7-1.el7.x86_64
>> qt5-qtdeclarative-static-5.9.7-1.el7.x86_64
>> qca-qt5-pkcs11-2.1.3-3.el7.x86_64
>> qca-qt5-nss-2.1.3-3.el7.x86_64
>> qt5-rpm-macros-5.9.7-2.el7.noarch
>> qt5-qtserialport-devel-5.9.7-1.el7.x86_64
>> qt5-qttools-libs-help-5.9.7-1.el7.x86_64
>> qt5-qtwebsockets-5.9.7-1.el7.x86_64
>> qt5-qttools-libs-designercomponents-5.9.7-1.el7.x86_64
>> qt5-qtscript-devel-5.9.7-1.el7.x86_64
>> qt5-qtcanvas3d-5.9.7-1.el7.x86_64
>> qt5-qdbusviewer-5.9.7-1.el7.x86_64
>> qt5-qtbase-static-5.9.7-2.el7.x86_64
>> qt5-qtsensors-devel-5.9.7-1.el7.x86_64
>> qca-qt5-cyrus-sasl-2.1.3-3.el7.x86_64
>> qt5-qtbase-devel-5.9.7-2.el7.x86_64
>> qt5-qtsvg-devel-5.9.7-1.el7.x86_64
>> qt5-qttools-libs-designer-5.9.7-1.el7.x86_64
>> qt5-designer-5.9.7-1.el7.x86_64
>> qt5-qtquick1-5.7.1-2.2bc722agit.el7.x86_64
>> qt5-qtquickcontrols-5.9.7-1.el7.x86_64
>> qt5-qtbase-mysql-5.9.7-2.el7.x86_64
>> qt5-qtbase-postgresql-5.9.7-2.el7.x86_64
>> qca-qt5-softstore-2.1.3-3.el7.x86_64
>> qt5-qtbase-common-5.9.7-2.el7.noarch
>> qt5-qtserialbus-5.9.7-1.el7.x86_64
>> qt5-qtwebchannel-5.9.7-1.el7.x86_64
>> python-qt5-rpm-macros-5.12.1-3.el7.noarch
>> qt5-qtlocation-devel-5.9.7-1.el7.x86_64
>> qt5-qtx11extras-devel-5.9.7-1.el7.x86_64
>> qt5-qtxmlpatterns-devel-5.9.7-1.el7.x86_64
>> qt5-qt3d-devel-5.9.7-1.el7.x86_64
>> qt5-qtwebsockets-devel-5.9.7-1.el7.x86_64
>> qca-qt5-gcrypt-2.1.3-3.el7.x86_64
>> qt5-qtserialbus-devel-5.9.7-1.el7.x86_64
>> python36-pyqt5-sip-4.19.16-3.el7.x86_64
>> qt5-qtscript-5.9.7-1.el7.x86_64
>> qt5-qtconnectivity-devel-5.9.7-1.el7.x86_64
>> qca-qt5-logger-2.1.3-3.el7.x86_64
>> qt5-qtsvg-5.9.7-1.el7.x86_64
>> qt5-qtconnectivity-5.9.7-1.el7.x86_64
>> qt5-doctools-5.9.7-1.el7.x86_64
>> qt5-qtaccountsservice-0.1.1-3.el7.x86_64
>> qt5-assistant-5.9.7-1.el7.x86_64
>> qca-qt5-botan-2.1.3-3.el7.x86_64
>> qca-qt5-ossl-2.1.3-3.el7.x86_64
>> qt5-qtbase-5.9.7-2.el7.x86_64
>> qt5-qtsensors-5.9.7-1.el7.x86_64
>> 

Re: [QGIS-Developer] Fwd: Compiling Problem QGis 3.12.1 on CentOS 7.6

2020-03-25 Thread Victor LOPES

Hello is someone can help with this case ?

Vic

Le 24/03/2020 à 17:42, piaff33z a écrit :
Hello all, I need some help to compile and install last version of 
QGis 3.12.1 :-)

Below my explanation about my last last blocking point.

Context :
My system is an CentOS Linux release 7.6.1810 (Core) on Linux 
3.10.0-957.10.1.el7.x86_64 #1 SMP



Making tools
-
Provide by CentOS :
gcc-c++-4.8.5-39.el7.x86_64
libgcc-4.8.5-39.el7.x86_64

Devtoolset installed if some products need to be compiled with more 
recent compiler :

devtoolset-7-gcc-7.3.1-5.16.el7.x86_64
gcc-4.8.5-39.el7.x86_64
devtoolset-7-gcc-c++-7.3.1-5.16.el7.x86_64



I compiled successfully software below to have last versions

lrwxrwxrwx. 1 root root    11 23 mars  15:15 gdal -> gdal-3.0.4/
drwxr-xr-x. 7 root root  4096 23 mars  15:15 gdal-3.0.4
lrwxrwxrwx. 1 root root    11 23 mars  15:52 grass -> grass-7.8.2
drwxr-xr-x. 4 root root  4096 23 mars  15:57 grass-7.8.2
lrwxrwxrwx. 1 root root    19 23 mars  17:11 libspatialite -> 
libspatialite-4.3.0

drwxr-xr-x. 4 root root  4096 23 mars  17:11 libspatialite-4.3.0
drwx--. 2 root root 16384 21 mars   2019 lost+found
lrwxrwxrwx. 1 root root    10 23 mars  17:23 proj -> proj-4.9.3
drwxr-xr-x. 6 root root  4096 23 mars  17:23 proj-4.9.3 ( I tried with 
proj-7.0.0 but is too recent for QGis 3.12.1 :-( )

lrwxrwxrwx. 1 root root    11 23 mars  14:05 sqlite -> sqlite-3.32
drwxr-xr-x. 6 root root  4096 23 mars  14:05 sqlite-3.32

--

Qt5 is provide by my distribution and I didn't try to compile it from 
source


qca-qt5-2.1.3-3.el7.x86_64
qt5-qttools-common-5.9.7-1.el7.noarch
qt5-qtwebkit-devel-5.9.1-2.el7.x86_64
qt5-qtwayland-devel-5.9.7-1.el7.x86_64
qt5-qtbase-gui-5.9.7-2.el7.x86_64
qt5-qtlocation-5.9.7-1.el7.x86_64
python36-qt5-webkit-5.12.1-3.el7.x86_64
qt5-qtgraphicaleffects-5.9.7-1.el7.x86_64
qt5-qtquickcontrols2-devel-5.9.7-1.el7.x86_64
qt5-qtstyleplugins-5.0.0-29.el7.x86_64
qt5-qtbase-odbc-5.9.7-2.el7.x86_64
qt5-qtserialport-5.9.7-1.el7.x86_64
qt5-qtenginio-1.6.2-2.el7.x86_64
qt5-qttools-devel-5.9.7-1.el7.x86_64
qt5-qtaccountsservice-devel-0.1.1-3.el7.x86_64
qt5-qtenginio-devel-1.6.2-2.el7.x86_64
qca-qt5-gnupg-2.1.3-3.el7.x86_64
qca-qt5-devel-2.1.3-3.el7.x86_64
qt5-qtwebkit-5.9.1-2.el7.x86_64
qt5-qttools-5.9.7-1.el7.x86_64
qt5-qtimageformats-5.9.7-1.el7.x86_64
qt5ct-0.35-2.el7.x86_64
qt5-qtx11extras-5.9.7-1.el7.x86_64
qt5-qtdeclarative-5.9.7-1.el7.x86_64
qt5-qtmultimedia-5.9.7-1.el7.x86_64
python36-qt5-5.12.1-3.el7.x86_64
qt5-linguist-5.9.7-1.el7.x86_64
qt5-qtconfiguration-0.3.0-3.el7.x86_64
qt5-qt3d-5.9.7-1.el7.x86_64
qt5-qtquick1-devel-5.7.1-2.2bc722agit.el7.x86_64
qt5-qtwebchannel-devel-5.9.7-1.el7.x86_64
qt5-qtdeclarative-static-5.9.7-1.el7.x86_64
qca-qt5-pkcs11-2.1.3-3.el7.x86_64
qca-qt5-nss-2.1.3-3.el7.x86_64
qt5-rpm-macros-5.9.7-2.el7.noarch
qt5-qtserialport-devel-5.9.7-1.el7.x86_64
qt5-qttools-libs-help-5.9.7-1.el7.x86_64
qt5-qtwebsockets-5.9.7-1.el7.x86_64
qt5-qttools-libs-designercomponents-5.9.7-1.el7.x86_64
qt5-qtscript-devel-5.9.7-1.el7.x86_64
qt5-qtcanvas3d-5.9.7-1.el7.x86_64
qt5-qdbusviewer-5.9.7-1.el7.x86_64
qt5-qtbase-static-5.9.7-2.el7.x86_64
qt5-qtsensors-devel-5.9.7-1.el7.x86_64
qca-qt5-cyrus-sasl-2.1.3-3.el7.x86_64
qt5-qtbase-devel-5.9.7-2.el7.x86_64
qt5-qtsvg-devel-5.9.7-1.el7.x86_64
qt5-qttools-libs-designer-5.9.7-1.el7.x86_64
qt5-designer-5.9.7-1.el7.x86_64
qt5-qtquick1-5.7.1-2.2bc722agit.el7.x86_64
qt5-qtquickcontrols-5.9.7-1.el7.x86_64
qt5-qtbase-mysql-5.9.7-2.el7.x86_64
qt5-qtbase-postgresql-5.9.7-2.el7.x86_64
qca-qt5-softstore-2.1.3-3.el7.x86_64
qt5-qtbase-common-5.9.7-2.el7.noarch
qt5-qtserialbus-5.9.7-1.el7.x86_64
qt5-qtwebchannel-5.9.7-1.el7.x86_64
python-qt5-rpm-macros-5.12.1-3.el7.noarch
qt5-qtlocation-devel-5.9.7-1.el7.x86_64
qt5-qtx11extras-devel-5.9.7-1.el7.x86_64
qt5-qtxmlpatterns-devel-5.9.7-1.el7.x86_64
qt5-qt3d-devel-5.9.7-1.el7.x86_64
qt5-qtwebsockets-devel-5.9.7-1.el7.x86_64
qca-qt5-gcrypt-2.1.3-3.el7.x86_64
qt5-qtserialbus-devel-5.9.7-1.el7.x86_64
python36-pyqt5-sip-4.19.16-3.el7.x86_64
qt5-qtscript-5.9.7-1.el7.x86_64
qt5-qtconnectivity-devel-5.9.7-1.el7.x86_64
qca-qt5-logger-2.1.3-3.el7.x86_64
qt5-qtsvg-5.9.7-1.el7.x86_64
qt5-qtconnectivity-5.9.7-1.el7.x86_64
qt5-doctools-5.9.7-1.el7.x86_64
qt5-qtaccountsservice-0.1.1-3.el7.x86_64
qt5-assistant-5.9.7-1.el7.x86_64
qca-qt5-botan-2.1.3-3.el7.x86_64
qca-qt5-ossl-2.1.3-3.el7.x86_64
qt5-qtbase-5.9.7-2.el7.x86_64
qt5-qtsensors-5.9.7-1.el7.x86_64
qt5-qtdeclarative-devel-5.9.7-1.el7.x86_64
qt5-qtquickcontrols2-5.9.7-1.el7.x86_64
qt5-qtconfiguration-devel-0.3.0-3.el7.x86_64
qt5-qtxmlpatterns-5.9.7-1.el7.x86_64
python36-qt5-base-5.12.1-3.el7.x86_64
qt5-qtwayland-5.9.7-1.el7.x86_64
qt5-qtmultimedia-devel-5.9.7-1.el7.x86_64
qt5-qttools-static-5.9.7-1.el7.x86_64

--

Result after compiliing with cmake3 --version
cmake3 version 3.14.6

[root@build-master]# cmake3 .. -DGDAL_LIBRARY=/opt/gdal/lib 
-DPROJ_LIBRARY=/opt/proj/lib -DPROJ_INCLUDE_DIR=/opt/proj/include 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-24 Thread Jürgen E . Fischer
Hi Anita,

On Fri, 24. Jan 2020 at 14:12:34 +, Anita Graser wrote:
> Is the following "unknown publisher" issue expected or a regression?
> 
> https://twitter.com/atanas/status/1220709096992710657

Ouch, the OSGeo certificate expired on Nov  6 12:00:00 2019 GMT.


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-24 Thread Anita Graser
Is the following "unknown publisher" issue expected or a regression?

https://twitter.com/atanas/status/1220709096992710657

Regards,
Anita





On Fri, Jan 24, 2020 at 9:06 AM Paolo Cavallini 
wrote:

> Thanks a lot everybody, nice cooperation!
> Cheers.
>
> On 24 January 2020 13:05:09 GMT+04:00, Mathieu Pellerin <
> nirvn.a...@gmail.com> wrote:
>>
>> Fantastic, thank you.
>>
>> On Fri, Jan 24, 2020, 15:48 Anita Graser  wrote:
>>
>>> I can do it.
>>>
>>> Regards,
>>> Anita
>>>
>>> On Fri, Jan 24, 2020 at 12:15 AM Mathieu Pellerin 
>>> wrote:
>>>
 Jürgen, thanks for the successful re-release of 3.10.2.

 Paolo, Anita, who is in a position to publish the drafted post on the
 blog?


 On Thu, Jan 23, 2020, 10:59 Mathieu Pellerin 
 wrote:

> +1 to that plan. We're 33% done already since the blocking PR has been
> merged.
>
> On Wed, Jan 22, 2020 at 6:47 PM Matthias Kuhn 
> wrote:
>
>> How about
>>
>> - Waiting for https://github.com/qgis/QGIS/pull/33971
>>
>> - Releasing 3.10.3
>>
>> - Announce on twitter, blog, news panel
>>
>> Clear cut for everyone (including those 95% of our users not
>> following [qgis on] twitter)
>>
>> Matthias
>> On 1/22/20 12:39 PM, Anita Graser wrote:
>>
>> Is it time to send an update on Twitter yet? I don't see new
>> installers at https://qgis.org/downloads/
>>
>> Regards,
>> Anita
>>
>> On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin <
>> nirvn.a...@gmail.com> wrote:
>>
>>> I think the QGIS twitter account already mentioned that the 3.10.2
>>> installer had been retired due to issues and re-build.
>>>
>>> On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:
>>>
 Hi all,

 Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those
 who have already downloaded the broken 3.10.2 may not think to update.

 Regards,
 Harrissou

 Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin <
 nirvn.a...@gmail.com> a écrit :

> Matthias,
>
> Good idea.
>
> Math
>
> On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
> wrote:
>
>> Hi Mathieu,
>>
>> Thanks a lot. It reads very well!
>>
>> Something that I'd like to add is that in case of still finding a
>> bug, users should file issues and to mention proximity of LTR 
>> replacement.
>> If you still happen to find QGIS behaving in an unexpected way,
>> please let us know on https://github.com/qgis/QGIS/issues
>> 
>> as always. We are very happy that QGIS 3.10 is now in shape to 
>> replace 3.4
>> as LTR in a month time.
>>
>> Bests
>> Matthias
>>
>>
>> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>>
>> Paolo, here's the draft blog post:
>>
>> *Public Service Announcement: Update to the latest point release
>> now*
>> --
>> QGIS users who have adopted the 3.10 version when initially
>> released at the end of October 2019 have likely noticed a sharp drop 
>> in
>> reliability. The underlying issues have now been addressed in 
>> 3.10.2, all
>> users are advised to update *now*.
>>
>> When QGIS 3.10 was first released in the end of October 2019, a
>> pair of libraries – namely GDAL and PROJ – were updated to their
>> next-generation versions. The advantages are plenty: GeoPDF export[1]
>> support, more accurate coordinate transformation, etc. For those
>> interested, more technical information on this is available here[2].
>>
>> The update of these crucial libraries led to a number of
>> regressions. While we expected some issues to arise, the seriousness 
>> of the
>> disruption caught us off guard. Yet, it was also somewhat 
>> inevitable: QGIS
>> is the first large GIS project to expose these next-generation 
>> libraries to
>> the masses. The large number of QGIS users across the globe were
>> essentially stress testing both new code within QGIS as well as the
>> libraries themselves.
>>
>> Thanks to dedicated users taking time to file in report and the
>> community helping out as well as our project sponsors for allowing 
>> us to
>> fund development time, developers have been able to fix all known
>> regressions in both in QGIS as well as underlying GDAL and PROJ 
>> libraries,
>> benefiting a large number of open source projects.
>>

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-24 Thread Paolo Cavallini
Thanks a lot everybody, nice cooperation!
Cheers.

On 24 January 2020 13:05:09 GMT+04:00, Mathieu Pellerin  
wrote:
>Fantastic, thank you.
>
>On Fri, Jan 24, 2020, 15:48 Anita Graser  wrote:
>
>> I can do it.
>>
>> Regards,
>> Anita
>>
>> On Fri, Jan 24, 2020 at 12:15 AM Mathieu Pellerin
>
>> wrote:
>>
>>> Jürgen, thanks for the successful re-release of 3.10.2.
>>>
>>> Paolo, Anita, who is in a position to publish the drafted post on
>the
>>> blog?
>>>
>>>
>>> On Thu, Jan 23, 2020, 10:59 Mathieu Pellerin 
>>> wrote:
>>>
 +1 to that plan. We're 33% done already since the blocking PR has
>been
 merged.

 On Wed, Jan 22, 2020 at 6:47 PM Matthias Kuhn 
 wrote:

> How about
>
> - Waiting for https://github.com/qgis/QGIS/pull/33971
>
> - Releasing 3.10.3
>
> - Announce on twitter, blog, news panel
>
> Clear cut for everyone (including those 95% of our users not
>following
> [qgis on] twitter)
>
> Matthias
> On 1/22/20 12:39 PM, Anita Graser wrote:
>
> Is it time to send an update on Twitter yet? I don't see new
>installers
> at https://qgis.org/downloads/
>
> Regards,
> Anita
>
> On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin
>
> wrote:
>
>> I think the QGIS twitter account already mentioned that the
>3.10.2
>> installer had been retired due to issues and re-build.
>>
>> On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:
>>
>>> Hi all,
>>>
>>> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because
>those
>>> who have already downloaded the broken 3.10.2 may not think to
>update.
>>>
>>> Regards,
>>> Harrissou
>>>
>>> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin
>
>>> a écrit :
>>>
 Matthias,

 Good idea.

 Math

 On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn
>
 wrote:

> Hi Mathieu,
>
> Thanks a lot. It reads very well!
>
> Something that I'd like to add is that in case of still
>finding a
> bug, users should file issues and to mention proximity of LTR
>replacement.
> If you still happen to find QGIS behaving in an unexpected
>way,
> please let us know on https://github.com/qgis/QGIS/issues
>
>
> as always. We are very happy that QGIS 3.10 is now in shape to
>replace 3.4
> as LTR in a month time.
>
> Bests
> Matthias
>
>
> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>
> Paolo, here's the draft blog post:
>
> *Public Service Announcement: Update to the latest point
>release
> now*
> --
> QGIS users who have adopted the 3.10 version when initially
> released at the end of October 2019 have likely noticed a
>sharp drop in
> reliability. The underlying issues have now been addressed in
>3.10.2, all
> users are advised to update *now*.
>
> When QGIS 3.10 was first released in the end of October 2019,
>a
> pair of libraries – namely GDAL and PROJ – were updated to
>their
> next-generation versions. The advantages are plenty: GeoPDF
>export[1]
> support, more accurate coordinate transformation, etc. For
>those
> interested, more technical information on this is available
>here[2].
>
> The update of these crucial libraries led to a number of
> regressions. While we expected some issues to arise, the
>seriousness of the
> disruption caught us off guard. Yet, it was also somewhat
>inevitable: QGIS
> is the first large GIS project to expose these next-generation
>libraries to
> the masses. The large number of QGIS users across the globe
>were
> essentially stress testing both new code within QGIS as well
>as the
> libraries themselves.
>
> Thanks to dedicated users taking time to file in report and
>the
> community helping out as well as our project sponsors for
>allowing us to
> fund development time, developers have been able to fix all
>known
> regressions in both in QGIS as well as underlying GDAL and
>PROJ libraries,
> benefiting a large number of open source projects.
>
> As a result of this collective effort by the community, QGIS
>3.10.2
> is now back to being the reliable and stable GIS software we
>all love. As
> such, we cannot stress enough the important of updating now.
>
> Once again, thanks to our community of testers, sponsors, and
> developers for their countless hours and efforts in making
>QGIS better.
>
> Happy mapping!
>
> [1] 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-24 Thread Mathieu Pellerin
Fantastic, thank you.

On Fri, Jan 24, 2020, 15:48 Anita Graser  wrote:

> I can do it.
>
> Regards,
> Anita
>
> On Fri, Jan 24, 2020 at 12:15 AM Mathieu Pellerin 
> wrote:
>
>> Jürgen, thanks for the successful re-release of 3.10.2.
>>
>> Paolo, Anita, who is in a position to publish the drafted post on the
>> blog?
>>
>>
>> On Thu, Jan 23, 2020, 10:59 Mathieu Pellerin 
>> wrote:
>>
>>> +1 to that plan. We're 33% done already since the blocking PR has been
>>> merged.
>>>
>>> On Wed, Jan 22, 2020 at 6:47 PM Matthias Kuhn 
>>> wrote:
>>>
 How about

 - Waiting for https://github.com/qgis/QGIS/pull/33971

 - Releasing 3.10.3

 - Announce on twitter, blog, news panel

 Clear cut for everyone (including those 95% of our users not following
 [qgis on] twitter)

 Matthias
 On 1/22/20 12:39 PM, Anita Graser wrote:

 Is it time to send an update on Twitter yet? I don't see new installers
 at https://qgis.org/downloads/

 Regards,
 Anita

 On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin 
 wrote:

> I think the QGIS twitter account already mentioned that the 3.10.2
> installer had been retired due to issues and re-build.
>
> On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:
>
>> Hi all,
>>
>> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those
>> who have already downloaded the broken 3.10.2 may not think to update.
>>
>> Regards,
>> Harrissou
>>
>> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin 
>> a écrit :
>>
>>> Matthias,
>>>
>>> Good idea.
>>>
>>> Math
>>>
>>> On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
>>> wrote:
>>>
 Hi Mathieu,

 Thanks a lot. It reads very well!

 Something that I'd like to add is that in case of still finding a
 bug, users should file issues and to mention proximity of LTR 
 replacement.
 If you still happen to find QGIS behaving in an unexpected way,
 please let us know on https://github.com/qgis/QGIS/issues
 
 as always. We are very happy that QGIS 3.10 is now in shape to replace 
 3.4
 as LTR in a month time.

 Bests
 Matthias


 On 1/22/20 10:58 AM, Mathieu Pellerin wrote:

 Paolo, here's the draft blog post:

 *Public Service Announcement: Update to the latest point release
 now*
 --
 QGIS users who have adopted the 3.10 version when initially
 released at the end of October 2019 have likely noticed a sharp drop in
 reliability. The underlying issues have now been addressed in 3.10.2, 
 all
 users are advised to update *now*.

 When QGIS 3.10 was first released in the end of October 2019, a
 pair of libraries – namely GDAL and PROJ – were updated to their
 next-generation versions. The advantages are plenty: GeoPDF export[1]
 support, more accurate coordinate transformation, etc. For those
 interested, more technical information on this is available here[2].

 The update of these crucial libraries led to a number of
 regressions. While we expected some issues to arise, the seriousness 
 of the
 disruption caught us off guard. Yet, it was also somewhat inevitable: 
 QGIS
 is the first large GIS project to expose these next-generation 
 libraries to
 the masses. The large number of QGIS users across the globe were
 essentially stress testing both new code within QGIS as well as the
 libraries themselves.

 Thanks to dedicated users taking time to file in report and the
 community helping out as well as our project sponsors for allowing us 
 to
 fund development time, developers have been able to fix all known
 regressions in both in QGIS as well as underlying GDAL and PROJ 
 libraries,
 benefiting a large number of open source projects.

 As a result of this collective effort by the community, QGIS 3.10.2
 is now back to being the reliable and stable GIS software we all love. 
 As
 such, we cannot stress enough the important of updating now.

 Once again, thanks to our community of testers, sponsors, and
 developers for their countless hours and efforts in making QGIS better.

 Happy mapping!

 [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
 [2] https://gdalbarn.com/

 On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini <
 cavall...@faunalia.it> wrote:

> Fully 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-24 Thread Anita Graser
I can do it.

Regards,
Anita

On Fri, Jan 24, 2020 at 12:15 AM Mathieu Pellerin 
wrote:

> Jürgen, thanks for the successful re-release of 3.10.2.
>
> Paolo, Anita, who is in a position to publish the drafted post on the blog?
>
>
> On Thu, Jan 23, 2020, 10:59 Mathieu Pellerin  wrote:
>
>> +1 to that plan. We're 33% done already since the blocking PR has been
>> merged.
>>
>> On Wed, Jan 22, 2020 at 6:47 PM Matthias Kuhn 
>> wrote:
>>
>>> How about
>>>
>>> - Waiting for https://github.com/qgis/QGIS/pull/33971
>>>
>>> - Releasing 3.10.3
>>>
>>> - Announce on twitter, blog, news panel
>>>
>>> Clear cut for everyone (including those 95% of our users not following
>>> [qgis on] twitter)
>>>
>>> Matthias
>>> On 1/22/20 12:39 PM, Anita Graser wrote:
>>>
>>> Is it time to send an update on Twitter yet? I don't see new installers
>>> at https://qgis.org/downloads/
>>>
>>> Regards,
>>> Anita
>>>
>>> On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin 
>>> wrote:
>>>
 I think the QGIS twitter account already mentioned that the 3.10.2
 installer had been retired due to issues and re-build.

 On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:

> Hi all,
>
> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those
> who have already downloaded the broken 3.10.2 may not think to update.
>
> Regards,
> Harrissou
>
> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin 
> a écrit :
>
>> Matthias,
>>
>> Good idea.
>>
>> Math
>>
>> On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
>> wrote:
>>
>>> Hi Mathieu,
>>>
>>> Thanks a lot. It reads very well!
>>>
>>> Something that I'd like to add is that in case of still finding a
>>> bug, users should file issues and to mention proximity of LTR 
>>> replacement.
>>> If you still happen to find QGIS behaving in an unexpected way,
>>> please let us know on https://github.com/qgis/QGIS/issues
>>> 
>>> as always. We are very happy that QGIS 3.10 is now in shape to replace 
>>> 3.4
>>> as LTR in a month time.
>>>
>>> Bests
>>> Matthias
>>>
>>>
>>> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>>>
>>> Paolo, here's the draft blog post:
>>>
>>> *Public Service Announcement: Update to the latest point release now*
>>> --
>>> QGIS users who have adopted the 3.10 version when initially released
>>> at the end of October 2019 have likely noticed a sharp drop in 
>>> reliability.
>>> The underlying issues have now been addressed in 3.10.2, all users are
>>> advised to update *now*.
>>>
>>> When QGIS 3.10 was first released in the end of October 2019, a pair
>>> of libraries – namely GDAL and PROJ – were updated to their 
>>> next-generation
>>> versions. The advantages are plenty: GeoPDF export[1] support, more
>>> accurate coordinate transformation, etc. For those interested, more
>>> technical information on this is available here[2].
>>>
>>> The update of these crucial libraries led to a number of
>>> regressions. While we expected some issues to arise, the seriousness of 
>>> the
>>> disruption caught us off guard. Yet, it was also somewhat inevitable: 
>>> QGIS
>>> is the first large GIS project to expose these next-generation 
>>> libraries to
>>> the masses. The large number of QGIS users across the globe were
>>> essentially stress testing both new code within QGIS as well as the
>>> libraries themselves.
>>>
>>> Thanks to dedicated users taking time to file in report and the
>>> community helping out as well as our project sponsors for allowing us to
>>> fund development time, developers have been able to fix all known
>>> regressions in both in QGIS as well as underlying GDAL and PROJ 
>>> libraries,
>>> benefiting a large number of open source projects.
>>>
>>> As a result of this collective effort by the community, QGIS 3.10.2
>>> is now back to being the reliable and stable GIS software we all love. 
>>> As
>>> such, we cannot stress enough the important of updating now.
>>>
>>> Once again, thanks to our community of testers, sponsors, and
>>> developers for their countless hours and efforts in making QGIS better.
>>>
>>> Happy mapping!
>>>
>>> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
>>> [2] https://gdalbarn.com/
>>>
>>> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini <
>>> cavall...@faunalia.it> wrote:
>>>
 Fully agreed. Mathieu, would you like to write it?
 Thanks.

 On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
 nirvn.a...@gmail.com> wrote:
>
> +100 on all that's been said here.

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-23 Thread Mathieu Pellerin
Jürgen, thanks for the successful re-release of 3.10.2.

Paolo, Anita, who is in a position to publish the drafted post on the blog?


On Thu, Jan 23, 2020, 10:59 Mathieu Pellerin  wrote:

> +1 to that plan. We're 33% done already since the blocking PR has been
> merged.
>
> On Wed, Jan 22, 2020 at 6:47 PM Matthias Kuhn  wrote:
>
>> How about
>>
>> - Waiting for https://github.com/qgis/QGIS/pull/33971
>>
>> - Releasing 3.10.3
>>
>> - Announce on twitter, blog, news panel
>>
>> Clear cut for everyone (including those 95% of our users not following
>> [qgis on] twitter)
>>
>> Matthias
>> On 1/22/20 12:39 PM, Anita Graser wrote:
>>
>> Is it time to send an update on Twitter yet? I don't see new installers
>> at https://qgis.org/downloads/
>>
>> Regards,
>> Anita
>>
>> On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin 
>> wrote:
>>
>>> I think the QGIS twitter account already mentioned that the 3.10.2
>>> installer had been retired due to issues and re-build.
>>>
>>> On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:
>>>
 Hi all,

 Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those who
 have already downloaded the broken 3.10.2 may not think to update.

 Regards,
 Harrissou

 Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin 
 a écrit :

> Matthias,
>
> Good idea.
>
> Math
>
> On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
> wrote:
>
>> Hi Mathieu,
>>
>> Thanks a lot. It reads very well!
>>
>> Something that I'd like to add is that in case of still finding a
>> bug, users should file issues and to mention proximity of LTR 
>> replacement.
>> If you still happen to find QGIS behaving in an unexpected way,
>> please let us know on https://github.com/qgis/QGIS/issues
>> 
>> as always. We are very happy that QGIS 3.10 is now in shape to replace 
>> 3.4
>> as LTR in a month time.
>>
>> Bests
>> Matthias
>>
>>
>> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>>
>> Paolo, here's the draft blog post:
>>
>> *Public Service Announcement: Update to the latest point release now*
>> --
>> QGIS users who have adopted the 3.10 version when initially released
>> at the end of October 2019 have likely noticed a sharp drop in 
>> reliability.
>> The underlying issues have now been addressed in 3.10.2, all users are
>> advised to update *now*.
>>
>> When QGIS 3.10 was first released in the end of October 2019, a pair
>> of libraries – namely GDAL and PROJ – were updated to their 
>> next-generation
>> versions. The advantages are plenty: GeoPDF export[1] support, more
>> accurate coordinate transformation, etc. For those interested, more
>> technical information on this is available here[2].
>>
>> The update of these crucial libraries led to a number of regressions.
>> While we expected some issues to arise, the seriousness of the disruption
>> caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
>> first large GIS project to expose these next-generation libraries to the
>> masses. The large number of QGIS users across the globe were essentially
>> stress testing both new code within QGIS as well as the libraries
>> themselves.
>>
>> Thanks to dedicated users taking time to file in report and the
>> community helping out as well as our project sponsors for allowing us to
>> fund development time, developers have been able to fix all known
>> regressions in both in QGIS as well as underlying GDAL and PROJ 
>> libraries,
>> benefiting a large number of open source projects.
>>
>> As a result of this collective effort by the community, QGIS 3.10.2
>> is now back to being the reliable and stable GIS software we all love. As
>> such, we cannot stress enough the important of updating now.
>>
>> Once again, thanks to our community of testers, sponsors, and
>> developers for their countless hours and efforts in making QGIS better.
>>
>> Happy mapping!
>>
>> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
>> [2] https://gdalbarn.com/
>>
>> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini <
>> cavall...@faunalia.it> wrote:
>>
>>> Fully agreed. Mathieu, would you like to write it?
>>> Thanks.
>>>
>>> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
>>> nirvn.a...@gmail.com> wrote:

 +100 on all that's been said here.

 Also, once 3.10.2 is updated to include the updated packages &
 above-referred fix, I'd suggest writing a QGIS.org blog post to inform
 users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a 
 bit
 on why 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Mathieu Pellerin
+1 to that plan. We're 33% done already since the blocking PR has been
merged.

On Wed, Jan 22, 2020 at 6:47 PM Matthias Kuhn  wrote:

> How about
>
> - Waiting for https://github.com/qgis/QGIS/pull/33971
>
> - Releasing 3.10.3
>
> - Announce on twitter, blog, news panel
>
> Clear cut for everyone (including those 95% of our users not following
> [qgis on] twitter)
>
> Matthias
> On 1/22/20 12:39 PM, Anita Graser wrote:
>
> Is it time to send an update on Twitter yet? I don't see new installers at
> https://qgis.org/downloads/
>
> Regards,
> Anita
>
> On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin 
> wrote:
>
>> I think the QGIS twitter account already mentioned that the 3.10.2
>> installer had been retired due to issues and re-build.
>>
>> On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:
>>
>>> Hi all,
>>>
>>> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those who
>>> have already downloaded the broken 3.10.2 may not think to update.
>>>
>>> Regards,
>>> Harrissou
>>>
>>> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin 
>>> a écrit :
>>>
 Matthias,

 Good idea.

 Math

 On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
 wrote:

> Hi Mathieu,
>
> Thanks a lot. It reads very well!
>
> Something that I'd like to add is that in case of still finding a bug,
> users should file issues and to mention proximity of LTR replacement.
> If you still happen to find QGIS behaving in an unexpected way, please
> let us know on https://github.com/qgis/QGIS/issues
> 
> as always. We are very happy that QGIS 3.10 is now in shape to replace 3.4
> as LTR in a month time.
>
> Bests
> Matthias
>
>
> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>
> Paolo, here's the draft blog post:
>
> *Public Service Announcement: Update to the latest point release now*
> --
> QGIS users who have adopted the 3.10 version when initially released
> at the end of October 2019 have likely noticed a sharp drop in 
> reliability.
> The underlying issues have now been addressed in 3.10.2, all users are
> advised to update *now*.
>
> When QGIS 3.10 was first released in the end of October 2019, a pair
> of libraries – namely GDAL and PROJ – were updated to their 
> next-generation
> versions. The advantages are plenty: GeoPDF export[1] support, more
> accurate coordinate transformation, etc. For those interested, more
> technical information on this is available here[2].
>
> The update of these crucial libraries led to a number of regressions.
> While we expected some issues to arise, the seriousness of the disruption
> caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
> first large GIS project to expose these next-generation libraries to the
> masses. The large number of QGIS users across the globe were essentially
> stress testing both new code within QGIS as well as the libraries
> themselves.
>
> Thanks to dedicated users taking time to file in report and the
> community helping out as well as our project sponsors for allowing us to
> fund development time, developers have been able to fix all known
> regressions in both in QGIS as well as underlying GDAL and PROJ libraries,
> benefiting a large number of open source projects.
>
> As a result of this collective effort by the community, QGIS 3.10.2 is
> now back to being the reliable and stable GIS software we all love. As
> such, we cannot stress enough the important of updating now.
>
> Once again, thanks to our community of testers, sponsors, and
> developers for their countless hours and efforts in making QGIS better.
>
> Happy mapping!
>
> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
> [2] https://gdalbarn.com/
>
> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
> wrote:
>
>> Fully agreed. Mathieu, would you like to write it?
>> Thanks.
>>
>> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
>> nirvn.a...@gmail.com> wrote:
>>>
>>> +100 on all that's been said here.
>>>
>>> Also, once 3.10.2 is updated to include the updated packages &
>>> above-referred fix, I'd suggest writing a QGIS.org blog post to inform
>>> users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a 
>>> bit
>>> on why 3.10.0/.1 were such rough releases. We can finish the post by
>>> thanking users that have reported bugs (an inevitable nightmare to go
>>> through as QGIS was exposing brand new GDAL3/PROJ6 versions to the 
>>> masses).
>>> IMHO, we should not skip this communication to our users.
>>>
>>> On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
>>> 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Anita Graser
Thank you for proof reading, Stefan!

Please note, however, that the tone of the message (i.e. "Posting that
would be embarrassing") may come off as rude.

As our code of conduct [0] states: "Be kind to others. Do not insult or put
down other participants."

Regards,
Anita

[0]
https://www.qgis.org/en/site/getinvolved/governance/codeofconduct/codeofconduct.html



On Wed, Jan 22, 2020 at 4:52 PM Stefan Steiger 
wrote:

> You made a mistake translating/editing:
>
> „the impor*tant* of“ è „the impor*tance* of“
>
>
>
> As such, we cannot stress enough the important of updating now.
> è
>
> As such, we cannot stress enough the *importance* of updating now.
>
>
>
> Posting that would be embarrassing
>
>
>
>
>
>
>
> *Von:* QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] *Im
> Auftrag von *Mathieu Pellerin
> *Gesendet:* Mittwoch, 22. Januar 2020 10:58
> *An:* Paolo Cavallini ; qgis-developer <
> qgis-developer@lists.osgeo.org>
> *Betreff:* Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2
> installer from site
>
>
>
> Paolo, here's the draft blog post:
>
>
>
> *Public Service Announcement: Update to the latest point release now*
> --
> QGIS users who have adopted the 3.10 version when initially released at
> the end of October 2019 have likely noticed a sharp drop in reliability.
> The underlying issues have now been addressed in 3.10.2, all users are
> advised to update *now*.
>
> When QGIS 3.10 was first released in the end of October 2019, a pair of
> libraries – namely GDAL and PROJ – were updated to their next-generation
> versions. The advantages are plenty: GeoPDF export[1] support, more
> accurate coordinate transformation, etc. For those interested, more
> technical information on this is available here[2].
>
> The update of these crucial libraries led to a number of regressions.
> While we expected some issues to arise, the seriousness of the disruption
> caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
> first large GIS project to expose these next-generation libraries to the
> masses. The large number of QGIS users across the globe were essentially
> stress testing both new code within QGIS as well as the libraries
> themselves.
>
> Thanks to dedicated users taking time to file in report and the community
> helping out as well as our project sponsors for allowing us to fund
> development time, developers have been able to fix all known regressions in
> both in QGIS as well as underlying GDAL and PROJ libraries, benefiting a
> large number of open source projects.
>
> As a result of this collective effort by the community, QGIS 3.10.2 is now
> back to being the reliable and stable GIS software we all love. As such, we
> cannot stress enough the important of updating now.
>
> Once again, thanks to our community of testers, sponsors, and developers
> for their countless hours and efforts in making QGIS better.
>
> Happy mapping!
>
> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
> [2] https://gdalbarn.com/
>
>
>
> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
> wrote:
>
> Fully agreed. Mathieu, would you like to write it?
> Thanks.
>
> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
> nirvn.a...@gmail.com> wrote:
>
> +100 on all that's been said here.
>
>
>
> Also, once 3.10.2 is updated to include the updated packages &
> above-referred fix, I'd suggest writing a QGIS.org blog post to inform
> users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
> on why 3.10.0/.1 were such rough releases. We can finish the post by
> thanking users that have reported bugs (an inevitable nightmare to go
> through as QGIS was exposing brand new GDAL3/PROJ6 versions to the masses).
> IMHO, we should not skip this communication to our users.
>
>
>
> On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
> wrote:
>
> Also, we better wait for a fix for
> https://github.com/qgis/QGIS/issues/33902 (incoming)...
>
> Gosh, will the nightmare ever end... Let's agree never to change
> anything in gdal or proj or qgis ever again ;)
>
> Nyall
>
>
> -- Forwarded message -
> From: Nyall Dawson 
> Date: Tue, 21 Jan 2020 at 06:28
> Subject: Urgent: Remove windows 3.10.2 installer from site
> To: qgis-developer 
>
>
> Can we please remove the 3.10.2 installer from the website as a matter
> of urgency? This installer was released using the older gdal 3.0.2 and
> proj 6.2 versions, which directly lead to crashes and reprojection
> failures in QGIS.
>
> QGIS SHOULD NEVER 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Stefan Steiger
You made a mistake translating/editing:
„the important of“ ==> „the importance of“

As such, we cannot stress enough the important of updating now.
==>
As such, we cannot stress enough the importance of updating now.


Posting that would be embarrassing



Von: QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] Im Auftrag 
von Mathieu Pellerin
Gesendet: Mittwoch, 22. Januar 2020 10:58
An: Paolo Cavallini ; qgis-developer 

Betreff: Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from 
site

Paolo, here's the draft blog post:

*Public Service Announcement: Update to the latest point release now*
--
QGIS users who have adopted the 3.10 version when initially released at the end 
of October 2019 have likely noticed a sharp drop in reliability. The underlying 
issues have now been addressed in 3.10.2, all users are advised to update *now*.

When QGIS 3.10 was first released in the end of October 2019, a pair of 
libraries – namely GDAL and PROJ – were updated to their next-generation 
versions. The advantages are plenty: GeoPDF export[1] support, more accurate 
coordinate transformation, etc. For those interested, more technical 
information on this is available here[2].

The update of these crucial libraries led to a number of regressions. While we 
expected some issues to arise, the seriousness of the disruption caught us off 
guard. Yet, it was also somewhat inevitable: QGIS is the first large GIS 
project to expose these next-generation libraries to the masses. The large 
number of QGIS users across the globe were essentially stress testing both new 
code within QGIS as well as the libraries themselves.

Thanks to dedicated users taking time to file in report and the community 
helping out as well as our project sponsors for allowing us to fund development 
time, developers have been able to fix all known regressions in both in QGIS as 
well as underlying GDAL and PROJ libraries, benefiting a large number of open 
source projects.

As a result of this collective effort by the community, QGIS 3.10.2 is now back 
to being the reliable and stable GIS software we all love. As such, we cannot 
stress enough the important of updating now.

Once again, thanks to our community of testers, sponsors, and developers for 
their countless hours and efforts in making QGIS better.

Happy mapping!

[1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
[2] https://gdalbarn.com/

On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
mailto:cavall...@faunalia.it>> wrote:
Fully agreed. Mathieu, would you like to write it?
Thanks.
On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin 
mailto:nirvn.a...@gmail.com>> wrote:
+100 on all that's been said here.

Also, once 3.10.2 is updated to include the updated packages & above-referred 
fix, I'd suggest writing a QGIS.org blog post to inform users of the worthiness 
of updating to 3.10.2(.2) *ASAP*, and expand a bit on why 3.10.0/.1 were such 
rough releases. We can finish the post by thanking users that have reported 
bugs (an inevitable nightmare to go through as QGIS was exposing brand new 
GDAL3/PROJ6 versions to the masses). IMHO, we should not skip this 
communication to our users.

On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
mailto:nyall.daw...@gmail.com>> wrote:
Also, we better wait for a fix for
https://github.com/qgis/QGIS/issues/33902 (incoming)...

Gosh, will the nightmare ever end... Let's agree never to change
anything in gdal or proj or qgis ever again ;)

Nyall


-- Forwarded message -
From: Nyall Dawson mailto:nyall.daw...@gmail.com>>
Date: Tue, 21 Jan 2020 at 06:28
Subject: Urgent: Remove windows 3.10.2 installer from site
To: qgis-developer 
mailto:qgis-developer@lists.osgeo.org>>


Can we please remove the 3.10.2 installer from the website as a matter
of urgency? This installer was released using the older gdal 3.0.2 and
proj 6.2 versions, which directly lead to crashes and reprojection
failures in QGIS.

QGIS SHOULD NEVER EVER*** be
used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj < 6.3.0.

This combination is a world of hurt for users :(

Tickets filed at https://trac.osgeo.org/osgeo4w/ticket/618, and
https://trac.osgeo.org/osgeo4w/ticket/617, and later today I'm going
to commit cmake blocks which will completely prevent compilation under
the affected gdal/proj versions.

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org<mailto:QGIS-Developer@lists.osgeo.org>
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

--
Please excuse my brevity.
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Luigi Pirelli
do we need a mechanism to notify and deprecate 3.10.2 in case packages are
still available all around?

Luigi Pirelli

**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Book: Mastering QGIS3 - 3rd Edition

* Hire a team: http://www.qcooperative.net
**


On Wed, 22 Jan 2020 at 12:47, Matthias Kuhn  wrote:

> How about
>
> - Waiting for https://github.com/qgis/QGIS/pull/33971
>
> - Releasing 3.10.3
>
> - Announce on twitter, blog, news panel
>
> Clear cut for everyone (including those 95% of our users not following
> [qgis on] twitter)
>
> Matthias
> On 1/22/20 12:39 PM, Anita Graser wrote:
>
> Is it time to send an update on Twitter yet? I don't see new installers at
> https://qgis.org/downloads/
>
> Regards,
> Anita
>
> On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin 
> wrote:
>
>> I think the QGIS twitter account already mentioned that the 3.10.2
>> installer had been retired due to issues and re-build.
>>
>> On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:
>>
>>> Hi all,
>>>
>>> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those who
>>> have already downloaded the broken 3.10.2 may not think to update.
>>>
>>> Regards,
>>> Harrissou
>>>
>>> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin 
>>> a écrit :
>>>
 Matthias,

 Good idea.

 Math

 On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
 wrote:

> Hi Mathieu,
>
> Thanks a lot. It reads very well!
>
> Something that I'd like to add is that in case of still finding a bug,
> users should file issues and to mention proximity of LTR replacement.
> If you still happen to find QGIS behaving in an unexpected way, please
> let us know on https://github.com/qgis/QGIS/issues
> 
> as always. We are very happy that QGIS 3.10 is now in shape to replace 3.4
> as LTR in a month time.
>
> Bests
> Matthias
>
>
> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>
> Paolo, here's the draft blog post:
>
> *Public Service Announcement: Update to the latest point release now*
> --
> QGIS users who have adopted the 3.10 version when initially released
> at the end of October 2019 have likely noticed a sharp drop in 
> reliability.
> The underlying issues have now been addressed in 3.10.2, all users are
> advised to update *now*.
>
> When QGIS 3.10 was first released in the end of October 2019, a pair
> of libraries – namely GDAL and PROJ – were updated to their 
> next-generation
> versions. The advantages are plenty: GeoPDF export[1] support, more
> accurate coordinate transformation, etc. For those interested, more
> technical information on this is available here[2].
>
> The update of these crucial libraries led to a number of regressions.
> While we expected some issues to arise, the seriousness of the disruption
> caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
> first large GIS project to expose these next-generation libraries to the
> masses. The large number of QGIS users across the globe were essentially
> stress testing both new code within QGIS as well as the libraries
> themselves.
>
> Thanks to dedicated users taking time to file in report and the
> community helping out as well as our project sponsors for allowing us to
> fund development time, developers have been able to fix all known
> regressions in both in QGIS as well as underlying GDAL and PROJ libraries,
> benefiting a large number of open source projects.
>
> As a result of this collective effort by the community, QGIS 3.10.2 is
> now back to being the reliable and stable GIS software we all love. As
> such, we cannot stress enough the important of updating now.
>
> Once again, thanks to our community of testers, sponsors, and
> developers for their countless hours and efforts in making QGIS better.
>
> Happy mapping!
>
> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
> [2] https://gdalbarn.com/
>
> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
> wrote:
>
>> Fully agreed. Mathieu, would you like to write it?
>> Thanks.
>>
>> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
>> nirvn.a...@gmail.com> wrote:
>>>
>>> +100 on all that's been said here.
>>>
>>> Also, once 3.10.2 is updated 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Luigi Pirelli
+1 to mathias proposal

Luigi Pirelli

**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Book: Mastering QGIS3 - 3rd Edition

* Hire a team: http://www.qcooperative.net
**


On Wed, 22 Jan 2020 at 12:47, Matthias Kuhn  wrote:

> How about
>
> - Waiting for https://github.com/qgis/QGIS/pull/33971
>
> - Releasing 3.10.3
>
> - Announce on twitter, blog, news panel
>
> Clear cut for everyone (including those 95% of our users not following
> [qgis on] twitter)
>
> Matthias
> On 1/22/20 12:39 PM, Anita Graser wrote:
>
> Is it time to send an update on Twitter yet? I don't see new installers at
> https://qgis.org/downloads/
>
> Regards,
> Anita
>
> On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin 
> wrote:
>
>> I think the QGIS twitter account already mentioned that the 3.10.2
>> installer had been retired due to issues and re-build.
>>
>> On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:
>>
>>> Hi all,
>>>
>>> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those who
>>> have already downloaded the broken 3.10.2 may not think to update.
>>>
>>> Regards,
>>> Harrissou
>>>
>>> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin 
>>> a écrit :
>>>
 Matthias,

 Good idea.

 Math

 On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
 wrote:

> Hi Mathieu,
>
> Thanks a lot. It reads very well!
>
> Something that I'd like to add is that in case of still finding a bug,
> users should file issues and to mention proximity of LTR replacement.
> If you still happen to find QGIS behaving in an unexpected way, please
> let us know on https://github.com/qgis/QGIS/issues
> 
> as always. We are very happy that QGIS 3.10 is now in shape to replace 3.4
> as LTR in a month time.
>
> Bests
> Matthias
>
>
> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>
> Paolo, here's the draft blog post:
>
> *Public Service Announcement: Update to the latest point release now*
> --
> QGIS users who have adopted the 3.10 version when initially released
> at the end of October 2019 have likely noticed a sharp drop in 
> reliability.
> The underlying issues have now been addressed in 3.10.2, all users are
> advised to update *now*.
>
> When QGIS 3.10 was first released in the end of October 2019, a pair
> of libraries – namely GDAL and PROJ – were updated to their 
> next-generation
> versions. The advantages are plenty: GeoPDF export[1] support, more
> accurate coordinate transformation, etc. For those interested, more
> technical information on this is available here[2].
>
> The update of these crucial libraries led to a number of regressions.
> While we expected some issues to arise, the seriousness of the disruption
> caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
> first large GIS project to expose these next-generation libraries to the
> masses. The large number of QGIS users across the globe were essentially
> stress testing both new code within QGIS as well as the libraries
> themselves.
>
> Thanks to dedicated users taking time to file in report and the
> community helping out as well as our project sponsors for allowing us to
> fund development time, developers have been able to fix all known
> regressions in both in QGIS as well as underlying GDAL and PROJ libraries,
> benefiting a large number of open source projects.
>
> As a result of this collective effort by the community, QGIS 3.10.2 is
> now back to being the reliable and stable GIS software we all love. As
> such, we cannot stress enough the important of updating now.
>
> Once again, thanks to our community of testers, sponsors, and
> developers for their countless hours and efforts in making QGIS better.
>
> Happy mapping!
>
> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
> [2] https://gdalbarn.com/
>
> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
> wrote:
>
>> Fully agreed. Mathieu, would you like to write it?
>> Thanks.
>>
>> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
>> nirvn.a...@gmail.com> wrote:
>>>
>>> +100 on all that's been said here.
>>>
>>> Also, once 3.10.2 is updated to include the updated packages &
>>> above-referred fix, I'd suggest writing 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Matthias Kuhn

How about

- Waiting for https://github.com/qgis/QGIS/pull/33971

- Releasing 3.10.3

- Announce on twitter, blog, news panel

Clear cut for everyone (including those 95% of our users not following 
[qgis on] twitter)


Matthias

On 1/22/20 12:39 PM, Anita Graser wrote:
Is it time to send an update on Twitter yet? I don't see new 
installers at https://qgis.org/downloads/


Regards,
Anita

On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin 
mailto:nirvn.a...@gmail.com>> wrote:


I think the QGIS twitter account already mentioned that the 3.10.2
installer had been retired due to issues and re-build.

On Wed, Jan 22, 2020 at 5:07 PM DelazJ mailto:del...@gmail.com>> wrote:

Hi all,

Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because
those who have already downloaded the broken 3.10.2 may not
think to update.

Regards,
Harrissou

Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin
mailto:nirvn.a...@gmail.com>> a écrit :

Matthias,

Good idea.

Math

On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn
mailto:matth...@opengis.ch>> wrote:

Hi Mathieu,

Thanks a lot. It reads very well!

Something that I'd like to add is that in case of
still finding a bug, users should file issues and to
mention proximity of LTR replacement.

If you still happen to find QGIS behaving in an
unexpected way, please let us know on
https://github.com/qgis/QGIS/issues


as always. We are very happy that QGIS 3.10 is now in
shape to replace 3.4 as LTR in a month time.

Bests
Matthias


On 1/22/20 10:58 AM, Mathieu Pellerin wrote:

Paolo, here's the draft blog post:

*Public Service Announcement: Update to the latest
point release now*
--
QGIS users who have adopted the 3.10 version when
initially released at the end of October 2019 have
likely noticed a sharp drop in reliability. The
underlying issues have now been addressed in 3.10.2,
all users are advised to update *now*.

When QGIS 3.10 was first released in the end of
October 2019, a pair of libraries – namely GDAL and
PROJ – were updated to their next-generation
versions. The advantages are plenty: GeoPDF export[1]
support, more accurate coordinate transformation,
etc. For those interested, more technical information
on this is available here[2].

The update of these crucial libraries led to a number
of regressions. While we expected some issues to
arise, the seriousness of the disruption caught us
off guard. Yet, it was also somewhat inevitable: QGIS
is the first large GIS project to expose these
next-generation libraries to the masses. The large
number of QGIS users across the globe were
essentially stress testing both new code within QGIS
as well as the libraries themselves.

Thanks to dedicated users taking time to file in
report and the community helping out as well as our
project sponsors for allowing us to fund development
time, developers have been able to fix all known
regressions in both in QGIS as well as underlying
GDAL and PROJ libraries, benefiting a large number of
open source projects.

As a result of this collective effort by the
community, QGIS 3.10.2 is now back to being the
reliable and stable GIS software we all love. As
such, we cannot stress enough the important of
updating now.

Once again, thanks to our community of testers,
sponsors, and developers for their countless hours
and efforts in making QGIS better.

Happy mapping!

[1]
https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
[2] https://gdalbarn.com/

On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini
mailto:cavall...@faunalia.it>> wrote:

Fully agreed. Mathieu, would you like to write it?
Thanks.

On 21 January 2020 06:39:08 GMT+04:00, Mathieu
Pellerin mailto:nirvn.a...@gmail.com>> wrote:

   

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Anita Graser
Is it time to send an update on Twitter yet? I don't see new installers at
https://qgis.org/downloads/

Regards,
Anita

On Wed, Jan 22, 2020 at 11:08 AM Mathieu Pellerin 
wrote:

> I think the QGIS twitter account already mentioned that the 3.10.2
> installer had been retired due to issues and re-build.
>
> On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:
>
>> Hi all,
>>
>> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those who
>> have already downloaded the broken 3.10.2 may not think to update.
>>
>> Regards,
>> Harrissou
>>
>> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin  a
>> écrit :
>>
>>> Matthias,
>>>
>>> Good idea.
>>>
>>> Math
>>>
>>> On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
>>> wrote:
>>>
 Hi Mathieu,

 Thanks a lot. It reads very well!

 Something that I'd like to add is that in case of still finding a bug,
 users should file issues and to mention proximity of LTR replacement.
 If you still happen to find QGIS behaving in an unexpected way, please
 let us know on https://github.com/qgis/QGIS/issues
 
 as always. We are very happy that QGIS 3.10 is now in shape to replace 3.4
 as LTR in a month time.

 Bests
 Matthias


 On 1/22/20 10:58 AM, Mathieu Pellerin wrote:

 Paolo, here's the draft blog post:

 *Public Service Announcement: Update to the latest point release now*
 --
 QGIS users who have adopted the 3.10 version when initially released at
 the end of October 2019 have likely noticed a sharp drop in reliability.
 The underlying issues have now been addressed in 3.10.2, all users are
 advised to update *now*.

 When QGIS 3.10 was first released in the end of October 2019, a pair of
 libraries – namely GDAL and PROJ – were updated to their next-generation
 versions. The advantages are plenty: GeoPDF export[1] support, more
 accurate coordinate transformation, etc. For those interested, more
 technical information on this is available here[2].

 The update of these crucial libraries led to a number of regressions.
 While we expected some issues to arise, the seriousness of the disruption
 caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
 first large GIS project to expose these next-generation libraries to the
 masses. The large number of QGIS users across the globe were essentially
 stress testing both new code within QGIS as well as the libraries
 themselves.

 Thanks to dedicated users taking time to file in report and the
 community helping out as well as our project sponsors for allowing us to
 fund development time, developers have been able to fix all known
 regressions in both in QGIS as well as underlying GDAL and PROJ libraries,
 benefiting a large number of open source projects.

 As a result of this collective effort by the community, QGIS 3.10.2 is
 now back to being the reliable and stable GIS software we all love. As
 such, we cannot stress enough the important of updating now.

 Once again, thanks to our community of testers, sponsors, and
 developers for their countless hours and efforts in making QGIS better.

 Happy mapping!

 [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
 [2] https://gdalbarn.com/

 On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
 wrote:

> Fully agreed. Mathieu, would you like to write it?
> Thanks.
>
> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
> nirvn.a...@gmail.com> wrote:
>>
>> +100 on all that's been said here.
>>
>> Also, once 3.10.2 is updated to include the updated packages &
>> above-referred fix, I'd suggest writing a QGIS.org blog post to inform
>> users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a 
>> bit
>> on why 3.10.0/.1 were such rough releases. We can finish the post by
>> thanking users that have reported bugs (an inevitable nightmare to go
>> through as QGIS was exposing brand new GDAL3/PROJ6 versions to the 
>> masses).
>> IMHO, we should not skip this communication to our users.
>>
>> On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
>> wrote:
>>
>>> Also, we better wait for a fix for
>>> https://github.com/qgis/QGIS/issues/33902 (incoming)...
>>>
>>> Gosh, will the nightmare ever end... Let's agree never to change
>>> anything in gdal or proj or qgis ever again ;)
>>>
>>> Nyall
>>>
>>>
>>> -- Forwarded message -
>>> From: Nyall Dawson 
>>> Date: Tue, 21 Jan 2020 at 06:28
>>> Subject: Urgent: Remove windows 3.10.2 installer from site
>>> To: qgis-developer 
>>>
>>>
>>> Can we please remove the 3.10.2 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Mathieu Pellerin
I think the QGIS twitter account already mentioned that the 3.10.2
installer had been retired due to issues and re-build.

On Wed, Jan 22, 2020 at 5:07 PM DelazJ  wrote:

> Hi all,
>
> Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those who
> have already downloaded the broken 3.10.2 may not think to update.
>
> Regards,
> Harrissou
>
> Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin  a
> écrit :
>
>> Matthias,
>>
>> Good idea.
>>
>> Math
>>
>> On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn 
>> wrote:
>>
>>> Hi Mathieu,
>>>
>>> Thanks a lot. It reads very well!
>>>
>>> Something that I'd like to add is that in case of still finding a bug,
>>> users should file issues and to mention proximity of LTR replacement.
>>> If you still happen to find QGIS behaving in an unexpected way, please
>>> let us know on https://github.com/qgis/QGIS/issues
>>> 
>>> as always. We are very happy that QGIS 3.10 is now in shape to replace 3.4
>>> as LTR in a month time.
>>>
>>> Bests
>>> Matthias
>>>
>>>
>>> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>>>
>>> Paolo, here's the draft blog post:
>>>
>>> *Public Service Announcement: Update to the latest point release now*
>>> --
>>> QGIS users who have adopted the 3.10 version when initially released at
>>> the end of October 2019 have likely noticed a sharp drop in reliability.
>>> The underlying issues have now been addressed in 3.10.2, all users are
>>> advised to update *now*.
>>>
>>> When QGIS 3.10 was first released in the end of October 2019, a pair of
>>> libraries – namely GDAL and PROJ – were updated to their next-generation
>>> versions. The advantages are plenty: GeoPDF export[1] support, more
>>> accurate coordinate transformation, etc. For those interested, more
>>> technical information on this is available here[2].
>>>
>>> The update of these crucial libraries led to a number of regressions.
>>> While we expected some issues to arise, the seriousness of the disruption
>>> caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
>>> first large GIS project to expose these next-generation libraries to the
>>> masses. The large number of QGIS users across the globe were essentially
>>> stress testing both new code within QGIS as well as the libraries
>>> themselves.
>>>
>>> Thanks to dedicated users taking time to file in report and the
>>> community helping out as well as our project sponsors for allowing us to
>>> fund development time, developers have been able to fix all known
>>> regressions in both in QGIS as well as underlying GDAL and PROJ libraries,
>>> benefiting a large number of open source projects.
>>>
>>> As a result of this collective effort by the community, QGIS 3.10.2 is
>>> now back to being the reliable and stable GIS software we all love. As
>>> such, we cannot stress enough the important of updating now.
>>>
>>> Once again, thanks to our community of testers, sponsors, and developers
>>> for their countless hours and efforts in making QGIS better.
>>>
>>> Happy mapping!
>>>
>>> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
>>> [2] https://gdalbarn.com/
>>>
>>> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
>>> wrote:
>>>
 Fully agreed. Mathieu, would you like to write it?
 Thanks.

 On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
 nirvn.a...@gmail.com> wrote:
>
> +100 on all that's been said here.
>
> Also, once 3.10.2 is updated to include the updated packages &
> above-referred fix, I'd suggest writing a QGIS.org blog post to inform
> users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
> on why 3.10.0/.1 were such rough releases. We can finish the post by
> thanking users that have reported bugs (an inevitable nightmare to go
> through as QGIS was exposing brand new GDAL3/PROJ6 versions to the 
> masses).
> IMHO, we should not skip this communication to our users.
>
> On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
> wrote:
>
>> Also, we better wait for a fix for
>> https://github.com/qgis/QGIS/issues/33902 (incoming)...
>>
>> Gosh, will the nightmare ever end... Let's agree never to change
>> anything in gdal or proj or qgis ever again ;)
>>
>> Nyall
>>
>>
>> -- Forwarded message -
>> From: Nyall Dawson 
>> Date: Tue, 21 Jan 2020 at 06:28
>> Subject: Urgent: Remove windows 3.10.2 installer from site
>> To: qgis-developer 
>>
>>
>> Can we please remove the 3.10.2 installer from the website as a matter
>> of urgency? This installer was released using the older gdal 3.0.2 and
>> proj 6.2 versions, which directly lead to crashes and reprojection
>> failures in QGIS.
>>
>> QGIS SHOULD NEVER EVER*** be
>> used with 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread DelazJ
Hi all,

Thanks Mathieu. Should it be 3.10.2 or 3.10.3? Asking because those who
have already downloaded the broken 3.10.2 may not think to update.

Regards,
Harrissou

Le mer. 22 janv. 2020 à 11:05, Mathieu Pellerin  a
écrit :

> Matthias,
>
> Good idea.
>
> Math
>
> On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn  wrote:
>
>> Hi Mathieu,
>>
>> Thanks a lot. It reads very well!
>>
>> Something that I'd like to add is that in case of still finding a bug,
>> users should file issues and to mention proximity of LTR replacement.
>> If you still happen to find QGIS behaving in an unexpected way, please
>> let us know on https://github.com/qgis/QGIS/issues
>> 
>> as always. We are very happy that QGIS 3.10 is now in shape to replace 3.4
>> as LTR in a month time.
>>
>> Bests
>> Matthias
>>
>>
>> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>>
>> Paolo, here's the draft blog post:
>>
>> *Public Service Announcement: Update to the latest point release now*
>> --
>> QGIS users who have adopted the 3.10 version when initially released at
>> the end of October 2019 have likely noticed a sharp drop in reliability.
>> The underlying issues have now been addressed in 3.10.2, all users are
>> advised to update *now*.
>>
>> When QGIS 3.10 was first released in the end of October 2019, a pair of
>> libraries – namely GDAL and PROJ – were updated to their next-generation
>> versions. The advantages are plenty: GeoPDF export[1] support, more
>> accurate coordinate transformation, etc. For those interested, more
>> technical information on this is available here[2].
>>
>> The update of these crucial libraries led to a number of regressions.
>> While we expected some issues to arise, the seriousness of the disruption
>> caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
>> first large GIS project to expose these next-generation libraries to the
>> masses. The large number of QGIS users across the globe were essentially
>> stress testing both new code within QGIS as well as the libraries
>> themselves.
>>
>> Thanks to dedicated users taking time to file in report and the community
>> helping out as well as our project sponsors for allowing us to fund
>> development time, developers have been able to fix all known regressions in
>> both in QGIS as well as underlying GDAL and PROJ libraries, benefiting a
>> large number of open source projects.
>>
>> As a result of this collective effort by the community, QGIS 3.10.2 is
>> now back to being the reliable and stable GIS software we all love. As
>> such, we cannot stress enough the important of updating now.
>>
>> Once again, thanks to our community of testers, sponsors, and developers
>> for their countless hours and efforts in making QGIS better.
>>
>> Happy mapping!
>>
>> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
>> [2] https://gdalbarn.com/
>>
>> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
>> wrote:
>>
>>> Fully agreed. Mathieu, would you like to write it?
>>> Thanks.
>>>
>>> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
>>> nirvn.a...@gmail.com> wrote:

 +100 on all that's been said here.

 Also, once 3.10.2 is updated to include the updated packages &
 above-referred fix, I'd suggest writing a QGIS.org blog post to inform
 users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
 on why 3.10.0/.1 were such rough releases. We can finish the post by
 thanking users that have reported bugs (an inevitable nightmare to go
 through as QGIS was exposing brand new GDAL3/PROJ6 versions to the masses).
 IMHO, we should not skip this communication to our users.

 On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
 wrote:

> Also, we better wait for a fix for
> https://github.com/qgis/QGIS/issues/33902 (incoming)...
>
> Gosh, will the nightmare ever end... Let's agree never to change
> anything in gdal or proj or qgis ever again ;)
>
> Nyall
>
>
> -- Forwarded message -
> From: Nyall Dawson 
> Date: Tue, 21 Jan 2020 at 06:28
> Subject: Urgent: Remove windows 3.10.2 installer from site
> To: qgis-developer 
>
>
> Can we please remove the 3.10.2 installer from the website as a matter
> of urgency? This installer was released using the older gdal 3.0.2 and
> proj 6.2 versions, which directly lead to crashes and reprojection
> failures in QGIS.
>
> QGIS SHOULD NEVER EVER*** be
> used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj < 6.3.0.
>
> This combination is a world of hurt for users :(
>
> Tickets filed at https://trac.osgeo.org/osgeo4w/ticket/618, and
> https://trac.osgeo.org/osgeo4w/ticket/617, and later today I'm going
> to commit cmake blocks which will 

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Mathieu Pellerin
Matthias,

Good idea.

Math

On Wed, Jan 22, 2020 at 5:02 PM Matthias Kuhn  wrote:

> Hi Mathieu,
>
> Thanks a lot. It reads very well!
>
> Something that I'd like to add is that in case of still finding a bug,
> users should file issues and to mention proximity of LTR replacement.
> If you still happen to find QGIS behaving in an unexpected way, please let
> us know on https://github.com/qgis/QGIS/issues
> 
> as always. We are very happy that QGIS 3.10 is now in shape to replace 3.4
> as LTR in a month time.
>
> Bests
> Matthias
>
>
> On 1/22/20 10:58 AM, Mathieu Pellerin wrote:
>
> Paolo, here's the draft blog post:
>
> *Public Service Announcement: Update to the latest point release now*
> --
> QGIS users who have adopted the 3.10 version when initially released at
> the end of October 2019 have likely noticed a sharp drop in reliability.
> The underlying issues have now been addressed in 3.10.2, all users are
> advised to update *now*.
>
> When QGIS 3.10 was first released in the end of October 2019, a pair of
> libraries – namely GDAL and PROJ – were updated to their next-generation
> versions. The advantages are plenty: GeoPDF export[1] support, more
> accurate coordinate transformation, etc. For those interested, more
> technical information on this is available here[2].
>
> The update of these crucial libraries led to a number of regressions.
> While we expected some issues to arise, the seriousness of the disruption
> caught us off guard. Yet, it was also somewhat inevitable: QGIS is the
> first large GIS project to expose these next-generation libraries to the
> masses. The large number of QGIS users across the globe were essentially
> stress testing both new code within QGIS as well as the libraries
> themselves.
>
> Thanks to dedicated users taking time to file in report and the community
> helping out as well as our project sponsors for allowing us to fund
> development time, developers have been able to fix all known regressions in
> both in QGIS as well as underlying GDAL and PROJ libraries, benefiting a
> large number of open source projects.
>
> As a result of this collective effort by the community, QGIS 3.10.2 is now
> back to being the reliable and stable GIS software we all love. As such, we
> cannot stress enough the important of updating now.
>
> Once again, thanks to our community of testers, sponsors, and developers
> for their countless hours and efforts in making QGIS better.
>
> Happy mapping!
>
> [1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
> [2] https://gdalbarn.com/
>
> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
> wrote:
>
>> Fully agreed. Mathieu, would you like to write it?
>> Thanks.
>>
>> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
>> nirvn.a...@gmail.com> wrote:
>>>
>>> +100 on all that's been said here.
>>>
>>> Also, once 3.10.2 is updated to include the updated packages &
>>> above-referred fix, I'd suggest writing a QGIS.org blog post to inform
>>> users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
>>> on why 3.10.0/.1 were such rough releases. We can finish the post by
>>> thanking users that have reported bugs (an inevitable nightmare to go
>>> through as QGIS was exposing brand new GDAL3/PROJ6 versions to the masses).
>>> IMHO, we should not skip this communication to our users.
>>>
>>> On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
>>> wrote:
>>>
 Also, we better wait for a fix for
 https://github.com/qgis/QGIS/issues/33902 (incoming)...

 Gosh, will the nightmare ever end... Let's agree never to change
 anything in gdal or proj or qgis ever again ;)

 Nyall


 -- Forwarded message -
 From: Nyall Dawson 
 Date: Tue, 21 Jan 2020 at 06:28
 Subject: Urgent: Remove windows 3.10.2 installer from site
 To: qgis-developer 


 Can we please remove the 3.10.2 installer from the website as a matter
 of urgency? This installer was released using the older gdal 3.0.2 and
 proj 6.2 versions, which directly lead to crashes and reprojection
 failures in QGIS.

 QGIS SHOULD NEVER EVER*** be
 used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj < 6.3.0.

 This combination is a world of hurt for users :(

 Tickets filed at https://trac.osgeo.org/osgeo4w/ticket/618, and
 https://trac.osgeo.org/osgeo4w/ticket/617, and later today I'm going
 to commit cmake blocks which will completely prevent compilation under
 the affected gdal/proj versions.

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

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Matthias Kuhn

Hi Mathieu,

Thanks a lot. It reads very well!

Something that I'd like to add is that in case of still finding a bug, 
users should file issues and to mention proximity of LTR replacement.


If you still happen to find QGIS behaving in an unexpected way, please 
let us know on https://github.com/qgis/QGIS/issues 
 
as always. We are very happy that QGIS 3.10 is now in shape to replace 
3.4 as LTR in a month time.


Bests
Matthias


On 1/22/20 10:58 AM, Mathieu Pellerin wrote:

Paolo, here's the draft blog post:

*Public Service Announcement: Update to the latest point release now*
--
QGIS users who have adopted the 3.10 version when initially released 
at the end of October 2019 have likely noticed a sharp drop in 
reliability. The underlying issues have now been addressed in 3.10.2, 
all users are advised to update *now*.


When QGIS 3.10 was first released in the end of October 2019, a pair 
of libraries – namely GDAL and PROJ – were updated to their 
next-generation versions. The advantages are plenty: GeoPDF export[1] 
support, more accurate coordinate transformation, etc. For those 
interested, more technical information on this is available here[2].


The update of these crucial libraries led to a number of regressions. 
While we expected some issues to arise, the seriousness of the 
disruption caught us off guard. Yet, it was also somewhat inevitable: 
QGIS is the first large GIS project to expose these next-generation 
libraries to the masses. The large number of QGIS users across the 
globe were essentially stress testing both new code within QGIS as 
well as the libraries themselves.


Thanks to dedicated users taking time to file in report and the 
community helping out as well as our project sponsors for allowing us 
to fund development time, developers have been able to fix all known 
regressions in both in QGIS as well as underlying GDAL and PROJ 
libraries, benefiting a large number of open source projects.


As a result of this collective effort by the community, QGIS 3.10.2 is 
now back to being the reliable and stable GIS software we all love. As 
such, we cannot stress enough the important of updating now.


Once again, thanks to our community of testers, sponsors, and 
developers for their countless hours and efforts in making QGIS better.


Happy mapping!

[1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
[2] https://gdalbarn.com/

On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini > wrote:


Fully agreed. Mathieu, would you like to write it?
Thanks.

On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin
mailto:nirvn.a...@gmail.com>> wrote:

+100 on all that's been said here.

Also, once 3.10.2 is updated to include the updated packages &
above-referred fix, I'd suggest writing a QGIS.org blog post
to inform users of the worthiness of updating to 3.10.2(.2)
*ASAP*, and expand a bit on why 3.10.0/.1 were such rough
releases. We can finish the post by thanking users that have
reported bugs (an inevitable nightmare to go through as QGIS
was exposing brand new GDAL3/PROJ6 versions to the masses).
IMHO, we should not skip this communication to our users.

On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson
mailto:nyall.daw...@gmail.com>> wrote:

Also, we better wait for a fix for
https://github.com/qgis/QGIS/issues/33902 (incoming)...

Gosh, will the nightmare ever end... Let's agree never to
change
anything in gdal or proj or qgis ever again ;)

Nyall


-- Forwarded message -
From: Nyall Dawson mailto:nyall.daw...@gmail.com>>
Date: Tue, 21 Jan 2020 at 06:28
Subject: Urgent: Remove windows 3.10.2 installer from site
To: qgis-developer mailto:qgis-developer@lists.osgeo.org>>


Can we please remove the 3.10.2 installer from the website
as a matter
of urgency? This installer was released using the older
gdal 3.0.2 and
proj 6.2 versions, which directly lead to crashes and
reprojection
failures in QGIS.

QGIS SHOULD NEVER
EVER*** be
used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj <
6.3.0.

This combination is a world of hurt for users :(

Tickets filed at
https://trac.osgeo.org/osgeo4w/ticket/618, and
https://trac.osgeo.org/osgeo4w/ticket/617, and later today
I'm going
to commit cmake blocks which will completely prevent
compilation under
the affected gdal/proj versions.

Nyall

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-22 Thread Mathieu Pellerin
Paolo, here's the draft blog post:

*Public Service Announcement: Update to the latest point release now*
--
QGIS users who have adopted the 3.10 version when initially released at the
end of October 2019 have likely noticed a sharp drop in reliability. The
underlying issues have now been addressed in 3.10.2, all users are advised
to update *now*.

When QGIS 3.10 was first released in the end of October 2019, a pair of
libraries – namely GDAL and PROJ – were updated to their next-generation
versions. The advantages are plenty: GeoPDF export[1] support, more
accurate coordinate transformation, etc. For those interested, more
technical information on this is available here[2].

The update of these crucial libraries led to a number of regressions. While
we expected some issues to arise, the seriousness of the disruption caught
us off guard. Yet, it was also somewhat inevitable: QGIS is the first large
GIS project to expose these next-generation libraries to the masses. The
large number of QGIS users across the globe were essentially stress testing
both new code within QGIS as well as the libraries themselves.

Thanks to dedicated users taking time to file in report and the community
helping out as well as our project sponsors for allowing us to fund
development time, developers have been able to fix all known regressions in
both in QGIS as well as underlying GDAL and PROJ libraries, benefiting a
large number of open source projects.

As a result of this collective effort by the community, QGIS 3.10.2 is now
back to being the reliable and stable GIS software we all love. As such, we
cannot stress enough the important of updating now.

Once again, thanks to our community of testers, sponsors, and developers
for their countless hours and efforts in making QGIS better.

Happy mapping!

[1] https://north-road.com/2019/09/03/qgis-3-10-loves-geopdf/
[2] https://gdalbarn.com/

On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
wrote:

> Fully agreed. Mathieu, would you like to write it?
> Thanks.
>
> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
> nirvn.a...@gmail.com> wrote:
>>
>> +100 on all that's been said here.
>>
>> Also, once 3.10.2 is updated to include the updated packages &
>> above-referred fix, I'd suggest writing a QGIS.org blog post to inform
>> users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
>> on why 3.10.0/.1 were such rough releases. We can finish the post by
>> thanking users that have reported bugs (an inevitable nightmare to go
>> through as QGIS was exposing brand new GDAL3/PROJ6 versions to the masses).
>> IMHO, we should not skip this communication to our users.
>>
>> On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
>> wrote:
>>
>>> Also, we better wait for a fix for
>>> https://github.com/qgis/QGIS/issues/33902 (incoming)...
>>>
>>> Gosh, will the nightmare ever end... Let's agree never to change
>>> anything in gdal or proj or qgis ever again ;)
>>>
>>> Nyall
>>>
>>>
>>> -- Forwarded message -
>>> From: Nyall Dawson 
>>> Date: Tue, 21 Jan 2020 at 06:28
>>> Subject: Urgent: Remove windows 3.10.2 installer from site
>>> To: qgis-developer 
>>>
>>>
>>> Can we please remove the 3.10.2 installer from the website as a matter
>>> of urgency? This installer was released using the older gdal 3.0.2 and
>>> proj 6.2 versions, which directly lead to crashes and reprojection
>>> failures in QGIS.
>>>
>>> QGIS SHOULD NEVER EVER*** be
>>> used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj < 6.3.0.
>>>
>>> This combination is a world of hurt for users :(
>>>
>>> Tickets filed at https://trac.osgeo.org/osgeo4w/ticket/618, and
>>> https://trac.osgeo.org/osgeo4w/ticket/617, and later today I'm going
>>> to commit cmake blocks which will completely prevent compilation under
>>> the affected gdal/proj versions.
>>>
>>> Nyall
>>> ___
>>> QGIS-Developer mailing list
>>> QGIS-Developer@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
> --
> Please excuse my brevity.
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-20 Thread Nathan Woodrow
Very much agree. Thanks for taking it on

On Tue., 21 Jan. 2020, 12:57 pm Mathieu Pellerin, 
wrote:

> Sure, I can draft something by the end of the day.
>
> On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
> wrote:
>
>> Fully agreed. Mathieu, would you like to write it?
>> Thanks.
>>
>> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
>> nirvn.a...@gmail.com> wrote:
>>>
>>> +100 on all that's been said here.
>>>
>>> Also, once 3.10.2 is updated to include the updated packages &
>>> above-referred fix, I'd suggest writing a QGIS.org blog post to inform
>>> users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
>>> on why 3.10.0/.1 were such rough releases. We can finish the post by
>>> thanking users that have reported bugs (an inevitable nightmare to go
>>> through as QGIS was exposing brand new GDAL3/PROJ6 versions to the masses).
>>> IMHO, we should not skip this communication to our users.
>>>
>>> On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
>>> wrote:
>>>
 Also, we better wait for a fix for
 https://github.com/qgis/QGIS/issues/33902 (incoming)...

 Gosh, will the nightmare ever end... Let's agree never to change
 anything in gdal or proj or qgis ever again ;)

 Nyall


 -- Forwarded message -
 From: Nyall Dawson 
 Date: Tue, 21 Jan 2020 at 06:28
 Subject: Urgent: Remove windows 3.10.2 installer from site
 To: qgis-developer 


 Can we please remove the 3.10.2 installer from the website as a matter
 of urgency? This installer was released using the older gdal 3.0.2 and
 proj 6.2 versions, which directly lead to crashes and reprojection
 failures in QGIS.

 QGIS SHOULD NEVER EVER*** be
 used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj < 6.3.0.

 This combination is a world of hurt for users :(

 Tickets filed at https://trac.osgeo.org/osgeo4w/ticket/618, and
 https://trac.osgeo.org/osgeo4w/ticket/617, and later today I'm going
 to commit cmake blocks which will completely prevent compilation under
 the affected gdal/proj versions.

 Nyall
 ___
 QGIS-Developer mailing list
 QGIS-Developer@lists.osgeo.org
 List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
 Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>>
>> --
>> Please excuse my brevity.
>>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-20 Thread Mathieu Pellerin
Sure, I can draft something by the end of the day.

On Tue, Jan 21, 2020 at 9:56 AM Paolo Cavallini 
wrote:

> Fully agreed. Mathieu, would you like to write it?
> Thanks.
>
> On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin <
> nirvn.a...@gmail.com> wrote:
>>
>> +100 on all that's been said here.
>>
>> Also, once 3.10.2 is updated to include the updated packages &
>> above-referred fix, I'd suggest writing a QGIS.org blog post to inform
>> users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
>> on why 3.10.0/.1 were such rough releases. We can finish the post by
>> thanking users that have reported bugs (an inevitable nightmare to go
>> through as QGIS was exposing brand new GDAL3/PROJ6 versions to the masses).
>> IMHO, we should not skip this communication to our users.
>>
>> On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
>> wrote:
>>
>>> Also, we better wait for a fix for
>>> https://github.com/qgis/QGIS/issues/33902 (incoming)...
>>>
>>> Gosh, will the nightmare ever end... Let's agree never to change
>>> anything in gdal or proj or qgis ever again ;)
>>>
>>> Nyall
>>>
>>>
>>> -- Forwarded message -
>>> From: Nyall Dawson 
>>> Date: Tue, 21 Jan 2020 at 06:28
>>> Subject: Urgent: Remove windows 3.10.2 installer from site
>>> To: qgis-developer 
>>>
>>>
>>> Can we please remove the 3.10.2 installer from the website as a matter
>>> of urgency? This installer was released using the older gdal 3.0.2 and
>>> proj 6.2 versions, which directly lead to crashes and reprojection
>>> failures in QGIS.
>>>
>>> QGIS SHOULD NEVER EVER*** be
>>> used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj < 6.3.0.
>>>
>>> This combination is a world of hurt for users :(
>>>
>>> Tickets filed at https://trac.osgeo.org/osgeo4w/ticket/618, and
>>> https://trac.osgeo.org/osgeo4w/ticket/617, and later today I'm going
>>> to commit cmake blocks which will completely prevent compilation under
>>> the affected gdal/proj versions.
>>>
>>> Nyall
>>> ___
>>> QGIS-Developer mailing list
>>> QGIS-Developer@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
> --
> Please excuse my brevity.
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-20 Thread Paolo Cavallini
Fully agreed. Mathieu, would you like to write it?
Thanks.

On 21 January 2020 06:39:08 GMT+04:00, Mathieu Pellerin  
wrote:
>+100 on all that's been said here.
>
>Also, once 3.10.2 is updated to include the updated packages &
>above-referred fix, I'd suggest writing a QGIS.org blog post to inform
>users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a
>bit
>on why 3.10.0/.1 were such rough releases. We can finish the post by
>thanking users that have reported bugs (an inevitable nightmare to go
>through as QGIS was exposing brand new GDAL3/PROJ6 versions to the
>masses).
>IMHO, we should not skip this communication to our users.
>
>On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson 
>wrote:
>
>> Also, we better wait for a fix for
>> https://github.com/qgis/QGIS/issues/33902 (incoming)...
>>
>> Gosh, will the nightmare ever end... Let's agree never to change
>> anything in gdal or proj or qgis ever again ;)
>>
>> Nyall
>>
>>
>> -- Forwarded message -
>> From: Nyall Dawson 
>> Date: Tue, 21 Jan 2020 at 06:28
>> Subject: Urgent: Remove windows 3.10.2 installer from site
>> To: qgis-developer 
>>
>>
>> Can we please remove the 3.10.2 installer from the website as a
>matter
>> of urgency? This installer was released using the older gdal 3.0.2
>and
>> proj 6.2 versions, which directly lead to crashes and reprojection
>> failures in QGIS.
>>
>> QGIS SHOULD NEVER EVER*** be
>> used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj < 6.3.0.
>>
>> This combination is a world of hurt for users :(
>>
>> Tickets filed at https://trac.osgeo.org/osgeo4w/ticket/618, and
>> https://trac.osgeo.org/osgeo4w/ticket/617, and later today I'm going
>> to commit cmake blocks which will completely prevent compilation
>under
>> the affected gdal/proj versions.
>>
>> Nyall
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

-- 
Please excuse my brevity.___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Urgent: Remove windows 3.10.2 installer from site

2020-01-20 Thread Mathieu Pellerin
+100 on all that's been said here.

Also, once 3.10.2 is updated to include the updated packages &
above-referred fix, I'd suggest writing a QGIS.org blog post to inform
users of the worthiness of updating to 3.10.2(.2) *ASAP*, and expand a bit
on why 3.10.0/.1 were such rough releases. We can finish the post by
thanking users that have reported bugs (an inevitable nightmare to go
through as QGIS was exposing brand new GDAL3/PROJ6 versions to the masses).
IMHO, we should not skip this communication to our users.

On Tue, Jan 21, 2020 at 7:27 AM Nyall Dawson  wrote:

> Also, we better wait for a fix for
> https://github.com/qgis/QGIS/issues/33902 (incoming)...
>
> Gosh, will the nightmare ever end... Let's agree never to change
> anything in gdal or proj or qgis ever again ;)
>
> Nyall
>
>
> -- Forwarded message -
> From: Nyall Dawson 
> Date: Tue, 21 Jan 2020 at 06:28
> Subject: Urgent: Remove windows 3.10.2 installer from site
> To: qgis-developer 
>
>
> Can we please remove the 3.10.2 installer from the website as a matter
> of urgency? This installer was released using the older gdal 3.0.2 and
> proj 6.2 versions, which directly lead to crashes and reprojection
> failures in QGIS.
>
> QGIS SHOULD NEVER EVER*** be
> used with gdal >= 3 and gdal < 3.0.3 or proj >6 and proj < 6.3.0.
>
> This combination is a world of hurt for users :(
>
> Tickets filed at https://trac.osgeo.org/osgeo4w/ticket/618, and
> https://trac.osgeo.org/osgeo4w/ticket/617, and later today I'm going
> to commit cmake blocks which will completely prevent compilation under
> the affected gdal/proj versions.
>
> Nyall
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: QGIS Trademark in

2019-07-22 Thread Paolo Cavallini
Hi Tim,
I agree, the current site gives clearly the impression that the are
officila representative for QGIS in Chile.
I think they should have a first sentence about the services they
provide for QGIS, making it clear they are a commercial company not
connected to QGIS.ORG.
Cheers.

On 22/07/19 11:06, Tim Sutton wrote:
> Here is their response. They have added a few links to QGIS.ORG
>  probably not satisfactory yet…can you collaboratively
> give me some talking points for the reply and I will put it together in
> a response to them.
> 
> Regards
> 
> Tim
> 
>> Begin forwarded message:
>>
>> *From: *Alexandra Momberg > >
>> *Subject: **Re: QGIS Trademark in*
>> *Date: *22 July 2019 at 05:06:53 WEST
>> *To: *Tim Sutton mailto:t...@kartoza.com>>
>>
>> Dear Tim,
>>
>> We inform you that we have made the changes required in our web page.
>>
>> Please revise, and tell us if it´s necessary to fill the form asking
>> for authorization for we use our web page:  qgis.chile.cl
>> , or if the modifications we have made are enough.
>>
>> We really appreciate your help, thank you very much.
>>
>> Best Regards,
>>
>>  
>>
>>  
>>     *     *  
>>
>> *Alexandra Momberg O.*
>>
>> *Directora Ejecutiva*
>>
>> * Huerfanos 1160 Oficina 1101, Santiago - Chile.
>> *
>>
>> *Teléfonos:  (56-2) 2791 1086 - 2 26314218*
>>
>> *Movil : +56 9 68310225*
>>
>> * alexandra.momb...@eprime.cl *
>>
>> * www.eprime.cl *
>>
>>
>>
>> El lun., 15 jul. 2019 a las 18:06, Alexandra Momberg
>> (mailto:alexandra.momb...@eprime.cl>>)
>> escribió:
>>
>> Dear Tim,
>>
>> Thank you for your email, I am very sorry for the inconvenience
>> caused, we will take your suggestion and we will make the
>> necessary changes in our home page as soon as possible.
>>
>> I would like to clarify that we made it clear in all our
>> presentations that GIS authorship is yours, and we are very
>> pleased and proud to be your sponsor.
>>
>> Thank you very much for your observations, we are very interested
>> to have the best relationship with your organization,  so your
>> suggestions are very welcome.
>>
>> Best Regards,
>>
>>
>>  
>>     *     *  
>>
>> *Alexandra Momberg O.*
>>
>> *Directora Ejecutiva*
>>
>> * Huerfanos 1160 Oficina 1101, Santiago - Chile.
>> 
>> *
>>
>> *Teléfonos:  (56-2) 2791 1086 - 2 26314218*
>>
>> *Movil : +56 9 68310225*
>>
>> * alexandra.momb...@eprime.cl *
>>
>> * www.eprime.cl *
>>
>>
>>
>> El dom., 14 jul. 2019 a las 18:37, Tim Sutton (> >) escribió:
>>
>> Dear Alexandra
>>
>> We are delighted that your company has chosen to support QGIS
>> with a Bronze sponsorship. We would like to however raise a
>> small issue with you. There is another domain linked to your
>> web site which contravenes our Trademark requirements:
>> https://qgischile.cl . It uses the word
>> ‘QGIS’ in the domain nameWhile we do encourage you to
>> advertise the fact that you are supporting QGIS financially
>> (and hopefully within the Chile GIS community too!), we do not
>> allow the use of our trademark in domain names. We provide a
>> detailed page here which outlines fair use policies etc.:
>>
>> 
>> https://www.qgis.org/en/site/getinvolved/governance/trademark/index.html
>>
>>
>> By the way the QGIS.org  home page is also
>> available in Spanish here so it would be really appreciated if
>> you could provide clear, discoverable outbound links to the
>> QGIS home page (https://www.qgis.org/es/site/index.html) where
>> you refer to QGIS on your web site (e.g.
>> here https://qgischile.cl/sobre-qgis/) and on your promotional
>> materials (e.g. here
>> 
>> https://qgischile.cl/wp-content/uploads/2019/06/Grupo4-1024x1024.jpg).
>>
>> To make it clear, we welcome and encourage you to carry out
>> commercial activities around QGIS, you just need to make it
>> really clear when you refer to QGIS that it is a product of
>> QGIS.org  and not your own company.
>>
>> If you are in any doubt as to how to proceed, please do not
>> hesitate to contact us and we will try to clarify things 

Re: [QGIS-Developer] Fwd: Plugin [1714] SSAM approval notification.

2019-06-14 Thread Paolo Cavallini
Scusa Gianluca, non li sto gestendo io in questo mese.
Saluti!

Il 14 giugno 2019 19:17:11 EEST, gianluca massei  ha scritto:
>Escuse me, on June 2, 2019 I uploaded a new version of Spatial
>Sustainability Assessment Model (SSAM)plugin but It's still not
>approved.
>Are there problems I haven't seen?
>Thanks you
>Gianluca
>
>Il giorno ven 17 mag 2019 alle ore 22:54  ha scritto:
>
>>
>> Plugin SSAM approval by pcav.
>> The plugin version "[1714] SSAM 1.0.0" is now approved
>> Link: http://plugins.qgis.org/plugins/SSAM/
>>
>
>
>-- 
>Dott. Gianluca Massei, PhD

-- 
Sorry for being short___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Paolo Cavallini
+1 on all.
Thanks Alessandro.

On 16/01/19 18:28, Alessandro Pasotti wrote:
> My 2 quick cents:
> 
> 1 - new features or significant changes to existing features *must*
> provide a description of the feature/changes or a link to it in some
> form (a QEP, the PR text, a blog post an extensive commit message etc.,
> suitable for copy-paste into the documentation)
> 2 - little documentation is better than no documentation at all. I
> suggest that the documentation team be less strict in accepting PRs and
> lower the bar: we/they can always make it better later
> 3 - (speaking about the server) consider the audience: we do not
> need/want to document the standard
> apache/nginx/fcgi/mod_rewrite/whatever web-server setup, but we may
> provide pointers to upstream documentation

-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Alessandro Pasotti
My 2 quick cents:

1 - new features or significant changes to existing features *must* provide
a description of the feature/changes or a link to it in some form (a QEP,
the PR text, a blog post an extensive commit message etc., suitable for
copy-paste into the documentation)
2 - little documentation is better than no documentation at all. I suggest
that the documentation team be less strict in accepting PRs and lower the
bar: we/they can always make it better later
3 - (speaking about the server) consider the audience: we do not need/want
to document the standard apache/nginx/fcgi/mod_rewrite/whatever web-server
setup, but we may provide pointers to upstream documentation



On Wed, Jan 16, 2019 at 5:48 PM Matteo Ghetta 
wrote:

> Fully agreed with all the comments.
>
> What are devs thoughts? ;)
>
> Cheers
>
> Matteo
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Matteo Ghetta
Fully agreed with all the comments.

What are devs thoughts? ;)

Cheers

Matteo
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Andreas Neumann
Yes - it is actually an example where the feature is already quite 
documented. Just not in the manual.


It is one of the better cases, when it comes to documentation.

Andreas

Am 16.01.19 um 16:07 schrieb Marco Bernasocchi:


Well to be fair, in this (and many) other cases, the "Naughty Dev" 
provided an amazingly well written description of the feature. That 
can just be copy pasted to the docs.


But yes, I think minimal docs, or maybe a changelog entry or a link to 
a blogpost would be good


Cheers

Marco


On 16.01.19 14:39, Alexandre Neto wrote:

+1

No more "the naughty developer didn't provide a description" 
messages, please.


Best regards,

Alexandre Neto

Paolo Cavallini > escreveu no dia quarta, 16/01/2019 às 
09:02:


Totally agreed:
* pushing at least a minimal documentation has to be a
requirement, just
like unit tests
* an automatic system is far preferable to a manual one.
Topic added to the TODO for the HF:

https://github.com/qgis/QGIS/wiki/22nd-Developer-Meeting-in-A-Coru%C3%B1a,-Spain
Thanks.

On 16/01/19 09:14, Andreas Neumann wrote:
> Hi Richard,
>
> It is something to consider - I agree that we have a
documentation crisis.
>
> On the other hand - I never see any QGIS user
reading/consulting that
> manual we provide (because it is hard to read a manual) -
that's why I
> sometimes - if a question from a user about feature x is raised - I
> don't answer directly but point to the chapter in the manual -
just to
> show users, that they should first read that manual, then
Google and
> consult stack exchange and then only ask if the other information
> sources don't help. Or attend a course ...
>
> Perhaps there are also other forms to consider besides the
manual to
> reveal hidden features?
>
> The visual changelog is a good resource to find out about new
and hidden
> features - but even that is often only a title and no text and
screenshot.
>
> Let's discuss it in A Coruna at the meeting. Perhaps we should
try your
> proposal, even if I expect some resistance from some
devs/customers.
>
> Greetings,
> Andreas
>
> Am 16.01.19 um 08:42 schrieb Richard Duivenvoorde:
>> Hi Devs,
>>
>> As I see we are in a "Documentation crisis" and seeing the
comment below
>> in a discussion (please do not take this personal!!!):
>>
>> """
>> No. From my side it's no documentation PR planned at the
moment. Feel
>> free to do something and to take the stuff from my blogpost.
>> """
>>
>> I think our project has to do something. Even throwing money
at people
>> (we did as PSC!) does not help...
>>
>> I'm really afraid QGIS will end up with a lot of HIDDEN
features and
>> possibilities. A lot of it's functionality is hiding because
it isn't
>> mentioned in the QGIS docs or blogs (maybe in other (company)
blogs),
>> but only in the code ...
>>
>> I do not want to be a PITA, but can we maybe add a mandatory
requirement
>> for a pull request that in case of a new feature the dev adds some
>> mandatory Text and Images about the feature IN the PR?
>>
>> He/she can also ask a community member to do that by giving some
>> interview.
>>
>> It is really NO fun for doc writers to find a [FEATURE] issue
in the doc
>> writing issues list. He/she has to start guessing how it was
>> implemented, try it out, or google for some blogpost or start
talking to
>> the dev etcetc. Really NO fun if you want to work on the
documenation
>> because it takes so much time!
>>
>> I think implementing developer is just the best person to
write one or
>> two paragraphs (and add some images, hey he has also tested during
>> coding isn't it?).
>> In this way doc writing could then be just 'copy and paste'
the text, do
>> some grammar fixes and add images from the PR of the dev in
the docs.
>>
>> I know a project like MapProxy handles it's PR's even more
rigid: if
>> Documentation is not part of the code PR, it is just nog
pulled. It is
>> easier there because they have text only docs IN the src tree;
that is
>> why I propose to do only text + images.
>>
>> I know this is an old idea, but seeing one dev asking about
already
>> implemented features to another dev was the drop...
>> And I'm aware that you cannot prevent this anyway as
nobody likes to
>> RTFM :-)
>>
>> Regards,
>>
>> Richard Duivenvoorde
>>
>>
>>  Forwarded Message 
>> Subject: Re: [qgis/QGIS-Enhancement-Proposals] Translation
of .qgs
>> project files (#90)
>> Date: Tue, 15 Jan 2019 12:28:40 -0800
>>
>> ...
>>
>> No. From my side it's 

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Marco Bernasocchi
Well to be fair, in this (and many) other cases, the "Naughty Dev"
provided an amazingly well written description of the feature. That can
just be copy pasted to the docs.

But yes, I think minimal docs, or maybe a changelog entry or a link to a
blogpost would be good

Cheers

Marco


On 16.01.19 14:39, Alexandre Neto wrote:
> +1
>
> No more "the naughty developer didn't provide a description" messages,
> please.
>
> Best regards,
>
> Alexandre Neto
>
> Paolo Cavallini mailto:cavall...@faunalia.it>>
> escreveu no dia quarta, 16/01/2019 às 09:02:
>
> Totally agreed:
> * pushing at least a minimal documentation has to be a
> requirement, just
> like unit tests
> * an automatic system is far preferable to a manual one.
> Topic added to the TODO for the HF:
> 
> https://github.com/qgis/QGIS/wiki/22nd-Developer-Meeting-in-A-Coru%C3%B1a,-Spain
> Thanks.
>
> On 16/01/19 09:14, Andreas Neumann wrote:
> > Hi Richard,
> >
> > It is something to consider - I agree that we have a
> documentation crisis.
> >
> > On the other hand - I never see any QGIS user reading/consulting
> that
> > manual we provide (because it is hard to read a manual) - that's
> why I
> > sometimes - if a question from a user about feature x is raised - I
> > don't answer directly but point to the chapter in the manual -
> just to
> > show users, that they should first read that manual, then Google and
> > consult stack exchange and then only ask if the other information
> > sources don't help. Or attend a course ...
> >
> > Perhaps there are also other forms to consider besides the manual to
> > reveal hidden features?
> >
> > The visual changelog is a good resource to find out about new
> and hidden
> > features - but even that is often only a title and no text and
> screenshot.
> >
> > Let's discuss it in A Coruna at the meeting. Perhaps we should
> try your
> > proposal, even if I expect some resistance from some devs/customers.
> >
> > Greetings,
> > Andreas
> >
> > Am 16.01.19 um 08:42 schrieb Richard Duivenvoorde:
> >> Hi Devs,
> >>
> >> As I see we are in a "Documentation crisis" and seeing the
> comment below
> >> in a discussion (please do not take this personal!!!):
> >>
> >> """
> >> No. From my side it's no documentation PR planned at the
> moment. Feel
> >> free to do something and to take the stuff from my blogpost.
> >> """
> >>
> >> I think our project has to do something. Even throwing money at
> people
> >> (we did as PSC!) does not help...
> >>
> >> I'm really afraid QGIS will end up with a lot of HIDDEN
> features and
> >> possibilities. A lot of it's functionality is hiding because it
> isn't
> >> mentioned in the QGIS docs or blogs (maybe in other (company)
> blogs),
> >> but only in the code ...
> >>
> >> I do not want to be a PITA, but can we maybe add a mandatory
> requirement
> >> for a pull request that in case of a new feature the dev adds some
> >> mandatory Text and Images about the feature IN the PR?
> >>
> >> He/she can also ask a community member to do that by giving some
> >> interview.
> >>
> >> It is really NO fun for doc writers to find a [FEATURE] issue
> in the doc
> >> writing issues list. He/she has to start guessing how it was
> >> implemented, try it out, or google for some blogpost or start
> talking to
> >> the dev etcetc. Really NO fun if you want to work on the
> documenation
> >> because it takes so much time!
> >>
> >> I think implementing developer is just the best person to write
> one or
> >> two paragraphs (and add some images, hey he has also tested during
> >> coding isn't it?).
> >> In this way doc writing could then be just 'copy and paste' the
> text, do
> >> some grammar fixes and add images from the PR of the dev in the
> docs.
> >>
> >> I know a project like MapProxy handles it's PR's even more
> rigid: if
> >> Documentation is not part of the code PR, it is just nog
> pulled. It is
> >> easier there because they have text only docs IN the src tree;
> that is
> >> why I propose to do only text + images.
> >>
> >> I know this is an old idea, but seeing one dev asking about already
> >> implemented features to another dev was the drop...
> >> And I'm aware that you cannot prevent this anyway as nobody
> likes to
> >> RTFM :-)
> >>
> >> Regards,
> >>
> >> Richard Duivenvoorde
> >>
> >>
> >>  Forwarded Message 
> >> Subject: Re: [qgis/QGIS-Enhancement-Proposals] Translation
> of .qgs
> >> project files (#90)
> >> Date: Tue, 15 Jan 2019 12:28:40 -0800
> >>
> >> ...
> >>
> >> No. From my side 

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Alexandre Neto
+1

No more "the naughty developer didn't provide a description" messages,
please.

Best regards,

Alexandre Neto

Paolo Cavallini  escreveu no dia quarta, 16/01/2019
às 09:02:

> Totally agreed:
> * pushing at least a minimal documentation has to be a requirement, just
> like unit tests
> * an automatic system is far preferable to a manual one.
> Topic added to the TODO for the HF:
>
> https://github.com/qgis/QGIS/wiki/22nd-Developer-Meeting-in-A-Coru%C3%B1a,-Spain
> Thanks.
>
> On 16/01/19 09:14, Andreas Neumann wrote:
> > Hi Richard,
> >
> > It is something to consider - I agree that we have a documentation
> crisis.
> >
> > On the other hand - I never see any QGIS user reading/consulting that
> > manual we provide (because it is hard to read a manual) - that's why I
> > sometimes - if a question from a user about feature x is raised - I
> > don't answer directly but point to the chapter in the manual - just to
> > show users, that they should first read that manual, then Google and
> > consult stack exchange and then only ask if the other information
> > sources don't help. Or attend a course ...
> >
> > Perhaps there are also other forms to consider besides the manual to
> > reveal hidden features?
> >
> > The visual changelog is a good resource to find out about new and hidden
> > features - but even that is often only a title and no text and
> screenshot.
> >
> > Let's discuss it in A Coruna at the meeting. Perhaps we should try your
> > proposal, even if I expect some resistance from some devs/customers.
> >
> > Greetings,
> > Andreas
> >
> > Am 16.01.19 um 08:42 schrieb Richard Duivenvoorde:
> >> Hi Devs,
> >>
> >> As I see we are in a "Documentation crisis" and seeing the comment below
> >> in a discussion (please do not take this personal!!!):
> >>
> >> """
> >> No. From my side it's no documentation PR planned at the moment. Feel
> >> free to do something and to take the stuff from my blogpost.
> >> """
> >>
> >> I think our project has to do something. Even throwing money at people
> >> (we did as PSC!) does not help...
> >>
> >> I'm really afraid QGIS will end up with a lot of HIDDEN features and
> >> possibilities. A lot of it's functionality is hiding because it isn't
> >> mentioned in the QGIS docs or blogs (maybe in other (company) blogs),
> >> but only in the code ...
> >>
> >> I do not want to be a PITA, but can we maybe add a mandatory requirement
> >> for a pull request that in case of a new feature the dev adds some
> >> mandatory Text and Images about the feature IN the PR?
> >>
> >> He/she can also ask a community member to do that by giving some
> >> interview.
> >>
> >> It is really NO fun for doc writers to find a [FEATURE] issue in the doc
> >> writing issues list. He/she has to start guessing how it was
> >> implemented, try it out, or google for some blogpost or start talking to
> >> the dev etcetc. Really NO fun if you want to work on the documenation
> >> because it takes so much time!
> >>
> >> I think implementing developer is just the best person to write one or
> >> two paragraphs (and add some images, hey he has also tested during
> >> coding isn't it?).
> >> In this way doc writing could then be just 'copy and paste' the text, do
> >> some grammar fixes and add images from the PR of the dev in the docs.
> >>
> >> I know a project like MapProxy handles it's PR's even more rigid: if
> >> Documentation is not part of the code PR, it is just nog pulled. It is
> >> easier there because they have text only docs IN the src tree; that is
> >> why I propose to do only text + images.
> >>
> >> I know this is an old idea, but seeing one dev asking about already
> >> implemented features to another dev was the drop...
> >> And I'm aware that you cannot prevent this anyway as nobody likes to
> >> RTFM :-)
> >>
> >> Regards,
> >>
> >> Richard Duivenvoorde
> >>
> >>
> >>  Forwarded Message 
> >> Subject: Re: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs
> >> project files (#90)
> >> Date: Tue, 15 Jan 2019 12:28:40 -0800
> >>
> >> ...
> >>
> >> No. From my side it's no documentation PR planned at the moment. Feel
> >> free to do something and to take the stuff from my blogpost.
> >>
> >> —
> >> You are receiving this because you are subscribed to this thread.
> >> Reply to this email directly, view it on GitHub
> >> <
> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/90#issuecomment-454539249
> >
> >>
> >>
> >>
> >> ___
> >> QGIS-Developer mailing list
> >> QGIS-Developer@lists.osgeo.org
> >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> 

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Paolo Cavallini
Totally agreed:
* pushing at least a minimal documentation has to be a requirement, just
like unit tests
* an automatic system is far preferable to a manual one.
Topic added to the TODO for the HF:
https://github.com/qgis/QGIS/wiki/22nd-Developer-Meeting-in-A-Coru%C3%B1a,-Spain
Thanks.

On 16/01/19 09:14, Andreas Neumann wrote:
> Hi Richard,
> 
> It is something to consider - I agree that we have a documentation crisis.
> 
> On the other hand - I never see any QGIS user reading/consulting that
> manual we provide (because it is hard to read a manual) - that's why I
> sometimes - if a question from a user about feature x is raised - I
> don't answer directly but point to the chapter in the manual - just to
> show users, that they should first read that manual, then Google and
> consult stack exchange and then only ask if the other information
> sources don't help. Or attend a course ...
> 
> Perhaps there are also other forms to consider besides the manual to
> reveal hidden features?
> 
> The visual changelog is a good resource to find out about new and hidden
> features - but even that is often only a title and no text and screenshot.
> 
> Let's discuss it in A Coruna at the meeting. Perhaps we should try your
> proposal, even if I expect some resistance from some devs/customers.
> 
> Greetings,
> Andreas
> 
> Am 16.01.19 um 08:42 schrieb Richard Duivenvoorde:
>> Hi Devs,
>>
>> As I see we are in a "Documentation crisis" and seeing the comment below
>> in a discussion (please do not take this personal!!!):
>>
>> """
>> No. From my side it's no documentation PR planned at the moment. Feel
>> free to do something and to take the stuff from my blogpost.
>> """
>>
>> I think our project has to do something. Even throwing money at people
>> (we did as PSC!) does not help...
>>
>> I'm really afraid QGIS will end up with a lot of HIDDEN features and
>> possibilities. A lot of it's functionality is hiding because it isn't
>> mentioned in the QGIS docs or blogs (maybe in other (company) blogs),
>> but only in the code ...
>>
>> I do not want to be a PITA, but can we maybe add a mandatory requirement
>> for a pull request that in case of a new feature the dev adds some
>> mandatory Text and Images about the feature IN the PR?
>>
>> He/she can also ask a community member to do that by giving some
>> interview.
>>
>> It is really NO fun for doc writers to find a [FEATURE] issue in the doc
>> writing issues list. He/she has to start guessing how it was
>> implemented, try it out, or google for some blogpost or start talking to
>> the dev etcetc. Really NO fun if you want to work on the documenation
>> because it takes so much time!
>>
>> I think implementing developer is just the best person to write one or
>> two paragraphs (and add some images, hey he has also tested during
>> coding isn't it?).
>> In this way doc writing could then be just 'copy and paste' the text, do
>> some grammar fixes and add images from the PR of the dev in the docs.
>>
>> I know a project like MapProxy handles it's PR's even more rigid: if
>> Documentation is not part of the code PR, it is just nog pulled. It is
>> easier there because they have text only docs IN the src tree; that is
>> why I propose to do only text + images.
>>
>> I know this is an old idea, but seeing one dev asking about already
>> implemented features to another dev was the drop...
>> And I'm aware that you cannot prevent this anyway as nobody likes to
>> RTFM :-)
>>
>> Regards,
>>
>> Richard Duivenvoorde
>>
>>
>>  Forwarded Message 
>> Subject: Re: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs
>> project files (#90)
>> Date: Tue, 15 Jan 2019 12:28:40 -0800
>>
>> ...
>>
>> No. From my side it's no documentation PR planned at the moment. Feel
>> free to do something and to take the stuff from my blogpost.
>>
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub
>> 
>>
>>
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Andreas Neumann

Hi Richard,

It is something to consider - I agree that we have a documentation crisis.

On the other hand - I never see any QGIS user reading/consulting that 
manual we provide (because it is hard to read a manual) - that's why I 
sometimes - if a question from a user about feature x is raised - I 
don't answer directly but point to the chapter in the manual - just to 
show users, that they should first read that manual, then Google and 
consult stack exchange and then only ask if the other information 
sources don't help. Or attend a course ...


Perhaps there are also other forms to consider besides the manual to 
reveal hidden features?


The visual changelog is a good resource to find out about new and hidden 
features - but even that is often only a title and no text and screenshot.


Let's discuss it in A Coruna at the meeting. Perhaps we should try your 
proposal, even if I expect some resistance from some devs/customers.


Greetings,
Andreas

Am 16.01.19 um 08:42 schrieb Richard Duivenvoorde:

Hi Devs,

As I see we are in a "Documentation crisis" and seeing the comment below
in a discussion (please do not take this personal!!!):

"""
No. From my side it's no documentation PR planned at the moment. Feel
free to do something and to take the stuff from my blogpost.
"""

I think our project has to do something. Even throwing money at people
(we did as PSC!) does not help...

I'm really afraid QGIS will end up with a lot of HIDDEN features and
possibilities. A lot of it's functionality is hiding because it isn't
mentioned in the QGIS docs or blogs (maybe in other (company) blogs),
but only in the code ...

I do not want to be a PITA, but can we maybe add a mandatory requirement
for a pull request that in case of a new feature the dev adds some
mandatory Text and Images about the feature IN the PR?

He/she can also ask a community member to do that by giving some interview.

It is really NO fun for doc writers to find a [FEATURE] issue in the doc
writing issues list. He/she has to start guessing how it was
implemented, try it out, or google for some blogpost or start talking to
the dev etcetc. Really NO fun if you want to work on the documenation
because it takes so much time!

I think implementing developer is just the best person to write one or
two paragraphs (and add some images, hey he has also tested during
coding isn't it?).
In this way doc writing could then be just 'copy and paste' the text, do
some grammar fixes and add images from the PR of the dev in the docs.

I know a project like MapProxy handles it's PR's even more rigid: if
Documentation is not part of the code PR, it is just nog pulled. It is
easier there because they have text only docs IN the src tree; that is
why I propose to do only text + images.

I know this is an old idea, but seeing one dev asking about already
implemented features to another dev was the drop...
And I'm aware that you cannot prevent this anyway as nobody likes to
RTFM :-)

Regards,

Richard Duivenvoorde


 Forwarded Message 
Subject:Re: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs
project files (#90)
Date:   Tue, 15 Jan 2019 12:28:40 -0800

...

No. From my side it's no documentation PR planned at the moment. Feel
free to do something and to take the stuff from my blogpost.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs project files (#90)

2019-01-16 Thread Nyall Dawson
On Wed, 16 Jan 2019 at 17:42, Richard Duivenvoorde  wrote:

> I do not want to be a PITA, but can we maybe add a mandatory requirement
> for a pull request that in case of a new feature the dev adds some
> mandatory Text and Images about the feature IN the PR?

Random idea: could we code up a test on Travis which checks if a PR
has the feature tag (or "feature" in the commit message), and rejects
if the commit message doesn't meet certain criteria?

Past experience has shown that policies which Travis enforces for us
are much more successful than ones we just decide.

Nyall

>
> He/she can also ask a community member to do that by giving some interview.
>
> It is really NO fun for doc writers to find a [FEATURE] issue in the doc
> writing issues list. He/she has to start guessing how it was
> implemented, try it out, or google for some blogpost or start talking to
> the dev etcetc. Really NO fun if you want to work on the documenation
> because it takes so much time!
>
> I think implementing developer is just the best person to write one or
> two paragraphs (and add some images, hey he has also tested during
> coding isn't it?).
> In this way doc writing could then be just 'copy and paste' the text, do
> some grammar fixes and add images from the PR of the dev in the docs.
>
> I know a project like MapProxy handles it's PR's even more rigid: if
> Documentation is not part of the code PR, it is just nog pulled. It is
> easier there because they have text only docs IN the src tree; that is
> why I propose to do only text + images.
>
> I know this is an old idea, but seeing one dev asking about already
> implemented features to another dev was the drop...
> And I'm aware that you cannot prevent this anyway as nobody likes to
> RTFM :-)
>
> Regards,
>
> Richard Duivenvoorde
>
>
>  Forwarded Message 
> Subject:Re: [qgis/QGIS-Enhancement-Proposals] Translation of .qgs
> project files (#90)
> Date:   Tue, 15 Jan 2019 12:28:40 -0800
>
> ...
>
> No. From my side it's no documentation PR planned at the moment. Feel
> free to do something and to take the stuff from my blogpost.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> 
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Ribbon-like UI for QGIS

2018-09-13 Thread Nyall Dawson
On Fri, 14 Sep 2018 at 15:29, Idan Miara  wrote:
>
> Nyall,
> Thank you for the input!
> Do you think it would be relatively easy to rebase on the latest 2.18 from 
> 2.8?

No, I don't think that would be an easy task at all! Even between 2.8
-> 2.18 there's been thousands, maybe 100's thousands of lines of code
changed.

You'd probably have more luck cherry-picking individual commits
between the kadas branch and QGIS 2.18.

Nyall


>
>
>
> On Fri, 14 Sep 2018, 02:57 Nyall Dawson,  wrote:
>>
>> On Thu, 13 Sep 2018 at 21:41, Idan Miara  wrote:
>>
>> > I see that kadas-albireo it is based on QGIS 2.8.
>> > Are there any plans to rebase to QGIS 3 or to send changes upstream to the 
>> > official QGIS build ?
>>
>> Unfortunately I don't think that's even possible now -- the
>> differences between the two codebases is just too extreme, given the
>> HUGE amount of changes made for QGIS 3.0. I suspect the effort of
>> re-writing the changes made in the fork would be less than the effort
>> required to port them now.
>>
>> Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Ribbon-like UI for QGIS

2018-09-13 Thread Idan Miara
Nyall,
Thank you for the input!
Do you think it would be relatively easy to rebase on the latest 2.18 from
2.8?



On Fri, 14 Sep 2018, 02:57 Nyall Dawson,  wrote:

> On Thu, 13 Sep 2018 at 21:41, Idan Miara  wrote:
>
> > I see that kadas-albireo it is based on QGIS 2.8.
> > Are there any plans to rebase to QGIS 3 or to send changes upstream to
> the official QGIS build ?
>
> Unfortunately I don't think that's even possible now -- the
> differences between the two codebases is just too extreme, given the
> HUGE amount of changes made for QGIS 3.0. I suspect the effort of
> re-writing the changes made in the fork would be less than the effort
> required to port them now.
>
> Nyall
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Ribbon-like UI for QGIS

2018-09-13 Thread Nyall Dawson
On Thu, 13 Sep 2018 at 21:41, Idan Miara  wrote:

> I see that kadas-albireo it is based on QGIS 2.8.
> Are there any plans to rebase to QGIS 3 or to send changes upstream to the 
> official QGIS build ?

Unfortunately I don't think that's even possible now -- the
differences between the two codebases is just too extreme, given the
HUGE amount of changes made for QGIS 3.0. I suspect the effort of
re-writing the changes made in the fork would be less than the effort
required to port them now.

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

Re: [QGIS-Developer] Fwd: Ribbon-like UI for QGIS

2018-09-13 Thread Idan Miara
Hi,

Thanks you all!

Marco,
I see that kadas-albireo  it
is based on QGIS 2.8.
Are there any plans to rebase to QGIS 3 or to send changes upstream to the
official QGIS build ?

Kind regards,
Idan.


On Thu, 13 Sep 2018 at 14:26, Marco Hugentobler  wrote:

> Hi Idan
>
>
> I guess you mean the software Kadas Albireo? It is here on github:
>
> https://github.com/sourcepole/kadas-albireo
>
>
> Regards,
>
> Marco
>
> Am 13.09.2018 um 13:12 schrieb Idan Miara:
>
> Hi,
>
> Would you please advise about the QGIS Ribbon UI fork that Tim mentioned ?
>
> Kind regards,
> Idan.
>
> -- Forwarded message -
> From: Tim Sutton 
> Date: Thu, 13 Sep 2018 at 14:03
> Subject: Re: [QGIS-Developer] Ribbon-like UI for QGIS
> To: Idan Miara 
> Cc: QGIS Developer 
>
>
> Hi Idan
>
> Sourcepole already did a very nice ribbon implementation for QGIS for
> their fork of QGIS for the Swiss military. It was on GitHub somewhere
>
> https://github.com/sourcepole?utf8=✓=qgis==
>
> But I can’t see where in their repos it is any more. There are no active
> plans to port this work to the official QGIS builds though.
>
>
> Regards
>
> Tim
>
> On 13 Sep 2018, at 12:47, Idan Miara  wrote:
>
> Hi,
>
> How complicated would it be to implement (or sponsor) a Ribbon-like UI to
> QGIS?
> (i.e. MS-office 2007+)
> Do you think people would like that kind of UI for QGIS?
>
> Regards,
> Idan.
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> —
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Ex Project chair:* QGIS.org
>
> Visit http://kartoza.com to find out about open source:
>
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
>
> *Skype*: timlinux
> *IRC:* timlinux on #qgis at freenode.net
>
>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Plugin version approval

2018-03-24 Thread Heikki Vesanto
Excellent. Thanks Paolo.

On Fri 23 Mar 2018, 23:11 Paolo Cavallini,  wrote:

> Done.
> Thanks for letting me know.
> All the best.
>
> Il 23/03/2018 11:16, Heikki Vesanto ha scritto:
> > I have a couple of new updates to my plugins that have been awaiting
> > approval since Monday:
> >
> > Version 1.1:
> > https://plugins.qgis.org/plugins/Multi_Ring_Buffer/
> >
> > Version 0.4:
> > https://plugins.qgis.org/plugins/SelectWithin/
> >
> > The current versions live in the repo do not work with QGIS 3.0. There
> > were some minor changes to the API between 2.99 and 3.0 when the
> > plugins were converted.
> >
> > So I have had a couple of bug reports:
> >
> > https://github.com/HeikkiVesanto/MultiRingBuffer/issues/6
> > https://github.com/HeikkiVesanto/MultiRingBuffer/issues/8
> >
> > Would be good to get these live soon.
> >
> > Thanks
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Plugin version approval

2018-03-23 Thread Paolo Cavallini
Done.
Thanks for letting me know.
All the best.

Il 23/03/2018 11:16, Heikki Vesanto ha scritto:
> I have a couple of new updates to my plugins that have been awaiting
> approval since Monday:
> 
> Version 1.1:
> https://plugins.qgis.org/plugins/Multi_Ring_Buffer/
> 
> Version 0.4:
> https://plugins.qgis.org/plugins/SelectWithin/
> 
> The current versions live in the repo do not work with QGIS 3.0. There
> were some minor changes to the API between 2.99 and 3.0 when the
> plugins were converted.
> 
> So I have had a couple of bug reports:
> 
> https://github.com/HeikkiVesanto/MultiRingBuffer/issues/6
> https://github.com/HeikkiVesanto/MultiRingBuffer/issues/8
> 
> Would be good to get these live soon.
> 
> Thanks
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 


-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: [SoC] [Action required] Please prepare the ideas page for GSoC 2018

2018-01-09 Thread Werner Macho
Hi Alex,

I can create the page, but I have no other ideas than my own ;)
Hope that a lot of ideas will come up .

thanks a lot
Werner

On Tue, Jan 9, 2018 at 3:59 PM, Alexander Bruy 
wrote:

> Hi,
>
> if we plan to participate in GSoC this year it is necessary to create
> ideas page
>
>
> -- Forwarded message --
> From: Margherita Di Leo 
> Date: 2018-01-09 16:57 GMT+02:00
> Subject: [SoC] [Action required] Please prepare the ideas page for GSoC
> 2018
> To: OSGeo Discussions , OSGeo-SoC <
> s...@lists.osgeo.org>
> Копія: "gsoc-adminosgeo.org" 
>
>
> Dear members of the Community,
>
> this is a reminder that to participate in GSoC also this year we need
> you to send us (admins:  ) the URL for your
> project's ideas page.
>
> Every idea should indicate a title, a description, 2 mentors and a
> test for the students to submit to your evaluation. The test aims at
> evaluating if the student is capable for the project, so please design
> the test having in mind the skills required to complete the project.
>
> Time is short, we need to collect all URLs by Jan 20.
>
> Thanks and please forward to your project community.
>
> Cheers,
>
> --
> Margherita Di Leo
>
> ___
> SoC mailing list
> s...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/soc
>
>
> --
> Alexander Bruy
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: My PostgreSQL/PostGIS function to create all missing spatial indexes

2017-12-03 Thread Jorge Gustavo Rocha
Good morning Michaël, Loïc,

Add PostGIS Table(s) dialogue already shows our spatial enabled tables.

We might just add another column to show if that geometry column is
already indexed or not. We can add another action button to create it,
enabled if missing.

I've added a very simple mockup in this gist [1].

This approach is more simple to implement, I think. It can be applied to
other providers as well.

Regards,

Jorge Gustavo

[1] https://gist.github.com/jgrocha/a51d763fbe702fa3bf84f8192a979923


On 03-12-2017 08:36, kimaidou wrote:
> Hi Jorge
> 
> This feature would be good to have in the DB manager, but I do not think
> we should create a function in any database without warning the user.
> 
> Inside QGIS, we should be less intrusive and only run the SELECT SQL
> inside the function to get all missing indexes, show them in a QGIS
> table view with checkboxes, and a button to create selected indexes.
> I could propose a PR for this if I find time (heavy workload this end of
> year...)
> 
> Regards
> Michaël
> 
> 2017-12-01 17:09 GMT+01:00 Jorge Gustavo Rocha  >:
> 
> Nice contribution, Michaël! Tested and approved :-)
> 
> We might use this query to offer the option "Check missing spatial
> indexes" in DB Manager, with an additional checkbox to "Add missing
> indexes". Initially just for the Postgis provider, but it can be
> implemented for other providers.
> 
> What do you think?
> 
> Regards,
> 
> Jorge Gustavo
> 
> 
> 

J. Gustavo
-- 
Jorge Gustavo Rocha
Departamento de Informática
Universidade do Minho
4710-057 Braga
Tel: +351 253604480
Fax: +351 253604471
Móvel: +351 910333888
skype: nabocudnosor
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: My PostgreSQL/PostGIS function to create all missing spatial indexes

2017-12-03 Thread Lbartoletti
  Hi,And what about some snippets/useful query in DB manager like‎ pgModeler ? Regards.Loïc. Envoyé de mon smartphone BlackBerry 10.De: kimaidouEnvoyé: dimanche 3 décembre 2017 09:37À: Jorge Gustavo RochaCc: qgis-developerObjet: Re: [QGIS-Developer] Fwd: My PostgreSQL/PostGIS function to create all missing spatial indexesHi JorgeThis feature would be good to have in the DB manager, but I do not think we should create a function in any database without warning the user.Inside QGIS, we should be less intrusive and only run the SELECT SQL inside the function to get all missing indexes, show them in a QGIS table view with checkboxes, and a button to create selected indexes.I could propose a PR for this if I find time (heavy workload this end of year...)RegardsMichaël2017-12-01 17:09 GMT+01:00 Jorge Gustavo Rocha <j...@di.uminho.pt>:Nice contribution, Michaël! Tested and approved :-)

We might use this query to offer the option "Check missing spatial
indexes" in DB Manager, with an additional checkbox to "Add missing
indexes". Initially just for the Postgis provider, but it can be
implemented for other providers.

What do you think?

Regards,

Jorge Gustavo


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: My PostgreSQL/PostGIS function to create all missing spatial indexes

2017-12-03 Thread kimaidou
Hi Jorge

This feature would be good to have in the DB manager, but I do not think we
should create a function in any database without warning the user.

Inside QGIS, we should be less intrusive and only run the SELECT SQL inside
the function to get all missing indexes, show them in a QGIS table view
with checkboxes, and a button to create selected indexes.
I could propose a PR for this if I find time (heavy workload this end of
year...)

Regards
Michaël

2017-12-01 17:09 GMT+01:00 Jorge Gustavo Rocha :

> Nice contribution, Michaël! Tested and approved :-)
>
> We might use this query to offer the option "Check missing spatial
> indexes" in DB Manager, with an additional checkbox to "Add missing
> indexes". Initially just for the Postgis provider, but it can be
> implemented for other providers.
>
> What do you think?
>
> Regards,
>
> Jorge Gustavo
>
>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: My PostgreSQL/PostGIS function to create all missing spatial indexes

2017-12-01 Thread kimaidou
I have improved my function.

Now it returns a table containing the schema, table name and column name.
You need to use it with
SELECT * FROM create_missing_spatial_indexes();

If you would like to only get the informations about missing indexes, there
is a new "simulate" parameter.
SELECT * FROM create_missing_spatial_indexes(True);

URL : https://gist.github.com/mdouchin/cfa0e37058bcf102ed490bc59d762042

Cheers,
Michaël

2017-12-01 12:10 GMT+01:00 Salvatore Larosa :

> Thank you very much!
>
> --
> Sent from my mobile phone
>
> Il 01 Dic 2017 12:01 PM, "kimaidou"  ha scritto:
>
>> Hi users and devs,
>>
>> I just created a very simple function [1] to create all the missing
>> spatial indexes on your table geometry columns.
>>
>> It is the 1st version, has no fancy parameter to choose tables or
>> schemas, nor return anything usefull (only notices).
>>
>> Use it with a simple
>> SELECT create_missing_spatial_indexes();
>>
>> [1] https://gist.github.com/mdouchin/cfa0e37058bcf102ed490bc59d762042
>>
>> Regards,
>> Michael
>>
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: My PostgreSQL/PostGIS function to create all missing spatial indexes

2017-12-01 Thread Salvatore Larosa
Thank you very much!

--
Sent from my mobile phone

Il 01 Dic 2017 12:01 PM, "kimaidou"  ha scritto:

> Hi users and devs,
>
> I just created a very simple function [1] to create all the missing
> spatial indexes on your table geometry columns.
>
> It is the 1st version, has no fancy parameter to choose tables or schemas,
> nor return anything usefull (only notices).
>
> Use it with a simple
> SELECT create_missing_spatial_indexes();
>
> [1] https://gist.github.com/mdouchin/cfa0e37058bcf102ed490bc59d762042
>
> Regards,
> Michael
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Re: [Qgis-psc] Feature freeze: Paid developer activities for QGIS 3.0

2017-11-03 Thread Denis Rouzaud
+1 from me too!
(I've been concerned by the release postpone quite some time, but having it
2 weeks or just before Christmas, won't be a huge change for organizations)

Le ven. 3 nov. 2017 à 12:08, Alexander Bruy  a
écrit :

> +1 from me too
>
> 2017-11-03 12:44 GMT+02:00 Matthias Kuhn :
> > Hi
> >
> > On 11/03/2017 11:36 AM, Martin Dobias wrote:
> >> Hi
> >>
> >> On Fri, Nov 3, 2017 at 11:18 AM, Andreas Neumann 
> wrote:
> >>> Hi all,
> >>>
> >>> I agree with Régis. It would be useful to have the layouts instead of
> the
> >>> old composers in QGIS 3. It would be better than the other
> alternatives,
> >>> even if it would mean a further delay of the QGIS 3 release.
> >> Agreed as well. The alternatives are really much, much inferior
> >> solutions. Nyall's estimate that he would need two weeks to get
> >> layouts replace old composer code is not that much extra time to ask
> >> after having QGIS 3.0 in development for ~1.5 year. It would be a
> >> shame if we missed the opportunity to get rid of the old composer code
> >> before 3.0 -- especially after so many great cleanups in 3.0 API that
> >> have been done. The print layouts is not just an ordinary feature - it
> >> is a result of a hugely successful crowdfunding campaign and many
> >> weeks of development - and something we all look forward to :-)
> >>
> >> The stability of the new codebase is reasonable concern to have, but
> >> Nyall is well known for delivering high quality results, and we still
> >> have some weeks for bug fixing before the release - and also
> >> afterwards.
> >
> > Count me +1 on these statements by Martin and Régis
> >
> >
> >>
> >>> We just have to think about the consequences. Personally, I would
> propose to
> >>> delay the QGIS 3 release again a bit, e.g. release later in December,
> just
> >>> before Christmas - because I do think that the bug fixing period, as
> it is
> >>> scheduled now is too short.
> >> That sounds sensible to me. Free copies of QGIS 3.0 as the Christmas
> >> present for everyone :-)
> >
> > That sounds very sensible to me, I won't make yet another proposal to
> > keep the original date for a "beta" release ;-)
> >
> > Matthias
> >
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> --
> Alexander Bruy
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Re: [Qgis-psc] Feature freeze: Paid developer activities for QGIS 3.0

2017-11-03 Thread Alexander Bruy
+1 from me too

2017-11-03 12:44 GMT+02:00 Matthias Kuhn :
> Hi
>
> On 11/03/2017 11:36 AM, Martin Dobias wrote:
>> Hi
>>
>> On Fri, Nov 3, 2017 at 11:18 AM, Andreas Neumann  wrote:
>>> Hi all,
>>>
>>> I agree with Régis. It would be useful to have the layouts instead of the
>>> old composers in QGIS 3. It would be better than the other alternatives,
>>> even if it would mean a further delay of the QGIS 3 release.
>> Agreed as well. The alternatives are really much, much inferior
>> solutions. Nyall's estimate that he would need two weeks to get
>> layouts replace old composer code is not that much extra time to ask
>> after having QGIS 3.0 in development for ~1.5 year. It would be a
>> shame if we missed the opportunity to get rid of the old composer code
>> before 3.0 -- especially after so many great cleanups in 3.0 API that
>> have been done. The print layouts is not just an ordinary feature - it
>> is a result of a hugely successful crowdfunding campaign and many
>> weeks of development - and something we all look forward to :-)
>>
>> The stability of the new codebase is reasonable concern to have, but
>> Nyall is well known for delivering high quality results, and we still
>> have some weeks for bug fixing before the release - and also
>> afterwards.
>
> Count me +1 on these statements by Martin and Régis
>
>
>>
>>> We just have to think about the consequences. Personally, I would propose to
>>> delay the QGIS 3 release again a bit, e.g. release later in December, just
>>> before Christmas - because I do think that the bug fixing period, as it is
>>> scheduled now is too short.
>> That sounds sensible to me. Free copies of QGIS 3.0 as the Christmas
>> present for everyone :-)
>
> That sounds very sensible to me, I won't make yet another proposal to
> keep the original date for a "beta" release ;-)
>
> Matthias
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alexander Bruy
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Fwd: Re: [Qgis-psc] Feature freeze: Paid developer activities for QGIS 3.0

2017-11-03 Thread Alessandro Pasotti
+1 from me too

On Fri, Nov 3, 2017 at 11:44 AM, Matthias Kuhn  wrote:

> Hi
>
> On 11/03/2017 11:36 AM, Martin Dobias wrote:
> > Hi
> >
> > On Fri, Nov 3, 2017 at 11:18 AM, Andreas Neumann 
> wrote:
> >> Hi all,
> >>
> >> I agree with Régis. It would be useful to have the layouts instead of
> the
> >> old composers in QGIS 3. It would be better than the other alternatives,
> >> even if it would mean a further delay of the QGIS 3 release.
> > Agreed as well. The alternatives are really much, much inferior
> > solutions. Nyall's estimate that he would need two weeks to get
> > layouts replace old composer code is not that much extra time to ask
> > after having QGIS 3.0 in development for ~1.5 year. It would be a
> > shame if we missed the opportunity to get rid of the old composer code
> > before 3.0 -- especially after so many great cleanups in 3.0 API that
> > have been done. The print layouts is not just an ordinary feature - it
> > is a result of a hugely successful crowdfunding campaign and many
> > weeks of development - and something we all look forward to :-)
> >
> > The stability of the new codebase is reasonable concern to have, but
> > Nyall is well known for delivering high quality results, and we still
> > have some weeks for bug fixing before the release - and also
> > afterwards.
>
> Count me +1 on these statements by Martin and Régis
>
>
> >
> >> We just have to think about the consequences. Personally, I would
> propose to
> >> delay the QGIS 3 release again a bit, e.g. release later in December,
> just
> >> before Christmas - because I do think that the bug fixing period, as it
> is
> >> scheduled now is too short.
> > That sounds sensible to me. Free copies of QGIS 3.0 as the Christmas
> > present for everyone :-)
>
> That sounds very sensible to me, I won't make yet another proposal to
> keep the original date for a "beta" release ;-)
>
> Matthias
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>



-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: [OSGeo-Discuss] Fwd: Google Summer of Code ideas page: action required latest by February 5th!

2017-02-01 Thread Barry Rowlingson
Okay, I've found the QGIS GSoC suggestions, I'll add my project.



On Wed, Feb 1, 2017 at 5:50 PM, Rowlingson, Barry
 wrote:
> Is there a wiki or somewhere a list of qgis-based projects for GSoC?
> I'd like to propose a QGIS-R mapping interface
>
> I've mentored a couple of projects in the past, would be nice to do another 
> one.
>
>
> On Wed, Feb 1, 2017 at 5:22 PM, Werner Macho  wrote:
>> Hi all!
>>
>> And again a reminder from OSGEO.
>> Hope that there will be some more mentors and ideas until sunday!
>>
>> best wishes
>> Werner
>>
>>
>> -- Forwarded message --
>> From: Margherita Di Leo 
>> Date: Wed, Feb 1, 2017 at 5:18 PM
>> Subject: [OSGeo-Discuss] Fwd: Google Summer of Code ideas page: action
>> required latest by February 5th!
>> To: OSGeo Discussions 
>>
>>
>> Dear All,
>>
>> This is a remind that the ideas page, complete with mentors, are due
>> by Feb 5th. Several projects are still missing, it would be a pity if
>> this is because they weren't reached by this email, so please spread
>> the word to your own community!
>>
>> Thanks
>>
>>
>> -- Forwarded message --
>> From: Margherita Di Leo 
>> Date: Mon, Jan 23, 2017 at 9:16 AM
>> Subject: Google Summer of Code ideas page: action required latest by
>> February 5th!
>> To: geofor...@lists.osgeo.org
>>
>>
>> Dear All,
>>
>>
>> It’s that time of the year again!
>>
>>
>> Applications for Google Summer of Code 2017 are now open for would-be
>> mentor organizations, and we are in the process of applying on behalf
>> of OSGeo. At this stage, it is extremely important that we put up a
>> nice and informative ideas page, that Google will look at in order to
>> evaluate OSGeo’s application.
>>
>>
>> *We need your help!*
>>
>>
>> As previous years, we will create an OSGeo Ideas page, that links to
>> software communities ideas pages. If you wish to participate, please,
>> start listing the ideas and the corresponding mentors of your software
>> community and send us the link to your wiki page latest by February
>> 5th.
>>
>>
>> And spread the word as much as you can!!
>>
>>
>> *Please note that from this year we have set up a group email for
>> admin purpose where you can reach all of us OSGeo GSoC admins at once:
>>  gsoc-ad...@osgeo.org.*
>>
>>
>> For further GSoC-related discussions e.g. inter/cross-project
>> ideas/proposals, ideas discussions, etc please use the long
>> established OSGeo’s SoC -- Google Summer of Code Coordination mailing
>> list (https://lists.osgeo.org/mailman/listinfo/soc).
>>
>>
>> Thank you
>>
>> the OSGeo GSoC Admins Team 2017
>>
>>
>>
>> --
>> Margherita Di Leo
>>
>>
>>
>> --
>> Margherita Di Leo
>>
>> ___
>> Discuss mailing list
>> disc...@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/discuss
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: [OSGeo-Discuss] Fwd: Google Summer of Code ideas page: action required latest by February 5th!

2017-02-01 Thread Barry Rowlingson
Is there a wiki or somewhere a list of qgis-based projects for GSoC?
I'd like to propose a QGIS-R mapping interface

I've mentored a couple of projects in the past, would be nice to do another one.


On Wed, Feb 1, 2017 at 5:22 PM, Werner Macho  wrote:
> Hi all!
>
> And again a reminder from OSGEO.
> Hope that there will be some more mentors and ideas until sunday!
>
> best wishes
> Werner
>
>
> -- Forwarded message --
> From: Margherita Di Leo 
> Date: Wed, Feb 1, 2017 at 5:18 PM
> Subject: [OSGeo-Discuss] Fwd: Google Summer of Code ideas page: action
> required latest by February 5th!
> To: OSGeo Discussions 
>
>
> Dear All,
>
> This is a remind that the ideas page, complete with mentors, are due
> by Feb 5th. Several projects are still missing, it would be a pity if
> this is because they weren't reached by this email, so please spread
> the word to your own community!
>
> Thanks
>
>
> -- Forwarded message --
> From: Margherita Di Leo 
> Date: Mon, Jan 23, 2017 at 9:16 AM
> Subject: Google Summer of Code ideas page: action required latest by
> February 5th!
> To: geofor...@lists.osgeo.org
>
>
> Dear All,
>
>
> It’s that time of the year again!
>
>
> Applications for Google Summer of Code 2017 are now open for would-be
> mentor organizations, and we are in the process of applying on behalf
> of OSGeo. At this stage, it is extremely important that we put up a
> nice and informative ideas page, that Google will look at in order to
> evaluate OSGeo’s application.
>
>
> *We need your help!*
>
>
> As previous years, we will create an OSGeo Ideas page, that links to
> software communities ideas pages. If you wish to participate, please,
> start listing the ideas and the corresponding mentors of your software
> community and send us the link to your wiki page latest by February
> 5th.
>
>
> And spread the word as much as you can!!
>
>
> *Please note that from this year we have set up a group email for
> admin purpose where you can reach all of us OSGeo GSoC admins at once:
>  gsoc-ad...@osgeo.org.*
>
>
> For further GSoC-related discussions e.g. inter/cross-project
> ideas/proposals, ideas discussions, etc please use the long
> established OSGeo’s SoC -- Google Summer of Code Coordination mailing
> list (https://lists.osgeo.org/mailman/listinfo/soc).
>
>
> Thank you
>
> the OSGeo GSoC Admins Team 2017
>
>
>
> --
> Margherita Di Leo
>
>
>
> --
> Margherita Di Leo
>
> ___
> Discuss mailing list
> disc...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/discuss
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Error during compiling QGIS master

2017-01-10 Thread matteo
Nyall,

I compiled gdal 2.1:

matteo@matteo-computer ~ $ gdalinfo --version
GDAL 2.1.0, released 2016/04/25

but I still get the same error during the compilation:

/home/matteo/lavori/QGIS/QGIS/src/core/qgsgml.cpp: In member function
‘void QgsGmlStreamingParser::endElement(const XML_Char*)’:
/home/matteo/lavori/QGIS/QGIS/src/core/qgsgml.cpp:871:57: error:
‘OGR_G_ExportToIsoWkb’ was not declared in this scope
 OGR_G_ExportToIsoWkb( hGeom, wkbNDR, pabyBuffer );
 ^
[ 13%] Building CXX object
src/core/CMakeFiles/qgis_core.dir/qgsmaplayer.cpp.o
src/core/CMakeFiles/qgis_core.dir/build.make:3814: recipe for target
'src/core/CMakeFiles/qgis_core.dir/qgsgml.cpp.o' failed
make[2]: *** [src/core/CMakeFiles/qgis_core.dir/qgsgml.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
CMakeFiles/Makefile2:1171: recipe for target
'src/core/CMakeFiles/qgis_core.dir/all' failed
make[1]: *** [src/core/CMakeFiles/qgis_core.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2



Am I missing something?

Thanks!

Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Error during compiling QGIS master

2017-01-10 Thread Nyall Dawson
On 10 Jan 2017 20:15, "matteo"  wrote:

Sorry for the encrypted mail ;)


Hi devs,

I just updated the repo and run the compilation but i get this error:

/home/matteo/lavori/QGIS/QGIS/src/core/qgsgml.cpp: In member function
‘void QgsGmlStreamingParser::endElement(const XML_Char*)’:
/home/matteo/lavori/QGIS/QGIS/src/core/qgsgml.cpp:871:57: error:
‘OGR_G_ExportToIsoWkb’ was not declared in this scope
 OGR_G_ExportToIsoWkb( hGeom, wkbNDR, pabyBuffer );
 ^
src/core/CMakeFiles/qgis_core.dir/build.make:3814: recipe for target
'src/core/CMakeFiles/qgis_core.dir/qgsgml.cpp.o' failed
make[2]: *** [src/core/CMakeFiles/qgis_core.dir/qgsgml.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
CMakeFiles/Makefile2:1171: recipe for target
'src/core/CMakeFiles/qgis_core.dir/all' failed
make[1]: *** [src/core/CMakeFiles/qgis_core.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2


What gdal version are you on?

Nyall




any hints?

Thanks!

Matteo

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: [Qt5] Compilation problems on windows

2016-12-19 Thread alisovenko
Hi!
I have a similar problem.
I try to build master qgis with qt 7.5.1 (windows 10 msvc 2013 and 2015).
But have Multiple errors and can not to build qgis:

qgis_core.lib(qgis_core.dll) : error LNK2005: "public: __thiscall
QVector::QVector(class QVector const &)" already defined in qgsgraph.obj [...] 
sgraph.obj
[E:\dev\nextgis.qgis\qgis-master-build\src\analysis\qgis_analysis.vcxproj] 
qgis_core.lib(qgis_core.dll) : error LNK2005: "public: __thiscall
QVector::~QVector(void)"
(??1?$QVector@VQVariantQAE@XZ already defined in qgsgraph.obj [...] 
qgis_core.lib(qgis_core.dll) : error LNK2005: "public: class QVector & __thiscall QVector::operator=(class
QVector const &)" (??4?$QVector@VQVariantQAEAAV0@ABV0@ 
@Z) already defined in qgsgraph.obj [...] 
qgis_core.lib(qgis_core.dll) : error LNK2005: "public: __thiscall
QVector::QVector(void)"
(??0?$QVector@VQVariantQAE@XZ) already defined in qgsgraph.obj [...] 

Maybe you know how to get rid of the error?




--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Fwd-Qt5-Compilation-problems-on-windows-tp5295744p5300521.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: [Qt5] Compilation problems on windows

2016-11-15 Thread Richard Duivenvoorde

Hi Anatoliy,

I'm not in the position to comment on the actual problems, sorry.

But can you please try QGIS master in the same setting?

Because that is the branch where all energy is put into at the moment.
2.18 had some experimental work for compiling with qt5 but is actually 
qt4, but in current master we go Qt5 all the way...


Regards,

Richard Duivenvoorde

On 14-11-16 23:54, Anatoliy Golubev wrote:

-- Forwarded message --
From: Anatoliy Golubev 
Date: 2016-11-15 1:49 GMT+03:00
Subject: [Qt5] Compilation problems on windows
To: qgis-developer 


Hi devs!

I compiled QGIS 2.18 with Qt 5.3.2 and Visual Studio 2013. There are
some problems:

0. VS 2013 dont support `noexcept` keyword and throws
qgsfield.h(383): error C3646: 'noexcept' : unknown override specifier

Setting USE_CXX_11 to FALSE manually lead to following error:
3>  Generating ui_qgsrelationreferenceconfigdlgbase.h
4>C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\include\xkeycheck.h(211): warning C4005: 'noexcept' : macro
redefinition
4>  command-line arguments :  see previous definition of 'noexcept'
4>C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\include\xkeycheck.h(212): warning C4005: 'nullptr' : macro
redefinition
4>  command-line arguments :  see previous definition of 'nullptr'
4>C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\include\xkeycheck.h(246): warning C4005: 'override' : macro
redefinition
4>  command-line arguments :  see previous definition of 'override'
4>C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\include\xkeycheck.h(250): fatal error C1189: #error :  The C++
Standard Library forbids macroizing keywords. Enable warning C4005 to
find the forbidden macro.

I added this defines to CMakeLists.txt to disable C1189 error and
redefine only noexcept:
ELSEIF (MSVC AND MSVC_VERSION GREATER 1600)
  SET(USE_CXX_11 TRUE)
+  ADD_DEFINITIONS("-D_ALLOW_KEYWORD_MACROS=1")
+  ADD_DEFINITIONS("-Dnoexcept=")

1. Q_WS_* macroses changed to Q_OS_* in Qt5
Q_WS_WIN macro in 'src/core/geometry/qgsgeometry.cpp:48' breaks
compilation on Windows.

2. Linking of all executables fails with:
2>MSVCRT.lib(crtexew.obj) : error LNK2019: unresolved external symbol
_WinMain@16 referenced in function ___tmainCRTStartup
2>D:\Projects\QGIS\build\output\Release\qgis_help.exe : fatal error
LNK1120: 1 unresolved externals

It is related to CMake Warning:
CMake Warning (dev) in src/helpviewer/CMakeLists.txt:
  Policy CMP0020 is not set: Automatically link Qt executables to qtmain
  target on Windows.  Run "cmake --help-policy CMP0020" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

Added 'CMAKE_POLICY (SET CMP0020 NEW)' to following files:
- src/app/CMakeLists.txt
- src/browser/CMakeLists.txt
- src/helpviewer/CmakeLists.txt

Setting this to root CMakeLists.txt has no effect, dont know why.

3. Running debug build fails with assert in method 'void
QgsMapLayerModel::addLayers( const QList& layers )'
line 96 (layers list is empty).
qgis output - http://pastebin.com/zaHv0hpz
call stack - http://pastebin.com/PVV8bsLW

Adding 'if ( layers.isEmpty() ) return;' fix this.

4. Multiple warnings:
6>qgis_core.lib(qgis_core.dll) : warning LNK4006: "public: __thiscall
QVector::QVector(class QVector const &)" (??0?$QVector@VQVariantQAE@ABV0@@Z) already
defined in qgsgraph.obj; second definition ignored
6>qgis_core.lib(qgis_core.dll) : warning LNK4006: "public: __thiscall
QVector::~QVector(void)"
(??1?$QVector@VQVariantQAE@XZ) already defined in qgsgraph.obj;
second definition ignored
6>qgis_core.lib(qgis_core.dll) : warning LNK4006: "public: class
QVector & __thiscall QVector::operator=(class QVector const &)"
(??4?$QVector@VQVariantQAEAAV0@ABV0@@Z) already defined in
qgsgraph.obj; second definition ignored
6>qgis_core.lib(qgis_core.dll) : warning LNK4006: "public: __thiscall
QVector::QVector(void)"
(??0?$QVector@VQVariantQAE@XZ) already defined in qgsgraph.obj;
second definition ignored.

Thats all ^_^
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: How to calculate time taken to render a vector layer?

2016-10-30 Thread Manikanta Kondeti
Hi,

There is an issue with bats installation on Mac OS X. So the current tool
you specified is not working on Mac OS X 10.11

Any other solution? or Does any python script work for computing this?



Thanks,
Manikant

On Sun, Oct 30, 2016 at 6:27 AM, Nathan Woodrow  wrote:

> Hey,
>
> I made a tool called qgis2img that can report the renderer time of a
> shapefile. Its a standalone Python script if you do a search there is notes
> on the web for it.
>
> - nathan
>
> On Sun, 30 Oct 2016 10:30 am Manikanta Kondeti 
> wrote:
>
>>
>> Hi,
>>
>>  As the subject says I have a shapefile and want to note the time it took
>> to render this shapefile when loaded. Any help regarding this will be very
>> helpful?
>>
>> Thanks,
>> Manikanta
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: How to calculate time taken to render a vector layer?

2016-10-29 Thread Nathan Woodrow
Hey,

I made a tool called qgis2img that can report the renderer time of a
shapefile. Its a standalone Python script if you do a search there is notes
on the web for it.

- nathan

On Sun, 30 Oct 2016 10:30 am Manikanta Kondeti 
wrote:

>
> Hi,
>
>  As the subject says I have a shapefile and want to note the time it took
> to render this shapefile when loaded. Any help regarding this will be very
> helpful?
>
> Thanks,
> Manikanta
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Plans after friday's release?

2016-10-20 Thread Matthias Kuhn
On 10/20/2016 11:16 AM, Mark Johnson wrote:
> 
> Would this halt all updates in the 2 branch?
> - I was hoping to submit the needed changes for gdal 2.*
> in QgsOgrProvider in the next week or so

If it's about fixes, they can happily go into 2.14 LTR and 2.18.

Matthias

> 
> Mark Johnson
> 
> 
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Re: [Geopackage] Geopackage on a shared network drive

2016-10-05 Thread Even Rouault
Le mercredi 05 octobre 2016 21:51:03, vous avez écrit :
> On 05-10-16 17:17, Even Rouault wrote:
> > Does such behaviour of files on network shares on Windows ring a bell to
> > someone ? I tried (quickly) to find if this was a documented behaviour
> > but didn't manage to find.
> 
> Hi Even, well this rang with me:
> 
> https://hub.qgis.org/issues/6448
> 
> it's an old discussion about reading shapefiles over a Windows network...
> 
> And it was also talking about VSI_CACHE, and I also (from the issue) had
> a little chat with Frank W about it:
> 
> http://irclogs.geoapt.com/gdal/%23gdal.2012-07-25.log
> 
> HTH maybe

Thanks for the pointers. Helpful indeed.

The situation has changed since now QGIS
opens the shapefile handle of the QgsOgrProvider object in read-only mode by
default (used to be read-write before latest 1.16 and 1.14 point releases), 
hence
I'm wondering if the VSI_CACHE mechanism has still some effect on the read-only 
handles owned
by the QgsOgrFeatureIterator objects, which are the ones that matter for 
rendering operations.

Seeing 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365433%28v=vs.85%29.aspx
which is about opportunistic locks, I would think that a read-write file handle 
would defeat
opportunistic locks, hence the slowness seen. That would also what Radim 
suggested in a comment :
"OpLocks are broken for read only files, not for read write files if opened as 
read only, at least this was observed on Windows XP + Samba"


-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Re: [Geopackage] Geopackage on a shared network drive

2016-10-05 Thread Richard Duivenvoorde
On 05-10-16 17:17, Even Rouault wrote:

> Does such behaviour of files on network shares on Windows ring a bell to 
> someone ? I tried (quickly) to find if this was a documented behaviour but 
> didn't manage to find.

Hi Even, well this rang with me:

https://hub.qgis.org/issues/6448

it's an old discussion about reading shapefiles over a Windows network...

And it was also talking about VSI_CACHE, and I also (from the issue) had
a little chat with Frank W about it:

http://irclogs.geoapt.com/gdal/%23gdal.2012-07-25.log

HTH maybe

Richard Duivenvoorde

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Re: [Geopackage] Geopackage on a shared network drive

2016-10-05 Thread Even Rouault
Le lundi 03 octobre 2016 11:49:52, Even Rouault a écrit :
> Le lundi 03 octobre 2016 10:33:25, Neumann, Andreas a écrit :
> > Hi Even,
> > 
> > Thank you for sharing this finding!
> > 
> > In that case I think that QGIS should offer a flag to open Geopackages
> > in read-only mode.
> 
> 
> I'm not sure we need an explicit flag for read-only mode (in the GUI I
> mean). This could bring some complications: for example should that be
> saved with the layer in a project file? But if so, then you'd be stuck to
> read-only later if you want to edit a layer, etc.
> 
> Read-only mode could be the default mode for opening, and re-open in read-
> write mode when this is needed. This is something I've done recently, but
> limited to MapInfo .tab, since opening .tab files in read-write mode
> prevented concurrent opening of the file in QGIS & MapInfo. I didn't want
> to mess with other formats, but fundamentally I don't see any reason why
> this couldn't be generalized to other formats (I'm not sure why QGIS has
> historically opened in read-write mode as first try. Probably because this
> was easier to implement)
> 
> For GPKG, there's just one subtelty though. I've fixed recently #15351 and
> to avoid deadlocks between readers, the first to open a GPKG needs
> to turn on write ahead log (WAL) journalisation, so the workflow would be
> :
> 
> - open in read only
> - check if journalisation is WAL
>- if so, done
>- if not, re-open in read-write, turn on WAL, re-open in read-only
> 
> And similar on closing to revert to the default DELETE journalisation mode.
> 
> 
> Hum, with further thinking, I don't undertstand why my suggestion in the
> discussion thread on the geopackage ML of changing the file permission to
> read- only made things faster. Because, for feature iterators, QGIS uses a
> dedicated OGR connection in read-only mode and does not use the provider
> connection that might be in read-write mode. Unless the reporter still
> uses GDAL 1.11, which used to open in read-write mode regardless of what
> the user specified (was fixed in GDAL 2.0). That must be it. I'll check
> back with the reporter. So probably all the above is not needed after
> all...

I have had several follow-up exchanges with Árni Geirsson and the conclusions 
I drew from his test results are :

- the apparent cause for performance degradation is that there exists a file 
handle opened in read/write mode on the GeoPackage. An existing file handle in 
read/write mode negatively impacts performance on read-only connections. And 
that is true when this R/W file handle is in the same process than the R/O file 
handle, or in other process (we tested ogr2ogr performance when reading a 
remote GPKG file, while QGIS opened on this GPKG)

Does such behaviour of files on network shares on Windows ring a bell to 
someone ? I tried (quickly) to find if this was a documented behaviour but 
didn't manage to find.
So my above suggested changes between 
 would appear to be worth 
(except that I went a bit too fast in my explanations and you don't want to 
turn WAL on files on network shares, but this is something I had already 
implemented per #15351)

- VSI_CACHE in the GeoPackage case (when enabled with SQLITE_USE_OGR_VFS=YES) 
does not seem to bring any performance improvement. And I'd wondering if this 
wouldn't be the case now for shapefile since (contrary to what I said above), 
both shapefile and mapinfo are now opened by default in read-only mode. Or 
perhaps VSI_CACHE has still effect since in sqlite case access are made on a 
sqlite page granularity (1024 bytes) whereas for shapefile that might be just a 
few bytes. But clearly there's something happening at Windows OS level when a 
R/W connection exists.

==> It would be cool if someone could test, with QGIS 2.16.3, shapefile 
performance on network share, by removing/commenting the set VSI_CACHE=YES 
environment variable of qgis.bat. 


> 
> > Even - since you are "Mr. Geopackage" in the QGIS project anyway - can
> > you please make sure that this can be covered in the upcoming Geopackage
> > improvements? Would a "read-only" mode also be useful for other data
> > formats? I opened a ticket at http://hub.qgis.org/issues/15652 and
> > assigned it to you. I have no idea how much effort this enhancement
> > would mean - can you please do an estimate and send me a quote for that?
> > Maybe we could still include it in the upcoming Geopackage improvements
> > financed by the Swiss QGIS user group.
> > 
> > ---
> > 
> > This also leads to a follow up question: many OGR data formats have
> > "open options". As far as I know, these options are not exposed to the
> > User in QGIS, other than the encoding - or did I miss something? Should
> > we introduce a "GUI" way in QGIS 3.x to expose these "open options" in
> > the "add vector layer" dialogue?
> 
> Open options cannot be specified through QGIS currently indeed. There are
> not so many vector drivers that expose them, mostly 

Re: [Qgis-developer] Fwd: Re: [Geopackage] Geopackage on a shared network drive

2016-10-03 Thread Matthias Kuhn
On 10/03/2016 12:16 PM, Even Rouault wrote:
> 
> Side note: on a quick try there's some oddity in the GUI. If I just change a 
> layer to Read-Only the "Toggle editing" button is still enabled. It becomes 
> disabled only after I choose the "Select features by id" mode and clicked on 
> a 
> feature. And symetrically when changing back to Read-Write.
> 

Thanks for the hint, should be fixed in here:

https://github.com/qgis/QGIS/pull/3562

Matthias
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Re: [Geopackage] Geopackage on a shared network drive

2016-10-03 Thread Even Rouault

> There's the "read only" setting (hidden away) under Project Properties
> -> Identify Layers which this could potentially hook into.

Didn't know that one! I see this is done through the 
QgsVectorLayer::setReadOnly( bool readonly )" interface. So in case we would 
need that at the provider level (which is not so confirmed in this case) we 
could plug that there.

Side note: on a quick try there's some oddity in the GUI. If I just change a 
layer to Read-Only the "Toggle editing" button is still enabled. It becomes 
disabled only after I choose the "Select features by id" mode and clicked on a 
feature. And symetrically when changing back to Read-Write.

> 
> Nyall
> 
> > ---
> > 
> > This also leads to a follow up question: many OGR data formats have "open
> > options". As far as I know, these options are not exposed to the User in
> > QGIS, other than the encoding - or did I miss something? Should we
> > introduce a "GUI" way in QGIS 3.x to expose these "open options" in the
> > "add vector layer" dialogue?
> > 
> > Thanks,
> > Andreas
> > 
> > On 2016-10-01 23:38, Even Rouault wrote:
> > 
> > FYI: An interesting finding to improve performance of large Geopackage on
> > a shared network drive.
> > 
> > --  Message transmis  --
> > 
> > Sujet : Re: [Geopackage] Geopackage on a shared network drive
> > Date : samedi 01 octobre 2016, 16:41:05
> > De : Árni Geirsson via Geopackage 
> > À : Even Rouault 
> > CC : geopack...@lists.opengeospatial.org
> > 
> > Yes! It renders very quickly after I set the read-only flag in the file
> > explorer.
> > That goes a long way towards solving the problem for me because as I
> > mentioned, the team would like to use this format to store geodata, not
> > to edit it and certainly not to make edits by multiple concurrent users.
> > Thank you so much for your help!
> > 
> > Árni
> > 
> > 
> > Árni Geirsson
> > *Alta ehf* // +354 582 5000 // +354 897 9549
> > www.alta.is  // Alta á Twitter  // Alta á
> > Facebook 
> > Gæða- og umhverfisstefna Alta 
> > 
> > 
> > 
> > 
> > On 1 October 2016 at 14:28, Even Rouault 
> > wrote:
> > 
> > Le samedi 01 octobre 2016 16:02:38, Árni Geirsson a écrit :
> > 
> > Hello Even
> > Thank you for your suggestion. I made the changes you suggested, adding
> > set SQLITE_USE_OGR_VFS=YES
> > after
> > set VSI_CACHE=TRUE
> > set VSI_CACHE_SIZE=100
> > but there was no difference. Was this perhaps not the right way to do it?
> > 
> > 
> > Yes, that's correct.
> > 
> > Hum actually reviewing the code, the cache mechanism is only enabled when
> > the
> > file is opened in read-only mode, whereas QGIS will open the file in
> > read-write
> > mode.
> > 
> > You could perhaps try to make the GPKG read-only in the explorer?, at
> > least just to test if it is a promising optimization. I guess write
> > support for the
> > cache mechanism could be added.
> > 
> > A drawback of a cache machnism is that it would defeat the updates in
> > SQLite
> > to deal with concurrent editing, but anyway such mechanisms don't work
> > very well on network shares.
> > 
> > Anyway, I would think that I am not alone in seeing this as a problem
> > 
> > but I
> > 
> > find very little about it on the web.
> > 
> > Árni
> > 
> > 
> > 
> > Árni Geirsson
> > *Alta ehf* // +354 582 5000 // +354 897 9549
> > www.alta.is  // Alta á Twitter  // Alta á
> > Facebook 
> > Gæða- og umhverfisstefna Alta 
> > 
> > 
> > 
> > 
> > On 30 September 2016 at 19:52, Even Rouault 
> > 
> > wrote:
> > 
> > Le vendredi 30 septembre 2016 00:44:45, Árni Geirsson via Geopackage a
> > 
> > écrit :
> > 
> > Dear Geopackage developers!
> > I look forward to the day when Geopackage replaces the old shapefiles
> > 
> > 
> > and I
> > 
> > thank you for your efforts. As a user in a small team that uses QGIS
> > and shares data on a NAS box, basically a Samba server for network
> > shares, I notice that Geopackage data loads very slowly, much more
> > slowly than a shapefile stored in exactly the same shared folder. I
> > have noticed this with Spatialite, too, and suspect that the problem
> > lies with Sqlite and some problem it has with the networking
> > 
> > protocol.
> > 
> > Since Geopackage is intended (as I understand) as a storage and
> > exchange format for geodata, rather than a general purpose database
> > format like Spatialite, I was
> > 
> > 
> > hoping
> > 
> > that this problem could be overcome and that the Geopackage data
> > 
> > would
> > 
> > 
> > load
> > 
> > as fast as the shapefile data from the network share. When the
> > Geopackage and shapefile data are both on a local 

Re: [Qgis-developer] Fwd: Re: [Geopackage] Geopackage on a shared network drive

2016-10-03 Thread Even Rouault
Le lundi 03 octobre 2016 10:33:25, Neumann, Andreas a écrit :
> Hi Even,
> 
> Thank you for sharing this finding!
> 
> In that case I think that QGIS should offer a flag to open Geopackages
> in read-only mode.


I'm not sure we need an explicit flag for read-only mode (in the GUI I mean). 
This could bring some complications: for example should that be saved with the 
layer in a project file? But if so, then you'd be stuck to read-only later if 
you want to edit a layer, etc.

Read-only mode could be the default mode for opening, and re-open in read-
write mode when this is needed. This is something I've done recently, but 
limited to MapInfo .tab, since opening .tab files in read-write mode prevented 
concurrent opening of the file in QGIS & MapInfo. I didn't want to mess with 
other formats, but fundamentally I don't see any reason why this couldn't be 
generalized to other formats (I'm not sure why QGIS has historically opened in 
read-write mode as first try. Probably because this was easier to implement)

For GPKG, there's just one subtelty though. I've fixed recently #15351 and to 
avoid deadlocks between readers, the first to open a GPKG needs to turn 
on write ahead log (WAL) journalisation, so the workflow would be :

- open in read only
- check if journalisation is WAL
   - if so, done
   - if not, re-open in read-write, turn on WAL, re-open in read-only

And similar on closing to revert to the default DELETE journalisation mode.


Hum, with further thinking, I don't undertstand why my suggestion in the 
discussion thread on the geopackage ML of changing the file permission to read-
only made things faster. Because, for feature iterators, QGIS uses a dedicated 
OGR connection in read-only mode and does not use the provider connection that 
might be in read-write mode. Unless the reporter still uses GDAL 1.11, which 
used to open in read-write mode regardless of what the user specified (was 
fixed 
in GDAL 2.0). That must be it. I'll check back with the reporter. So probably 
all the above is not needed after all...

> 
> Even - since you are "Mr. Geopackage" in the QGIS project anyway - can
> you please make sure that this can be covered in the upcoming Geopackage
> improvements? Would a "read-only" mode also be useful for other data
> formats? I opened a ticket at http://hub.qgis.org/issues/15652 and
> assigned it to you. I have no idea how much effort this enhancement
> would mean - can you please do an estimate and send me a quote for that?
> Maybe we could still include it in the upcoming Geopackage improvements
> financed by the Swiss QGIS user group.
> 
> ---
> 
> This also leads to a follow up question: many OGR data formats have
> "open options". As far as I know, these options are not exposed to the
> User in QGIS, other than the encoding - or did I miss something? Should
> we introduce a "GUI" way in QGIS 3.x to expose these "open options" in
> the "add vector layer" dialogue?

Open options cannot be specified through QGIS currently indeed. There are not 
so many vector drivers that expose them, mostly those who are of the database 
type (with some redundancy with the way configuring the connection is already 
offered in the GUI). Some notable exceptions in the regular file category are 
CSV and GML.
One downside of open options is that they can be rather esoteric and hard to 
understand for the average user, so I guess they should be presented in a 
expandable tab.

GDAL offers the possibility to auto-discover which open options are available 
for a format, but that doesn't solve the issue with internationalization in 
QGIS. Although I think I discussed with someone about this and one possibility 
mentionned was to dump, at QGIS build time, the strings to translate from GDAL 
in a QGIS resource file. I didn't look how internationalization worked in QGIS.

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Re: [Geopackage] Geopackage on a shared network drive

2016-10-03 Thread Nyall Dawson
On 3 October 2016 at 18:33, Neumann, Andreas  wrote:
> Hi Even,
>
> Thank you for sharing this finding!
>
> In that case I think that QGIS should offer a flag to open Geopackages in
> read-only mode.
>
> Even - since you are "Mr. Geopackage" in the QGIS project anyway - can you
> please make sure that this can be covered in the upcoming Geopackage
> improvements? Would a "read-only" mode also be useful for other data
> formats? I opened a ticket at http://hub.qgis.org/issues/15652 and assigned
> it to you. I have no idea how much effort this enhancement would mean - can
> you please do an estimate and send me a quote for that? Maybe we could still
> include it in the upcoming Geopackage improvements financed by the Swiss
> QGIS user group.

There's the "read only" setting (hidden away) under Project Properties
-> Identify Layers which this could potentially hook into.

Nyall

>
> ---
>
> This also leads to a follow up question: many OGR data formats have "open
> options". As far as I know, these options are not exposed to the User in
> QGIS, other than the encoding - or did I miss something? Should we introduce
> a "GUI" way in QGIS 3.x to expose these "open options" in the "add vector
> layer" dialogue?
>
> Thanks,
> Andreas
>
> On 2016-10-01 23:38, Even Rouault wrote:
>
> FYI: An interesting finding to improve performance of large Geopackage on a
> shared network drive.
>
> --  Message transmis  --
>
> Sujet : Re: [Geopackage] Geopackage on a shared network drive
> Date : samedi 01 octobre 2016, 16:41:05
> De : Árni Geirsson via Geopackage 
> À : Even Rouault 
> CC : geopack...@lists.opengeospatial.org
>
> Yes! It renders very quickly after I set the read-only flag in the file
> explorer.
> That goes a long way towards solving the problem for me because as I
> mentioned, the team would like to use this format to store geodata, not to
> edit it and certainly not to make edits by multiple concurrent users.
> Thank you so much for your help!
>
> Árni
>
>
> Árni Geirsson
> *Alta ehf* // +354 582 5000 // +354 897 9549
> www.alta.is  // Alta á Twitter  // Alta á
> Facebook 
> Gæða- og umhverfisstefna Alta 
>
>
>
>
> On 1 October 2016 at 14:28, Even Rouault  wrote:
>
> Le samedi 01 octobre 2016 16:02:38, Árni Geirsson a écrit :
>
> Hello Even
> Thank you for your suggestion. I made the changes you suggested, adding
> set SQLITE_USE_OGR_VFS=YES
> after
> set VSI_CACHE=TRUE
> set VSI_CACHE_SIZE=100
> but there was no difference. Was this perhaps not the right way to do it?
>
>
> Yes, that's correct.
>
> Hum actually reviewing the code, the cache mechanism is only enabled when
> the
> file is opened in read-only mode, whereas QGIS will open the file in
> read-write
> mode.
>
> You could perhaps try to make the GPKG read-only in the explorer?, at least
> just to test if it is a promising optimization. I guess write support for
> the
> cache mechanism could be added.
>
> A drawback of a cache machnism is that it would defeat the updates in
> SQLite
> to deal with concurrent editing, but anyway such mechanisms don't work very
> well on network shares.
>
> Anyway, I would think that I am not alone in seeing this as a problem
>
> but I
>
> find very little about it on the web.
>
> Árni
>
>
>
> Árni Geirsson
> *Alta ehf* // +354 582 5000 // +354 897 9549
> www.alta.is  // Alta á Twitter  // Alta á
> Facebook 
> Gæða- og umhverfisstefna Alta 
>
>
>
>
> On 30 September 2016 at 19:52, Even Rouault 
>
> wrote:
>
> Le vendredi 30 septembre 2016 00:44:45, Árni Geirsson via Geopackage a
>
> écrit :
>
> Dear Geopackage developers!
> I look forward to the day when Geopackage replaces the old shapefiles
>
>
> and I
>
> thank you for your efforts. As a user in a small team that uses QGIS
> and shares data on a NAS box, basically a Samba server for network
> shares, I notice that Geopackage data loads very slowly, much more
> slowly than a shapefile stored in exactly the same shared folder. I
> have noticed this with Spatialite, too, and suspect that the problem
> lies with Sqlite and some problem it has with the networking
>
> protocol.
>
> Since Geopackage is intended (as I understand) as a storage and
> exchange format for geodata, rather than a general purpose database
> format like Spatialite, I was
>
>
> hoping
>
> that this problem could be overcome and that the Geopackage data
>
> would
>
>
> load
>
> as fast as the shapefile data from the network share. When the
> Geopackage and shapefile data are both on a local drive, I see no
> difference in the loading speed.
>
> Do you think this will be 

Re: [Qgis-developer] Fwd: Re: [Geopackage] Geopackage on a shared network drive

2016-10-03 Thread Neumann, Andreas
Hi Even, 

Thank you for sharing this finding! 

In that case I think that QGIS should offer a flag to open Geopackages
in read-only mode. 

Even - since you are "Mr. Geopackage" in the QGIS project anyway - can
you please make sure that this can be covered in the upcoming Geopackage
improvements? Would a "read-only" mode also be useful for other data
formats? I opened a ticket at http://hub.qgis.org/issues/15652 and
assigned it to you. I have no idea how much effort this enhancement
would mean - can you please do an estimate and send me a quote for that?
Maybe we could still include it in the upcoming Geopackage improvements
financed by the Swiss QGIS user group. 

--- 

This also leads to a follow up question: many OGR data formats have
"open options". As far as I know, these options are not exposed to the
User in QGIS, other than the encoding - or did I miss something? Should
we introduce a "GUI" way in QGIS 3.x to expose these "open options" in
the "add vector layer" dialogue? 

Thanks,
Andreas 

On 2016-10-01 23:38, Even Rouault wrote:

> FYI: An interesting finding to improve performance of large Geopackage on a 
> shared network drive.
> 
> --  Message transmis  --
> 
> Sujet : Re: [Geopackage] Geopackage on a shared network drive
> Date : samedi 01 octobre 2016, 16:41:05
> De : Árni Geirsson via Geopackage 
> À : Even Rouault 
> CC : geopack...@lists.opengeospatial.org
> 
> Yes! It renders very quickly after I set the read-only flag in the file
> explorer.
> That goes a long way towards solving the problem for me because as I
> mentioned, the team would like to use this format to store geodata, not to
> edit it and certainly not to make edits by multiple concurrent users.
> Thank you so much for your help!
> 
> Árni
> 
> Árni Geirsson
> *Alta ehf* // +354 582 5000 // +354 897 9549
> www.alta.is [1]  // Alta á Twitter  // Alta á
> Facebook 
> Gæða- og umhverfisstefna Alta 
> 
> On 1 October 2016 at 14:28, Even Rouault  wrote:
> 
> Le samedi 01 octobre 2016 16:02:38, Árni Geirsson a écrit : Hello Even
> Thank you for your suggestion. I made the changes you suggested, adding
> set SQLITE_USE_OGR_VFS=YES
> after
> set VSI_CACHE=TRUE
> set VSI_CACHE_SIZE=100
> but there was no difference. Was this perhaps not the right way to do it? 
> Yes, that's correct.
> 
> Hum actually reviewing the code, the cache mechanism is only enabled when
> the
> file is opened in read-only mode, whereas QGIS will open the file in
> read-write
> mode.
> 
> You could perhaps try to make the GPKG read-only in the explorer?, at least
> just to test if it is a promising optimization. I guess write support for
> the
> cache mechanism could be added.
> 
> A drawback of a cache machnism is that it would defeat the updates in
> SQLite
> to deal with concurrent editing, but anyway such mechanisms don't work very
> well on network shares.
> 
> Anyway, I would think that I am not alone in seeing this as a problem but I 
> find very little about it on the web.
> 
> Árni
> 
> Árni Geirsson
> *Alta ehf* // +354 582 5000 // +354 897 9549
> www.alta.is [1]  // Alta á Twitter  // Alta á
> Facebook 
> Gæða- og umhverfisstefna Alta 
> 
> On 30 September 2016 at 19:52, Even Rouault 
> 
> wrote: Le vendredi 30 septembre 2016 00:44:45, Árni Geirsson via Geopackage a
> 
> écrit : Dear Geopackage developers!
> I look forward to the day when Geopackage replaces the old shapefiles 
> and I
> 
> thank you for your efforts. As a user in a small team that uses QGIS
> and shares data on a NAS box, basically a Samba server for network
> shares, I notice that Geopackage data loads very slowly, much more
> slowly than a shapefile stored in exactly the same shared folder. I
> have noticed this with Spatialite, too, and suspect that the problem
> lies with Sqlite and some problem it has with the networking
 protocol. 

> Since Geopackage is intended (as I understand) as a storage and
> exchange format for geodata, rather than a general purpose database
> format like Spatialite, I was 
> hoping
> 
> that this problem could be overcome and that the Geopackage data
 would 

> load
> 
> as fast as the shapefile data from the network share. When the
> Geopackage and shapefile data are both on a local drive, I see no
> difference in the loading speed.
> 
> Do you think this will be solved? 
> QGIS tweaks GDAL/OGR to use a large buffer size to speed up network
> access to
> shapefiles (or any format that uses the GDAL I/O layer, which is called
> "VSI").
> 
> If you look at the qgis.bat in c:\osgeo4w\bin, you will see :
> set VSI_CACHE=TRUE
> set 

Re: [Qgis-developer] Fwd: Toolbars - SVG icons management - QGIS 2.16

2016-08-19 Thread Christophe Damour

Hi Mathieu,

Thank you very much for your advice.
Backgrounds were indeed text objects, they now display well on QGIS 2.16 
after I transformed them into paths.


I still wonder what has changed with QGIS 2.16...

Have a nice day,

--
Christophe

Le 19/08/2016 à 08:47, Mathieu Pellerin a écrit :

Hey Christophe,

I won't answer your question directly I'm afraid, but there might be a 
better-practice / compatibility improvement you can do to your icons.


Question first: are the background O\D elements text objects, or 
paths? If the answer is text objects, you'd be better transform those 
into paths.


Math

On Fri, Aug 19, 2016 at 1:25 PM, Christophe Damour > wrote:


Hi,

Has anything changed regarding the way SVG icons are handled in
QGIS 2.16 ?

My python plugin's toolbar doesn't display well anymore in QGIS 2.16 :
- QGIS 2.14 :

- QGIS 2.16 :


My SVGs are 64x64 pixels, and I add them to the toolbar using this
code :
QIcon(os.path.join(pluginDir, 'icons/config.svg'))

Thanks for any hint.

-- 
Christophe




___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org 
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Unsubscribe:
http://lists.osgeo.org/mailman/listinfo/qgis-developer





___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: Toolbars - SVG icons management - QGIS 2.16

2016-08-19 Thread Mathieu Pellerin
Hey Christophe,

I won't answer your question directly I'm afraid, but there might be a
better-practice / compatibility improvement you can do to your icons.

Question first: are the background O\D elements text objects, or paths? If
the answer is text objects, you'd be better transform those into paths.

Math

On Fri, Aug 19, 2016 at 1:25 PM, Christophe Damour 
wrote:

> Hi,
>
> Has anything changed regarding the way SVG icons are handled in QGIS 2.16 ?
>
> My python plugin's toolbar doesn't display well anymore in QGIS 2.16 :
> - QGIS 2.14 :
>
> - QGIS 2.16 :
>
>
> My SVGs are 64x64 pixels, and I add them to the toolbar using this code :
> QIcon(os.path.join(pluginDir, 'icons/config.svg'))
>
> Thanks for any hint.
>
> --
> Christophe
>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Fwd: [SoC] GSoC GDAL DWG Support [Week 12 report, final]

2016-08-17 Thread Neumann, Andreas
Hi Paolo, 

I'll let Jürgen comment in more detail. 

But their approach is different to the libdxfrw approach. Also - again
the main bottleneck would be the limited OGR features styles. Also, the
approach Jürgen will do will generate label/symbology rules as good as
possible and provide caching in a SpatiaLite or geopackage file behind
the scenes.  

But it is good to have choice. If we can enable this in our "Add Vector
Layer" dialog as well, people could then decide whether they want the
OGR DXF/DWG driver or the QGIS native one through libdxfrw. 

Greetings, 

Andreas 

On 2016-08-17 08:32, Paolo Cavallini wrote:

> Hi all,
> does this have any impact on our developmant?
> All the best.
> 
>  Messaggio Inoltrato 
> *Week 12 Report [Final] blogpost link
> *
> 
> Brief description of the idea.
> 
> The aim of my project was to extend GDAL supported formats with DWG.
> 
> The state of the project as it was BEFORE your GSOC.
> 
> There was a DWG support, but it was not built-in by default, and GDAL
> Driver was based on third-party library Teigha (which is not X/MIT
> licensed, not even close).
> 
> The addition that your project brought to the software.
> 
> Libopencad (GDAL CAD Driver engine)
> 
> Overview
> 
> Libopencad is a library written in C++11, which provides a way to
> read/write CAD (DWG/DXF/DXFB) files. It was designed to have a uniformal
> API to work with any CAD files. It has a base class - CADFile.
> Inheriting this class it's possible to create a 'driver' for any CAD
> format, all you need to do - is to overwrite interface functions like
> 'GetGeometry(index)', and others. Now it has an implementation for
> DWG2000 (R15), but only for read.
> 
> Library comes with 'cadinfo' utility, which prints out everything
> library can get from file - header variables, CAD custom classes,
> presented layers and geometries with their attributes.
> 
> Internal structure
> 
> Library presents CAD objects in different ways - base class CADObject
> and other CAD...Object classes are exact analogues of how DWG format
> stores information about its objects. CADGeometry, and other classes
> which inherits it, are done for API access to CAD...Object classes.
> 
> Library supports 3 modes of reading - READ_ALL (means everything which
> can be extracted from CAD file will be read) READ_FAST (skipping some
> kind of meanless information - linetypes, CRC check, etc), READ_FASTEST
> (only geometries reading, additional info is skipped).
> 
> When parsing the file, library does not store any information it does
> not need. First, it reads file meta-information, and creates a file map.
> It only stores some info about presented layers, and header variables.
> Then, when calling application uses CADLayer.GetGeometry(index), it
> actually reads a geometry from file, using prepared file map. Sometimes
> it will be slower than having everything you have read in cache, but
> gives you more flexibility what you want to store in memory, and what
> you wont.
> 
> Library also has special classes which incapsulates I/O functions, so
> it's possible to reimplement them for your needs - by default it uses
> std::fstream, but you can make it possible to work with network by make
> a class inherited from CADFileIO.
> 
> Supported geometries list:
> 
> Point, Circle, Ellipse, Arc, Text, Solid, Spline, Line, Polyline 2D,
> Polyline 3D, LWPolyline, Ray, Raster (Images), MText, MLine, XLine,
> Polyface Mesh, 3DFace.
> 
> GDAL CAD Driver
> 
> Overview
> 
> GDAL CAD Driver uses libopencad as a datasource. Not everything that
> libopencad can read from file is mapped into OGR infrastructure, but it
> will be done in near future. Current features are:
> 
> 1.
> 
> OpenOptions are presented with 2 options:
> 
> - MODE - READ_ALL/READ_FAST/READ_FASTEST (means the same as library
> OpenOptions).
> 
> - ADD_UNSUPPORTED_GEOMETRIES_DATA (YES/NO) - unstable feature, if some
> of the objects cannot be mapped into OGR representation (or its just not
> implemented yet), it will be presented as a CADUnknown object -
> OGRFeature without geometric representation, but with basic info -
> geometry type, some additional params.
> 
> 2.
> 
> CAD header variables are mapped into metadata.
> 
> 3.
> 
> Unlike DXF driver, CAD driver stores vector data in the appropriate
> layers (not all entities in single layer).
> 
> 4.
> 
> Raster subdatasets are also supported.
> 
> 5.
> 
> Coordinate system is extracted from DWG file (if it is presented in
> accordance with ESRI Docs for DWG files), or from %FILENAME%.prj
> file in the same directory.
> 
> 6.
> 
> CAD Geometry attributes mapping is completely done into
> OGRLayerDefn. So, any ACAD BlockReference attributes will be seen in
> OGRLayerDefn.
> 
> Add all the links (hopefully permanent) to access the relevant code and
> documentation for the user to get started with testing your application.
> 
> During the planning 

Re: [Qgis-developer] Fwd: [SoC] GSoC GDAL DWG Support [Week 12 report, final]

2016-08-17 Thread Paolo Cavallini
Il 17/08/2016 08:52, Neumann, Andreas ha scritto:

> I'll let Jürgen comment in more detail.
> 
> But their approach is different to the libdxfrw approach. Also - again
> the main bottleneck would be the limited OGR features styles. Also, the
> approach Jürgen will do will generate label/symbology rules as good as
> possible and provide caching in a SpatiaLite or geopackage file behind
> the scenes. 
> 
> But it is good to have choice. If we can enable this in our "Add Vector
> Layer" dialog as well, people could then decide whether they want the
> OGR DXF/DWG driver or the QGIS native one through libdxfrw.

Thanks Andreas for the clarification.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

  1   2   3   4   >