Re: [QGIS-Developer] QGIS Server 3 status

[René-Luc Dhont]

Hi Devs,

Here is a new feature for embbeding QGIS Server in Python application!
https://github.com/qgis/QGIS/pull/5408

Etienne, you can probably used it in GeoNodes to dynamically build Web 
Services.


Regards,
René-Luc

Le 03/10/2017 à 10:09, Etienne Trimaille a écrit :

Hi devs,

We would like to start testing QGIS Server 3: OGC services and Python 
plugins.


I think I read that the QGIS Server refactoring was finished and it 
seems that most of OGC tests are working: 
http://37.187.164.233/ogc/latest_wms_1_3_0.html


Is it possible to have the status of QGIS Server 3?
Are there some major known issues? Are Python plugins fully supported? 
Can we start porting plugins to the QGIS 3 Server API? Is there some 
highlights to know for Python plugins?


Thanks for the all the work which has been done!

Regards,
Etienne



___
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 Server 3 status

[Anita Graser]

On Wed, Oct 18, 2017 at 8:38 AM, Anita Graser  wrote:

>
>
> On Tue, Oct 17, 2017 at 10:59 PM, Tim Sutton  wrote:
>
>> Hi Anita
>>
>> Are you going to put it on the QGIS blog? Could you share the draft then
>> it is on WP so I can make some edits?
>>
>
> S
> ​ure, I'll do that in the evening.
>

​Done!

Feel free to hit publish once you've checked it Tim!

Regards,
Anita
___
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 Server 3 status

[Richard Duivenvoorde]

On 18-10-17 11:13, Richard Duivenvoorde wrote:
> I think it is maybe best if we create a (translatable) rst page into the
> web page with some more information about the tests, and add a link
> there to the test.qgis.org site (and maybe to the 'latest').

Ok, done

https://github.com/qgis/QGIS-Website/commit/4aa5654e75e32a755a857c09bf2140d4024aec37

later see:

http://qgis.org/en/site/getinvolved/tests.html

please add text or more tests

Regards,

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

Re: [QGIS-Developer] QGIS Server 3 status

[Richard Duivenvoorde]

On 18-10-17 09:22, Régis Haubourg wrote:
> Hi, 
> in fact it is test.qgis.org  with no "s". My bad,
> sorry.  

I added an ServerAlias now: so test and tests should work

> Richard, what do you think of our proposal to add a subdirectory like
> "http://test.qgis.org/ogc_cite; ? In case we get one day other reports
> like performance benchmark, that would avoid to have to move it afterwards. 

Done, and renamed all html's to the naming convention

@Paul: so you will scp them into the right dir yes?

I think it is maybe best if we create a (translatable) rst page into the
web page with some more information about the tests, and add a link
there to the test.qgis.org site (and maybe to the 'latest').

I'll also try to add the travis and docker build widgets in it.
Anything else we have on Continues testing?
@Juergen: do we have a page for debian/windows builds?

> Tim, I'd be please to help you build the huge changelog. Did you create
> a projecta instance for qgis 3.0 already?

See: http://changelog.qgis.org/en/qgis/version/3.0.0/ for work in progress

Regards,

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

Re: [QGIS-Developer] QGIS Server 3 status

[Yves Jacolin]

Le mercredi 18 octobre 2017, 09:22:51 CEST Régis Haubourg a écrit :
> Richard, what do you think of our proposal to add a subdirectory like "
> http://test.qgis.org/ogc_cite; ? In case we get one day other reports like
> performance benchmark, that would avoid to have to move it afterwards.

Régis, All,

We are late but we are still working on the HTML report in QGIS Benchmark (a 
first work a little buggy is already in the source code). Currently the 
benchmark runs on our own server but we other GeoMapfish applications (demo, 
test) so it is not a perfect benchmark as you can't really compare with older 
benchmark (who knows if new applications has been deploied on the server?).

Patrick will take care of the final work next week. I should be able to test 
the week after.

Y.

signature.asc
Description: This is a digitally signed message part.
___
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 Server 3 status

[Tom Chadwin]

I'd be very happy to help out with proofing the changelog - I don't think I
know enough to help write it in the first place, but I'll happily fix some
typos.

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
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

Re: [QGIS-Developer] QGIS Server 3 status

[Régis Haubourg]

Hi,
in fact it is test.qgis.org with no "s". My bad, sorry.

Richard, what do you think of our proposal to add a subdirectory like "
http://test.qgis.org/ogc_cite; ? In case we get one day other reports like
performance benchmark, that would avoid to have to move it afterwards.

Tim, I'd be please to help you build the huge changelog. Did you create a
projecta instance for qgis 3.0 already?

Cheers,
Régis


2017-10-17 23:30 GMT+02:00 Nyall Dawson :

> On 18 October 2017 at 06:36, Anita Graser  wrote:
>
> Nice work Anita!
>
> > - Build a OGC compliancy platform and integrate it to a continuous
> > integration platform. Conformity reports are now pushed to
> tests.qgis.org
>
> For me tests.qgis.org just redirects to the homepage. Is this link
> correct?
>
> Nyall
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Server 3 status

[G. Allegri]

I will take part to the testing in the next days. i will ask my collegues
at Gis3W to test it too, having a quite complex application (G3WSuite)
built on QGIS Server 2.x

giovanni


Mail
priva di virus. www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2017-10-18 8:38 GMT+02:00 Anita Graser :

>
>
> On Tue, Oct 17, 2017 at 10:59 PM, Tim Sutton  wrote:
>
>> Hi Anita
>>
>> Are you going to put it on the QGIS blog? Could you share the draft then
>> it is on WP so I can make some edits?
>>
>
> S
> ​ure, I'll do that in the evening.
>
> Regards,
> Anita​
>
> ___
> 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 Server 3 status

[Anita Graser]

On Tue, Oct 17, 2017 at 10:59 PM, Tim Sutton  wrote:

> Hi Anita
>
> Are you going to put it on the QGIS blog? Could you share the draft then
> it is on WP so I can make some edits?
>

S
​ure, I'll do that in the evening.

Regards,
Anita​
___
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 Server 3 status

[Luca Manganelli]

On Tue, Oct 17, 2017 at 10:36 PM, Anita Graser  wrote:

> - Remove all singleton calls
>
>
>
​what are singleton calls? (could be explained in the web page, too) :-)​
___
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 Server 3 status

[Andreas Neumann]

Hi Anita,

Maybe you could add a section about "testing wanted / needed" at the end 
of the blog post?


I think after such a lot of refactoring, users can expect 
incompatibilities with the previous 2x version. Thats why a call for 
testing should be included. Otherwise existing QGIS server users maybe 
just upgrade without noticing and run into issues.


We just recently came across an incompatibility in the 
GetProjectSettings command where the new version behaves differently 
than the old version regarding the visibility state of groups - issue 
report still pending. Issue was discovered by Eric Lemoine (Camptocamp).


Greetings,

Andreas


On 17.10.2017 22:36, Anita Graser wrote:
I've extended Régis' draft with some of the more recent information. 
Please let me know what you think. I'll try to publish in a couple of 
days.


-- start --
*
*
*QGIS server refactoring is done!
*
As you may know, QGIS is jumping to a new major version (yes!). Doing 
so was made necessary because of the need to switch to python 3, QT5, 
but also because we needed to break the QGIS API in several places. 
(http://blog.qgis.org/2016/02/10/qgis-3-0-plans/ 
)


A year ago, a tiny troll 
from switzerland rang a 
bell about the strong need for love server code base required. Indeed, 
the API was locked by some old methods of QGIS server. In short, QGIS 
server was reparsing the qgs project file in his own way, and created 
dependencies to part of QGIS we needed to drop.


As outsourcing the server code base was not an option, so we had to 
refactor it. The involved parties decided to get engaged in a code 
sprint 
 in 
the city of Lyon , France dedicated to sharing their vision, planning 
the work and finally making all the following 
 happen:


*Higher level refactoring*

All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, 
GetPrint etc..) have been rewritten. Some like WMS were entirely 
rewritten. Kudos to the devs!


*New features*

- Multi-thread rendering  like 
in the desktop


- A new option to trust layer metadata 
 and thus speed up project loading


- WFS 1.1 support https://github.com/qgis/QGIS/pull/5297 



- Full Python bindings for the server API

- Server Services as plugins like providers


*Deep, complex and unrewarding tasks
*

- Remove all singleton calls

- Cut all the dependencies to the old QGIS project file parser

- Minimize dependencies to GUI library. Since fonts are necessary to 
render maps, totally removing them was not feasable.


*Infrastructure tasks*

- Build a OGC compliancy platform 
 and 
integrate it to a continuous integration platform. Conformity reports 
are now pushed to tests.qgis.org 

/
/
- Add unit tests ... and again more unit tests

- Stress QGIS server against security leaks 
 (SQL 
injections and other malicious attacks)


- Start profiling and bench marking performances. This work still need 
some love - and funding - to be achieved



A presentation 
 was 
given at FOSS4G-EU in July.


*Congratulations* to the developers who worked hard on that work.

Now this deserves to be well tested, please report back any issues!


___
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 Server 3 status

[Tim Sutton]

Hi



> On 17 Oct 2017, at 23:30, Nyall Dawson  wrote:
> 
> On 18 October 2017 at 06:36, Anita Graser  wrote:
> 
> Nice work Anita!
> 
>> - Build a OGC compliancy platform and integrate it to a continuous
>> integration platform. Conformity reports are now pushed to tests.qgis.org
> 
> For me tests.qgis.org just redirects to the homepage. Is this link correct?
> 


That must have broken today / yesterday as we were looking at the test page at 
our PSC meeting on monday night - Richard do you know what is going on? I 
redirects for me too….

Regards

Tim

> 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

—






Tim Sutton

Co-founder: Kartoza
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

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

Re: [QGIS-Developer] QGIS Server 3 status

[Nyall Dawson]

On 18 October 2017 at 06:36, Anita Graser  wrote:

Nice work Anita!

> - Build a OGC compliancy platform and integrate it to a continuous
> integration platform. Conformity reports are now pushed to tests.qgis.org

For me tests.qgis.org just redirects to the homepage. Is this link correct?

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

Re: [QGIS-Developer] QGIS Server 3 status

[Régis Haubourg]

Hi Anita,
 since today, qgis server reaches OGC compliancy for wms 1.3.0 on basic and
queryable levels. We have a blog post ready for that. There are 5 tests
missing for a full compliancy and we are just trying to evaluate how much
work this is.
We already could start a certification process in the current state, but I
guess a full compliancy would be a much better message to the world .
Anyway posting right now seems a good idea! We need more folks testing the
beast.
Régis

Le 17 oct. 2017 22:36, "Anita Graser"  a écrit :

> I've extended Régis' draft with some of the more recent information.
> Please let me know what you think. I'll try to publish in a couple of days.
>
> -- start --
>
>
> *QGIS server refactoring is done!*
> As you may know, QGIS is jumping to a new major version (yes!). Doing so
> was made necessary because of the need to switch to python 3, QT5, but also
> because we needed to break the QGIS API in several places. (
> http://blog.qgis.org/2016/02/10/qgis-3-0-plans/)
>
> A year ago, a tiny troll  from
> switzerland rang a bell about the strong need for love server code base
> required. Indeed, the API was locked by some old methods of QGIS server.
> In short, QGIS server was reparsing the qgs project file in his own way,
> and created dependencies to part of QGIS we needed to drop.
>
> As outsourcing the server code base was not an option, so we had to
> refactor it. The involved parties decided to get engaged in a code sprint
>  in
> the city of Lyon , France dedicated to sharing their vision, planning the
> work and finally making all the following
>  happen:
>
> *Higher level refactoring*
>
> All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint
> etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to
> the devs!
>
> *New features*
>
> - Multi-thread rendering  like in
> the desktop
>
> - A new option to trust layer metadata
>  and thus speed up project loading
>
> - WFS 1.1 support https://github.com/qgis/QGIS/pull/5297
>
> - Full Python bindings for the server API
>
> - Server Services as plugins like providers
>
>
>
> *Deep, complex and unrewarding tasks*
>
> - Remove all singleton calls
>
> - Cut all the dependencies to the old QGIS project file parser
>
> - Minimize dependencies to GUI library. Since fonts are necessary to
> render maps, totally removing them was not feasable.
>
> *Infrastructure tasks*
>
> - Build a OGC compliancy platform
>  
> and
> integrate it to a continuous integration platform. Conformity reports are
> now pushed to tests.qgis.org
>
> - Add unit tests ... and again more unit tests
>
> - Stress QGIS server against security leaks
>  (SQL
> injections and other malicious attacks)
>
> - Start profiling and bench marking performances. This work still need
> some love - and funding - to be achieved
>
>
> A presentation
> 
>  was
> given at FOSS4G-EU in July.
>
> *Congratulations* to the developers who worked hard on that work.
>
> Now this deserves to be well tested, please report back any issues!
>
___
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 Server 3 status

[Tim Sutton]

Hi Anita

Are you going to put it on the QGIS blog? Could you share the draft then it is 
on WP so I can make some edits?

For now I also put your text as a placeholder in the changelog for 3.0 here

changelog.qgis.org/en/qgis/version/3.0.0/#qgis-server-overhaul 


By the way I’d love it if non-coders (and of course coders also welcome) out 
there who are looking for a way to contribute to QGIS could contact me and help 
to write up the changelog for 3.0….Its going to be a massive job since our 
developer community have been rather busy adding lots of new features and 
tweaks in QGIS 3.0!

Regards

Tim

> On 17 Oct 2017, at 22:36, Anita Graser  wrote:
> 
> I've extended Régis' draft with some of the more recent information. Please 
> let me know what you think. I'll try to publish in a couple of days.
> 
> -- start --
> 
> QGIS server refactoring is done!
> 
> As you may know, QGIS is jumping to a new major version (yes!). Doing so was 
> made necessary because of the need to switch to python 3, QT5, but also 
> because we needed to break the QGIS API in several places. 
> (http://blog.qgis.org/2016/02/10/qgis-3-0-plans/ 
> ) 
> 
> A year ago, a tiny troll  from 
> switzerland rang a bell about the strong need for love server code base 
> required. Indeed, the API was locked by some old methods of QGIS server. In 
> short, QGIS server was reparsing the qgs project file in his own way, and 
> created dependencies to part of QGIS we needed to drop.
>
> As outsourcing the server code base was not an option, so we had to refactor 
> it. The involved parties decided to get engaged in a code sprint 
>  in 
> the city of Lyon , France dedicated to sharing their vision, planning the 
> work and finally making all the following 
>  happen:
> 
> Higher level refactoring
> 
> All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint 
> etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to 
> the devs!
> 
> New features
> 
> - Multi-thread rendering  like in the 
> desktop
> 
> - A new option to trust layer metadata 
>  and thus speed up project loading
> 
> - WFS 1.1 support https://github.com/qgis/QGIS/pull/5297 
>  
> 
> - Full Python bindings for the server API
> 
> - Server Services as plugins like providers
> 
> 
> Deep, complex and unrewarding tasks
> 
> - Remove all singleton calls
> 
> - Cut all the dependencies to the old QGIS project file parser
> 
> - Minimize dependencies to GUI library. Since fonts are necessary to render 
> maps, totally removing them was not feasable. 
> 
> Infrastructure tasks
> 
> - Build a OGC compliancy platform 
>  
> and integrate it to a continuous integration platform. Conformity reports are 
> now pushed to tests.qgis.org  
> 
> - Add unit tests ... and again more unit tests
> 
> - Stress QGIS server against security leaks 
>  (SQL 
> injections and other malicious attacks)
> 
> - Start profiling and bench marking performances. This work still need some 
> love - and funding - to be achieved
> 
> 
> A presentation 
> 
>  was given at FOSS4G-EU in July. 
> 
> Congratulations to the developers who worked hard on that work. 
> 
> Now this deserves to be well tested, please report back any issues!
> ___
> 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 Server 3 status

[Anita Graser]

I've extended Régis' draft with some of the more recent information. Please
let me know what you think. I'll try to publish in a couple of days.

-- start --


*QGIS server refactoring is done!*
As you may know, QGIS is jumping to a new major version (yes!). Doing so
was made necessary because of the need to switch to python 3, QT5, but also
because we needed to break the QGIS API in several places. (
http://blog.qgis.org/2016/02/10/qgis-3-0-plans/)

A year ago, a tiny troll  from
switzerland rang a bell about the strong need for love server code base
required. Indeed, the API was locked by some old methods of QGIS server. In
short, QGIS server was reparsing the qgs project file in his own way, and
created dependencies to part of QGIS we needed to drop.

As outsourcing the server code base was not an option, so we had to
refactor it. The involved parties decided to get engaged in a code sprint
 in
the city of Lyon , France dedicated to sharing their vision, planning the
work and finally making all the following
 happen:

*Higher level refactoring*

All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint
etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to
the devs!

*New features*

- Multi-thread rendering  like in
the desktop

- A new option to trust layer metadata
 and thus speed up project loading

- WFS 1.1 support https://github.com/qgis/QGIS/pull/5297

- Full Python bindings for the server API

- Server Services as plugins like providers



*Deep, complex and unrewarding tasks*

- Remove all singleton calls

- Cut all the dependencies to the old QGIS project file parser

- Minimize dependencies to GUI library. Since fonts are necessary to render
maps, totally removing them was not feasable.

*Infrastructure tasks*

- Build a OGC compliancy platform

and
integrate it to a continuous integration platform. Conformity reports are
now pushed to tests.qgis.org

- Add unit tests ... and again more unit tests

- Stress QGIS server against security leaks
 (SQL
injections and other malicious attacks)

- Start profiling and bench marking performances. This work still need some
love - and funding - to be achieved


A presentation

was
given at FOSS4G-EU in July.

*Congratulations* to the developers who worked hard on that work.

Now this deserves to be well tested, please report back any issues!
___
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 Server 3 status

[René-Luc Dhont]

And I'm waiting to add WFS 1.1.0 support:
https://github.com/qgis/QGIS/pull/5297

Regards,
René-Luc

Le 13/10/2017 à 08:58, Régis Haubourg a écrit :

Hi Anita,

among the news, Paul is currently tackling OGC conformity issues.
see :
https://github.com/qgis/QGIS/pull/5044
https://github.com/qgis/QGIS/pull/5084
https://github.com/qgis/QGIS/pull/5145
https://github.com/qgis/QGIS/pull/5150
https://github.com/qgis/QGIS/pull/5157
https://github.com/qgis/QGIS/pull/5303

We still have some harder issues due to crashes of the OGC testing 
platform.


All tests are made using the "basic" level test (see 
http://cite.opengeospatial.org/teamengine/about/wms/1.3.0/site/)


When all will be green at this level, we'll run the platform with the 
other testing levels so that we have a good overview of our path for a 
full conformity of WMS 1.3.


We'll prepare a dedicated blog post toi describe what were the issues 
and what we did to fix them.


Cheers!
Régis

2017-10-12 22:56 GMT+02:00 Anita Graser >:


Thanks everyone so far! Please keep the info coming. I'll draft a
blog post on the weekend.

Regards,
Anita

On Thu, Oct 5, 2017 at 9:34 AM, Alessandro Pasotti
> wrote:

Hi Règis,

thanks for the nice summary!

Maybe it would be interesting for python devs to stress out
how QGIS server 3 brings the bindings and the plugins to a new
level: while the original filter-style python plugins, are
still available, the new service-oriented plugin-based
architecture allows Python developers to create new services
(for example WPS) by implementing a new `QgsService` directly
in Python. Overriding existing services is also possible.

The server API has now full python bindings and a QGIS server
can be easily implemented directly in Python and wrapped into
your favourite framework (see this simple wsgi experiment:
https://gist.github.com/elpaso/0cd7fb6a0518dc46c45557d9133438b8

).

For more examples of the API, I think there are some basic
examples in the official Python tests:

https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsserver_services.py#L79





Cheers





On Wed, Oct 4, 2017 at 10:49 PM, Régis Haubourg
>
wrote:

Well, from a user point of view, that's a bit hard since
all this is 90 % refactoring.. which is supposed to be
transparent for users.

We have the trust and multithreaded features, that should
(and early testers today found it slower today) and the
ability to code new services using python.
We can also show some numbers about OGC conformity tests
and the goal of reaching OGC certification (WMS only by now).

Alessandro, René-Luc and David, do you have some user
oriented examples for the new modular API ?



2017-10-04 22:18 GMT+02:00 Anita Graser
>:

Great overview, thanks for drafting Régis!

Some additional ideas: Could we add a section with the
key improvements from an user perspective?

I'm particularly intrigued by the services / plugins
part. Could you elaborate?

Regards,
Anita



On Wed, Oct 4, 2017 at 9:42 PM, Régis Haubourg
> wrote:

Hi again,
here is my very first draft:

 Several images can be pulled from the joined
slides given at Foss4G-EU here

https://drive.google.com/file/d/0BzatQbprJ-hjWF95VzdHbGRsVEk/view?usp=sharing




René-Luc, David, Paul, don't hesitate to amend that!




*Qgis server refactoring is done!
*
As you may know, QGIS is jumping to a new major
version (yes!).
Doing so was made necessary because of the need to
switch to python 3, QT5, but also because we
needed to break the QGIS API in several places.

A year ago, a tiny troll

Re: [QGIS-Developer] QGIS Server 3 status

[Régis Haubourg]

Hi Anita,

among the news, Paul is currently tackling OGC conformity issues.
see :
https://github.com/qgis/QGIS/pull/5044
https://github.com/qgis/QGIS/pull/5084
https://github.com/qgis/QGIS/pull/5145
https://github.com/qgis/QGIS/pull/5150
https://github.com/qgis/QGIS/pull/5157
https://github.com/qgis/QGIS/pull/5303

We still have some harder issues due to crashes of the OGC testing
platform.

All tests are made using the "basic" level test (see
http://cite.opengeospatial.org/teamengine/about/wms/1.3.0/site/)

When all will be green at this level, we'll run the platform with the other
testing levels so that we have a good overview of our path for a full
conformity of WMS 1.3.

We'll prepare a dedicated blog post toi describe what were the issues and
what we did to fix them.

Cheers!
Régis

2017-10-12 22:56 GMT+02:00 Anita Graser :

> Thanks everyone so far! Please keep the info coming. I'll draft a blog
> post on the weekend.
>
> Regards,
> Anita
>
> On Thu, Oct 5, 2017 at 9:34 AM, Alessandro Pasotti 
> wrote:
>
>> Hi Règis,
>>
>> thanks for the nice summary!
>>
>> Maybe it would be interesting for python devs to stress out how QGIS
>> server 3 brings the bindings and the plugins to a new level: while the
>> original filter-style python plugins, are still available, the new
>> service-oriented plugin-based architecture allows Python developers to
>> create new services (for example WPS) by implementing a new `QgsService`
>> directly in Python. Overriding existing services is also possible.
>>
>> The server API has now full python bindings and a QGIS server can be
>> easily implemented directly in Python and wrapped into your favourite
>> framework (see this simple wsgi experiment:
>> https://gist.github.com/elpaso/0cd7fb6a0518dc46c45557d9133438b8 ).
>>
>> For more examples of the API, I think there are some basic examples in
>> the official Python tests: https://github.com/qgis/QGIS/b
>> lob/master/tests/src/python/test_qgsserver_services.py#L79
>>
>>
>> Cheers
>>
>>
>>
>>
>>
>> On Wed, Oct 4, 2017 at 10:49 PM, Régis Haubourg > > wrote:
>>
>>> Well, from a user point of view, that's a bit hard since all this is 90
>>> % refactoring.. which is supposed to be transparent for users.
>>>
>>> We have the trust and multithreaded features, that should (and early
>>> testers today found it slower today) and the ability to code new services
>>> using python.
>>> We can also show some numbers about OGC conformity tests and the goal of
>>> reaching OGC certification (WMS only by now).
>>>
>>> Alessandro, René-Luc and David, do you have some user oriented examples
>>> for the new modular API ?
>>>
>>>
>>>
>>> 2017-10-04 22:18 GMT+02:00 Anita Graser :
>>>
 Great overview, thanks for drafting Régis!

 Some additional ideas: Could we add a section with the key improvements
 from an user perspective?

 I'm particularly intrigued by the services / plugins part. Could you
 elaborate?

 Regards,
 Anita



 On Wed, Oct 4, 2017 at 9:42 PM, Régis Haubourg <
 regis.haubo...@gmail.com> wrote:

> Hi again,
> here is my very first draft:
>
>  Several images can be pulled from the joined slides given at
> Foss4G-EU here https://drive.google.com/file/
> d/0BzatQbprJ-hjWF95VzdHbGRsVEk/view?usp=sharing
>
> René-Luc, David, Paul, don't hesitate to amend that!
>
> 
> 
>
>
> *Qgis server refactoring is done!*
> As you may know, QGIS is jumping to a new major version (yes!).
> Doing so was made necessary because of the need to switch to python 3,
> QT5, but also because we needed to break the QGIS API in several places.
>
> A year ago, a tiny troll
> from switzerland rang
> a bell about the strong need for love server code base required.
>
> Indeed, the API was locked by some old methods of QGIS server. In
> short, QGIS server was reparsing the qgs project file in his own way, and
> created dependencies to part of QGIS we needed to drop.
>
> As outsourcing the server code base was not an option, so we had to
> refactor it.
>
> The involved parties decided to get engaged in a code sprint
>  
> in
> the city of Lyon , France dedicated to sharing their vision, planning the
> work and finally making all the following
>  happen
> :
>
>
>
> *# Deep, complex and unrewarding tasks:*
>
> - Remove all singleton calls
>
> - Cut all the dependencies to the old qgis project parser
>
> - Minimize dependencies to GUI library. Since fonts are necessary to

Re: [QGIS-Developer] QGIS Server 3 status

[Anita Graser]

Thanks everyone so far! Please keep the info coming. I'll draft a blog post
on the weekend.

Regards,
Anita

On Thu, Oct 5, 2017 at 9:34 AM, Alessandro Pasotti 
wrote:

> Hi Règis,
>
> thanks for the nice summary!
>
> Maybe it would be interesting for python devs to stress out how QGIS
> server 3 brings the bindings and the plugins to a new level: while the
> original filter-style python plugins, are still available, the new
> service-oriented plugin-based architecture allows Python developers to
> create new services (for example WPS) by implementing a new `QgsService`
> directly in Python. Overriding existing services is also possible.
>
> The server API has now full python bindings and a QGIS server can be
> easily implemented directly in Python and wrapped into your favourite
> framework (see this simple wsgi experiment: https://gist.github.com/
> elpaso/0cd7fb6a0518dc46c45557d9133438b8 ).
>
> For more examples of the API, I think there are some basic examples in the
> official Python tests: https://github.com/qgis/QGIS/
> blob/master/tests/src/python/test_qgsserver_services.py#L79
>
>
> Cheers
>
>
>
>
>
> On Wed, Oct 4, 2017 at 10:49 PM, Régis Haubourg 
> wrote:
>
>> Well, from a user point of view, that's a bit hard since all this is 90 %
>> refactoring.. which is supposed to be transparent for users.
>>
>> We have the trust and multithreaded features, that should (and early
>> testers today found it slower today) and the ability to code new services
>> using python.
>> We can also show some numbers about OGC conformity tests and the goal of
>> reaching OGC certification (WMS only by now).
>>
>> Alessandro, René-Luc and David, do you have some user oriented examples
>> for the new modular API ?
>>
>>
>>
>> 2017-10-04 22:18 GMT+02:00 Anita Graser :
>>
>>> Great overview, thanks for drafting Régis!
>>>
>>> Some additional ideas: Could we add a section with the key improvements
>>> from an user perspective?
>>>
>>> I'm particularly intrigued by the services / plugins part. Could you
>>> elaborate?
>>>
>>> Regards,
>>> Anita
>>>
>>>
>>>
>>> On Wed, Oct 4, 2017 at 9:42 PM, Régis Haubourg >> > wrote:
>>>
 Hi again,
 here is my very first draft:

  Several images can be pulled from the joined slides given at Foss4G-EU
 here https://drive.google.com/file/d/0BzatQbprJ-hjWF95VzdHbGRsVEk
 /view?usp=sharing

 René-Luc, David, Paul, don't hesitate to amend that!

 
 


 *Qgis server refactoring is done!*
 As you may know, QGIS is jumping to a new major version (yes!).
 Doing so was made necessary because of the need to switch to python 3,
 QT5, but also because we needed to break the QGIS API in several places.

 A year ago, a tiny troll
 from switzerland rang a
 bell about the strong need for love server code base required.

 Indeed, the API was locked by some old methods of QGIS server. In
 short, QGIS server was reparsing the qgs project file in his own way, and
 created dependencies to part of QGIS we needed to drop.

 As outsourcing the server code base was not an option, so we had to
 refactor it.

 The involved parties decided to get engaged in a code sprint
  
 in
 the city of Lyon , France dedicated to sharing their vision, planning the
 work and finally making all the following
  happen :



 *# Deep, complex and unrewarding tasks:*

 - Remove all singleton calls

 - Cut all the dependencies to the old qgis project parser

 - Minimize dependencies to GUI library. Since fonts are necessary to
 render maps, totally removing them was not feasable.

 *# Higher level refactoring*

 All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS,
 GetPrint etc..) have been rewritten. Some like WMS were entirely rewritten.
 Kudos to the dev's


 *# New features and architecture stuff*

 - QGIS Server Services as plugins like providers. (slide 10 would be a
 nice figure here)

 - Multi-thread rendering  -
 like in the desktop

 - A new option to trust layer metadata
  and speed up project loading


 *# Infrastructure tasks*

 - Build a OGC compliancy platform
 
  and
 integrate it to a continuous integration platform. Conformity reports are
 now pushed to tests.qgis.org *XXX waiting for Richard to expose them

Re: [QGIS-Developer] QGIS Server 3 status

[Burghardt.Scholle]

Hi,

oh, shame on me. Of course I meant "FcgidInitialEnv 
QGIS_SERVER_PARALLEL_RENDERING True"! 
Please excuse me and thank you for the hint with the log level. I will try it.

Burghardt

> -Ursprüngliche Nachricht-
> Von: David Marteau [mailto:dmart...@3liz.com]
> Gesendet: Montag, 9. Oktober 2017 12:19
> An: Scholle, Burghardt (15-3 GIS)
> Cc: qgis-developer@lists.osgeo.org
> Betreff: Re: [QGIS-Developer] QGIS Server 3 status
> 
> Hi
> 
> According to the source
> https://github.com/qgis/QGIS/blob/master/src/server/qgsserversettings.cp
> p#L47: setting QGIS_SERVER_PARALLEL_RENDERING to False or not setting
> QGIS_SERVER_PARALLEL_RENDERING is the same thing as the default value
> is 'false'.
> 
> Using the appropriate log level you can get metric on the rendering time
> from qgis: imho, comparing this metric would be a good starting point putting
> aside external configuration (except for the postgres connection) and isolate
> any bottleneck.
> 
> David.
> 
> > Le 9 oct. 2017 à 11:53, <burghardt.scho...@stadt.wolfsburg.de>
> <burghardt.scho...@stadt.wolfsburg.de> a écrit :
> >
> > Hi David,
> >
> > I will answer you directly and give you the desired information. I've done
> some tests with a sample application, which you can see under the URL
> https://lxgis1.stadt.wolfsburg.de/qgis_wcl/index.html.
> > The map topic "Stadtplan" is based on the qgis server 2.14.19, the
> "Stadtplan (Dev)"-topic is based on qgis server 2.99 (codeversion 825a323).
> Subsequent tests I've done with the layers "Luftbilder" and "Infrastruktur".
> The former are geotiff's, the latter are generated from a PostGIS database.
> As client I use a customized version of the "OL3 Mobile Client" from
> Sourcepole.
> >
> > If I look at the access times in the developer tools of the Firefox, they
> speak a clear language:
> > - Topic "Stadtplan" -> moving the map, zoom in / zoom out takes about
> > 0.5 s on the intranet (!)
> > - Topic "Stadtplan (Dev)" -> moving the map, zoom in / zoom out takes
> > about 1.2 s with the setting "FcgidInitialEnv
> > QGIS_SERVER_PARALLEL_RENDERING False" in my apache config
> > - Without setting "FcgidInitialEnv QGIS_SERVER_PARALLEL_RENDERING
> > False" the access takes about 0.7 s
> > Result: without using multiprocessing / multithreading, the QGIS server is
> faster under these test conditions, but still clearly slower than the older
> version!
> >
> > Hope this description helps
> >
> > Burghardt
> >
> > ***
> >
> > Burghardt Scholle
> > mailto:burghardt.scho...@stadt.wolfsburg.de
> >
> >> Hi,
> >>
> >> Do we have metrics on this ?  Does it mean  that
> QGIS_SERVER_PARALLEL_RENDERING=False is also slower than previous
> version ?
> >>
> >>
> >> David M.
> >>
> >>
> >>
> >>> Le 4 oct. 2017 à 14:15, Matthias Kuhn  a écrit :
> >>>
> >>> Hi,
> >>>
> >>> I had some questions from people interested in performance.
> >>>
> >>> I advised them to set the following
> >>>
> >>> * QGIS_SERVER_PARALLEL_RENDERING=True
> >>> * Trust project flag
> >>>
> >>> Apparently parallelized rendering works (system stats) but it was
> >>> reported to be slower than older versions.
> >>>
> >>> Is there something else that needs to be done? Is there more
> >>> information I can ask for / give?
> >>>
> >>> Thanks a lot
> >>> Matthias
> >>
> >
> >
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
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 Server 3 status

[David Marteau]

Hi

According to the source 
https://github.com/qgis/QGIS/blob/master/src/server/qgsserversettings.cpp#L47: 
setting QGIS_SERVER_PARALLEL_RENDERING to False or not setting 
QGIS_SERVER_PARALLEL_RENDERING is the same thing as the default value is 
'false'.

Using the appropriate log level you can get metric on the rendering time from 
qgis: imho, comparing this metric would be a good starting point putting aside 
external configuration (except for the postgres connection) and isolate any 
bottleneck. 

David.

> Le 9 oct. 2017 à 11:53,  
>  a écrit :
> 
> Hi David,
> 
> I will answer you directly and give you the desired information. I've done 
> some tests with a sample application, which you can see under the URL 
> https://lxgis1.stadt.wolfsburg.de/qgis_wcl/index.html.
> The map topic "Stadtplan" is based on the qgis server 2.14.19, the "Stadtplan 
> (Dev)"-topic is based on qgis server 2.99 (codeversion 825a323). Subsequent 
> tests I've done with the layers "Luftbilder" and "Infrastruktur". The former 
> are geotiff's, the latter are generated from a PostGIS database. As client I 
> use a customized version of the "OL3 Mobile Client" from Sourcepole.
> 
> If I look at the access times in the developer tools of the Firefox, they 
> speak a clear language:
> - Topic "Stadtplan" -> moving the map, zoom in / zoom out takes about 0.5 s 
> on the intranet (!)
> - Topic "Stadtplan (Dev)" -> moving the map, zoom in / zoom out takes about 
> 1.2 s with the setting "FcgidInitialEnv QGIS_SERVER_PARALLEL_RENDERING False" 
> in my apache config
> - Without setting "FcgidInitialEnv QGIS_SERVER_PARALLEL_RENDERING False" the 
> access takes about 0.7 s
> Result: without using multiprocessing / multithreading, the QGIS server is 
> faster under these test conditions, but still clearly slower than the older 
> version!
> 
> Hope this description helps
> 
> Burghardt
> 
> ***
> 
> Burghardt Scholle
> mailto:burghardt.scho...@stadt.wolfsburg.de
> 
>> Hi,
>> 
>> Do we have metrics on this ?  Does it mean  that 
>> QGIS_SERVER_PARALLEL_RENDERING=False is also slower than previous version ?
>> 
>> 
>> David M.
>> 
>> 
>> 
>>> Le 4 oct. 2017 à 14:15, Matthias Kuhn  a écrit :
>>> 
>>> Hi,
>>> 
>>> I had some questions from people interested in performance.
>>> 
>>> I advised them to set the following
>>> 
>>> * QGIS_SERVER_PARALLEL_RENDERING=True
>>> * Trust project flag
>>> 
>>> Apparently parallelized rendering works (system stats) but it was
>>> reported to be slower than older versions.
>>> 
>>> Is there something else that needs to be done? Is there more information
>>> I can ask for / give?
>>> 
>>> Thanks a lot
>>> Matthias
>> 
> 
> 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
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 Server 3 status

[Burghardt.Scholle]

Hi David,

I will answer you directly and give you the desired information. I've done some 
tests with a sample application, which you can see under the URL 
https://lxgis1.stadt.wolfsburg.de/qgis_wcl/index.html.
The map topic "Stadtplan" is based on the qgis server 2.14.19, the "Stadtplan 
(Dev)"-topic is based on qgis server 2.99 (codeversion 825a323). Subsequent 
tests I've done with the layers "Luftbilder" and "Infrastruktur". The former 
are geotiff's, the latter are generated from a PostGIS database. As client I 
use a customized version of the "OL3 Mobile Client" from Sourcepole.

If I look at the access times in the developer tools of the Firefox, they speak 
a clear language:
- Topic "Stadtplan" -> moving the map, zoom in / zoom out takes about 0.5 s on 
the intranet (!)
- Topic "Stadtplan (Dev)" -> moving the map, zoom in / zoom out takes about 1.2 
s with the setting "FcgidInitialEnv QGIS_SERVER_PARALLEL_RENDERING False" in my 
apache config
- Without setting "FcgidInitialEnv QGIS_SERVER_PARALLEL_RENDERING False" the 
access takes about 0.7 s
Result: without using multiprocessing / multithreading, the QGIS server is 
faster under these test conditions, but still clearly slower than the older 
version!

Hope this description helps

Burghardt

***

Burghardt Scholle
mailto:burghardt.scho...@stadt.wolfsburg.de

>Hi,
>
>Do we have metrics on this ?  Does it mean  that 
>QGIS_SERVER_PARALLEL_RENDERING=False is also slower than previous version ?
>
>
>David M.
>
>
>
>> Le 4 oct. 2017 à 14:15, Matthias Kuhn  a écrit :
>> 
>> Hi,
>> 
>> I had some questions from people interested in performance.
>> 
>> I advised them to set the following
>> 
>> * QGIS_SERVER_PARALLEL_RENDERING=True
>> * Trust project flag
>> 
>> Apparently parallelized rendering works (system stats) but it was
>> reported to be slower than older versions.
>> 
>> Is there something else that needs to be done? Is there more information
>> I can ask for / give?
>> 
>> Thanks a lot
>> Matthias
>


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

Re: [QGIS-Developer] QGIS Server 3 status

[Tim Sutton]

Hi

> On 05 Oct 2017, at 10:09, David Marteau  wrote:
> 
> Hi,
> 
> Thanks for the overview. 
> 
> We need more examples of embedding the server in python and I plan to publish 
> some concrete examples from our use cases asap.

Thats great David! Looking forward to testing it out. Can you maybe publish 
your examples in the python cookbook?

Regards

Tim

> 
> David M.
> 
> 
>> Le 5 oct. 2017 à 09:34, Alessandro Pasotti > > a écrit :
>> 
>> Hi Règis,
>> 
>> thanks for the nice summary!
>> 
>> Maybe it would be interesting for python devs to stress out how QGIS server 
>> 3 brings the bindings and the plugins to a new level: while the original 
>> filter-style python plugins, are still available, the new service-oriented 
>> plugin-based architecture allows Python developers to create new services 
>> (for example WPS) by implementing a new `QgsService` directly in Python. 
>> Overriding existing services is also possible.
>> 
>> The server API has now full python bindings and a QGIS server can be easily 
>> implemented directly in Python and wrapped into your favourite framework 
>> (see this simple wsgi experiment: 
>> https://gist.github.com/elpaso/0cd7fb6a0518dc46c45557d9133438b8 
>>  ).
>> 
>> For more examples of the API, I think there are some basic examples in the 
>> official Python tests: 
>> https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsserver_services.py#L79
>>  
>> 
>>  
>> 
>> 
>> Cheers
>> 
>> 
>> 
>> 
>> 
>> On Wed, Oct 4, 2017 at 10:49 PM, Régis Haubourg > > wrote:
>> Well, from a user point of view, that's a bit hard since all this is 90 % 
>> refactoring.. which is supposed to be transparent for users. 
>> 
>> We have the trust and multithreaded features, that should (and early testers 
>> today found it slower today) and the ability to code new services using 
>> python.   
>> We can also show some numbers about OGC conformity tests and the goal of 
>> reaching OGC certification (WMS only by now). 
>> 
>> Alessandro, René-Luc and David, do you have some user oriented examples for 
>> the new modular API ? 
>> 
>> 
>> 
>> 2017-10-04 22:18 GMT+02:00 Anita Graser > >:
>> Great overview, thanks for drafting Régis!
>> 
>> Some additional ideas: Could we add a section with the key improvements from 
>> an user perspective? 
>> 
>> I'm particularly intrigued by the services / plugins part. Could you 
>> elaborate?
>> 
>> Regards,
>> Anita
>> 
>> 
>> 
>> On Wed, Oct 4, 2017 at 9:42 PM, Régis Haubourg > > wrote:
>> Hi again, 
>> here is my very first draft:
>> 
>>  Several images can be pulled from the joined slides given at Foss4G-EU here 
>> https://drive.google.com/file/d/0BzatQbprJ-hjWF95VzdHbGRsVEk/view?usp=sharing
>>  
>> 
>>  
>> 
>> René-Luc, David, Paul, don't hesitate to amend that!
>> 
>> 
>> 
>> Qgis server refactoring is done!
>> 
>> As you may know, QGIS is jumping to a new major version (yes!).  
>> Doing so was made necessary because of the need to switch to python 3, QT5, 
>> but also because we needed to break the QGIS API in several places. 
>> 
>> A year ago, a tiny troll  
>> from switzerland rang a bell 
>> about the strong need for love server code base required. 
>> 
>> Indeed, the API was locked by some old methods of QGIS server. In short, 
>> QGIS server was reparsing the qgs project file in his own way, and created 
>> dependencies to part of QGIS we needed to drop.
>>
>> As outsourcing the server code base was not an option, so we had to refactor 
>> it. 
>> 
>> The involved parties decided to get engaged in a code sprint 
>>  in 
>> the city of Lyon , France dedicated to sharing their vision, planning the 
>> work and finally making all the following 
>>  happen :
>> 
>> 
>> # Deep, complex and unrewarding tasks:
>> 
>> - Remove all singleton calls
>> 
>> - Cut all the dependencies to the old qgis project parser
>> 
>> - Minimize dependencies to GUI library. Since fonts are necessary to render 
>> maps, totally removing them was not feasable. 
>> 
>> # Higher level refactoring
>> 
>> All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint 
>> etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to 
>> the dev's
>> 
>> 
>> # New features and architecture stuff
>> 
>> - 

Re: [QGIS-Developer] QGIS Server 3 status

[David Marteau]

Hi,

Thanks for the overview. 

We need more examples of embedding the server in python and I plan to publish 
some concrete examples from our use cases asap.

David M.


> Le 5 oct. 2017 à 09:34, Alessandro Pasotti  a écrit :
> 
> Hi Règis,
> 
> thanks for the nice summary!
> 
> Maybe it would be interesting for python devs to stress out how QGIS server 3 
> brings the bindings and the plugins to a new level: while the original 
> filter-style python plugins, are still available, the new service-oriented 
> plugin-based architecture allows Python developers to create new services 
> (for example WPS) by implementing a new `QgsService` directly in Python. 
> Overriding existing services is also possible.
> 
> The server API has now full python bindings and a QGIS server can be easily 
> implemented directly in Python and wrapped into your favourite framework (see 
> this simple wsgi experiment: 
> https://gist.github.com/elpaso/0cd7fb6a0518dc46c45557d9133438b8 
>  ).
> 
> For more examples of the API, I think there are some basic examples in the 
> official Python tests: 
> https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsserver_services.py#L79
>  
> 
>  
> 
> 
> Cheers
> 
> 
> 
> 
> 
> On Wed, Oct 4, 2017 at 10:49 PM, Régis Haubourg  > wrote:
> Well, from a user point of view, that's a bit hard since all this is 90 % 
> refactoring.. which is supposed to be transparent for users. 
> 
> We have the trust and multithreaded features, that should (and early testers 
> today found it slower today) and the ability to code new services using 
> python.   
> We can also show some numbers about OGC conformity tests and the goal of 
> reaching OGC certification (WMS only by now). 
> 
> Alessandro, René-Luc and David, do you have some user oriented examples for 
> the new modular API ? 
> 
> 
> 
> 2017-10-04 22:18 GMT+02:00 Anita Graser  >:
> Great overview, thanks for drafting Régis!
> 
> Some additional ideas: Could we add a section with the key improvements from 
> an user perspective? 
> 
> I'm particularly intrigued by the services / plugins part. Could you 
> elaborate?
> 
> Regards,
> Anita
> 
> 
> 
> On Wed, Oct 4, 2017 at 9:42 PM, Régis Haubourg  > wrote:
> Hi again, 
> here is my very first draft:
> 
>  Several images can be pulled from the joined slides given at Foss4G-EU here 
> https://drive.google.com/file/d/0BzatQbprJ-hjWF95VzdHbGRsVEk/view?usp=sharing 
> 
>  
> 
> René-Luc, David, Paul, don't hesitate to amend that!
> 
> 
> 
> Qgis server refactoring is done!
> 
> As you may know, QGIS is jumping to a new major version (yes!).  
> Doing so was made necessary because of the need to switch to python 3, QT5, 
> but also because we needed to break the QGIS API in several places. 
> 
> A year ago, a tiny troll  from 
> switzerland rang a bell about the strong need for love server code base 
> required. 
> 
> Indeed, the API was locked by some old methods of QGIS server. In short, QGIS 
> server was reparsing the qgs project file in his own way, and created 
> dependencies to part of QGIS we needed to drop.
>
> As outsourcing the server code base was not an option, so we had to refactor 
> it. 
> 
> The involved parties decided to get engaged in a code sprint 
>  in 
> the city of Lyon , France dedicated to sharing their vision, planning the 
> work and finally making all the following 
>  happen :
> 
> 
> # Deep, complex and unrewarding tasks:
> 
> - Remove all singleton calls
> 
> - Cut all the dependencies to the old qgis project parser
> 
> - Minimize dependencies to GUI library. Since fonts are necessary to render 
> maps, totally removing them was not feasable. 
> 
> # Higher level refactoring
> 
> All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint 
> etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to 
> the dev's
> 
> 
> # New features and architecture stuff
> 
> - QGIS Server Services as plugins like providers. (slide 10 would be a nice 
> figure here) 
> 
> - Multi-thread rendering  - like in 
> the desktop
> 
> - A new option to trust layer metadata 
>  and speed up project loading
> 
> 
> # Infrastructure tasks
> 
> - Build a OGC compliancy platform 
> 

Re: [QGIS-Developer] QGIS Server 3 status

[Alessandro Pasotti]

Hi Règis,

thanks for the nice summary!

Maybe it would be interesting for python devs to stress out how QGIS server
3 brings the bindings and the plugins to a new level: while the original
filter-style python plugins, are still available, the new service-oriented
plugin-based architecture allows Python developers to create new services
(for example WPS) by implementing a new `QgsService` directly in Python.
Overriding existing services is also possible.

The server API has now full python bindings and a QGIS server can be easily
implemented directly in Python and wrapped into your favourite framework
(see this simple wsgi experiment:
https://gist.github.com/elpaso/0cd7fb6a0518dc46c45557d9133438b8 ).

For more examples of the API, I think there are some basic examples in the
official Python tests:
https://github.com/qgis/QGIS/blob/master/tests/src/python/test_qgsserver_services.py#L79


Cheers





On Wed, Oct 4, 2017 at 10:49 PM, Régis Haubourg 
wrote:

> Well, from a user point of view, that's a bit hard since all this is 90 %
> refactoring.. which is supposed to be transparent for users.
>
> We have the trust and multithreaded features, that should (and early
> testers today found it slower today) and the ability to code new services
> using python.
> We can also show some numbers about OGC conformity tests and the goal of
> reaching OGC certification (WMS only by now).
>
> Alessandro, René-Luc and David, do you have some user oriented examples
> for the new modular API ?
>
>
>
> 2017-10-04 22:18 GMT+02:00 Anita Graser :
>
>> Great overview, thanks for drafting Régis!
>>
>> Some additional ideas: Could we add a section with the key improvements
>> from an user perspective?
>>
>> I'm particularly intrigued by the services / plugins part. Could you
>> elaborate?
>>
>> Regards,
>> Anita
>>
>>
>>
>> On Wed, Oct 4, 2017 at 9:42 PM, Régis Haubourg 
>> wrote:
>>
>>> Hi again,
>>> here is my very first draft:
>>>
>>>  Several images can be pulled from the joined slides given at Foss4G-EU
>>> here https://drive.google.com/file/d/0BzatQbprJ-hjWF95VzdHbGRsVEk
>>> /view?usp=sharing
>>>
>>> René-Luc, David, Paul, don't hesitate to amend that!
>>>
>>> 
>>> 
>>>
>>>
>>> *Qgis server refactoring is done!*
>>> As you may know, QGIS is jumping to a new major version (yes!).
>>> Doing so was made necessary because of the need to switch to python 3,
>>> QT5, but also because we needed to break the QGIS API in several places.
>>>
>>> A year ago, a tiny troll from
>>> switzerland rang a bell about the strong need for love server code base
>>> required.
>>>
>>> Indeed, the API was locked by some old methods of QGIS server. In short,
>>> QGIS server was reparsing the qgs project file in his own way, and created
>>> dependencies to part of QGIS we needed to drop.
>>>
>>> As outsourcing the server code base was not an option, so we had to
>>> refactor it.
>>>
>>> The involved parties decided to get engaged in a code sprint
>>>  in
>>> the city of Lyon , France dedicated to sharing their vision, planning the
>>> work and finally making all the following
>>>  happen :
>>>
>>>
>>>
>>> *# Deep, complex and unrewarding tasks:*
>>>
>>> - Remove all singleton calls
>>>
>>> - Cut all the dependencies to the old qgis project parser
>>>
>>> - Minimize dependencies to GUI library. Since fonts are necessary to
>>> render maps, totally removing them was not feasable.
>>>
>>> *# Higher level refactoring*
>>>
>>> All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS,
>>> GetPrint etc..) have been rewritten. Some like WMS were entirely rewritten.
>>> Kudos to the dev's
>>>
>>>
>>> *# New features and architecture stuff*
>>>
>>> - QGIS Server Services as plugins like providers. (slide 10 would be a
>>> nice figure here)
>>>
>>> - Multi-thread rendering  -
>>> like in the desktop
>>>
>>> - A new option to trust layer metadata
>>>  and speed up project loading
>>>
>>>
>>> *# Infrastructure tasks*
>>>
>>> - Build a OGC compliancy platform
>>> 
>>>  and
>>> integrate it to a continuous integration platform. Conformity reports are
>>> now pushed to tests.qgis.org *XXX waiting for Richard to expose them in
>>> the website*
>>>
>>> - Add unit tests... and again more unit tests
>>>
>>> - Stress QGIS server against security leaks
>>>  (SQL
>>> injections and other malicious attacks)
>>>
>>> - Start profiling and bench marking performances. This work still need
>>> some love - and funding 

Re: [QGIS-Developer] QGIS Server 3 status

[Régis Haubourg]

Well, from a user point of view, that's a bit hard since all this is 90 %
refactoring.. which is supposed to be transparent for users.

We have the trust and multithreaded features, that should (and early
testers today found it slower today) and the ability to code new services
using python.
We can also show some numbers about OGC conformity tests and the goal of
reaching OGC certification (WMS only by now).

Alessandro, René-Luc and David, do you have some user oriented examples for
the new modular API ?



2017-10-04 22:18 GMT+02:00 Anita Graser :

> Great overview, thanks for drafting Régis!
>
> Some additional ideas: Could we add a section with the key improvements
> from an user perspective?
>
> I'm particularly intrigued by the services / plugins part. Could you
> elaborate?
>
> Regards,
> Anita
>
>
>
> On Wed, Oct 4, 2017 at 9:42 PM, Régis Haubourg 
> wrote:
>
>> Hi again,
>> here is my very first draft:
>>
>>  Several images can be pulled from the joined slides given at Foss4G-EU
>> here https://drive.google.com/file/d/0BzatQbprJ-hjWF95VzdHbGRsVEk
>> /view?usp=sharing
>>
>> René-Luc, David, Paul, don't hesitate to amend that!
>>
>> 
>> 
>>
>>
>> *Qgis server refactoring is done!*
>> As you may know, QGIS is jumping to a new major version (yes!).
>> Doing so was made necessary because of the need to switch to python 3,
>> QT5, but also because we needed to break the QGIS API in several places.
>>
>> A year ago, a tiny troll from
>> switzerland rang a bell about the strong need for love server code base
>> required.
>>
>> Indeed, the API was locked by some old methods of QGIS server. In short,
>> QGIS server was reparsing the qgs project file in his own way, and created
>> dependencies to part of QGIS we needed to drop.
>>
>> As outsourcing the server code base was not an option, so we had to
>> refactor it.
>>
>> The involved parties decided to get engaged in a code sprint
>>  in
>> the city of Lyon , France dedicated to sharing their vision, planning the
>> work and finally making all the following
>>  happen :
>>
>>
>>
>> *# Deep, complex and unrewarding tasks:*
>>
>> - Remove all singleton calls
>>
>> - Cut all the dependencies to the old qgis project parser
>>
>> - Minimize dependencies to GUI library. Since fonts are necessary to
>> render maps, totally removing them was not feasable.
>>
>> *# Higher level refactoring*
>>
>> All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS,
>> GetPrint etc..) have been rewritten. Some like WMS were entirely rewritten.
>> Kudos to the dev's
>>
>>
>> *# New features and architecture stuff*
>>
>> - QGIS Server Services as plugins like providers. (slide 10 would be a
>> nice figure here)
>>
>> - Multi-thread rendering  - like
>> in the desktop
>>
>> - A new option to trust layer metadata
>>  and speed up project loading
>>
>>
>> *# Infrastructure tasks*
>>
>> - Build a OGC compliancy platform
>>  
>> and
>> integrate it to a continuous integration platform. Conformity reports are
>> now pushed to tests.qgis.org *XXX waiting for Richard to expose them in
>> the website*
>>
>> - Add unit tests... and again more unit tests
>>
>> - Stress QGIS server against security leaks
>>  (SQL
>> injections and other malicious attacks)
>>
>> - Start profiling and bench marking performances. This work still need
>> some love - and funding - to be achieved
>>
>>
>> A presentation
>> 
>>  was
>> given at FOSS4G-EU in July.
>>
>> *Congratulations* to the developers who worked hard on that work.
>>
>> Now this deserves to be well tested, please report back any issues!
>>
>>
>>
>> 2017-10-04 15:17 GMT+02:00 Anita Graser :
>>
>>>
>>>
>>> On Wed, Oct 4, 2017 at 1:23 PM, Régis Haubourg >> > wrote:
>>>
 Hi

 Yes, refactoring is now complete! see : https://github.com/qgis/QGIS-E
 nhancement-Proposals/issues/74#issuecomment-334123595

 Anita, I'll draft an article tonight if you still agree to review it,
 that would be great!

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

Re: [QGIS-Developer] QGIS Server 3 status

[Anita Graser]

Great overview, thanks for drafting Régis!

Some additional ideas: Could we add a section with the key improvements
from an user perspective?

I'm particularly intrigued by the services / plugins part. Could you
elaborate?

Regards,
Anita



On Wed, Oct 4, 2017 at 9:42 PM, Régis Haubourg 
wrote:

> Hi again,
> here is my very first draft:
>
>  Several images can be pulled from the joined slides given at Foss4G-EU
> here https://drive.google.com/file/d/0BzatQbprJ-
> hjWF95VzdHbGRsVEk/view?usp=sharing
>
> René-Luc, David, Paul, don't hesitate to amend that!
>
> 
> 
>
>
> *Qgis server refactoring is done!*
> As you may know, QGIS is jumping to a new major version (yes!).
> Doing so was made necessary because of the need to switch to python 3,
> QT5, but also because we needed to break the QGIS API in several places.
>
> A year ago, a tiny troll from
> switzerland rang a bell about the strong need for love server code base
> required.
>
> Indeed, the API was locked by some old methods of QGIS server. In short,
> QGIS server was reparsing the qgs project file in his own way, and created
> dependencies to part of QGIS we needed to drop.
>
> As outsourcing the server code base was not an option, so we had to
> refactor it.
>
> The involved parties decided to get engaged in a code sprint
>  in
> the city of Lyon , France dedicated to sharing their vision, planning the
> work and finally making all the following
>  happen :
>
>
>
> *# Deep, complex and unrewarding tasks:*
>
> - Remove all singleton calls
>
> - Cut all the dependencies to the old qgis project parser
>
> - Minimize dependencies to GUI library. Since fonts are necessary to
> render maps, totally removing them was not feasable.
>
> *# Higher level refactoring*
>
> All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint
> etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to
> the dev's
>
>
> *# New features and architecture stuff*
>
> - QGIS Server Services as plugins like providers. (slide 10 would be a
> nice figure here)
>
> - Multi-thread rendering  - like
> in the desktop
>
> - A new option to trust layer metadata
>  and speed up project loading
>
>
> *# Infrastructure tasks*
>
> - Build a OGC compliancy platform
>  
> and
> integrate it to a continuous integration platform. Conformity reports are
> now pushed to tests.qgis.org *XXX waiting for Richard to expose them in
> the website*
>
> - Add unit tests... and again more unit tests
>
> - Stress QGIS server against security leaks
>  (SQL
> injections and other malicious attacks)
>
> - Start profiling and bench marking performances. This work still need
> some love - and funding - to be achieved
>
>
> A presentation
> 
>  was
> given at FOSS4G-EU in July.
>
> *Congratulations* to the developers who worked hard on that work.
>
> Now this deserves to be well tested, please report back any issues!
>
>
>
> 2017-10-04 15:17 GMT+02:00 Anita Graser :
>
>>
>>
>> On Wed, Oct 4, 2017 at 1:23 PM, Régis Haubourg 
>> wrote:
>>
>>> Hi
>>>
>>> Yes, refactoring is now complete! see : https://github.com/qgis/QGIS-E
>>> nhancement-Proposals/issues/74#issuecomment-334123595
>>>
>>> Anita, I'll draft an article tonight if you still agree to review it,
>>> that would be great!
>>>
>>
>>
>> ​Sure!
>>
>> Anita
>>
>>
>>
>>
>>
>
___
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 Server 3 status

[Régis Haubourg]

Hi again,
here is my very first draft:

 Several images can be pulled from the joined slides given at Foss4G-EU
here
https://drive.google.com/file/d/0BzatQbprJ-hjWF95VzdHbGRsVEk/view?usp=sharing


René-Luc, David, Paul, don't hesitate to amend that!




*Qgis server refactoring is done!*
As you may know, QGIS is jumping to a new major version (yes!).
Doing so was made necessary because of the need to switch to python 3, QT5,
but also because we needed to break the QGIS API in several places.

A year ago, a tiny troll from
switzerland rang a bell about the strong need for love server code base
required.

Indeed, the API was locked by some old methods of QGIS server. In short,
QGIS server was reparsing the qgs project file in his own way, and created
dependencies to part of QGIS we needed to drop.

As outsourcing the server code base was not an option, so we had to
refactor it.

The involved parties decided to get engaged in a code sprint
 in
the city of Lyon , France dedicated to sharing their vision, planning the
work and finally making all the following
 happen :



*# Deep, complex and unrewarding tasks:*

- Remove all singleton calls

- Cut all the dependencies to the old qgis project parser

- Minimize dependencies to GUI library. Since fonts are necessary to render
maps, totally removing them was not feasable.

*# Higher level refactoring*

All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint
etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to
the dev's


*# New features and architecture stuff*

- QGIS Server Services as plugins like providers. (slide 10 would be a nice
figure here)

- Multi-thread rendering  - like in
the desktop

- A new option to trust layer metadata
 and speed up project loading


*# Infrastructure tasks*

- Build a OGC compliancy platform

and
integrate it to a continuous integration platform. Conformity reports are
now pushed to tests.qgis.org *XXX waiting for Richard to expose them in the
website*

- Add unit tests... and again more unit tests

- Stress QGIS server against security leaks
 (SQL
injections and other malicious attacks)

- Start profiling and bench marking performances. This work still need some
love - and funding - to be achieved


A presentation

was
given at FOSS4G-EU in July.

*Congratulations* to the developers who worked hard on that work.

Now this deserves to be well tested, please report back any issues!



2017-10-04 15:17 GMT+02:00 Anita Graser :

>
>
> On Wed, Oct 4, 2017 at 1:23 PM, Régis Haubourg 
> wrote:
>
>> Hi
>>
>> Yes, refactoring is now complete! see : https://github.com/qgis/QGIS-E
>> nhancement-Proposals/issues/74#issuecomment-334123595
>>
>> Anita, I'll draft an article tonight if you still agree to review it,
>> that would be great!
>>
>
>
> ​Sure!
>
> Anita
>
>
>
>
>
___
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 Server 3 status

[David Marteau]

Hi,

Do we have metrics on this ?  Does it mean  that 
QGIS_SERVER_PARALLEL_RENDERING=False is also slower than previous version ?


David M.



> Le 4 oct. 2017 à 14:15, Matthias Kuhn  a écrit :
> 
> Hi,
> 
> I had some questions from people interested in performance.
> 
> I advised them to set the following
> 
> * QGIS_SERVER_PARALLEL_RENDERING=True
> * Trust project flag
> 
> Apparently parallelized rendering works (system stats) but it was
> reported to be slower than older versions.
> 
> Is there something else that needs to be done? Is there more information
> I can ask for / give?
> 
> Thanks a lot
> Matthias
> 
> On 10/04/2017 02:09 PM, René-Luc Dhont wrote:
>> Hi,
>> 
>> It seems that the QGIS refactoring is complete!
>> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74
>> https://github.com/qgis/qgis3.0_api/issues/57
>> https://github.com/qgis/QGIS/pull/4824
>> 
>> You can use QGIS Server like this in Python
>> 
>> from qgis.server import QgsServer, QgsServerRequest,
>> QgsBufferServerRequest, QgsBufferServerResponse
>> 
>> server = QgsServer()
>> 
>> qs = "?" + "&".join(["%s=%s" % i for i in list({
>>"MAP": '/tmp/qgis_project.qgs',
>>"SERVICE": "WFS",
>>"VERSION": "1.0.0",
>>"REQUEST": "GetCapabilities"
>>}.items())])
>> requestMethod = QgsServerRequest.GetMethod
>> headers = {}
>> data = '' #can be the xml request for requestMethod =
>> QgsServerRequest.PostMethod
>> 
>> request = QgsBufferServerRequest(qs, requestMethod, headers, data)
>> response = QgsBufferServerResponse()
>> server.handleRequest(request, response)
>> 
>> headers = []
>> rh = response.headers()
>> rk = sorted(rh.keys())
>> for k in rk:
>>headers.append(("%s: %s" % (k, rh[k])).encode('utf-8'))
>> 
>> body = bytes(response.body())
>> 
>> Now QGIS Server needs somes enhancement and cleanup.
>> 
>> René-Luc D'Hont
>> 3Liz
>> 
>> Le 04/10/2017 à 13:23, Régis Haubourg a écrit :
>>> Hi 
>>> 
>>> Yes, refactoring is now complete! see :
>>> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74#issuecomment-334123595
>>> 
>>> Anita, I'll draft an article tonight if you still agree to review it,
>>> that would be great!
>>> 
>>> Régis
>>> 
>>> 
>>> 
>>> 2017-10-03 14:25 GMT+02:00 Anita Graser >> >>:
>>> 
>>> 
>>> 
>>>On Tue, Oct 3, 2017 at 11:19 AM, Régis Haubourg
>>> 
>>> >> wrote:
>>> 
>>>Hi Etienne, 
>>> 
>>>from my point of view, this is the perfect time to start
>>>stressing QGIS server 3! We just discussed bout starting
>>>working with it this morning on a new project. 
>>> 
>>>Maybe Alessandro and René-Luc can tell us more about the
>>>plugin side. 
>>> 
>>>Paul is currently fixing issues raised by the OGC test
>>>engines. Richard, could you find some time to expose them on a
>>>public url? 
>>> 
>>> 
>>>​What would you think about publishing a QGIS Server update on
>>>blog.qgis.org  >> > once the latest information
>>>has been gathered? I'd like to see Server presented and advertised
>>>more ​widely.
>>> 
>>>​I'd be glad to help write the post if someone can help with the
>>>necessary insights.
>>> 
>>>Regards,
>>>Anita​
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> 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 Server 3 status

[Anita Graser]

On Wed, Oct 4, 2017 at 1:23 PM, Régis Haubourg 
wrote:

> Hi
>
> Yes, refactoring is now complete! see : https://github.com/qgis/QGIS-
> Enhancement-Proposals/issues/74#issuecomment-334123595
>
> Anita, I'll draft an article tonight if you still agree to review it, that
> would be great!
>


​Sure!

Anita
___
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 Server 3 status

[Régis Haubourg]

Hi Matthias,
in my tests that were made a few month ago, it was a lot faster on project
load and a bit faster with parallel rendering for multi layer requests.
Still I found it still slower than desktop rendering on the very same
extent. I'm not aware of additional settings.
We did not have the opportunity to deploy a performance benchmark, maybe
Yves can tell us if things have moved on this front?
Régis

2017-10-04 14:15 GMT+02:00 Matthias Kuhn :

> Hi,
>
> I had some questions from people interested in performance.
>
> I advised them to set the following
>
> * QGIS_SERVER_PARALLEL_RENDERING=True
> * Trust project flag
>
> Apparently parallelized rendering works (system stats) but it was
> reported to be slower than older versions.
>
> Is there something else that needs to be done? Is there more information
> I can ask for / give?
>
> Thanks a lot
> Matthias
>
> On 10/04/2017 02:09 PM, René-Luc Dhont wrote:
> > Hi,
> >
> > It seems that the QGIS refactoring is complete!
> > https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74
> > https://github.com/qgis/qgis3.0_api/issues/57
> > https://github.com/qgis/QGIS/pull/4824
> >
> > You can use QGIS Server like this in Python
> >
> > from qgis.server import QgsServer, QgsServerRequest,
> > QgsBufferServerRequest, QgsBufferServerResponse
> >
> > server = QgsServer()
> >
> > qs = "?" + "&".join(["%s=%s" % i for i in list({
> > "MAP": '/tmp/qgis_project.qgs',
> > "SERVICE": "WFS",
> > "VERSION": "1.0.0",
> > "REQUEST": "GetCapabilities"
> > }.items())])
> > requestMethod = QgsServerRequest.GetMethod
> > headers = {}
> > data = '' #can be the xml request for requestMethod =
> > QgsServerRequest.PostMethod
> >
> > request = QgsBufferServerRequest(qs, requestMethod, headers, data)
> > response = QgsBufferServerResponse()
> > server.handleRequest(request, response)
> >
> > headers = []
> > rh = response.headers()
> > rk = sorted(rh.keys())
> > for k in rk:
> > headers.append(("%s: %s" % (k, rh[k])).encode('utf-8'))
> >
> > body = bytes(response.body())
> >
> > Now QGIS Server needs somes enhancement and cleanup.
> >
> > René-Luc D'Hont
> > 3Liz
> >
> > Le 04/10/2017 à 13:23, Régis Haubourg a écrit :
> >> Hi
> >>
> >> Yes, refactoring is now complete! see :
> >> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/
> 74#issuecomment-334123595
> >>
> >> Anita, I'll draft an article tonight if you still agree to review it,
> >> that would be great!
> >>
> >> Régis
> >>
> >>
> >>
> >> 2017-10-03 14:25 GMT+02:00 Anita Graser  >> >:
> >>
> >>
> >>
> >> On Tue, Oct 3, 2017 at 11:19 AM, Régis Haubourg
> >> > wrote:
> >>
> >> Hi Etienne,
> >>
> >> from my point of view, this is the perfect time to start
> >> stressing QGIS server 3! We just discussed bout starting
> >> working with it this morning on a new project.
> >>
> >> Maybe Alessandro and René-Luc can tell us more about the
> >> plugin side.
> >>
> >> Paul is currently fixing issues raised by the OGC test
> >> engines. Richard, could you find some time to expose them on a
> >> public url?
> >>
> >>
> >> ​What would you think about publishing a QGIS Server update on
> >> blog.qgis.org  once the latest information
> >> has been gathered? I'd like to see Server presented and advertised
> >> more ​widely.
> >>
> >> ​I'd be glad to help write the post if someone can help with the
> >> necessary insights.
> >>
> >> Regards,
> >> Anita​
> >>
> >>
> >>
> >>
> >>
> >> ___
> >> 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 Server 3 status

[Matthias Kuhn]

Hi,

I had some questions from people interested in performance.

I advised them to set the following

* QGIS_SERVER_PARALLEL_RENDERING=True
* Trust project flag

Apparently parallelized rendering works (system stats) but it was
reported to be slower than older versions.

Is there something else that needs to be done? Is there more information
I can ask for / give?

Thanks a lot
Matthias

On 10/04/2017 02:09 PM, René-Luc Dhont wrote:
> Hi,
> 
> It seems that the QGIS refactoring is complete!
> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74
> https://github.com/qgis/qgis3.0_api/issues/57
> https://github.com/qgis/QGIS/pull/4824
> 
> You can use QGIS Server like this in Python
> 
> from qgis.server import QgsServer, QgsServerRequest,
> QgsBufferServerRequest, QgsBufferServerResponse
> 
> server = QgsServer()
> 
> qs = "?" + "&".join(["%s=%s" % i for i in list({
> "MAP": '/tmp/qgis_project.qgs',
> "SERVICE": "WFS",
> "VERSION": "1.0.0",
> "REQUEST": "GetCapabilities"
> }.items())])
> requestMethod = QgsServerRequest.GetMethod
> headers = {}
> data = '' #can be the xml request for requestMethod =
> QgsServerRequest.PostMethod
> 
> request = QgsBufferServerRequest(qs, requestMethod, headers, data)
> response = QgsBufferServerResponse()
> server.handleRequest(request, response)
> 
> headers = []
> rh = response.headers()
> rk = sorted(rh.keys())
> for k in rk:
> headers.append(("%s: %s" % (k, rh[k])).encode('utf-8'))
> 
> body = bytes(response.body())
> 
> Now QGIS Server needs somes enhancement and cleanup.
> 
> René-Luc D'Hont
> 3Liz
> 
> Le 04/10/2017 à 13:23, Régis Haubourg a écrit :
>> Hi 
>>
>> Yes, refactoring is now complete! see :
>> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74#issuecomment-334123595
>>
>> Anita, I'll draft an article tonight if you still agree to review it,
>> that would be great!
>>
>> Régis
>>
>>
>>
>> 2017-10-03 14:25 GMT+02:00 Anita Graser > >:
>>
>>
>>
>> On Tue, Oct 3, 2017 at 11:19 AM, Régis Haubourg
>> > wrote:
>>
>> Hi Etienne, 
>>
>> from my point of view, this is the perfect time to start
>> stressing QGIS server 3! We just discussed bout starting
>> working with it this morning on a new project. 
>>  
>> Maybe Alessandro and René-Luc can tell us more about the
>> plugin side. 
>>
>> Paul is currently fixing issues raised by the OGC test
>> engines. Richard, could you find some time to expose them on a
>> public url? 
>>
>>
>> ​What would you think about publishing a QGIS Server update on
>> blog.qgis.org  once the latest information
>> has been gathered? I'd like to see Server presented and advertised
>> more ​widely.
>>
>> ​I'd be glad to help write the post if someone can help with the
>> necessary insights.
>>
>> Regards,
>> Anita​
>>
>>
>>
>>
>>
>> ___
>> 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 Server 3 status

[René-Luc Dhont]

Hi,

It seems that the QGIS refactoring is complete!
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74
https://github.com/qgis/qgis3.0_api/issues/57
https://github.com/qgis/QGIS/pull/4824

You can use QGIS Server like this in Python

from qgis.server import QgsServer, QgsServerRequest, 
QgsBufferServerRequest, QgsBufferServerResponse


server = QgsServer()

qs = "?" + "&".join(["%s=%s" % i for i in list({
"MAP": '/tmp/qgis_project.qgs',
"SERVICE": "WFS",
"VERSION": "1.0.0",
"REQUEST": "GetCapabilities"
}.items())])
requestMethod = QgsServerRequest.GetMethod
headers = {}
data = '' #can be the xml request for requestMethod = 
QgsServerRequest.PostMethod


request = QgsBufferServerRequest(qs, requestMethod, headers, data)
response = QgsBufferServerResponse()
server.handleRequest(request, response)

headers = []
rh = response.headers()
rk = sorted(rh.keys())
for k in rk:
headers.append(("%s: %s" % (k, rh[k])).encode('utf-8'))

body = bytes(response.body())

Now QGIS Server needs somes enhancement and cleanup.

René-Luc D'Hont
3Liz

Le 04/10/2017 à 13:23, Régis Haubourg a écrit :

Hi

Yes, refactoring is now complete! see : 
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74#issuecomment-334123595


Anita, I'll draft an article tonight if you still agree to review it, 
that would be great!


Régis



2017-10-03 14:25 GMT+02:00 Anita Graser >:




On Tue, Oct 3, 2017 at 11:19 AM, Régis Haubourg
> wrote:

Hi Etienne,

from my point of view, this is the perfect time to start
stressing QGIS server 3! We just discussed bout starting
working with it this morning on a new project.
Maybe Alessandro and René-Luc can tell us more about the
plugin side.

Paul is currently fixing issues raised by the OGC test
engines. Richard, could you find some time to expose them on a
public url?


​What would you think about publishing a QGIS Server update on
blog.qgis.org  once the latest information
has been gathered? I'd like to see Server presented and advertised
more ​widely.

​I'd be glad to help write the post if someone can help with the
necessary insights.

Regards,
Anita​





___
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 Server 3 status

[Régis Haubourg]

Hi

Yes, refactoring is now complete! see :
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74#issuecomment-334123595

Anita, I'll draft an article tonight if you still agree to review it, that
would be great!

Régis



2017-10-03 14:25 GMT+02:00 Anita Graser :

>
>
> On Tue, Oct 3, 2017 at 11:19 AM, Régis Haubourg 
> wrote:
>
>> Hi Etienne,
>>
>> from my point of view, this is the perfect time to start stressing QGIS
>> server 3! We just discussed bout starting working with it this morning on a
>> new project.
>>
>> Maybe Alessandro and René-Luc can tell us more about the plugin side.
>>
>> Paul is currently fixing issues raised by the OGC test engines. Richard,
>> could you find some time to expose them on a public url?
>>
>>
> ​What would you think about publishing a QGIS Server update on
> blog.qgis.org once the latest information has been gathered? I'd like to
> see Server presented and advertised more ​widely.
>
> ​I'd be glad to help write the post if someone can help with the necessary
> insights.
>
> Regards,
> Anita​
>
>
>
___
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 Server 3 status

[Anita Graser]

On Tue, Oct 3, 2017 at 11:19 AM, Régis Haubourg 
wrote:

> Hi Etienne,
>
> from my point of view, this is the perfect time to start stressing QGIS
> server 3! We just discussed bout starting working with it this morning on a
> new project.
>
> Maybe Alessandro and René-Luc can tell us more about the plugin side.
>
> Paul is currently fixing issues raised by the OGC test engines. Richard,
> could you find some time to expose them on a public url?
>
>
​What would you think about publishing a QGIS Server update on blog.qgis.org
once the latest information has been gathered? I'd like to see Server
presented and advertised more ​widely.

​I'd be glad to help write the post if someone can help with the necessary
insights.

Regards,
Anita​
___
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 Server 3 status

[Régis Haubourg]

Hi Etienne,

from my point of view, this is the perfect time to start stressing QGIS
server 3! We just discussed bout starting working with it this morning on a
new project.

Maybe Alessandro and René-Luc can tell us more about the plugin side.

Paul is currently fixing issues raised by the OGC test engines. Richard,
could you find some time to expose them on a public url?

Regards,
Régis


2017-10-03 10:09 GMT+02:00 Etienne Trimaille :

> Hi devs,
>
> We would like to start testing QGIS Server 3: OGC services and Python
> plugins.
>
> I think I read that the QGIS Server refactoring was finished and it seems
> that most of OGC tests are working: http://37.187.164.
> 233/ogc/latest_wms_1_3_0.html
>
> Is it possible to have the status of QGIS Server 3?
> Are there some major known issues? Are Python plugins fully supported? Can
> we start porting plugins to the QGIS 3 Server API? Is there some highlights
> to know for Python plugins?
>
> Thanks for the all the work which has been done!
>
> Regards,
> Etienne
>
>
> ___
> 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] QGIS Server 3 status

[Etienne Trimaille]

Hi devs,

We would like to start testing QGIS Server 3: OGC services and Python
plugins.

I think I read that the QGIS Server refactoring was finished and it seems
that most of OGC tests are working:
http://37.187.164.233/ogc/latest_wms_1_3_0.html

Is it possible to have the status of QGIS Server 3?
Are there some major known issues? Are Python plugins fully supported? Can
we start porting plugins to the QGIS 3 Server API? Is there some highlights
to know for Python plugins?

Thanks for the all the work which has been done!

Regards,
Etienne
___
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