[QGIS-Developer] Fwd: PyQGIS QgsLayoutExporter gives error "QPen::setWidthF: Setting a pen width that is out of range"

[roberto benet via QGIS-Developer]

Hello,

I have a PyQGIS app, that generates a PDFs from an Atlas.

If I generate the PDF directly from QGIS Desktop all PDF generate correctly.

But If I generate the PDF with my PyQGIS app, some PDF don't generate
properly (some elements do not appear) and give error "QPen::setWidthF:
Setting a pen width that is out of range".

The first PDF contains all the elements, the other PDF are parts of first
PDF, so the elements are missing in some PDFs that are in the first.

One year ago, this app works perfect.

I have tried to change all PDF export options, but the error continues.

I make this question in Gis StackExchange, and no one give any answer:

https://gis.stackexchange.com/questions/469644/pyqgis-qgslayoutexporter-gives-error-qpensetwidthf-setting-a-pen-width-that

Here is a part of my code:

# Generate atlas

# Es una QgsLayoutAtlas

myAtlas.beginRender()

myAtlas.next()

for i in range(0, myAtlas.count()):



exporter = QgsLayoutExporter(myAtlas.layout())

file_name=os.path.join(dir_destiny,'Individuals')+'/'+myAtlas.currentFilename()+".pdf"



pdf_settings=QgsLayoutExporter.PdfExportSettings()

pdf_settings.forceVectorOutput=False

pdf_settings.exportMetadata = False

pdf_settings.appendGeoreference = False



#pdf_settings.textRenderFormat =
QgsRenderContext.TextFormatAlwaysOutlines  # For "Always Export Text
as Paths"

pdf_settings.textRenderFormat =
QgsRenderContext.TextFormatAlwaysText # For "Always Export Text as
Text Objects"



pdf_settings.rasterizeWholeImage = True # For "Disable tiled
raster layer exports" Hace que ocupe menos si es TRUE

pdf_settings.simplifyGeometries = False



exporter.exportToPdf(file_name,pdf_settings)



Thank you In advance for your attention and help.



Kind regards,



Robert Benet
___
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.

[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.

[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

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

[Giordano Cetti via QGIS-Developer]

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

[QGIS-Developer] Fwd: hover over mouse to read raster value not showing in 3.30.0

[Paul N via QGIS-Developer]

Paul N

-- Forwarded message -
From: Paul N 
Date: Mon, 20 Mar, 2023, 4:40 pm
Subject: hover over mouse to read raster value not showing in 3.30.0
To: 


I am trying to read raster values by hover over mouse to read raster value,
but option not visible in identifying tool setting. It only shows three
option already exists in qgis 3.28.3. Mouse hower option not visible in
3.30.0 .

Regards

Paul N
___
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

[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

[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

[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

[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 

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

[Even Rouault via QGIS-Developer]

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 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)

[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)

[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)

[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)

[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

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

[Richard Duivenvoorde via QGIS-Developer]

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] Fwd: Jenks Raster Styling?

[C Hamilton via QGIS-Developer]

I am posting this email to the developers group because my current comments
are more developer related. I am contemplating writing a plugin to make up
for the lack of Natural Breaks (Jenks) not in QGIS raster styling. There is
a feature request already to have this added as a core capability, but it
is unfunded.

https://github.com/qgis/QGIS/issues/39746

I received a request for Jenks raster styling from a team that doesn't
really care whether they use QGIS or Arc. They really like the speed of
QGIS, but the manager gets the question of why doesn't QGIS have Jenks
raster styling because they need it and it is available in Arc. I have
queried some of our folks to see if it is possible to get this funded to be
developed in core QGIS, but that process is quite time consuming and
wouldn't happen anytime soon so my question for near term use is whether it
is worth doing a plugin for it or not. That is really based on the
difficulty of implementation. I'm not really supposed to be taking on new
QGIS plugin development, but if it doesn't take me too much time, then my
management probably won't complain too much.

I have been looking at the documentation for the QGIS classification
methods. I believe these contain all that is needed for doing the raster
classification. Am I correct?

QgsClassificationMethod
https://api.qgis.org/api/3.22/classQgsClassificationMethod.html

QgsClassificationJenks
https://api.qgis.org/api/3.22/classQgsClassificationJenks.html

It appears that you pass in a List of values and it outputs a list of the
ranges. I don't think this needs to be a sorted list. Hopefully that is
the case. I think I could use these classification routines for all of the
styles it supports and apply them to rasters. This seems to be the process:

1. From the input raster image copy all the pixel intensities to a List to
pass to either QgsClassificationMethod or QgsClassificationJenks.
2. The output of these classification methods is a list
of QgsClassificationRange.
3. I am guessing that once you get the output classification ranges you
would then map them to equal segments of the selected color ramp. You would
then add each range to a manual value, color and label.
4. For Interpolation it probably should be set to either Linear or
Discrete. I'm not exactly sure what Mode does and what setting it should be.

There may be a problem with large images and the large number of pixel
values. NODATA values would be skipped. If the imagery gets overly large
only decimated pixels would probably be the way to go. How would you
developers handle this if the image is large? I wouldn't want to create
such a large list to pass to the classification methods that it would crash
QGIS or cause problems.

Am I missing anything that could potentially be a problem?

Rather than a plugin, how much effort would it take for one of you core
QGIS developers to implement and add to QGIS?

Thanks,

Calvin

-- Forwarded message -
With Graduated vector symbology there are various modes such as Equal
Count, Equal Interval, Logarithmic scale ,Natural Breaks (Jenks), Pretty
Breaks, and Standard Deviation to apply the graduated style to the vector
data.

With raster styling there are only "Interpolation" options Discrete, Linear
and Exact, and then the "Mode" of Continuous, Equal Interval, and Quantile.

Is it possible to implement similar styling methods such as Jenks in raster
as you have with vector? Can these styles at least be simulated in some way
with how QGIS is now?

Thanks,

Calvin
___
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 ?

[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 ?

[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 ?

[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 ?

[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 ?

[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 ?

[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 ?

[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 ?

[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 ?

[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 ?

[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 ?

[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

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

[Richard Duivenvoorde via QGIS-Developer]

Hi Dev's,

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?

Regards,

Richard


 Forwarded Message 
Subject:Re: [Qgis-user] Latest development version of QGIS as a .msi 
standalone installer ?
Date:   Wed, 24 Aug 2022 11:51:28 +0200
From:   Luca Manganelli via Qgis-user 
Reply-To:   Luca Manganelli 
To: qgis-u...@lists.osgeo.org

Il giorno mer 24 ago 2022 alle ore 11:16 Richard Duivenvoorde mailto:rdmaili...@duif.net>> ha scritto:
 > Are you sure there is not something wrong with your install/OS?

I discovered the root cause of the problem. The operating system is Windows 7.
In this page https://qgis.org/it/site/forusers/download.html 
 there are no "Operating System 
Requirements", so I googled through internet to see that Win 7 is not supported because of 
Python 3.9.
I suggest you to add these informations

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

___
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] Fwd: [Qgis-user] Determine loading time of WFS layers

[Richard Duivenvoorde via QGIS-Developer]

See mail from userlist: I was wondering if Qt Result has the response time in 
it... then we could add it to the DeveloperTools?

Or if not, would timestamping (at start and finish) be OK for QGIS?

Regards,

Richard Duivenvoorde

 Forwarded Message 
Subject:[Qgis-user] Determine loading time of WFS layers
Date:   Tue, 23 Aug 2022 12:42:52 +
From:   Inka Tauber via Qgis-user 
Reply-To:   inka.tau...@lung.mv-regierung.de
To: qgis-u...@lists.osgeo.org



Hello,

is there any way to determine the loading time of WFS layers in QGIS? For WMS 
maps this can be done in a webbrowser, but many of our WFS layers contain huge 
amounts of data, so webbrowsers crash.

Regards


Allgemeine Datenschutzinformation:
Der telefonische, schriftliche oder elektronische Kontakt mit dem Ministerium 
für Klimaschutz, Landwirtschaft, ländliche Räume und Umwelt 
Mecklenburg-Vorpommern ist mit der Speicherung und Verarbeitung der von Ihnen 
ggf. mitgeteilten persönlichen Daten verbunden. Rechtsgrundlage hierfür ist 
Art. 6 Absatz 1 Buchstabe e der Datenschutzgrundverordnung (DSGVO) der 
Europäischen Union in Verbindung mit § 4 Abs. 1 Landesdatenschutzgesetz (DSG 
M-V).
Weitere Informationen erhalten Sie hier: https://www.regierung-mv.de/Datenschutz___
Qgis-user mailing list
qgis-u...@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

___
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

[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

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

[Piet via QGIS-Developer]

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

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

[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

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

[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



smime.p7s
Description: S/MIME Cryptographic 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: Future of PDAL in Debian

[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

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

[Richard Duivenvoorde]

FYI, see below: anybody using PDAL and able to help packaging PDAL in Debian?

Regards,

Richard Duivenvoorde


 Forwarded Message 
Subject: Future of PDAL in Debian
Resent-Date: Mon,  4 Oct 2021 03:37:35 + (UTC)
Resent-From: debian-...@lists.debian.org
Date: Mon, 4 Oct 2021 05:37:18 +0200
From: Sebastiaan Couwenberg 
To: Debian GIS Project 

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.
___
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] Fwd: Re: QGIS Docs: ReStructureText flavour?

[Jonathan Moules]

Thanks Rosa!

Both yes and no.

That does have the spec (though no reference to the "only::" thing), but 
it doesn't say what parser to use for it.


I see that the :ref: thing is pulled from python 
(https://devguide.python.org/documenting/#cross-linking-markup) but 
again, the parsers I've been trying are barfing on that (and one is a 
Python IDE!) meaning I can't actually reliably preview an RST which I 
imagine reduces contributions (I've lost an hour to this so far!).


A more general question to the community would be: Wouldn't it make more 
sense to use plain RST to allow the largest toolset possible to edit the 
docs?


Thanks again,

Jonathan


On 2021-03-31 13:28, l wrote:

Hey.
Is this what you are looking for:
https://docs.qgis.org/testing/en/docs/documentation_guidelines/writing.html#writing-documentation?
Best,
Rosa



-
MSc Rosa Aguilar - PhD Candidate
University of Twente
Faculty of Geoinformation Science and Earth Observation
Connect with me on LinkedIn
https://rosaguilar.github.io
-
The essential is invisible to the eye. Saint-Exupéry

-Original Message-
From: QGIS-Developer  On 
Behalf Of Jonathan Moules

Sent: 31 March 2021 14:21
To: QGIS Developer Mailing List 
Subject: [QGIS-Developer] QGIS Docs: ReStructureText flavour?

Hi List,

What flavour is the RST behind the QGIS docs? There are quite a few 
things in here that are syntax erroring all the parsers I'm trying and 
aren't in the basic RST spec either 
(https://docutils.sourceforge.io/docs/user/rst/cheatsheet.txt).


For example using ":ref:" for internal hyperlinks when the spec says 
they should be done like this:

https://docutils.sourceforge.io/docs/user/rst/quickref.html#internal-hyperlink-targets
(there is no "ref" in the specs). Or the `.. only:: html` that starts 
some files.


I tried looking at the QGIS Docs page but I couldn't see anything 
about what RST standard the docs should be written to. Where can I 
find the spec?


Cheers,

Jonathan

___
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] Fwd: GDAL2tiles in local crs in QGIS

[Marco Bernasocchi]

Hi all,
just a short/probably stupid question that I'm loosing way too much time on
already :)

is there a way to have gdal2tiles create tiles in a local crs (for example
EPSG:2056) and load them into QGIS?
I'm doing
gdal2tiles.py --profile=raster --zoom=0-5 --s_srs=EPSG:2056
CH_over_2000_lv95.tif test_tiles

and it looks like the resulting tilemapresource.xml and the openlayers
example are correct, but loading them in QGIS using

file:///home/marco/gis/test_tiles/{z}/{x}/{y}.png

I get a wrong placement (crs of the tiles is set to 3857, which is
"workaroundable") and wrong tiles alignment (looks like 0,0 top left vs 0,0
bottom left).

I know the TMS "standard" is old but it would still be nice to be able to
quickly take a tiff, chop it up in tiles and use it in QGIS. And using
--xyz parameter results in correct tiles but in 3857

Am I doing something stupidly wrong :) ? or is WMTS really the only way to
have tiles in local crs?

Cheers
Marco


-- 
Marco Bernasocchi
OPENGIS.ch CEO
QGIS.org Chair

Find a meeting time on my calendar 
!
ma...@opengis.ch
+41 (0)79 467 24 70 <+41794672470>







-- 
Marco Bernasocchi
OPENGIS.ch CEO
QGIS.org Chair

Find a meeting time on my calendar 
!
ma...@opengis.ch
+41 (0)79 467 24 70 <+41794672470>


___
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

[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

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

[Luiz Motta]

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

[QGIS-Developer] Fwd: [TC-Announce] OGC Geopackage Standards Working Group updates its Charter; public comment requested

[Even Rouault]

Of potential interest. "Develop a logical model for GeoPackage so that future 
implementations can be separated from the current requirement to use SQLite." 
is intriguing

--  Forwarded Message  --

Subject: [TC-Announce] OGC Geopackage Standards Working Group updates its 
Charter; public comment requested
Date: mercredi 28 octobre 2020, 10:07:46 CET
From: announce--- via TC-Announce 
To: tc-annou...@lists.opengeospatial.org

OGC Geopackage Standards Working Group updates its Charter; public comment
requested

New purpose of SWG is to revise the GeoPackage Encoding Standard and revise
existing, or produce new, extensions to improve and increase functionality



Contact: i...@ogc.org 

28 October 2020: The Open Geospatial Consortium (OGC) seeks public comment
on a revision of the Geopackage Standards Working Group (SWG) charter.
Comments are due by November 17, 2020.

The Geopackage Standards Working Group (SWG)

provides a consensus forum for revisions to the GeoPackage Encoding
Standard including approved extensions as well as the development of new
GeoPackage extensions. The SWG adopted a new charter outlining plans for
future development of the Standard.

GeoPackage was originally developed with three main goals in mind: 

 To be a convenient, efficient, and interoperable container for geospatial
information; 
 To enable operations in all computing environments, including those with
Disconnected, Degraded, Intermittent, or Limited (DDIL) network
connectivity; 
 For GeoPackage to be extensible, allowing it to evolve to meet future
operational needs.

For a good primer on Geopackage please read the post entitled
#GeoPackageDay 2020 - what is GeoPackage?

on the OGC Blog

.

The revised charter outlines the new objectives for the SWG:

 Develop a logical model for GeoPackage so that future implementations can
be separated from the current requirement to use SQLite.
 Revise existing GeoPackage standards and extensions, namely the GeoPackage
Encoding Standard 1.3.0, the GeoPackage Tiled Gridded Coverage Extension,
and the GeoPackage Related Tables Extension. In particular, the SWG will
review all outstanding Change Request Proposals submitted before the
adoption of this charter.
 Develop new GeoPackage extensions that have been requested by OGC Domain
Working Groups

.
 Perform outreach to promote GeoPackage understanding and use.

Revisions to the version 1.3.0 of the GeoPackage Encoding Standard will
improve the interoperability, capability, and clarity of the Standard. The
Tiled Gridded Coverage and Related Tables Extensions have not been revised
since their initial release and will likely benefit from additional review.
New extensions would enable new capabilities that have been requested by
the OGC community.

The Geopackage SWG plans to perform these activities by the end of calendar
year 2022.

For a good primer on Geopackage please read the post entitled
#GeoPackageDay 2020 - what is GeoPackage?

or any of the many Geopackage posts available on the OGC Blog

.

The draft revised GeoPackage SWG charter

is available for review and comment on the OGC Portal. Comments are due by
November 17, 2020, and should be submitted via the method outlined on the
draft revised GeoPackage SWG charter's public comment request page

.

About OGC

The Open Geospatial Consortium (OGC) is an international consortium of more
than 500 businesses, government agencies, research organizations, and
universities driven to make geospatial (location) information and services
FAIR - Findable, Accessible, Interoperable, and Reusable.

OGC's member-driven consensus process creates royalty free, publicly
available geospatial standards. Existing at the cutting edge, OGC actively
analyzes and anticipates emerging tech trends, and runs an agile,
collaborative Research and Development (R) lab that builds and tests
innovative prototype solutions to members' use cases.

OGC members together form a global 

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

[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

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

[Nedret Ozay]

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

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

[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

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

[Nyall Dawson]

(forwarding back to list)

-- Forwarded message -
From: Alexis R.L. 
Date: Thu, 15 Oct 2020 at 07:07
Subject: Re: [QGIS-Developer] GPKG and FID -- can we fix this mess?
To: Nyall Dawson 


> Greetings,
> Can't we have the full reset option as a failsafe method? This way we work 
> normally and when there is an error related to fids we simply scrap them.
> Personally I don't get fid issues these days and never rely on the fids. I 
> also don't use GML so the other aspects don't affect me.
> Thanks,
> Alex

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?

Nyall


Le mar. 13 oct. 2020 à 17:45, Nyall Dawson  a écrit :
>
> Hi list,
>
> (Linus Torvalds-style harsh truths incoming, read only after coffee/alcohol!)
>
> Having spent an incredibly frustrating day fighting with the
> limitations of GPKG and the horrible workflow that they mandate, I'd
> love to start brainstorming on how we can fix this.
>
> While previous discussions have related to the GPKG sqlite wal mess,
> that has (to the extent of my experience) been resolved in the latest
> release. So I'd like to focus on what I see as the biggest pain point
> of GPKG: the FID column.
>
> This is a pain point for numerous reasons:
>
> - The type constraint on the fid column makes it really hard to
> translate datasets with an existing, non-numeric "fid" column into
> geopackage. Eg. GML files often have a textual fid string, and
> attempting to convert these to gpkg results in a string of errors
> about string values not being usable as fid values, and an empty
> result layer. The only workaround here is to translate first to an
> alternative format (such as shp!), delete the fid column, and THEN
> save as gpkg.
>
> - The fid unique constraint, while understandable, results in a HUGE
> raft of issues while working with these. It's SO easy to get a
> situation where you have duplicate fids in an edit buffer, and no way
> to save these features back to the gpkg. You get a series of 1000s of
> errors about duplicate fid, and then an ambiguous state where you're
> completely unsure exactly what's been saved and what's about to be
> lost. This isn't just attributable to a single tool in QGIS -- it's
> possible to end up with duplicate fids through so many different
> operations, including really simple stuff like copying and pasting
> features!
>
> I've fought with this since we've really started to push GPKG and,
> frankly, I've given up. I don't think there's any way to fix the
> current situation and leave fids as they currently behave.
>
> So what I propose is a radical re-think about how GPKG fids are
> handled and exposed by QGIS (and by GDAL).
>
> I propose that we
>
> 1. demote fids to being only a "semi-permanent" row identifier, with
> the message being that "sometimes these WILL change and you can't rely
> on them as a permanent id field for joins and row identification". If
> users require a permanent unique identifier (i.e. a primary key) on
> their table then THEY have to make and manage that themselves, just
> like shapefiles etc.
>
> 2. expose fids as a read-only field. Users can still see them if they
> want, but they cannot edit them.
>
> 3. make QGIS (or GDAL?) ALWAYS generate a completely new fid whenever
> a row is changed or added. Throwaway the old value, make a new one on
> EVERY edit/addition.
>
> 4 We COMPLETELY ignore any existing fid value set for features added
> to a GPKG layer. I.e. in the case of translating a GML with a text fid
> field, we completely ignore the incoming GML fid values and instead
> use the "always generate a new fid" rule.
>
> Yes, these changes will break existing workflows, and possibly break
> existing tools/scripts. But honestly, in my experience and the
> experience of my customers, there's a COMPLETE lack of faith and trust
> in GPKG at this stage. EVERYONE has their horror stories of lost data
> and mangled datasets. We've got to do something drastic, and we've got
> to do it sooner rather than later to salvage what little hope does
> remain for this format.
>
> Thoughts?
>
> 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

[QGIS-Developer] Fwd: [Qgis-user] Latest runtime version (2008?)

[Richard Duivenvoorde]

Hi Lukas,

I am forwarding your message to the Developers list 
https://lists.osgeo.org/mailman/listinfo/qgis-developer

I'm not sure if the 2008 runtime is actually being used (for 3.10), I hope 
Juergen can maybe answer this question.

Regards,

Richard Duivenvoorde




 Forwarded Message 
Subject:[Qgis-user] Latest runtime version
Date:   Tue, 8 Sep 2020 09:57:17 +0200
From:   Lukas Fiddrich 
To: qgis-u...@lists.osgeo.org



Dear QGIS Community,
 
Can you help me with the runtime version of QGIS 3? 
As For using QGIS at my workplace, it need to get permitted by the 
IT-Department. They figured out, that QGIS 3.10.9 has an outdated C++ runtime 
environment (Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17). Is 
there any newer or older QGIS 3 version with a still supported C++ runtime 
environment?
 
If I am wrong here with this question, could you give me a hint where I can 
adress this question correctly?
 
Kind regards
Lukas
___
Qgis-user mailing list
qgis-u...@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user___
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

[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

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

[SOHINI GOSWAMI]

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.
*Sample  Image of the plugin attempted :*

[image: image.png]

-- 
*Sohini Goswami*
*Executive ,GIS Cell*
*Ph: +918169824459*
*CESC Ventures.*


[image: Mailtrack]

Sender
notified by
Mailtrack

09/04/20,
02:03:36 PM


-- 
*Sohini Goswami*
*Executive ,GIS Cell*
*Ph: +918169824459*
*CESC Ventures.*

[image: Mailtrack]

Sender
notified by
Mailtrack

09/06/20,
11:38:01 PM
___
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] Fwd: NEXTGEN new release: SpatiaLite 5.0.0 RC1

[Jeff McKenna]

Forwarding this great news to the QGIS dev team...


 Forwarded Message 




Hi list,

I'm glad to announce that after a very long pause of about two years
a new Relase Candidate is finally available.

The wait was not in vain;this is certainly the most advanced and 
sophisticated

SpatiaLite version ever been released and supports many cool new features:
1. full rasterlite2 integration
2. ISO Topology support
3. supporting new PROJ 6/7
4. supporting Stored Procedures
... and many others

please check the documentation about 5.0 from here:
https://www.gaia-gis.it/fossil/libspatialite/wiki?name=5.0.0-doc

full documentation about all SQL functions supported by 5.0 is here:
http://www.gaia-gis.it/gaia-sins/spatialite-sql-5.0.0.html

source tarballs can be downloaded from here:
http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-5.0.0-RC1.tar.gz
http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-5.0.0-RC1.zip

http://www.gaia-gis.it/gaia-sins/spatialite-tools-5.0.0-RC1.tar.gz
http://www.gaia-gis.it/gaia-sins/spatialite-tools-5.0.0-RC1.zip

pre-built binaries for Windows are here:
http://www.gaia-gis.it/gaia-sins/windows-bin-NEXTGEN-x86
http://www.gaia-gis.it/gaia-sins/windows-bin-NEXTGEN-amd64

I'll give in a following post further detailed infos about the
current state of all other members of the family (freexl,
readosm, rasterlite2, virtualPG and the GUI tool).

Happy testing,
Sandro




___
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] Fwd: QGIS installation error from own build

[Sachin Kumar]

-- Forwarded message -
From: Sachin Kumar 
Date: Wed 22 Apr, 2020, 9:41 PM
Subject: QGIS installation error from own build
To: , , <
qgis-community-t...@lists.osgeo.org>


I am building *QGIS 3.10.5* on Windows 10 Pro and Visual Studio 2015.
Everything is going right and solution build successful and installed in
OSGeo4W/apps/qgis-test folder. After that I had run perl creatensis.pl in
command prompt and it create a package with name
*“QGIS-OSGeo4W-3.10.5-1-Setup-x86_64”* with is default download, which run
successful after installation.

When I copied my build files from qgis-test folder to
“..\ms-windows\osgeo4w\unpacked-x86_64\apps\qgis” and copied
“OSGeo4W/apps/qgis-test/bin/qgis.exe” to
“..\ms-windows\osgeo4w\unpacked-x86_64\bin and rename *qgis.exe*to
*qgis-bin*”. After that run perl creatensis.pl I get
“QGIS-OSGeo4W-3.10.5-2-Setup-x86_64.exe”.

After installation I get following error:

Error loading QGIS
Oops, looks like an error loading QGIS
Details:
Could not load qgis_app.dll
Windows Error: The specified module could not be found.
Help:
Check C:\Program Files\QGIS 3.10\bin\qgis-bin.env for correct environment
paths


[image: error.PNG]

Earlier I also get the same error hence I format my system and install
fresh Window 10 Pro, but now again I am getting the same error. Is there
any bug during packaging? Any solution
___
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] Fwd: QGIS installation error from own build

[Sachin Kumar]

-- Forwarded message -
From: Sachin Kumar 
Date: Wed 22 Apr, 2020, 9:41 PM
Subject: QGIS installation error from own build
To: , , <
qgis-community-t...@lists.osgeo.org>


I am building *QGIS 3.10.5* on Windows 10 Pro and Visual Studio 2015.
Everything is going right and solution build successful and installed in
OSGeo4W/apps/qgis-test folder. After that I had run perl creatensis.pl in
command prompt and it create a package with name
*“QGIS-OSGeo4W-3.10.5-1-Setup-x86_64”* with is default download, which run
successful after installation.

When I copied my build files from qgis-test folder to
“..\ms-windows\osgeo4w\unpacked-x86_64\apps\qgis” and copied
“OSGeo4W/apps/qgis-test/bin/qgis.exe” to
“..\ms-windows\osgeo4w\unpacked-x86_64\bin and rename *qgis.exe*to
*qgis-bin*”. After that run perl creatensis.pl I get
“QGIS-OSGeo4W-3.10.5-2-Setup-x86_64.exe”.

After installation I get following error:

Error loading QGIS
Oops, looks like an error loading QGIS
Details:
Could not load qgis_app.dll
Windows Error: The specified module could not be found.
Help:
Check C:\Program Files\QGIS 3.10\bin\qgis-bin.env for correct environment
paths


[image: error.PNG]

Earlier I also get the same error hence I format my system and install
fresh Window 10 Pro, but now again I am getting the same error. Is there
any bug during packaging? Any solution
___
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] Fwd: Re: Fwd: Compiling Problem QGis 3.12.1 on CentOS 7.6

[Victor LOPES]

 Message transféré 
Sujet : 	Re: [QGIS-Developer] Fwd: Compiling Problem QGis 3.12.1 on 
CentOS 7.6

Date :  Wed, 25 Mar 2020 14:05:15 +0100
De :Victor LOPES 
Pour :  Jorge Gustavo Rocha 



Hello Jorge, thanks for your reply :-)
As you guess qtbase5-dev is for debian and equivalent is 
qt5-qtbase-devel-5.9.7-2.el7.x86_64 for Centos


QIDevice is not present in this package but after some search I found is 
present in qtiocompressor-2.3.1-5.el7.nux.x86_64 and 
qtiocompressor-devel-2.3.1-5.el7.nux.x86_64


/usr/include/QtSolutions
/usr/include/QtSolutions/QtIOCompressor
/usr/include/QtSolutions/qtiocompressor.h        => In this file

...
class QtIOCompressorPrivate;
class QT_QTIOCOMPRESSOR_EXPORT QtIOCompressor : public QIODevice
{
Q_OBJECT
public:
enum StreamFormat { ZlibFormat, GzipFormat, RawZipFormat };
    QtIOCompressor(QIODevice *device, int compressionLevel = 6, int 
bufferSize = 65500);

...

/usr/lib64/libQtSolutions_IOCompressor-2.3.so
/usr/lib64/qt4/mkspecs/features/qtiocompressor.prf
/usr/share/doc/qtiocompressor-devel-2.3.1
/usr/share/doc/qtiocompressor-devel-2.3.1/doc
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/classic.css
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/images
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/images/qt-logo.png
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/index.html
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/qtiocompressor-members.html
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/qtiocompressor.dcf
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/qtiocompressor.html
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/qtiocompressor.index
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/qtiocompressor.qch
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/html/qtiocompressor.qhp
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/images
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/images/qt-logo.png
/usr/share/doc/qtiocompressor-devel-2.3.1/doc/index.qdoc
/usr/share/doc/qtiocompressor-devel-2.3.1/examples
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/examples.pro
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/gzip
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/gzip/compressed.gz
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/gzip/gzip.pro
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/gzip/main.cpp
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/simple
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/simple/main.cpp
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/simple/simple.pro
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/xml
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/xml/main.cpp
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/xml/xml.pro
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/ziplist
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/ziplist/archive.zip
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/ziplist/main.cpp
/usr/share/doc/qtiocompressor-devel-2.3.1/examples/ziplist/ziplist.pro

But despite, I have always this problem :

[root@audric build-master]# . ../../c
-- QGIS version: 3.12.1 BucureÈti (31201)
-- Found OpenCL C++ headers: /usr/include
-- Could not find GRASS 7
-- Found Proj: /opt/proj/lib version 4 (4.9.3)
-- Found GEOS: /usr/lib64/libgeos_c.so (3.4.2)
-- Found GDAL: /opt/gdal/lib (3.0.4)
-- Found Expat: /lib64/libexpat.so
-- Found Qwt: /usr/lib64/libqwt.so (6.1.1)
-- Found libzip: /usr/lib64/libzip.so
-- Found Sqlite3: /opt/sqlite/lib
-- Found PostgreSQL: /usr/lib64/libpq.so
-- Qt WebKit support enabled
-- Found Qt version: 5.9.7
-- Found QScintilla2: /usr/lib64/libqscintilla2.so (2.8)
-- Found QCA: /usr/lib64/libqca-qt5.so (2.0.3)
-- QCA OpenSSL plugin C++ check failed to compile
-- QCA OpenSSL plugin C++ check compile output:
-- Change Dir: 
/images/compile/QGIS-final-3_12_1/build-master/CMakeFiles/CMakeTmp


Run Build Command(s):/usr/bin/gmake cmTC_5b7bb/fast
/usr/bin/gmake -f CMakeFiles/cmTC_5b7bb.dir/build.make 
CMakeFiles/cmTC_5b7bb.dir/build
gmake[1] : on entre dans le répertoire « 
/images/compile/QGIS-final-3_12_1/build-master/CMakeFiles/CMakeTmp »

Building CXX object CMakeFiles/cmTC_5b7bb.dir/qcaossl.cpp.o
/usr/bin/c++   -I/usr/include/qt5 -I/usr/include/qt5/QtCore 
-I/usr/lib64/qt5/./mkspecs/linux-g++ -I/usr/include/QtCrypto -fPIC    
-std=gnu++11 -o CMakeFiles/cmTC_5b7bb.dir/qcaossl.cpp.o -c 
/images/compile/QGIS-final-3_12_1/build-master/CMakeFiles/CMakeTmp/qcaossl.cpp

In file included from /usr/include/QtCrypto/qca.h:38:0,
 from /usr/include/QtCrypto/QtCrypto:1,
 from 
/images/compile/QGIS-final-3_12_1/build-master/CMakeFiles/CMakeTmp/qcaossl.cpp:2:
/usr/include/QtCrypto/qca_basic.h:318:14: erreur: âQIODeviceâ has not 
been declared

  void update(QIODevice *file);
  ^
gmake[1]: *** [CMakeFiles/cmTC_5b7bb.dir/qcaossl.cpp.o] Erreur 1
gmake[1] : on quitte le répertoire « 
/images/compile/QGIS-final-3_12_1/build-mas

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

[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

[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

[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 

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

[piaff33z]

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 root11 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 root11 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 root19 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 root10 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 root11 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
-DSQLITE3_INCLUDE_DIR=/opt/sqlite/include -DSQLITE3_LIBRARY=/opt/sqlite/lib
-DGRASS_INCLUDE_DIR=/opt/grass/include 

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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

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

[Nyall Dawson]

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] Fwd: [Qgis-psc] Policies document

[Paolo Cavallini]

Hi all,
if anyone knows of a policy document not listed in the ticket, please
let me know. The current situation (one developer, one documentation,
and one plugin document) looks OK to me.
Thanks for help.
Cheers.


 Messaggio Inoltrato 
Oggetto: [Qgis-psc] Policies document
Data: Mon, 16 Dec 2019 12:13:59 +0100
Mittente: Paolo Cavallini 
A: qgis-psc 

Hi all,
regarding:
https://github.com/qgis/PSC/issues/2
Condensate all policies into one page
I'd like to list all of them to our Governance menu on the website
(unless there are better proposals).
Could everybody helping me listing the current policies, adding the
links to the ticket?
Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
Qgis-psc mailing list
qgis-...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-psc
___
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] Fwd: [PROJ] Interested in helping for inclusion of grids for Spain, Austria, Slovakia, Brazil ?

[Nyall Dawson]

Forwarding a request for assistance from the PROJ mailing list -- this
is a great opportunity for our Spanish, Catalan, Austrian, Slovakian
and Brazilian communities to contribute (amongst others!)


-- Forwarded message -
From: Even Rouault 
Date: Mon, 2 Dec 2019 at 09:18
Subject: [PROJ] Interested in helping for inclusion of grids for
Spain, Austria, Slovakia, Brazil ?
To: 


Hi,

I'm requesting help from good wills of the community to help us grow
our datasets of grids at
https://github.com/OSGeo/proj-datumgrid/
Below a few candidates I've identified, mentionned in EPSG and with a
number of them with
download links, but license clarification would be needed.

Community members from those countries are probably in a better
position than me to
connect with the relevant authority and see if they'd be willing to
adopt one of the licenses
mentionned at 
https://github.com/OSGeo/proj-datumgrid#about-the-datum-grid-package

Spain
-

* Peninsula and Baleares:

Anyone from the Spanish community to help clarifying license of
https://www.fomento.gob.es/recursos_mfom/gridshift1.zip (ED50 to ETRS89),
presumably whith IGN Spain

The download link is accessible from
https://www.fomento.gob.es/organos-colegiados/consejo-superior-geografico/csg/etrs89/etrs89-nuevo-sistema-de-referencia-geodesico-oficial-en-espana

This file has a sort of CC license
(https://gist.github.com/rouault/1ff4ad2d8053e068f9dbf451572692f4) but with a
annoying non-modification clause that makes it incompatible with our
requirements
(we might want to transform it to another format like GeoTIFF),
and no version/link to the actual CC license.

* Catalonia:

Grid specific to Catalonia for ED50 to ETRS89 : 100800401.gsb
File found in 
http://www.icgc.cat/content/download/48766/337962/version/1/file/Malla_NTv2_11_03.zip
but no explicit license mention.
https://www.icgc.cat/en/Web/Help/Legal-notice has a vague mention of
Creative Commons,
but no precise identification of which variant of it, and which version.

Austria
---

The AT_GIS_GRID.gsb grid for MGI to ETRS89 is available at
http://www.bev.gv.at/portal/page?_pageid=713,2157075&_dad=portal&_schema=PORTAL
:

http://www.bev.gv.at/pls/portal/docs/PAGE/BEV_PORTAL_CONTENT_ALLGEMEIN/0200_PRODUKTE/UNENTGELTLICHE_PRODUKTE_DES_BEV/GIS-Grid.zip

Copyright info I could find is
"Hinsichtlich seiner Datenbanken verfügt das BEV über das ausschließliche
Werknutzungsrecht gemäß §§ 40f bis 40h UrhG und das sui generis-Recht
gemäß §§ 76c bis 76e UrhG."

which by itself is not super promising.

Slovakia


https://www.geoportal.sk/en/geodeticke-zaklady/download/ offers for
download 3 grids
referenced by EPSG:
Slovakia_ETRS89h_to_Baltic1957.gtx
Slovakia_ETRS89h_to_EVRF2007.gtx
Slovakia_JTSK03_to_JTSK.LAS / .LOS

I've emailed the contact mentionned on the site to get info regarding
the license.
But wouldn't hurt to get feedback of knowledgeable people too.

Brazil
--

Looking for official download links & license for the following:

Corrego Alegre 1961 to SIRGAS 2000: CA61_003.gsb
Corrego Alegre 1970-72 to SIRGAS 2000: CA7072_003.gsb
SAD69 to SIRGAS 2000: SAD69_003.gsb
SAD69(96) to SIRGAS 2000: SAD96_003.gsb

https://www.killetsoft.de/p_gdln_e.htm has download links but official
ones from IBGE
would be preferable if possible.


Of course there are certainly gaps to fill for other countries I've
not mentionned...

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
PROJ mailing list
p...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/proj
___
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] Fwd: Call for review on RFC 4 text: Remote access to grids and GeoTIFF grids

[Even Rouault]

Hi,

the below can be of interest for QGIS in the future.

Particularly the part that describes a capability to access grids stored 
remotely:
https://github.com/rouault/PROJ/blob/rfc4_remote_and_geotiff_grid/docs/source/community/rfc/rfc-4.rst#network-access-to-grids

and more specifically I'd be interested in hearing if the proposed callback 
mechanism
intended to make QGIS able to plug its networking mechanisms into PROJ looks 
reasonable.

Even

--  Forwarded Message  --

Subject: Call for review on RFC 4 text: Remote access to grids and GeoTIFF grids
Date: lundi 25 novembre 2019, 13:46:37 CET
From: Even Rouault 
To: p...@lists.osgeo.org

Hi,

As announced last week, you'll find a RFC describing two new capabilities,
remote access to grids and a GeoTIFF-based format for grids, in
https://github.com/OSGeo/PROJ/pull/1747

You can get an (almost correct) preview of it by going through
https://github.com/rouault/PROJ/blob/rfc4_remote_and_geotiff_grid/docs/source/community/rfc/rfc-4.rst
(some links will not work in this preview: expected given that this rendering 
doesn't go through Sphinx)

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
-
-- 
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: QGIS Trademark in

[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 

[QGIS-Developer] Fwd: QGIS Trademark in

[Tim Sutton]

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 
> 
> 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 where needed.
> 
> Thanks in anticipation!
> 
> Regards
> 
> Tim
> 
>  
> 
> 
> 
> 
> ---
> 
> Tim Sutton
> t...@qgis.org 
> 
> 
> 
> 

—









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

I'd love to connect. Here's my calendar link  to 
make finding time easy.

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: 

[QGIS-Developer] Fwd: External python package dependency in plugins

[matteo]

forwarding to the dev list


 Forwarded Message 
Subject:Re: [QGIS-Developer] External python package dependency in 
plugins
Date:   Fri, 21 Jun 2019 21:21:41 +0200
From:   Olivier Dalang 
To: matteo 



Hi,

Big +1 for this.

I think it should come with clear guidelines for devs though (esp. how
to correctly specify versions to avoid conflicting requirements with
unnecessary pins).

If we want to support this, what about using a requirements.txt file
rather than the metadata file?

It's more or less a standard which has some benefits such as automatic
vulnerability alerts or dependency graph on GitHub.

Cheers,

Olivier

On Fri, Jun 21, 2019, 09:34 matteo mailto:matteo.ghe...@gmail.com>> wrote:

Hi Tom,

I totally agree. Having a nice way to install external packages would be
a great addition.

Some times ago I was involved in a project that needed external packages
and we developed an "in house" prototype, but it was far from ideal

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

___
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 [1714] SSAM approval notification.

[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

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

[gianluca massei]

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
___
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] Fwd: [qgis/QGIS] curved labels: only a few are drawn (#12173)

[Paolo Cavallini]

Hi all,
the first of my tickets to be closed on the new system - wow.
One ssmall but I believe significant thing: now to see who cloded or
commented it one should go to the website, whereas before the name of
the bugfixer was included in the mail. I think peolpe doing stuff
deserve as much visibility as possible: is there a way to show this?
Thanks.

 Forwarded Message 
Subject:Re: [qgis/QGIS] curved labels: only a few are drawn (#12173)
Date:   Thu, 30 May 2019 00:29:09 -0700
From:   Nyall Dawson 
Reply-To:   qgis/QGIS

To: qgis/QGIS 
CC: Paolo Cavallini , Mention




Closed #12173 .

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
,
or mute the thread
.

___
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] Fwd: Qgis server systemd

[adib saliba]

-- Forwarded message -
From: adib saliba 
Date: Thu, May 23, 2019 at 10:08 AM
Subject: Re: [QGIS-Developer] Qgis server systemd
To: Eric 


Dear Eric
Thank you very much for your response
I already followed the link you mentioned, i am using ubuntu 19.04 with
nginx php-fpm postgresql qgis server stable release and lizmap web client
with wmts caching.
my problem is that the memory is not recycling after the main  process
finishes (i get all the image tiles), and it is always increasing till the
system is out of memory.
the only solution i found is to use RuntimeMaxSec variable to restart the
service.
please find attached the conf files i'm using

Thanks and best regards
Adib

On Thu, May 23, 2019 at 7:39 AM Eric  wrote:

>
>
> Le 22 mai 2019 20:48:06 GMT+02:00, adib saliba  a
> écrit :
> >
> >Dear sirs, I have a question regarding qgis server setup:
> >I deployed qgis server on ubuntu server using nginx+systemd
> >| tried 2types of service : simple and forking with
> >number of process = number of cores.
> >The type=simple is faster but it is not freeing up
> >memory even if I'm using Restart=always, the
> >type=forking is freeing memory but gives error
> >prematurely closed connection to fastcgi upstream.
> >Could you please advise me how to correctly configure the service type
> >simple to freeup memory?
>
>
> Hi Adib
>
> We've been using Type=simple without experiencing the memory issue you are
> seeing. See
> https://oslandia.com/en/2018/11/23/deploying-qgis-server-with-systemd/
> for the actual set-up we use. It would be good to know more about your
> set-up and the memory issue you're having.
>
>
> Cheers,
> --
> Éric
>


qgis-server-fcgi
Description: Binary data


qgis-server-fcgi@.socket
Description: Binary data


qgis-server-fcgi@.service
Description: Binary data
___
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] Fwd: [TC-Announce] OGC invites developers to the OGC API Hackathon

[Paul Van Genuchten]

Fyi, Anyone plans to join in London? Work on ‘ogc:api features’ (aka wfs3) 
implementation in qgis. Travel sponsorship may be available.

Cheers, Paul

Begin doorgestuurd bericht:

> Van: announce--- via TC-Announce 
> Datum: 3 april 2019 om 15:33:12 CEST
> Aan: tc-annou...@lists.opengeospatial.org
> Onderwerp: [TC-Announce] OGC invites developers to the OGC API Hackathon
> Antwoord aan: "annou...@opengeospatial.org" 
> 
>  
> 
> OGC invites developers to the OGC API Hackathon
> 
> Participate in the most important hackathon in OGC history!
> 
> 
> 
> Contact: i...@opengeospatial.org
> 
> 3 April 2019: The Open Geospatial Consortium (OGC) invites interested 
> developers to the OGC API Hackathon, held in London on June 20 & 21, 2019.
> 
> The most important hackathon in OGC history is coming quickly. This hackathon 
> will test draft OpenAPI-based specifications for features, coverages, map 
> tiles, and processes using a common Application Programming Interface (API) 
> template. The template will be based on the work completed to date on the OGC 
> API - features specification (formerly referred to as WFS3). This event will 
> be instrumental to the evolution of OGC web standards to a modern API-based 
> approach, setting the course for open geospatial standards - in and outside 
> OGC - for the next decade.
> 
> The Hackathon will focus on implementing and testing draft API specifications 
> for geospatial information on the web. Emphasis will be placed on making the 
> APIs web-friendly for non-geospatial experts. Links to the draft 
> specifications are in the Hackathon Invitation (see link, below). Optimally, 
> participants will have client, server, or both implementations in advance of 
> the event. Be prepared to update your implementation during the hackathon. 
> Datasets and cloud processing resources are being identified for use in 
> testing during the event. See the Invitation and the Hackathon Initiative 
> Page for more the latest information.
> 
> An OGC Hackathon is a collaborative and inclusive event driven by innovative 
> and rapid programming with minimum process and organization constraints to 
> support the development of new applications and open standards.
> 
> Ordnance Survey is providing an excellent venue and project management 
> support. The event is planned for June 20 & 21, 2019 at the Geovation Hub in 
> London, UK.
> 
> “As a Strategic Member of OGC, Ordnance Survey is pleased to support this 
> effort,” said Simon Green, Head of Data Architecture at Ordnance Survey. “As 
> we look towards the strategic enabling capabilities that cloud-native 
> geospatial processing delivers, we anticipate that the future of geospatial 
> interoperability will be increasingly based upon API’s that are built on Web 
> standards, leveraging the strengths of the World Wide Web.  We are honoured 
> to host and facilitate this crucially important hackathon in partnership with 
> OGC, from which we and others can look forward to benefiting from the highly 
> anticipated results.”
> 
> There will be opportunity for joint discussion with all participants on the 
> goals and objectives of the event as well as final briefing of findings and 
> opinions of the participants. However, the majority of the time will be spent 
> in collaboration between participants in active coding.
> 
> We are seeking organizations to sponsor travel for key Hackathon Participants 
> to attend and participate in the event. For more information on sponsorship 
> opportunities and benefits, contact Scott Simmons ssimm...@opengeospatial.org.
> 
> For more information on the Hackathon, including venue information, 
> registration requirements, and expected skill sets, visit the OGC API 
> Hackathon event page on OGC’s website, or register on Eventbrite. The 
> Hackathon is open to anyone: OGC membership is not a requirement.
> 
>  
> 
> About OGC
> 
> The Open Geospatial Consortium (OGC) is an international consortium of more 
> than 525 companies, government agencies, research organizations, and 
> universities participating in a consensus process to develop publicly 
> available geospatial standards. OGC standards support interoperable solutions 
> that ‘geo-enable’ the Web, wireless and location-based services, and 
> mainstream IT. OGC standards empower technology developers to make geospatial 
> information and services accessible and useful within any application that 
> needs to be geospatially enabled. Visit the OGC website at 
> www.opengeospatial.org.
> 
>  
> This press release is also available online at: 
> opengeospatial.org/pressroom/pressreleases/2981 
> EDITORS: When publishing this on your blog or website, we kindly request that 
> you link back to the above URL.
> The image used in the PR is available without text or logo here.
>  
> 
> 
> 
> --
> This message has been sent to tc-annou...@lists.opengeospatial.org
> 
> To forward a message to someone you may use this link 
> 
> 
> 
> 
> 
> 
> 

[QGIS-Developer] Fwd: Transifex: GitHub integration - announcing early access

[matteo]

Hi devs,

sorry for cross-posting but I want to be be sure that all of you get
this email.

It seems that github-transifex have a direct integration.

Don't really know how/if we can dig into this topic, but it is worth to
mention ;)

Cheers

Matteo


 Forwarded Message 
Subject:Transifex: GitHub integration - announcing early access
Date:   Wed, 06 Feb 2019 23:38:58 +
From:   Tatiana Tadi 
To: Matteo Ghetta 



Hi Matteo,

I hope this email finds you well.

We are excited to introduce you to our new Github integration. Over the
past months, our team has been working hard on this new initiative to
make it easier for our customers to integrate their Github repositories
with Transifex. With the new GitHub Integration, you will be able to
connect a localization project in Transifex with a specific repository
in GitHub using only the Transifex user interface.

We will continue to stabilize this release and fix any remaining issues
over the coming weeks so we would greatly appreciate it if you could
help us ensure that this is a high-quality release by testing this out
and providing us with your valuable feedback.

So, if you are interested, we will be glad to enable this feature for
your account providing you with early access to this new enhancement.
More information about this can be found in our documentation guide here
.

However, if you would prefer an official release instead, then we will
get back to you as soon as this happens.

Of course, it is up to you to select either option but gathering your
feedback for the upcoming official release would be extremely valuable.

Please, let us know how you would like to proceed.

Thank you in advance!


Kind Regards,



--
Tatiana Tadi
| Transifex 
Join Our Community! 

How would you rate my reply?
Satisfaction Rating Icons      
{#HS:772629182-64920#}
___
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)

[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)

[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)

[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)

[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)

[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)

[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)

[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)

[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)

[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

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

[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