Re: [QGIS-Developer] applying an SLD to a WMS layer

[Charles Dixon-Paver]

Don't thank me yet! My in-between-meetings mailing list brain was at work
and I should have phrased that differently. I was actually meaning to ask
whether that would work on wms layers and I haven't tested it out

On Tue, 26 Oct 2021, 19:02 Kurt Menke,  wrote:

> Thanks Charles,
> This may be the ticket!
>
> On Tue, Oct 26, 2021 at 6:30 PM Charles Dixon-Paver 
> wrote:
>
>> Just to chime in, all these responses seem to be discussing sld and wms
>> server configuration options, but the original question mentioned applying
>> edits to the qgis project file. I would think the simplest solution is to
>> use something like loadSldStyle[1] from pyqgis? Not sure if I'm missing the
>> point of the conversation though.
>>
>> [1]
>> https://qgis.org/pyqgis/master/core/QgsMapLayer.html#qgis.core.QgsMapLayer.loadSldStyle
>>
>> On Tue, 26 Oct 2021 at 14:21, Jorge Gustavo Rocha 
>> wrote:
>>
>>> Hi René,
>>>
>>> I'm just asking questions to fully understand the use case. Thank you
>>> for your feedback. You mentioned an interesting point.
>>>
>>> As you mentioned, the solution can be based on the server side if the
>>> map server accepts an SLD.
>>>
>>> This approach can not be used against WMS services working behind
>>> caches/tiling services providing only predefined styles.
>>>
>>> Regards,
>>>
>>> Jorge Gustavo
>>>
>>> On 26/10/21 12:43, René-Luc Dhont wrote:
>>> > Hi Jorge,
>>> >
>>> > WMS Server can process SLD  provide in a GetMap Request.
>>> > QGIS Server is able to apply an SLD to a layer and provide the
>>> resulting
>>> > image. The SLD can be provided through the SLD_BODY parameter or the
>>> > SLD parameter for linked file.
>>> >
>>> https://docs.qgis.org/3.16/en/docs/server_manual/services.html#qgisserver-wms-getmap
>>> > This capability is mainly exploited by web clients
>>> >
>>> > René-Luc
>>> >
>>> > Le 26/10/2021 à 12:26, Jorge Gustavo Rocha a écrit :
>>> >> Hi Kurt,
>>> >>
>>> >> By design, WMS GetMap requests returns images. Those are rendered on
>>> >> the server side, by the map server. Many services just provide those
>>> >> rendered images.
>>> >>
>>> >> Are you trying to provide advanced image processing capabilities on
>>> >> the client side to apply an SLD on top those images?
>>> >>
>>> >> Or would you like to try other GetMap formats, more friendly to
>>> >> process on the client side? Like svg or kml? Some of these formats
>>> are
>>> >> available as vendor options of the map server.
>>> >>
>>> >> Regards,
>>> >>
>>> >> Jorge Gustavo
>>> >>
>>> >>
>>> >> On 26/10/21 10:58, Kurt Menke wrote:
>>> >>> Hello,
>>> >>> We have been developing web apps that allow the user to download the
>>> >>> selected extent and data layers as a QGIS project file. Many of the
>>> >>> layers are hosted by the government as WMS services. We are
>>> wondering
>>> >>> if anyone has looked into the possibility of applying an SLD style
>>> to
>>> >>> a WMS layer in QGIS. We were hoping to be able to edit the *.qgs
>>> file
>>> >>> programmatically. We would be interested in sponsoring the effort
>>> >>> depending on the level of effort required, assuming it is even
>>> possible.
>>> >>> Best,
>>> >>> Kurt
>>> >>>
>>> >>> --
>>> >>>
>>> >>> Kurt Menke
>>> >>>
>>> >>> GIS-Consultant
>>> >>> --
>>> >>> Septima P/S
>>> >>> Frederiksberggade 19, 2nd Floor
>>> >>> 1459 Copenhagen
>>> >>>
>>> >>> Tlf: +45 5114 6444
>>> >>>
>>> >>> ___
>>> >>> 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
>>> >>>
>>> >>
>>> >> J. Gustavo
>>> >
>>> >
>>> > ___
>>> > QGIS-Developer mailing list
>>> > QGIS-Developer@lists.osgeo.org
>>> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> >
>>>
>>> J. Gustavo
>>> --
>>> Jorge Gustavo Rocha
>>> Departamento de Informática
>>> Universidade do Minho
>>> 4710-057 Braga
>>> Gabinete 3.29 (Piso 3)
>>> Tel: +351 253604480
>>> Fax: +351 253604471
>>> Móvel: +351 910333888
>>> skype: nabocudnosor
>>> ___
>>> QGIS-Developer mailing list
>>> QGIS-Developer@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>
___
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] applying an SLD to a WMS layer

[Charles Dixon-Paver]

Just to chime in, all these responses seem to be discussing sld and wms
server configuration options, but the original question mentioned applying
edits to the qgis project file. I would think the simplest solution is to
use something like loadSldStyle[1] from pyqgis? Not sure if I'm missing the
point of the conversation though.

[1]
https://qgis.org/pyqgis/master/core/QgsMapLayer.html#qgis.core.QgsMapLayer.loadSldStyle

On Tue, 26 Oct 2021 at 14:21, Jorge Gustavo Rocha  wrote:

> Hi René,
>
> I'm just asking questions to fully understand the use case. Thank you
> for your feedback. You mentioned an interesting point.
>
> As you mentioned, the solution can be based on the server side if the
> map server accepts an SLD.
>
> This approach can not be used against WMS services working behind
> caches/tiling services providing only predefined styles.
>
> Regards,
>
> Jorge Gustavo
>
> On 26/10/21 12:43, René-Luc Dhont wrote:
> > Hi Jorge,
> >
> > WMS Server can process SLD  provide in a GetMap Request.
> > QGIS Server is able to apply an SLD to a layer and provide the resulting
> > image. The SLD can be provided through the SLD_BODY parameter or the
> > SLD parameter for linked file.
> >
> https://docs.qgis.org/3.16/en/docs/server_manual/services.html#qgisserver-wms-getmap
> > This capability is mainly exploited by web clients
> >
> > René-Luc
> >
> > Le 26/10/2021 à 12:26, Jorge Gustavo Rocha a écrit :
> >> Hi Kurt,
> >>
> >> By design, WMS GetMap requests returns images. Those are rendered on
> >> the server side, by the map server. Many services just provide those
> >> rendered images.
> >>
> >> Are you trying to provide advanced image processing capabilities on
> >> the client side to apply an SLD on top those images?
> >>
> >> Or would you like to try other GetMap formats, more friendly to
> >> process on the client side? Like svg or kml? Some of these formats are
> >> available as vendor options of the map server.
> >>
> >> Regards,
> >>
> >> Jorge Gustavo
> >>
> >>
> >> On 26/10/21 10:58, Kurt Menke wrote:
> >>> Hello,
> >>> We have been developing web apps that allow the user to download the
> >>> selected extent and data layers as a QGIS project file. Many of the
> >>> layers are hosted by the government as WMS services. We are wondering
> >>> if anyone has looked into the possibility of applying an SLD style to
> >>> a WMS layer in QGIS. We were hoping to be able to edit the *.qgs file
> >>> programmatically. We would be interested in sponsoring the effort
> >>> depending on the level of effort required, assuming it is even
> possible.
> >>> Best,
> >>> Kurt
> >>>
> >>> --
> >>>
> >>> Kurt Menke
> >>>
> >>> GIS-Consultant
> >>> --
> >>> Septima P/S
> >>> Frederiksberggade 19, 2nd Floor
> >>> 1459 Copenhagen
> >>>
> >>> Tlf: +45 5114 6444
> >>>
> >>> ___
> >>> 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
> >>>
> >>
> >> J. Gustavo
> >
> >
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> J. Gustavo
> --
> Jorge Gustavo Rocha
> Departamento de Informática
> Universidade do Minho
> 4710-057 Braga
> Gabinete 3.29 (Piso 3)
> Tel: +351 253604480
> Fax: +351 253604471
> Móvel: +351 910333888
> skype: nabocudnosor
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
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] Changelog Time for 3.22

[Charles Dixon-Paver]

Hi, and thanks for raising this Frank.

I've noticed a bunch of the entries have just been tagged with a category
rather than undergoing a full edit from the PR text, which we need to try
to make more "user friendly" and less "developer-centric". The technical
details of each PR are still available on github and I think the changelog
targets a different audience.

We have set up a list of expected conventions for entries here:

https://github.com/qgis/QGIS/wiki/Changelog-Workflows#conventions-for-changelog-entries

Feel free to contribute changes there as well.

Whilst I think the contextual and writing style stuff is not of critical
concern, there are a couple major red flags we need to try eliminate before
publication, including:


   - Headers - The records should not contain any headers (in HTMl or
   markdown) in the content section as this interferes with the ToC generated
   in the Visual Changelog. This is critical because I think the PR template
   or convention includes a description header etc.
   - Tags - Some PRs use [tag-id]Title syntax to try and automatically tag
   pull requests, which need to be removed
   - PRs and Links - There are commonly a bunch of references
   - List and content formatting - Sometimes pushing from git does not end
   up with nicely rendered markdown, so we should try and fix it
   - Entry title - Often a developer will write a sentence for describing
   the functionality, which is certainly helpful for the review process. For
   changelogs we can move this to the description and use a simple 3 - 8 word
   (there's no real rule) title so that it's rendered nicely and without too
   much wrapping in the ToC
   - Extraneous details - I think it's better to be concise and we can
   remove some content from a lot of the entries. Many PRs justify what, why,
   and how some functionality was developed and introduced, whereas for the
   changelog we just need to know what it does.

I would ask that contributors rather refrain from simply tagging entries
until they have gone through some form of editing, as it makes it difficult
to track what has been reviewed fully and what has not - I prefer to work
through the entries methodically and if need be I am happy run through all
the entries and simply tag them before the final release date. Certainly
review the entries available in the general section, and feel free to edit
them if you would like, but don't move them into a category until they're
"publishing-ready". Also, anybody can feel free to ping me if they see a
feature missing!

Regards

On Mon, 4 Oct 2021 at 13:13, Frank Sokolic 
wrote:

> Hi changelog contributors,
>
> I've been reading through the changelog entries, checking grammar and
> readability, and noticed that many entries refer to PR. Given that the
> target audience of the changelog is more than just developers /
> contributors, would anybody be unhappy if I changed PR to something like
> "feature" or "function"? So an entry that currently reads "This PR allows
> users to ..." would change to "This feature allows users to ...".
>
> Regards, Frank.
>
>
> On 2021/09/26 11:51, Tim Sutton wrote:
>
> Hi All
>
> Since we are in feature freeze now,  can I ask you all (especially
> contributors of new features to) please clean up your entries in the
> changelog - lots of them need tidy ups to be presentable for the changelog.
>
> https://changelog.qgis.org/en/qgis/version/3.22/
>
> Even if you didn't develop features, it would be great if you are able to
> contribute improvements to make the changelog readable. If you need any
> help, contact myself or Charles (char...@kartoza.com).
>
> Thanks!
>
> Regards
>
> Tim
>
> --
>
> --
>
> 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 listqgis-develo...@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] SVG toolbar icons suddenly appearing in black

[Charles Dixon-Paver]

Hi Raymond,

I am on Windows with 3.20 and the icons are blue for me.

I opened the SVG in inkscape and saved an "optimized svg", which runs
scours against it, and all that changed is the  definition was added and version="1.1" was injected into
the svg tag.

One oddity though, is that when I changed the feature colour and saved it,
the "bright" svg version retained the .a {fill: #1b3d6e;}
data element, but the *path* tag got a fill="#00f" added into it. I imagine
QGIS is recognising the CSS (for me) but giving preference to the fill
attribute.

Still, all icons are blue for me...

[image: image.png]

It could also be a contrast issue on the users screens changing, where the
blue icon is simply appearing black, but I imagine most likely the system
is not recognizing that css style in the svg.

I hope that helps you.


On Thu, 23 Sept 2021 at 11:26, Raymond Nijssen 
wrote:

> Hi devs!
>
> The dark blue icons on my plugin toolbar buttons are black for some of
> my customers (on Windows). One of them mentioned that they turned black
> after a QGIS update. On my Linux system they are still blue. I guess it
> has to do with Qt.
>
>
>
> Here's the content of the svg file:
>
> http://www.w3.org/2000/svg; viewBox="0 0 32 32">
>
>  
>.a {
>  fill: #1b3d6e;
>}
>  
>
>
> d="M15.52,6.54a7.29,7.29,0,0,0-1.77,7.38l-9.9,9.9-.34,4.33,5.94-.6v-2.8h2.8V22h2.8l3.37-3.36a7.26,7.26,0,1,0-2.9-12Zm5.37,2.1a2,2,0,1,1,0,2.81A2,2,0,0,1,20.89,8.64Z"/>
> 
>
>
>
> And here's how I make the buttons:
>
> icon_fn = os.path.join(self.plugin_dir, 'img', 'icon_configuration.svg')
> icon = QIcon(icon_fn)
> action = QAction(icon, 'Configure', self.iface.mainWindow())
> self.toolbar.addAction(action)
>
>
>
>
> Hope anyone can clarify. The svg files were made by a designer, I guess
> in some Adobe application. Hope I don't need adjusting them.
>
> Kind regards,
> Raymond
>
> ___
> 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] DWG files preview in QGIS

[Charles Dixon-Paver]

Hi there.

I am unable to read your previous message as the supplied image seems to
have been converted to plain text. I would recommend sending a link via an
internet image service like https://imgur.com/

If you were unable to access or review the link to the demo project I
provided previously, I have added to my gdrive temporarily so that you may
download it.

https://drive.google.com/file/d/1PZLy5_M4n6se0D74AWplrmqwIXh5-ZCX/view?usp=sharing

In terms of the visualisation aspect, I think that has already been
addressed. Within the example project is a points layer which contains the
attributes linking to relevant files and many different layer styles for
you to review depending on how you want to visualise your data. Just right
click the layer and navigate to the styles section of the context menu.
These styles were available:

   - atlas - highlighting the currently active atlas feature as used in the
   layout
   - call_out - an example of using label callouts to identify relevant
   drawings for each feature based on offset attributes
   - default - simple points
   - offset_from_point - positioning the drawing adjacent to point using
   map scale and scale dependant rendering and a custom styled feature form
   for displaying the drawing for a feature from the identify tool
   - raster - replacing the point symbol with a picture of the drawing
   - raster_and_point - simple multilayered symbol example
   - raster_map_units - raster symbol set to use map units for size/ scale
   and daraw effects to help it stand out from background map
   - raster_scaled - A simple example of using a raster symbol with
   effective scale dependant rendering

I would be surprised if one of these styles (or indeed the available
actions and example layout) would not suit your needs with a bit of
additional configuration.

Regards


On Sun, 1 Aug 2021 at 10:56, todor lambev  wrote:

> Thank you very much, Charles.
> It was a long week on the field / I had to do a significant bathymetric
> survey in the Black see / and I did not have the chance to work on this but
> I think that I will manage.
> I bought a DWG->PDF/PNG converter because I think that would be more
> reliable if you have to convert many files at once. With a few clicks, it
> converts all DWG files (almost 15 000) to PNG files. Than using the example
> sent by you I loaded all profiles in QGIS and now the only tricky part is
> the visualization... At the moment it looks like this:
>
> When I zoom in, I can see in more details but the zoom is limited... But I
> think that I could work with it.
>
> Thank you once again for your help and all the best.
>
> Todor Lambev, PhD Student- - - - -*Institute of Oceanology
> **Department of coastal zones dynamics
> mob: +359 886 75 72 85;
> Varna, Bulgaria
> URL: http://www.io-bas.bg <http://www.io-bas.bg>*
>
>
>
>
>
> > Оригинално писмо 
> >От: Charles Dixon-Paver char...@kartoza.com
> >Относно: Re: [QGIS-Developer] DWG files preview in QGIS
> >До: todor lambev 
> >Изпратено на: 26.07.2021 10:28
>
> There should be no need to buy additional software to bulk convert DWG
> files to PNG format. If you have access to autocad you should be able to
> bulk export your layouts. I could likely share an auto lisp routine but
> without an autocad license and sample data I wouldn't be able to test it.
>
> As I said, I personally used the Autodesk True View application (which is
> free) to bulk export to pdf. You can also use a program like imagemajick to
> bulk convert PDF to PNG, so although it's a more complex workflow than
> exporting directly to PNG it is certainly possible without purchasing
> separate software.
>
> If you struggle with automating these steps let me know. I expect it to be
> quite a common procedure for users who work with CAD data and it may be
> worth a quick YouTube tutorial or similar. Even if it does take some extra
> time to develop, if you pay an open source consultant to develop a solution
> rather than paying for conversion software, everyone can benefit.
>
> On Mon, 26 Jul 2021, 01:31 todor lambev, < totol...@abv.bg> wrote:
>
> Dear Charles,
>
> Thank you very much for your reply. I learned something new and usefull.
> I have to buy a DWG -> PNG convertor now but I think that will be fair if
> I need to preview all the files.
>
>
> Best regards
>
> Todor Lambev, PhD Student- - - - -*Institute of Oceanology
> **Department of coastal zones dynamics
> mob: +359 886 75 72 85;
> Varna, Bulgaria
> URL: http://www.io-bas.bg <http://www.io-bas.bg>*
>
>
>
>
>
> > Оригинално писмо 
> >От: Charles Dixon-Paver char...@kartoza.com
> >Относно: Re: [QGIS-Developer] DWG files preview in QGIS
> >До: todor lambev &l

Re: [QGIS-Developer] DWG files preview in QGIS

[Charles Dixon-Paver]

There should be no need to buy additional software to bulk convert DWG
files to PNG format. If you have access to autocad you should be able to
bulk export your layouts. I could likely share an auto lisp routine but
without an autocad license and sample data I wouldn't be able to test it.

As I said, I personally used the Autodesk True View application (which is
free) to bulk export to pdf. You can also use a program like imagemajick to
bulk convert PDF to PNG, so although it's a more complex workflow than
exporting directly to PNG it is certainly possible without purchasing
separate software.

If you struggle with automating these steps let me know. I expect it to be
quite a common procedure for users who work with CAD data and it may be
worth a quick YouTube tutorial or similar. Even if it does take some extra
time to develop, if you pay an open source consultant to develop a solution
rather than paying for conversion software, everyone can benefit.

On Mon, 26 Jul 2021, 01:31 todor lambev,  wrote:

> Dear Charles,
>
> Thank you very much for your reply. I learned something new and usefull.
> I have to buy a DWG -> PNG convertor now but I think that will be fair if
> I need to preview all the files.
>
>
> Best regards
>
> Todor Lambev, PhD Student- - - - -*Institute of Oceanology
> **Department of coastal zones dynamics
> mob: +359 886 75 72 85;
> Varna, Bulgaria
> URL: http://www.io-bas.bg <http://www.io-bas.bg>*
>
>
>
>
>
> > Оригинално писмо 
> >От: Charles Dixon-Paver char...@kartoza.com
> >Относно: Re: [QGIS-Developer] DWG files preview in QGIS
> >До: todor lambev 
> >Изпратено на: 23.07.2021 00:20
>
> No problem Todor, although it may be worth bearing in mind that these
> sorts of usability questions are typically better suited to the QGIS User
> mailing list and may get a better response from there.
>
> In terms of your query, I would say it is certainly possible to achieve in
> QGIS, but there are a few limits to what is possible and what is practical.
>
> Like I mentioned before, I believe what you are after is better served
> using raster files displaying your CAD information, so converting your DWGs
> to a raster format beforehand would be beneficial.
>
> Previewing the DWG file itself in QGIS probably isn't easily feasible, the
> easiest approach likely being some sort of HTML viewer integration. You can
> also convert the DWG to GPKG using QGIS tools to make it easier to work
> with, but again I feel this is not what you seem to need for your use case.
>
> I would expect some data from a DWG to be unsupported by QGIS when
> converting it, as well as having data which is outside of the drawing
> paperspace not be included in the preview image (amongst other issues
> depending on the structure/ design of the DWGs). Jorge outlined the code
> needed to load the DWG with an external program using an action as
> well, but that would specifically require loading an instance of a third
> party program. My suggestion would be to build the map project as outlined
> in the presentation with raster images, and attach an action to open the
> complete drawing for further introspection.
>
> I have created a small demo project which demonstrates how to achieve the
> outcomes I described. It includes various actions for launching file
> previews and contains a number of different layer styles and approaches for
> rendering the data in various manners as you would like. You can also
> configure the feature identification tool to automatically load the feature
> form and use the QGIS drag and Drop form designer to configure an image
> preview. The project also demonstrates using the QGIS atlas feature with
> print layouts to achieve the specific outcome highlighted in the
> presentation document.
>
> [image: output_3.png]
>
> You can download the files and project, DWG_integration_example.zip, from
> the following temporary file share:
>
> https://filebin.net/qxrw2xc94syeioo4
>
> (The Chrome browser security may complain it is unsafe, but you should be
> able to download it with firefox or edge etc)
>
> SHA256: 7E9E5A398BFAE4115EEE6D5C1B2073ED7314C6B7186AB61818D613B389991FD7
>
> I used some sample DWGs from the internet and bulk exported them to PDF
> using TrueView before converting to PNG, so this is definitely something
> you can make at least semi-automatic. If you have access to autocad, I
> imagine there are a number of options available for bulk exporting/
> plotting/ publishing, if not from within the software itself, certainly
> using AutoLisp.
>
> You could of course try to build similar DWG viewing functionality and
> leverage it in QGIS similar to what I have demonstrated with raster data,
> but I doubt it wou

Re: [QGIS-Developer] [Qgis-user] QGIS data source speed profiling

[Charles Dixon-Paver]

You can use the F12 key to access the developer tools which have a panel
for recording and monitoring network requests, as well as timing certain
operations for debug purposes.

One other trick I thought of to try was to use the label expression
epoch($now) on both a remote and local layer to show the time that an
expression is evaluated per layer which should give some indication of how
quickly a layer is available to QGIS. I then added a canvas decoration with
the same expression and every time I panned I could get the difference in
milliseconds between the layers. This actually kind of worked to my
surprise. Although not ideal it certainly should give you some sort of
feedback on vector layers and identify some of the slower layers.

Some of the members of the development list may have more sophisticated
methods available so I've copied that list into the response.

Regards

On Fri, 23 Jul 2021 at 15:59, Hugh Kelley  wrote:

> Hi all,
>
> I have a number of qgis files with a layers pulling datasets from a
> variety of sources that include local and shared drive files, shp, gpkg,
> tiff, and a few more, postgres databases and web feature services and map
> tile services.
>
> I'm wondering if anyone has any recommended workflows or tools for
> understanding the time required to refresh these layers. Some are faster
> than others and I have suspicions but I'd like to be able to see actual
> data confirming what I think are the slower layers.
>
> It's complicated by the fact that some symbologies take longer to render
> than others and that for non-local data sources, the connection speeds may
> change.
>
> Thanks for any suggestions. happy friday!
>
>
> Hugh
>
> ___
> 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] DWG files preview in QGIS

[Charles Dixon-Paver]

It's not totally clear to me what the objective is for your DWGs.

By "preview", do you mean wish to just view an overview image of the DWG
contents? If that is the case, I would recommend using a separate command
line/ batch process to produce raster format previews as DWGs. You can then
create a new field for the accompanying raster file using the field
calculator and QGIS expressions.

With the rasters you can use the preview option in the feature form, or
even use a "Raster Image Marker" based symbol at certain scales to
represent the DXF previews.

Another option for previews is to use the "Show map tips" option from the
QGIS toolbars. In the "Display" section of the layer properties you will
find that tooltips can use HTML code which will render a "web preview" of
the feature when you hover the cursor on it. for example, the
following should allow image previews:



In theory, you could likely combine this with a DWG rendering library such
as https://sharecad.org/it/DWGOnlinePlugin but I expect it will be
difficult to use and not very efficient, hence why I would suggest
converting the data to raster beforehand. One other thing you could do as
well is to use the "web view" of the QGIS form to render an html template
with an integrated viewer, but again, this is likely difficult and not
necessary.

I am not aware of any "preview" plugin for rendering DWG data within QGIS.

If your aim is to "load" the DWG into your project from a command available
within the point feature attributes, this is supported by using GitHub
actions and some custom code, although the process may be quite cumbersome.
Actions functionality was covered on the last QGIS Open Day[1] and I
recommend watching the demonstration if that is your use case.
Alternatively, there is also some written material on this topic [2] f you
would prefer to start there

[1] https://github.com/qgis/QGIS/wiki/QOD-June-2021#qgis-actions-deep-dive
[2]
https://courses.spatialthoughts.com/pyqgis-in-a-day.html#creating-custom-python-actions


On Tue, 20 Jul 2021 at 16:40, todor lambev  wrote:

> Dear QGIS developers,
>
> I have a strange need. Could you help me?
> I have 30 000 DWG files that are not georeferenced, each file has unique
> and a specific name. I have a point shapefile which in its attribute table
> contains a column with the names of the *dwg files.
>
> My question is: How I can load to preview the DWG files in QGIS next to
> the points or to preview the DWG by clicking on the point (similar to the
> photo preview widget)?
>
> I hope that you won't skip my question and will help me to find a solution
> basically because otherwise, I have to do it manually...
>
> Best regards
>
> Todor Lambev, PhD Student- - - - -*Institute of Oceanology
> **Department of coastal zones dynamics
> mob: +359 886 75 72 85;
> Varna, Bulgaria
> URL: http://www.io-bas.bg *
>
> ___
> 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] [Qgis-user] Missing plugins in version 3.20

[Charles Dixon-Paver]

It may well be the issue, although not one I was aware of. I am unsure if
the volunteers and developer handling packing and distribution have the
resources to test Windows 7. I have copied the developer list so hopefully
someone else can provide insight.


On Wed, 07 Jul 2021, 00:27 Pat Brown,  wrote:

> I have always used the standalone installer. I see that there is a note
> saying that WIN 7 no longer works but as this is mentioned under the
> OSGeo4W installer I thought it only applied to that. Am I wrong in this
> assumption? I am still using WIN 7 and all version 3.x have worked fine so
> far. Do think that WIN 7 could be my problem?
>
> On Tue, Jul 6, 2021, 23:58 Charles Dixon-Paver 
> wrote:
>
>> It seems that QGIS 3.20 is unable to access python correctly. It is
>> possible that this is an ENV/ Path error that may be resolved by launching
>> QGIS from a relevant batch file, such as C:\OSGeo4W\bin\qgis.bat (or
>> similar depending on your installation configuration)
>>
>> Are you using the "new" OSGeo4W installer? If not and you attempted to
>> upgrade from the old installer it could be causing the issue.
>>
>> There was an update to OSGeo4W for the latest release that is not really
>> backwards compatible. The current recommendation is to uninstall QGIS/
>> remove the historic OSGeo4W installation directory (or rename it), download
>> the latest installer from QGIS.org [1] and install a new instance of QGIS
>> from there.
>>
>> If you are using the LTR (stable release), then using the existing
>> installer to upgrade should be fine, but you likely won't be able to use
>> 3.20 correctly. There is more information on the downloads page related to
>> this.
>>
>> [1] https://www.qgis.org/en/site/forusers/download.html
>>
>>
>> On Tue, 6 Jul 2021 at 23:17, Pat Brown  wrote:
>>
>>> Hi Charles,
>>>Tried with a new user profile and I get the same result. The attached
>>> pics show what is displayed at each tab of the plugin manager
>>>
>>> On Tue, 6 Jul 2021 at 22:55, Charles Dixon-Paver 
>>> wrote:
>>>
>>>> Hi there,
>>>>
>>>> Have you tried to access the plugins with a fresh user profile?
>>>>
>>>> Also, the plugins manager has a settings tab. Can you give some more
>>>> information on the current configuration settings, such as the configured
>>>> plugin repository URL?
>>>>
>>>> On Tue, 6 Jul 2021 at 22:49, Pat Brown  wrote:
>>>>
>>>>> Hi
>>>>> I asked this a few days ago and I am wondering if perhaps no-one
>>>>> else has come across this problem.
>>>>> "I have installed the above version but it only shows 4 plug-ins.
>>>>> Whether I click on ALL or INSTALLED it still only shows 4. If I go back to
>>>>> 3.18 it works fine. Can anybody suggest a possible solution?"
>>>>> I uninstalled all versions on my PC and reinstalled 3.20 but still
>>>>> have the same problem. I then uninstalled 3.20 and reinstalled 3.18 and 
>>>>> the
>>>>> plugins work fine.
>>>>> Is there maybe a way to contact the developers to see if I can find a
>>>>> cause of my problem?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Pat
>>>>> ___
>>>>> 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] Feature discussion

[Charles Dixon-Paver]

There is a save project macro under the project properties which I believe
can be used to achieve this using the pyqgis api. Perhaps other users can
share snippets that perform the functions you are requesting, as I am not
entirely convinced that all of this functionality is useful enough to all
users to warrant inclusion as core features, or at least that this
functionality by default uses the bottom progress bar used by processing
tools rather than a separate and obtrusive dialogue.

On Thu, 1 Jul 2021 at 10:35, Paul Wittle 
wrote:

> Hi,
>
>
>
> I suspect this has already been asked a few times but I thought I’d ask
> anyway.
>
>
>
> Is there a feature request to get a dialogue box to appear when saving a
> project?
>
>
>
> I’m asking because if the knock on impact of Covid is more people working
> from home and using home broadband then I feel like there may need to be a
> greater level of user feedback. To give an example if I take a project file
> of about 4MB and save it locally it is finished in seconds (definitely
> under a minute) but if I take the same project file and save it to a
> network location via a VPN then the save time is longer; say a minute or
> two. Based on my investigation this seems to match up with peoples home
> broadband as in the UK the upload speed is pretty variable / often quite
> poor when compared with download speeds.
>
>
>
> I think it would be useful if there was a dialog that appears if a part of
> the process takes longer than x seconds. The dialog might say:
>
>- Creating project file
>- Saving to disk
>- Saving backup
>
>
>
> I think those are the main tasks involved in the save but it would be
> useful if the user is told that it is saving to disk but taking a while as
> hopefully they will then investigate their connection speed first.
>
>
>
> Not to worry if this has already been discussed and rejected but I thought
> I’d ask to see what the options / opinions are.
>
>
>
> Thanks,
>
> Paul
>
>
> This e-mail and any files transmitted with it are intended solely for the
> use of the individual or entity to whom they are addressed. It may contain
> unclassified but sensitive or protectively marked material and should be
> handled accordingly. Unless you are the named addressee (or authorised to
> receive it for the addressee) you may not copy or use it, or disclose it to
> anyone else. If you have received this transmission in error please notify
> the sender immediately. All traffic may be subject to recording and/or
> monitoring in accordance with relevant legislation. Any views expressed in
> this message are those of the individual sender, except where the sender
> specifies and with authority, states them to be the views of Dorset
> Council. Dorset Council does not accept service of documents by fax or
> other electronic means. Virus checking: Whilst all reasonable steps have
> been taken to ensure that this electronic communication and its attachments
> whether encoded, encrypted or otherwise supplied are free from computer
> viruses, Dorset Council accepts no liability in respect of any loss, cost,
> damage or expense suffered as a result of accessing this message or any of
> its attachments. For information on how Dorset Council processes your
> information, please see www.dorsetcouncil.gov.uk/data-protection
> ___
> 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] Visual Changelog for 3.20

[Charles Dixon-Paver]

I think I'm done there unless anyone is still pointing out issues...

On Fri, 18 Jun 2021 at 17:19, Andreas Neumann  wrote:

> Hi Richard,
>
> Yes - the notable fixes are already done.
>
> Yeah - I'm not too late this time ;-)
>
> Thank you for working on the visual changelog publication!
>
> Andreas
>
>
> On 2021-06-18 17:03, Richard Duivenvoorde wrote:
>
> Hi,
>
> Anybody is still busy with items on
> https://changelog.qgis.org/en/qgis/version/3.20/
>
> Or can I pull it in the website and rebuild the site with the changelog in
> it?
> (I see Andreas(?) already added the Notable fixes?)
>
> 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 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] It's time to contribute to the Changelog for QGIS 3.20!

[Charles Dixon-Paver]

I have captured additional entries for the following PRs:

https://github.com/qgis/QGIS/pull/42326
https://github.com/qgis/QGIS/pull/42286
https://github.com/qgis/QGIS/pull/41724
https://github.com/qgis/QGIS/pull/43193
https://github.com/qgis/QGIS/pull/42588
https://github.com/qgis/QGIS/pull/42401
https://github.com/qgis/QGIS/pull/41208
https://github.com/qgis/QGIS/pull/42587
https://github.com/qgis/QGIS/pull/42289
https://github.com/qgis/QGIS/pull/43559

The platform does retain the links to the original pull request... But I
don't think they are pulled through into the feed. Perhaps this CSV output
is a feature request for the changelog platform.

The ChangelogHarvested label is also used to identify items which have been
added to the changelog. You can use "-label:ChangelogHarvested" to exclude
them from PR searches on GitHub.

Note that sometimes a single feature is extended with multiple PRs within a
single release cycle, in which case the changelog entries are combined
where reasonable, so you may not find an entry for every PR with the
Feature or ChangelogHarvested labels.

On Fri, 11 Jun 2021 at 10:51, Totò  wrote:

> For the future I would like to suggest to create a CSV file with the titles
> of the new features and the link to the PR, this would facilitate the
> verification of the new features within the changelog.
>
> to search for features I used this filter:
>
>
> https://github.com/qgis/QGIS/pulls?q=is%3Apr+is%3Aclosed+label%3Afeature+merged%3A2021-02-18T00%3A00%3A00Z..2021-06-11T00%3A00%3A00Z+
>
> thank you so much for the great job
>
>
>
>
> -
> https://pigrecoinfinito.com/
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> ___
> 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] It's time to contribute to the Changelog for QGIS 3.20!

[Charles Dixon-Paver]

Thanks for catching this. These would have been merged without the
changelog label so I will add them. If anyone else notices any missing
features from the release please be sure to share a link to the PR.

On Fri, 11 Jun 2021 at 10:21, Totò  wrote:

> Good morning
> from a quick search it seems that these new features are missing
>
> can someone please confirm?
>
> https://github.com/qgis/QGIS/pull/42326
> https://github.com/qgis/QGIS/pull/42286
> https://github.com/qgis/QGIS/pull/41724
> https://github.com/qgis/QGIS/pull/43193
> https://github.com/qgis/QGIS/pull/42588
> https://github.com/qgis/QGIS/pull/42401
> https://github.com/qgis/QGIS/pull/41208
>
> Hello
>
>
>
> -
> https://pigrecoinfinito.com/
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> ___
> 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] [ui] blue != blue

[Charles Dixon-Paver]

>From what I can see, the SAP HANA icon is "close enough" in colour scheme
to the existing ones, as I checked the colours for the hana icon against
the postgres one in inkscape and got these results:

Postgis
Fill: #6e97c4ff
Stroke: #476280ff

Hana:
Fill: #6e97c4ff
Stroke: #425a75ff

The design isn't too off-putting, but I feel like there are issues with it:

1) The "bits" around the central chip are not visible against a dark
background, so it's not a "good" design.
2) The generic computer component doesn't seem ideal. It's differentiated
enough from existing providers to be useful, but it's generic enough that
it should be used for some other button or component, not tied to a
"branded" database.

I would personally like to see it using the "SAP" logo, to make a "DB2"
looking replacement, but it might not be ok with their corporate branding
terms. I can't think of a great replacement off the top of my head though.

The point cloud one I feel is pretty jarring and way off. I've attached an
svg of what I think it should look like.

On Wed, 3 Feb 2021 at 16:02, Richard Duivenvoorde 
wrote:

> On 2/3/21 2:54 PM, Richard Duivenvoorde wrote:
> > Hi,
> >
> > Am I the only one, getting blind (not really, just finding it not so
> nice) of the different use of blue for Point Cloud in the Datasource button
> bars (like in the Data Source Manager).
>
> I do not have a really good feeling for colors, but recently also the Hana
> icons were added:
>
>
> https://github.com/qgis/QGIS/blob/master/images/themes/default/mActionAddHanaLayer.svg
>
> https://github.com/qgis/QGIS/blob/master/images/themes/default/mIconHana.svg
>
> does that 'fit' in the 'color scheme'? (asking to peeps with
> designer/cartography backgrounds)
>
> (not sure who did the earlier cleanup of our icon theme)
>
> 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
>
___
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] Stale bot and older requests/issues - possible enhancement

[Charles Dixon-Paver]

I agree with Jorge and am personally not a fan of a simple "pay a
commercial partner" message, which is why I think a separate link like
Matthias suggested is a great idea, and any message which might be
interpreted as "It's open source, so fix it yourself" could be harmful.

I think a large part of the problem is an awareness issue, where there is a
lack of understanding of the development process and ecosystem at large.
Users should know that donations and sustaining memberships go a long way
to feature development and squashing bugs too, but they also need to know
that it cannot be guaranteed that a specific issue will be addressed unless
they make their own arrangements to address it.

When you factor in community engagement, hackfests, crowd funding, and all
the other initiatives the project is undertaking, I feel like there is a
lot more that users can do besides buying a support contract.

Mostly I think the message would need to be concise but meaningful, and
although it may be frustrating for "seasoned veterans" of the community to
keep seeing it pop-up, I think it is a fair way to engage with users in a
way that supports a healthy ecosystem. I think if it gets too "spammy", the
simple solution is to extend the timeframe before the message is applied.

I made an error in my previous suggested notice and would certainly replace
"how to sponsor the development of this functionality" with "how to support
the development of this functionality".

But that's just my three cents ;-)


On Fri, 8 Jan 2021 at 17:58, Jorge Gustavo Rocha  wrote:

> Hi,
>
> I have a different opinion on this. We should emphasis the community
> component of our QGIS open source project. Just asking to pay if they
> want the issue solved, is what any commercial software project does. It
> does not help to create new contributors.
>
> Reporting and working on issues is (should be) included in our strategy
> to promote participation and get new blood. It is a good place to engage
> new users into QGIS development.
>
> Users should be encourage to know better the community and the people
> behind the software. If a issue is tagged as stale, we should help them
> to identify and know the people related/behind that feature. Without
> knowing the people and without communication, there is no community.
>
> When people know and trust the community behind software, they will
> invest money in. In other words, it is too soon to ask for money for
> someone that just filled an issue in github.
>
> Just my two cents.
>
> Jorge Gustavo
>
> Às 00:42 de 07/01/21, Nyall Dawson escreveu:
> > Hi list,
> >
> > I've a small request to consider for stale bot and issues/feature
> > requests. I think that if a ticket remains open for say > 90 days
> > since the last comment, it would be nice if stale bot added a comment
> > like:
> >
> > "Unfortunately this bug/feature request has not seen any solution in
> > the recent QGIS release. If this fix/feature is important to you or
> > your organisation, you can help to fast-track its development by
> > sponsoring this work. To do so, contact one of the QGIS commercial
> > support providers listed at ... to discuss how you could fund this
> > functionality".
> >
> > I think it's a non-threatening, non-begging way to advise bug
> > reporters on the alternative ways they can fast track development in
> > QGIS.
> >
> > 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
> >
>
> J. Gustavo
> --
> Jorge Gustavo Rocha
> Departamento de Informática
> Universidade do Minho
> 4710-057 Braga
> Gabinete 3.29 (Piso 3)
> Tel: +351 253604480
> Fax: +351 253604471
> Móvel: +351 910333888
> skype: nabocudnosor
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
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] Stale bot and older requests/issues - possible enhancement

[Charles Dixon-Paver]

How about something like:

Unfortunately this issue has not been addressed by the QGIS community for
some time. If you would like to expedite the resolution of this issue and
more like it, please refer to the https://qgis.org/en/site/getinvolved/facilitation.html;>facilitating
development guide for information on how to sponsor the development of
this functionality.

And make a facilitation page that explains the various resolution options
nicely.

Not sure if that's OK for non-native speakers

On Fri, 8 Jan 2021 at 02:51, Alexandre Neto  wrote:

>
> On Thu, Jan 7, 2021 at 11:44 PM Nyall Dawson 
> wrote:
>
>>
>>
>> What I'm trying to convey here is that there's a chance the ticket
>> will be addressed without sponsorship, but if they DO sponsor it will
>> get addressed immediately. So "fast track" here means something a
>> little like "short cut".  Is there better wording you think may convey
>> this same meaning?
>>
>> Nyall
>>
>>
>>
> Maybe "Speed up" or "accelerate"
>
> But maybe it's just my limited vocabulary.
>
> Alexandre
>
>
>> >
>> > Other than that +1
>> >
>> > Alexandre Neto
>> >
>> > A quinta, 7/01/2021, 08:33, Matthias Kuhn 
>> escreveu:
>> >>
>> >> Hi Nyall,
>> >>
>> >> I would also appreciate a hint like this.
>> >> Maybe it could be done even more subtle by shortening this text and
>> adding a link to a page "learn how to make things progress"?
>> >>
>> >> I'd also very much appreciate the voices of users on this topic
>> (that's a classical "we don't only want to hear the dev side" topic).
>> >>
>> >> Matthias
>> >>
>> >> On Thu, Jan 7, 2021 at 1:42 AM Nyall Dawson 
>> wrote:
>> >>>
>> >>> Hi list,
>> >>>
>> >>> I've a small request to consider for stale bot and issues/feature
>> >>> requests. I think that if a ticket remains open for say > 90 days
>> >>> since the last comment, it would be nice if stale bot added a comment
>> >>> like:
>> >>>
>> >>> "Unfortunately this bug/feature request has not seen any solution in
>> >>> the recent QGIS release. If this fix/feature is important to you or
>> >>> your organisation, you can help to fast-track its development by
>> >>> sponsoring this work. To do so, contact one of the QGIS commercial
>> >>> support providers listed at ... to discuss how you could fund this
>> >>> functionality".
>> >>>
>> >>> I think it's a non-threatening, non-begging way to advise bug
>> >>> reporters on the alternative ways they can fast track development in
>> >>> QGIS.
>> >>>
>> >>> 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 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] [Qgis-community-team] Changelog check

[Charles Dixon-Paver]

I'm wondering if we should remove the "Feature: " prefix from these
entries. It seems a little redundant to me. I've not encountered a
duplication of a case sensitive match that I can recall (and I feel that it
would have stood out), so a simple find and replace with casing match
should work.

I don't know if I should go ahead and PR this or is someone attached to
these header prefixes?

On Sat, 24 Oct 2020 at 00:48, Tim Sutton  wrote:

> Thank you so much for all your hard work Richard and Charles and everyone
> else involved! It looks great to me.
>
> Regards
>
> Tim
>
> On Fri, Oct 23, 2020 at 7:21 PM Richard Duivenvoorde 
> wrote:
>
>> Hi All,
>>
>> I (silently) incorporated the Visual Changelog for 3.16 into the site, so
>> you devs can check for glitches:
>> https://qgis.org/en/site/forusers/visualchangelog316/index.html
>>
>> Please edit (or Pull Request) on the rst sources now, if you see
>> something that can be made better:
>>
>> https://github.com/qgis/QGIS-Website/edit/master/source/site/forusers/visualchangelog316/index.rst
>>
>> Thanks All for making this possible (specially Charles & Other
>> Kartozians).
>>
>> Regards,
>>
>> Richard Duivenvoorde
>>
>> PS sources (to translate) will be uploaded to transifex when releases are
>> actually available and the website is updated to reflect 3.16
>> ___
>> Qgis-community-team mailing list for organizing community resources such
>> as documentation, translation etc..
>> qgis-community-t...@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
>
>
>
> --
>
> --
> ​
>
> Tim Sutton
> 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
> Tim is a member of the QGIS Project Steering Committee
>
> ---
> Kartoza is a merger between Linfiniti and Afrispatial
> ___
> 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] qgis-dev icon color

[Charles Dixon-Paver]

I am usually quite critical with design work, but have always been very
fond of the QGIS3 branding.

Although I agreed with the idea of a red "dev" indication over the existing
logo, I had wondered if there was a creative way I could tweak the logo for
differing version icons and actually have it work. I didn't have high
hopes, as it would have to check all three boxes for being pretty, being
unique/ distinguishable and also retain the QGIS identity.

After a quick experiment I have concluded that the "Irish" logo is the best
one and pretty much any and all modifications I performed were failures. If
you want to see the results I put it on imgur. Warning: it's not pretty.

https://imgur.com/a/JBmqUp6

On Sat, 24 Oct 2020 at 09:10, Tobias Wendorff <
tobias.wendo...@tu-dortmund.de> wrote:

> Am 24.10.2020 um 09:05 schrieb Richard Duivenvoorde:
>  >
> > Didn't we have a versions with a big 'DEV' in red over it?
> > Or is that an option to add that programmatically (during dev build)?
> Then we would just keep one nice green icon :-)
>
> In the OSGeo4W-build, qgis-dev-bin.exe only has one icon (the normal
> "irish" one).
> ___
> 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] Missing Changelog Features

[Charles Dixon-Paver]

Typically the workflow is that most days I'll loop through any pull
requests labelled "feature" and see if they describe the new functionality
well enough to produce a changelog entry. This will usually be over the
review period before merging, so if there is something outstanding or
unclear I can ask the developer for more information/ screenshots etc
before the PR gets merged.

The Changelog label indicates that an item is "ready to harvest" and I
generally only apply it to *open* PRs with the feature label, then I
harvest the closed PRs with the Changelog label applied.

In your case it's a bit different though because I think between yourself
and Matheiu you might often be ready to merge before I even see the PR
(being the ninja-wizards I know you to be), so if you want to merge a
new feature before it's been tagged for changelog inclusion just add the
"Changelog" label yourself rather than letting the changelog workflow
become a blocker. Then I'll change the label to "ChangelogHarvested" once I
pull it into the changelog.qgis.org system.

I think it would get a bit messy having everyone trying to tag and label
these entries though, so I think we make this the exception for core
maintainers rather than the rule for most developers.

Alternatively I could periodically go through merged PRs with the feature
label that haven't been labelled with Changelog or Changelog harvested.
It's just an extra manual step (and point of failure), but I'm happy to
take that on rather than add extra work for the core devs, so let me know
if you would prefer that.

Fortunately the workflow has worked for the majority of new features
anyway, so we should still be ready to publish on release day!

Regards

On Tue, 13 Oct 2020 at 01:04, Nyall Dawson  wrote:

> On Mon, 12 Oct 2020 at 22:59, Charles Dixon-Paver 
> wrote:
>
> > @Nyall I noticed that you have introduced a lot of new features that
> jumped straight from PR=>merged without the changelog label.
>
> Sorry about this! I guess I'm a little confused by the responsibility
> here -- should we be tagging "Changelog" ourselves for anything which
> we deem as important to include in the changelog? Or is this a label
> which you want to reserve for your use only?
>
> >
> > With how hard and fast you introduce new contributions I think it would
> be folly for the changelog process to become a blocker for your work, so I
> don't particularly have an issue with this sidestepping of the "usual"
> process (PR=>feature label=>changelog label=>merge).
> >
> > You also typically provide detailed descriptions of the feature so
> that's not an issue for me, but if you could label your new features
> "Changelog" when you merge them so that I can include them as a part of the
> standard harvesting workflow I'd appreciate it.
> >
> > I tried to go collect all of those that are merged which you have tagged
> as "feature" for the next release and have added the following PRs to the
> changelog list:
> >
> > https://github.com/qgis/QGIS/pull/38316
> > https://github.com/qgis/QGIS/pull/38651
> > https://github.com/qgis/QGIS/pull/38652
> > https://github.com/qgis/QGIS/pull/38654
> > https://github.com/qgis/QGIS/pull/38624
> > https://github.com/qgis/QGIS/pull/37958
>
> I had a look, and think you've caught them all!
>
> Nyall
>
> >
> > If anyone has suggestions for improving the changelog maintenance
> workflow please let me know. It's documented on
> https://github.com/qgis/QGIS/wiki/Changelog-Workflows
> >
> > Regards
> >
> > --
> > Charles Dixon-Paver - GIS Specialist
> > Cell: +27(0)720607511
> >
> --
> > Visit http://kartoza.com to find out about open source:
> > * Full stack web, desktop and mobile geospatial software development
> > * GIS training
> > * Support, hosting and maintenance
> > * Consulting services
> >
> ---
> > ___
> > 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] Missing Changelog Features

[Charles Dixon-Paver]

Greetings developers,

Totò graciously pointed out that PR #38025 was missing from the changelog
entries for 3.16 LTS

This happened because the feature label was not applied to the PR... At
this point I spend most of my time doing copy editing and not monitoring
the PR queue, so if a feature is not labelled as such it won't get labelled
for inclusion in the changelog.

I had a quick dig through the PR list and found a bunch of similar features:

https://github.com/qgis/QGIS/pull/38448
https://github.com/qgis/QGIS/pull/38331
https://github.com/qgis/QGIS/pull/37593
https://github.com/qgis/QGIS/pull/37588

There's a lot of great functionality there that I think is important to
showcase and publish and it would be a shame if it fell through the cracks.
There may be others like this so if anybody finds any I missed please let
me know.

I would ask that those that have made PRs which introduce new features just
double check that their PRs are labelled with the "feature" label in
future, and that new features for 3.16 are labelled "Changelog" or
"ChangelogHarvested". Don't apply the changelog label yourself, just let me
know and I will do it.

@Nyall I noticed that you have introduced a lot of new features that jumped
straight from PR=>merged without the changelog label.

With how hard and fast you introduce new contributions I think it would be
folly for the changelog process to become a blocker for your work, so I
don't particularly have an issue with this sidestepping of the "usual"
process (PR=>feature label=>changelog label=>merge).

You also typically provide detailed descriptions of the feature so that's
not an issue for me, but if you could label your new features "Changelog"
when you merge them so that I can include them as a part of the standard
harvesting workflow I'd appreciate it.

I tried to go collect all of those that are merged which you have tagged as
"feature" for the next release and have added the following PRs to the
changelog list:

https://github.com/qgis/QGIS/pull/38316
https://github.com/qgis/QGIS/pull/38651
https://github.com/qgis/QGIS/pull/38652
https://github.com/qgis/QGIS/pull/38654
https://github.com/qgis/QGIS/pull/38624
https://github.com/qgis/QGIS/pull/37958

If anyone has suggestions for improving the changelog maintenance workflow
please let me know. It's documented on
https://github.com/qgis/QGIS/wiki/Changelog-Workflows

Regards

-- 
Charles Dixon-Paver - GIS Specialist
Cell: +27(0)720607511
--
Visit http://kartoza.com to find out about open source:
* Full stack web, desktop and mobile geospatial software development
* GIS training
* Support, hosting and maintenance
* Consulting services
---
___
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] Need help troubleshooting Browser Panel freezing QGIS

[Charles Dixon-Paver]

Have you tried a fresh user profile to see if the problem persists? This
should be a quick way to test if it's data connection or plugin related.

On Fri, 9 Oct 2020 at 04:45, i-s-o <46.i.s.o...@gmail.com> wrote:

> The Browser Panel hasn't worked for me for at least the past couple of
> years (I'm on Windows 10). My best guess: this is related to my computer
> being part of a Windows Domain. Seeing that DB Manager may be discontinued,
> and several of its functionalities are being moved to the Browser Panel, I
> tried to figure out what is wrong with it.
>
> The problem manifests itself when I disconnect my laptop from the company
> network: if the Browser Panel is enabled, QGIS would freeze 20-40 seconds
> every minute or so during active use. I am pretty sure this is not limited
> to my computer: I provide training to other staff, and they all have the
> same problem (both OSGeo4W-advanced and standalone installations).
>
> Note that the problem disappears if I remotely connect to my company's
> network via VPN: it looks like QGIS Browser Panel (or Qt) is periodically
> trying to query some resource(s) on the company's network, and gives up
> after some time.
>
> I ran QGIS with debug options, but I didn't see a clear pattern pointing
> to the source of the problem. Any suggestions about what to do next to
> figure out what's going on?
>
> Here is a redacted log around the freeze episodes:
>
> ..\..\..\src\app\main.cpp(510) : (main) [0ms] Starting qgis main
> ..\..\..\src\core\qgsapplication.cpp(172) :
> (QgsApplication::QgsApplication) [32ms] loading of qgis translation failed
> C:/tools/OSGeo4W64/apps/qgis-dev/./i18n//qgis_en_US
> ..\..\..\src\core\qgsapplication.cpp(187) :
> (QgsApplication::QgsApplication) [0ms] loading of qt translation failed
> C:/tools/OSGeo4W64/apps/Qt5/translations/qt_en_US
> ..\..\..\src\core\qgsmessagelog.cpp(29) : (QgsMessageLog::logMessage)
> [488ms] 2020-10-01T11:31:52 [1] Successfully loaded globalsettingsfile
> path: C:/tools/OSGeo4W64/apps/qgis-dev/./resources/qgis_global_settings.ini
> ..\..\..\src\app\main.cpp(1080) : (main) [2ms] User profile details:
> ... skip
> line 645
> ..\..\..\src\gui\qgsmaptool.cpp(90) : (QgsMapTool::activate) [0ms] Cursor
> has been set
> ..\..\..\src\gui\qgsmapcanvas.cpp(529) : (QgsMapCanvas::refresh) [16ms]
> CANVAS refresh - invalid settings -> nothing to do
> ..\..\..\src\core\qgsdataitem.cpp(391) : (QgsDataItem::populate) [10543ms]
> mPath = favorites:
> ..\..\..\src\core\qgsdataitem.cpp(463) : (QgsDataItem::populate) [0ms]
> mPath = favorites:
> ... skip
> line 743
> ..\..\..\src\core\qgsbrowsermodel.cpp(783) :
> (QgsBrowserModel::addProviderRootItem) [0ms] Add new top level item :
> Spatial Bookmarks
> ..\..\..\src\gui\qgsbrowsertreeview.cpp(73) :
> (QgsBrowserTreeView::restoreState) [1ms] mExpandPaths = favorites:
> ..\..\..\src\core\qgsbrowsermodel.cpp(406) : (QgsBrowserModel::findPath)
> [0ms] Arrived favorites:
> ..\..\..\src\core\qgsbrowsermodel.cpp(579) :
> (QgsBrowserModel::itemDataChanged) [11946ms] Entered
> ..\..\..\src\core\qgsbrowsermodel.cpp(579) :
> (QgsBrowserModel::itemDataChanged) [340ms] Entered
> ... skip
> line 14860
> ..\..\..\src\providers\wms\qgswmsprovider.cpp(247) :
> (QgsWmsProvider::~QgsWmsProvider) [0ms] deconstructing.
> ..\..\..\src\core\qgsmaprenderersequentialjob.cpp(131) :
> (QgsMapRendererSequentialJob::internalFinished) [0ms] SEQUENTIAL finished
> ..\..\..\src\core\qgsmaprenderersequentialjob.cpp(37) :
> (QgsMapRendererSequentialJob::~QgsMapRendererSequentialJob) [0ms]
> SEQUENTIAL destruct
> ..\..\..\src\core\qgsmaprenderercustompainterjob.cpp(73) :
> (QgsMapRendererCustomPainterJob::~QgsMapRendererCustomPainterJob) [0ms]
> QPAINTER destruct
> ..\..\..\src\core\qgsmaplayer.cpp(165) : (QgsMapLayer::name) [32572ms]
> returning name 'OpenStreetMap'
> ..\..\..\src\core\qgsmaplayer.cpp(165) : (QgsMapLayer::name) [193ms]
> returning name 'OpenStreetMap'
> ..\..\..\src\core\qgsvectorlayer.cpp(1769) :
> (QgsVectorLayer::setDataProvider) [32020ms] Instantiated the data provider
> plugin
> ..\..\..\src\core\qgsdatasourceuri.cpp(213) :
> (QgsDataSourceUri::QgsDataSourceUri) [0ms] parameter
> "Point?crs":"EPSG:4326=time:datetime(0,0)={f2264946-651d-4539-aecc-e474431c88c9}"
> added
> ... skip
> line 14973
> ..\..\..\src\core\qgsmaplayer.cpp(165) : (QgsMapLayer::name) [1ms]
> returning name 'temporal-test-ML'
> ..\..\..\src\core\qgsmaplayer.cpp(165) : (QgsMapLayer::name) [1ms]
> returning name 'temporal-test-ML'
> ..\..\..\src\core\qgsmaplayer.cpp(165) : (QgsMapLayer::name) [21210ms]
> returning name 'temporal-test-ML'
> ..\..\..\src\gui\qgsmapcanvas.cpp(557) : (QgsMapCanvas::refreshMap) [33ms]
> CANVAS refresh!
> ... skip
> line 48764
> ..\..\..\src\core\qgsmaplayer.cpp(165) : (QgsMapLayer::name) [0ms]
> returning name 'OpenStreetMap'
> ..\..\..\src\core\qgsmaplayer.cpp(165) : (QgsMapLayer::name) [24ms]
> returning name 'temporal-test-ML'
> ..\..\..\src\core\qgsmaplayer.cpp(165) : (QgsMapLayer::name) [28438ms]

[QGIS-Developer] Changelog maintenance

[Charles Dixon-Paver]

Greetings QGIS community,

With the release of 3.16 LTS around the corner, we are hoping to have the
changelog ready to publish at the time of release. The developers have been
hard at work implementing a wealth of new features, which of course makes
for a lot of new entries in the changelog which need some help getting
dressed up and "publication ready".

It would be great if some community members would like to get involved in
the changelog maintenance process. It is a great way to contribute to the
community without the need for highly specialised skills. The skills you
will need are:

- Strong command of the English language
- Decent writing ability
- Some basic understanding of the QGIS functionalities and changes you will
be describing...

Basically, the process entails taking the contents from Pull Requests of
features introduced by the developers and tidying up the entry into a more
publication friendly format suitable for end users.

We have detailed the workflow for changelog maintenance [1], which includes
a recording of our walkthrough of the changelog maintenance process from
kwakfest.

Of particular interest to those interested in partaking are the
conventions[2] used when editing changelog entries.

To get involved, you will need to sign up or have an account at the
changelog site[3] and contact myself or Tim Sutton in order to get edit
permissions for the changelog entries.

The more eyes we have going over these entries, the less likely it is that
errors will be overlooked. Looking forward to hearing from you all.

Emails and queries can be directed to charles[at]kartoza.com

[1] https://github.com/qgis/QGIS/wiki/Changelog-Workflows
[2]
https://github.com/qgis/QGIS/wiki/Changelog-Workflows#conventions-for-changelog-entries
[3] https://changelog.qgis.org

Regards

-- 
Charles Dixon-Paver - GIS Specialist
Cell: +27(0)720607511
--
Visit http://kartoza.com to find out about open source:
* Full stack web, desktop and mobile geospatial software development
* GIS training
* Support, hosting and maintenance
* Consulting services
---
___
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] Coordinates of a pixel

[Charles Dixon-Paver]

Glad to hear you found a solution. In general, I usually favour the
approach of developing a solution which works in a local coordinate system
and projecting after the fact. It's usually a lot simpler and allows me to
leave the "rocket science" to the rocket scientists...

One caveat you should be aware of though is that calculating positions on
systems that are not cylindrical (e.g. a conical projection like albers
ea), working at very high latitudes (where cylindrical projections probably
aren't suitable anyway) or using images that have some sort of rotation
applied etc may make things considerably more complex and even totally
break your localised implementation (depending on how intelligent the
solution is). I usually try to build things that are dynamic by somehow
binding units/ CRS to the current map frame or similar logic, but in an
instance like this it's probably better to have a hard-coded
"all-or-nothing" solution.

There may also be other situations where things get a bit fuzzy, but I
think as long as you're using UTM and images aren't rotated you should be
OK (just be aware of these limitations if you plan on implementing this for
users in other regions).

Regards

On Sat, 5 Sep 2020 at 02:58, Miguel-Ángel Fas-Millán 
wrote:

> Hi again,
> Thanks for your replies. Charles was right, the deviation between WGS and
> ETRS was not the problem. Finally I'm using UTM while moving through the
> dataset and only convert to geographic coordinates when I arrive at the
> point of interest. The previous way of doing it was quite more complex and
> it seems it added inaccuracies here and there.
>
> Thanks again for your time,
>
> Miguel
>
> El mar., 1 sept. 2020 a las 19:59, Charles Dixon-Paver (<
> char...@kartoza.com>) escribió:
>
>> I would wager that those deviations between WGS and ETRS are unlikely to
>> be the cause of this discrepancy, unless your implementation somehow
>> compounds the inaccuracies between them. The way it's "calculated" in a GIS
>> is by referencing the image to a coordinate system and then returning the
>> coordinates at a specified location (a process which is totally abstract
>> from image pixels).
>>
>> I haven't tested the code you're using, but from what I can see the most
>> likely culprit is some abstract issue with the implementation which is
>> difficult for us to resolve here (although a bug is certainly possible).
>> For example, if you are using a DSM that is in geographic coordinates, the
>> pixel sizes/ cell resolution are geographic units. That means that each
>> cell is not a uniform distance (in meters) in size, yet the function you
>> link to seems to require an input distance parameter in meters.
>> Transforming units between coordinate systems is not trivial and likely
>> requires expert advice. This may not be the case though, as I may be
>> misunderstanding your requirements entirely.
>>
>> I believe Tims response was merely an example of how to get the details
>> of an image which has been imported into QGIS in a similar manner as what I
>> suggested with a world file. Depending on the usage and accuracy required,
>> you can quite easily use the pixel size and the raster extents/ origin to
>> calculate a pixel position (although not very robust,  I find it is often
>> useful).
>>
>> I hope that helps somewhat rather than confusing the issue further. As I
>> stated before, perhaps someone has an idea of where to point you in the
>> codebase (in either QGIS or upstream projects like proj and GDAL), but I
>> don't think you're entirely on the right path here...
>>
>> On Tue, 1 Sep 2020 at 17:59, Miguel-Ángel Fas-Millán <
>> fas.mil...@gmail.com> wrote:
>>
>>> Hi again,
>>>
>>> Charles > I checked that, but no. The deviation is not so high. I
>>> suspect that the way it's calculated in QGIS is taking something into
>>> account that the function I'm using (and the web, both return same result)
>>> is not.  Maybe this? My DSM is in ETRS89: "*Note that the World
>>> Geodetic System WGS84 and the European Reference System ETRS89 are
>>> virtually identical and that coordinate transformation between the two
>>> systems in practical navigation is unnecessary. However, for high-precision
>>> surveying work - be aware that the two systems deviates more than half a
>>> meter.*"
>>> But I don't know how to take that deviation into account in the function
>>> or why it seems to affect only  the longitude.
>>>
>>> Code of the calculateEndingGlobalCoordinates that I'm using:
>>> https://github.com/mgavaghan/geodesy/blob/master/src/main/jav

Re: [QGIS-Developer] Coordinates of a pixel

[Charles Dixon-Paver]

I would wager that those deviations between WGS and ETRS are unlikely to be
the cause of this discrepancy, unless your implementation somehow
compounds the inaccuracies between them. The way it's "calculated" in a GIS
is by referencing the image to a coordinate system and then returning the
coordinates at a specified location (a process which is totally abstract
from image pixels).

I haven't tested the code you're using, but from what I can see the most
likely culprit is some abstract issue with the implementation which is
difficult for us to resolve here (although a bug is certainly possible).
For example, if you are using a DSM that is in geographic coordinates, the
pixel sizes/ cell resolution are geographic units. That means that each
cell is not a uniform distance (in meters) in size, yet the function you
link to seems to require an input distance parameter in meters.
Transforming units between coordinate systems is not trivial and likely
requires expert advice. This may not be the case though, as I may be
misunderstanding your requirements entirely.

I believe Tims response was merely an example of how to get the details of
an image which has been imported into QGIS in a similar manner as what I
suggested with a world file. Depending on the usage and accuracy required,
you can quite easily use the pixel size and the raster extents/ origin to
calculate a pixel position (although not very robust,  I find it is often
useful).

I hope that helps somewhat rather than confusing the issue further. As I
stated before, perhaps someone has an idea of where to point you in the
codebase (in either QGIS or upstream projects like proj and GDAL), but I
don't think you're entirely on the right path here...

On Tue, 1 Sep 2020 at 17:59, Miguel-Ángel Fas-Millán 
wrote:

> Hi again,
>
> Charles > I checked that, but no. The deviation is not so high. I suspect
> that the way it's calculated in QGIS is taking something into account that
> the function I'm using (and the web, both return same result) is not.
> Maybe this? My DSM is in ETRS89: "*Note that the World Geodetic System
> WGS84 and the European Reference System ETRS89 are virtually identical and
> that coordinate transformation between the two systems in practical
> navigation is unnecessary. However, for high-precision surveying work - be
> aware that the two systems deviates more than half a meter.*"
> But I don't know how to take that deviation into account in the function
> or why it seems to affect only  the longitude.
>
> Code of the calculateEndingGlobalCoordinates that I'm using:
> https://github.com/mgavaghan/geodesy/blob/master/src/main/java/org/gavaghan/geodesy/GeodeticCalculator.java
>
> Tim > Good to know. Not sure how could I leverage those data. I called
> pixels  to the DSM cells but really I'm not interested in the graphical
> part, just in how is calculating the coordinates of those cells from the
> xllcenter and yllcenter correctly.
>
>
>
>
> El mar., 1 sept. 2020 a las 15:32, Tim Sutton ()
> escribió:
>
>> Hi
>>
>> Also you can get the extents of the layer in the layer properties ->
>> Information tab e.g.:
>>
>>
>> Name DEM_10m
>> Path /home/timlinux/gisdata/Rwanda/DEM_10m.tif
>> CRS EPSG:4326 - WGS 84 - Geographic
>> Extent 28.9592194665249139,-2.8404830825979692 :
>> 30.8994723851809887,-1.0469841014800894
>> Unit degrees
>> Width 21524
>> Height 19896
>> Data type Int16 - Sixteen bit signed integer
>> GDAL Driver Description GTiff
>> GDAL Driver Metadata GeoTIFF
>> Dataset Description /home/timlinux/gisdata/Rwanda/DEM_10m.tif
>> Compression
>> Band 1
>> RepresentationType=THEMATIC
>> STATISTICS_APPROXIMATE=YES
>> STATISTICS_MAXIMUM=3821
>> STATISTICS_MEAN=1697.9520539082
>> STATISTICS_MINIMUM=15
>> STATISTICS_STDDEV=341.19933119234
>> STATISTICS_VALID_PERCENT=56.38
>> More information
>> AREA_OR_POINT=Area
>> DataType=Generic
>> Dimensions X: 21524 Y: 19896 Bands: 1
>> Origin 28.9592,-1.04698
>> Pixel Size 9.01436962765319623e-05,-9.01436962765319623e-05
>>
>> Regards
>>
>> Tim
>>
>>
>> On Tue, Sep 1, 2020 at 9:51 AM Charles Dixon-Paver 
>> wrote:
>>
>>> I took a cursory glance at the calculator you used and the description
>>> you've given, and I think there's a possibility you're simply using an
>>> easting value in the calculator. You could try multiplying your input
>>> longitude by -1 for a quick fix (although I haven't tested this will work
>>> at all).
>>>
>>> On Tue, 1 Sep 2020 at 03:31, Miguel-Ángel Fas-Millán <
>>> fas.mil...@gmail.com> wrote:
>>>
>>>> Thanks for 

Re: [QGIS-Developer] Coordinates of a pixel

[Charles Dixon-Paver]

I took a cursory glance at the calculator you used and the description
you've given, and I think there's a possibility you're simply using an
easting value in the calculator. You could try multiplying your input
longitude by -1 for a quick fix (although I haven't tested this will work
at all).

On Tue, 1 Sep 2020 at 03:31, Miguel-Ángel Fas-Millán 
wrote:

> Thanks for your reply. Well, let me provide more details to explain why I
> was asking that.
> I have a DSM, with its xllcenter/yllcenter coordinates and I need to know
> the coordinates of the (in this case) center of any of the squares/cells
> (which, maybe wrongly, I called pixels) represented by this dataset. To
> that I've been using a function equivalent to the provided by this
> calculator: https://geodesy.noaa.gov/cgi-bin/Inv_Fwd/forward2.prl , which
> takes as parameters the starting point, azimuth, distance, and returns the
> ending coordinates.
>
> For instance, I want to calculate the coordinates of the first cell of the
> dataset (top left of the matrix). So I do:
>
> calculateEndingGlobalCoordinates(Ellipsoid.*WGS84*, start_coords, 0.0,
> nrows*cellsize) //0.0 for north
>
> The problem is that it returns a value with a latitude that seems ok, but
> a wrong longitude. When I place that coordinate in QGIS, it is out of the
> image, quite at left of the top left corner.
>
> Unsurprisingly, if I place the coordinates obtained with this method (or
> with the online calculator mentioned) in google maps, to check if it makes
> sense looking at what's there in the satellite images, they make no sense
> at all.
>
> However, if I take the coordinates appearing in QGIS when I hover one of
> the cells, and place them in google maps, it makes perfect sense. With a
> few meters of difference, but well, at least it is on the right track. (I
> am that sure because I took as reference a ATC tower, which is the highest
> element in a wide area).
>
> That's why I wanted to check what's the difference between the mentioned
> method I was using and whatever is made in the code to return those quite
> correct coordinates.
>
>
>
>
> El mar., 1 sept. 2020 a las 0:01, Charles Dixon-Paver (<
> char...@kartoza.com>) escribió:
>
>> Someone can correct me if I'm wrong, but I think there's a
>> misunderstanding here of how this raster data is handled in a GIS. From my
>> understanding of the question, I don't know that what you're asking for is
>> available "in the code" the way you expect.
>>
>> The coordinates are showing the position of the cursor relative to the
>> origin of the assigned coordinate reference system. The raster data is
>> "projected" onto that reference system, which assigns positions to some
>> points on the image and stretches, rotates or distorts the image in
>> accordance with the images affine parameters that ensure all the different
>> parts of the image remain spatially correct. How the GIS knows where to get
>> these parameters varies between data types and file formats.
>>
>> Playing around with the georeferencer tool in QGIS should give you a
>> pretty clear understanding of how this "projection" works.
>>
>> There are ways to get the coordinates of a position or pixel within an
>> image programmatically, the easiest of which that I can think of is using
>> values from a world file [1] with an xy position (in pixels) of the pixel
>> of interest. The code required for achieving this, however, is probably
>> going to be dependant on a wide variety of factors (not least of all the
>> CRS units and pixel size). Alternatively, you could likely grab the
>> coordinate position of a pixel from within a QGIS project, but that doesn't
>> seem to be what you're after. Perhaps a developer familiar with the GDAL or
>> QGIS code bases can point you in the direction of some wizardry that will
>> achieve what it is you are looking for without a clearer understanding of
>> your use case though.
>>
>> [1] https://en.wikipedia.org/wiki/World_file
>>
>> On Mon, 31 Aug 2020 at 19:57, Miguel-Ángel Fas-Millán <
>> fas.mil...@gmail.com> wrote:
>>
>>> Hi all,
>>> New around here and as a QGIS user. I need to find something in the
>>> code, I hope you can help me.
>>> When you open a DSM and place the mouse on any pixel, you can see the
>>> coordinates of that point. Could someone tell me where in the code is made
>>> the calculation of those coordinates?
>>>
>>> Regards,
>>>
>>> Angel
>>>
>>> ___
>>> 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] Coordinates of a pixel

[Charles Dixon-Paver]

Someone can correct me if I'm wrong, but I think there's a misunderstanding
here of how this raster data is handled in a GIS. From my understanding of
the question, I don't know that what you're asking for is available "in the
code" the way you expect.

The coordinates are showing the position of the cursor relative to the
origin of the assigned coordinate reference system. The raster data is
"projected" onto that reference system, which assigns positions to some
points on the image and stretches, rotates or distorts the image in
accordance with the images affine parameters that ensure all the different
parts of the image remain spatially correct. How the GIS knows where to get
these parameters varies between data types and file formats.

Playing around with the georeferencer tool in QGIS should give you a pretty
clear understanding of how this "projection" works.

There are ways to get the coordinates of a position or pixel within an
image programmatically, the easiest of which that I can think of is using
values from a world file [1] with an xy position (in pixels) of the pixel
of interest. The code required for achieving this, however, is probably
going to be dependant on a wide variety of factors (not least of all the
CRS units and pixel size). Alternatively, you could likely grab the
coordinate position of a pixel from within a QGIS project, but that doesn't
seem to be what you're after. Perhaps a developer familiar with the GDAL or
QGIS code bases can point you in the direction of some wizardry that will
achieve what it is you are looking for without a clearer understanding of
your use case though.

[1] https://en.wikipedia.org/wiki/World_file

On Mon, 31 Aug 2020 at 19:57, Miguel-Ángel Fas-Millán 
wrote:

> Hi all,
> New around here and as a QGIS user. I need to find something in the
> code, I hope you can help me.
> When you open a DSM and place the mouse on any pixel, you can see the
> coordinates of that point. Could someone tell me where in the code is made
> the calculation of those coordinates?
>
> Regards,
>
> Angel
>
> ___
> 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] [Qgis-user] Informal online virtual meeting to hack - AKA QHackFriday

[Charles Dixon-Paver]

Hello all,

Please note that I will be running a session which goes through the
changelog management process as part of the QHackFriday tomorrow
(28/08/2020) . It is a great opportunity for those who wish to contribute
to the QGIS project but do not know where to begin. No special technical
knowledge is required in order to become a part of the changelog
maintenance team.

More info on the (informal) agenda and topics we will cover is available on
the wiki at:
https://github.com/qgis/QGIS/wiki/QHF-August-2020


You may register as a participant on the wiki, or join us by simply
connecting to https://meet.jit.si/QHackFriday at 12h00 UTC.

Looking forward to seeing everyone there.

Regards

On Thu, 27 Aug 2020 at 15:24, Jeff McKenna 
wrote:

> Note that tomorrow's QHackFriday event page is:
> https://github.com/qgis/QGIS/wiki/QHF-August-2020
>
> (it took some clicking to find it)
>
> -jeff
>
>
>
>
> --
> Jeff McKenna
> MapServer Consulting and Training Services
> co-founder of FOSS4G
> http://gatewaygeo.com/
>
>
>
>
> On 2020-08-21 2:49 p.m., Marco Bernasocchi wrote:
> > Dear Community,
> >
> >
> > 2020, as we all know, has been a special year and among plenty other
> > issues we had to cancel all our beloved hackfests. Since we first
> > started holding bi-annual hackfests in 2009, it will be the first time
> > without an event where our friendly community can meet.
> >
> >
> >
> > That can’t be! We are a modern and thriving community based on exchange,
> > discussion and collaboration and should foster this even when physical
> > meetings are not possible.
> >
> >
> > I’m super excited to announce that after some very motivating
> > discussions on the HackFest telegram channel [2] and in the PSC,
> > starting from next week on every last Friday of each monthwe will hold
> > an informal online virtual meeting to hack around, document, discuss and
> > in general meet the awesome QGIS community.
> >
> >
> > There will normally be no formal agenda, no fixed schedule nor
> > moderators, simply join the QHackFriday(pronounced KwakFriday) on jitsi
> > [0] and say hi!
> >
> >
> > I added a page to the wiki [1], so if you have topics that you like to
> > discuss/present you can put them there and others might join you.
> >
> >
> > Stay safe and see you next Friday!
> >
> >
> >
> > [0] https://meet.jit.si/QHackFriday
> >
> > [1] https://github.com/qgis/QGIS/wiki/QHackFriday
> >
> > [2] https://t.me/joinchat/Aq2V5RPoxYYhXqUPoxRWPQ
> >
> > Picture 1: https://www.umwelt.uni-hannover.de/qgis.html
> > 
> >
> > Picture 2: https://qgis2015.wordpress.com <
> https://qgis2015.wordpress.com/>
> >
> >
> >
> > --
> > Marco Bernasocchi
> >
> > QGIS.org Chair
> > OPENGIS.ch CEO
> > http://berna.io 
>
> ___
> 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] How to setup Visual Studio 2019 environment for QGIS C++ development?

[Charles Dixon-Paver]

If you are wanting to use Linux functionality directly within Windows 10,
Microsoft has introduced Windows Subsystem for Linux. If you're having
trouble with Visual Studio but want to stick with Windows it's perhaps a
feasible solution.

https://docs.microsoft.com/en-us/windows/wsl/about

Regards

On Wed, 5 Aug 2020 at 01:50, BELGACEM NEDJIMA  wrote:

> Hi,
> Here is some explanation about making .sln files for QGIS project.
> QGIS uses CMake to generate the .sln file. Ideally in a simple CMake
> project you run CMake where the CMakeFiles.txt is located (usually at the
> root of the source tree) and provide paths to the external libraries you
> use the you generate .sln files and build the project normally but since
> QGIS uses a lots of libraries some of them don't support Visual Studio well
> and you end up having some really complicated error messages.
> About 3 months ago I tried to use visual studio 2019 and changed
> somethings in the build script. I managed to generate solution files but
> QGIS couldn't compile. I ended up having to switch to linux.
> I hope you find a solution soon.
>
>
> On Tue, Aug 4, 2020, 10:48 PM  wrote:
>
>> Hi Ismail and thank you for your link to the pull request.
>> Currently that PR has not been accepted, because of some checks not being
>> successful.
>>
>> I do not really know exactly what that pull request is trying to do (but
>> as many as 42 files seem to be involved in the PR) but as far as I can see
>> it does not include a ".sln" file (Visual Studio solution file) nor any
>> ".vcxproj" files (Visual C++ project files) nor a file "packages.config"
>> (for NuGet managed libraries).
>>
>> I think I read somewhere here in the QGIS developer list archive that
>> someone estimated that 90% percent of the QGIS developers are using Linux.
>> If that is true then I believe the reason might be that Windows
>> developers (which are used to NuGet and Visual Studio solutions files and
>> project files) may choose to give up when they feel it seems difficult to
>> even get started with the development environment for QGIS with Windows.
>>
>> Can anyone answer this question:
>> Would it, for some reason, be impossible to provide a Visual Studio
>> solution file (and .vcxproj files) that can simply be opened, and then the
>> required dependencies would be retrieved automatically with NuGet
>> (according to NuGet references in the ".vcxproj" files or
>> "packages.config") ?
>> One obvious reason could be that there may be some required libraries
>> which are not available through NuGet but those kind of files therefore
>> really will need a manual installation.
>> But I mean is it possible to provide easy instructions with only very FEW
>> manual installations for Windows, and then the majority of the dependencies
>> would be retrieved through NuGet when you open a Visual Studio solution
>> file which hopefully would be available from the github repository?
>>
>> The only kind of libraries I myself have used with NuGet is .NET
>> libraries but as far as I understand, NuGet can also be used for native C++
>> libraries:
>> https://devblogs.microsoft.com/nuget/native-support/
>>
>> I believe that the QGIS project would get more contributors if you can
>> provide a development environment that are EASY to GET STARTED WITH for
>> potential newcomers using Windows Visual Studio.
>>
>>   -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
>>
>>
>> Sent: Tuesday, August 04, 2020 at 12:22 AM
>> From: "Ismail Sunni" 
>> To: tom...@gmx.com
>> Cc: "QGIS Developer List" 
>> Subject: Re: [QGIS-Developer] How to setup Visual Studio 2019 environment
>> for QGIS C++ development?
>>
>> Hi Tomjan,
>>
>> Perhaps you want to see this PR https://github.com/qgis/QGIS/pull/38102
>> for your question.
>>  Best regards
>>
>>
>> On Mon, Aug 3, 2020, 23:44 mailto:tom...@gmx.com]> wrote:
>>
>> I would be interested in learning to contribute to QGIS.
>> My previous C++ experience is that about 20 years ago I did some (for a
>> couple of years) Visual C++ programming with Microsoft's MFC as the GUI.
>> Now I think I could refresh my C++ skills and also learn QT which I have
>> never programmed with so far.
>>
>> However, I am not a Linux user, but always have been using Windows
>> (currently Windows 10).
>> It seems to be a complicated obstacle to get started running QGIS through
>> Visual Studio 2019.
>>
>> I think it would be great with a tutorial (webpage or youtube video
>> tutorial) about how to get started with an example showing how to do all
>> necessary installations/configurations/setup until you can compile and run
>> QGIS with a breakpoint in Visual Studio 2019.
>>
>> I have seen that the "INSTALL" file in the repository refers to Visual
>> Studio 2015, but it seems awkward if it really would be necessary to use
>> such an ancient version?
>> Is nobody of the QGIS developers using Visual Studio 2019?
>>  ___
>> QGIS-Developer mailing list
>> 

Re: [QGIS-Developer] Updates to the way changelog entries are managed

[Charles Dixon-Paver]

Hi Everyone,

As Tim has mentioned I will be maintaining the changelog content going
forward and we have made some modifications to the workflow.

If anybody has any further questions, if you are not entirely sure how
these changes have been implemented or would like me to step through the
process with you, feel free to reach out and I will be happy to assist
wherever I can.

Additional help from volunteers would be appreciated and I would love to
discuss the development of some sort of QA procedure to ensure that we
produce the best quality content possible.

Regards

On Mon, 6 Jul 2020 at 11:29, Tim Sutton  wrote:

> Hi QGIS Devs and PSC
>
> I just wanted to update you on some improvements we are making to the way
> the changelog is managed. As you know each release it is a bit of a chore
> getting the changelog into shape and out in a timely fashion. Most of the
> delays come in the post-editing of content, trying to make the PR text
> clear and understandable and consistent. Kartoza recently hired Charles (in
> CC) as a resident GIS geek and I have tasked him to maintain the Changelog
> as part of his open source contribution. What I have set up is this:
>
>
> 1) I have Charles (GitHub user: zacharlie) to the ‘Community’ GitHub group
> which has triage rights
>
> 2) Tasked Charles to read each PR that has a ‘Feature’ label as it comes
> in and in the comments section, nudge the author if the description is not
> clear / well described. Would be grateful if the PR gatekeepers could hold
> back on merging Feature PR’s that have issues, do not have a Changelog tag
> applied. Note that the English doesn’t need to be perfect (we are
> understanding  that English may not be your mother toungue), the important
> thing is that the functionality is well described - we will tidy up the
> English in step 6 below.
>
> 3) Once the PR description is good, Charles will add the ‘Changelog’ tag
> to it.
>
> 4) Once the PR is merged, we will regularly Harvest the ‘Changelog tagged
> entries to the Changelog site.
>
> 5)  We have added an additional tag on GitHub called ‘ChangelogHarvested’
> which will be applied after and entry is harvested, and the Changelog tag
> then removed (and should bot be readied to avoid duplicates being pulled
> in).
>
> 6) The entry will then be tidied up on the changelog site ready for the
> release. Additional volunteers (e.g. Toto, Frank) who have helped in the
> past are warmly invited to help improve the clarity and consistency of the
> entries on the changelog site.
>
> 7) When the release comes near we just need the paid bug fixing entries
> added (usually managed by Andreas Neumann) and then Richard can pull the
> changelog to the QGIS web site.
>
>
> I have started the Changelog for 3.16 here:
> https://changelog.qgis.org/en/qgis/version/3.16/
>
>
> I hope that works for everyone, and that we get smoother changelog
> production in the future!
>
> Regards
>
> Tim
>
>
>
> —
>
>
>
>
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Honorary PSC Member and 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: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Changelog Maintainer

[Charles Dixon-Paver]

I have changed those tags Tim identified from h2 to h3... apologies for the
miss.

Regarding the misrendering of code blocks, I found that the content site
and the published page have significant differences in the way they handle
the CSS etc so it's hard to know how it'll turn out in the end. I'll chat
to Tim about making some changes and maybe we can make a plan to prevent
these issues cropping up in the future.

On Wed, 1 Jul 2020 at 16:04, Tim Sutton  wrote:

> Hi Richard
>
>
>
>
> On 1 Jul 2020, at 14:52, Richard Duivenvoorde  wrote:
>
> On 7/1/20 9:22 AM, Charles Dixon-Paver wrote:
>
> Hello everyone, Charlie here.
>
> As Tim mentioned I am a new set of hands working with Katoza and will be
> reviewing the changelog content going forward.
>
> I have been through the content for the 3.14 release and it should be good
> to go @Richard.
>
> I also wanted to take a moment and give a tip of the hat to all of you
> who have been involved with bringing a project like this to life. I believe
> there are countless others like me who never found/ made the time to be
> involved or took the opportunity to thank everybody for their contributions
> to something that provides a tremendous amount of value to such a large
> community of users.
>
>
> Hi Charles,
>
> THANKS!
>
> See: https://www.qgis.org/en/site/forusers/visualchangelog314/index.html
> Note: only english build for now, next full build this evening.
>
> This went very smoothly, only hickups was about some codeblock which ended
> up in one line.
>
> @All: please have a look and fix stuff (via github/rst) now or let me know.
>
>
> Oh I found two small little things:
>
>
>- Rendering principle
>
> <https://www.qgis.org/en/site/forusers/visualchangelog314/index.html#rendering-principle>
>- Static dataset
>
> <https://www.qgis.org/en/site/forusers/visualchangelog314/index.html#static-dataset>
>
> @Charles can you look at the mesh entry and change the markdown for those
> so they dont appear as heading 1 and thus category entries in the rendered
> HTML?
>
>
> If there are no objections, I will push the texts to Transifex later, so
> people can translate.
>
> One other remark: though VERY nice, the animated gifs become bigger and
> bigger every time:
>
> It's now 67Mb for 3.14 ( which is indeed packed with features :-) )
>
>
> This is one of the longest changelings we every had, and as more people
> participate by adding screencasts I guess this is going to be a natural
> side effect….we can think on how to reduce it in future  - maybe generate
> thumbs always and require a click to see the animated GIF’s
>
> Thanks so much Richard, Charles and all others who contributed to the
> changelog (and of course the devs who made the actual features :-P and the
> poor translators who will spend their time translating this).
>
> Regards
>
> Tim
>
>
>
> $ du -hs vis* | sort -rn
> 67M visualchangelog314
> 37M visualchangelog38
> 35M visualchangelog34
> 32M visualchangelog216
> 28M visualchangelog310
> 23M visualchangelog312
> 19M visualchangelog30
> 13M visualchangelog220
> 13M visualchangelog212
> 12M visualchangelog200
> 5.8M visualchangelog260
> 4.0M visualchangelog210
> 3.8M visualchangelog218
> 3.6M visualchangelog36
> 3.0M visualchangelog240
> 3.0M visualchangelog214
> 2.7M visualchangelog28
> 1.8M visualchangelog32
>
> Thanks to all!
>
> Regards,
>
> Richard Duivenvoorde
>
>
> —
>
>
>
>
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Honorary PSC Member and 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
> <https://calendly.com/timlinux/30min> to make finding time easy.
>
>
___
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