On Tuesday, September 27, 2016 15:45:41 Nicolas Boisteault wrote:
> Count on me for testing, documentation and suggestions.
>
> I'd prefer to have QGIS Server in core but if it has to become a third
> party software would it be a good idea to develop it in Python or any
> other developper-friendly
Count on me for testing, documentation and suggestions.
I'd prefer to have QGIS Server in core but if it has to become a third
party software would it be a good idea to develop it in Python or any
other developper-friendly language rather than Qt/C++. This might not
possible due to performance
Hi René-Luc,
Very well said, likewise here in the Pacific Island QGIS Server and
Lizmap are major parts of our GIS projects, especially for Utilities.
On the same note we would love to see QGIS Server maintained, count me
IN participating and maintaining QGIS.
cheers,
Edwin
On Mon, Sep 26, 201
Il 26/09/2016 18:06, Matthias Kuhn ha scritto:
> Wow, I am impressed by the amount of feedback and active interest in the
> QGIS server.
>
> With this motivation behind it I am confident this part of the project
> can be continued in a solid and sustainable way.
>
> From a technical perspective I
Wow, I am impressed by the amount of feedback and active interest in the
QGIS server.
With this motivation behind it I am confident this part of the project
can be continued in a solid and sustainable way.
From a technical perspective I also fully agree with Jürgen that keeping
the source code in
I would prefer mantaining it in QGIS core too, but we need to find the
resources to keep it up to date with QGIS 3 refactoring. I thought this was
the problem...
giovanni
Il 26 set 2016 17:08, "David Marteau" ha scritto:
> Hi
>
> Are you telling that the server codebase could rely on these feat
Hi
Are you telling that the server codebase could rely on these features
(multiproject management and layer cache) with
the actual refactoring ? This would be really a good thing - (and also a
better handling of the layer registry that introduces weird
things with the ownership of layers).
A
Hi Andreas,
On Mon, 26. Sep 2016 at 14:37:30 +0200, Neumann, Andreas wrote:
> I have to say it comes a bit as a surprise to me that suddenly QGIS
> server is not regarded as a core component of QGIS anymore.
Me too. To me it's also not so clear why it should be separated more from
core. I gues
Hi all,
Le lundi 26 septembre 2016 à 14:37 +0200, Neumann, Andreas a écrit :
> Hi all,
> So I assume the discussion is not about kicking QGIS server out of the
> project, but about finding a way to improve the
> situation and make QGIS server more reliable and renovate the code base -
> right?
Hi all,
So I assume the discussion is not about kicking QGIS server out of the
project, but about finding a way to improve the situation and make QGIS
server more reliable and renovate the code base - right?
I have to say it comes a bit as a surprise to me that suddenly QGIS
server is not regar
Gis3W is also highly interested in partecipating, since we employ QGIS
Server in critical components of our business .
It's ok for us to keep QGIS Server out of the main repo. This would give
also the opportunity to manage a different release cycle.
The QGIS 3 refactoring is a great opportunity to
Hi René-Luc
> * Who is interested in participating in QGIS Server (code, ideas,
> review, tests) ?
count me in for tests.
cheers
-- G --
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinf
On Sat, Sep 24, 2016 at 1:19 PM, Tom Palan wrote:
> Hi,
>
> my company uses QGIS server for providing infrastructure GIS to
> communities. We are currently starting with the first customers, and losing
> QGIS server would require fundamental changes to our system.
> So we are very interested in 1
Hi,
my company uses QGIS server for providing infrastructure GIS to communities. We
are currently starting with the first customers, and losing QGIS server would
require fundamental changes to our system.
So we are very interested in 1. keeping QGIS server 2. providing dev time &
money to make
Hi René,
Thank to everyone participating in this.
>* Who is interested in participating in QGIS Server (code, ideas,
review, tests) ?
I am also interested in helping out with the effort.
All the best,
Tudor
On Friday, September 23, 2016 3:45 PM, René-Luc Dhont
wrote:
Hi devs,
The
> I know QGIS
> depends on GDAL mostly in terms of I/O, so it really should be solved on
> both GDAL and QGIS levels. But as far as I know GDAL dev community doesn’t
> have any particular plans to implement MVT driver (or, perhaps, they
> do?:).
This is something I'd love to see in GDAL. As usual,
oper
> Subject: [Qgis-developer] [QGIS Server] Maintain it and create a team
> Message-ID: <25bba341-9db8-40eb-7bda-8918c76f7...@gmail.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi devs,
>
> The Qt4 and Python 2.7 is going away from QGIS master, fol
Hi René-Luc
2016-09-23 14:45 GMT+02:00 René-Luc Dhont :
> Hi devs,
>
> The Qt4 and Python 2.7 is going away from QGIS master, following this PR:
> Require python 3 and qt5 https://github.com/qgis/QGIS/pull/3510
>
> But a part of the project directly suffered of this: QGIS Server. As
> explain on
Hi all,
Il 23/09/2016 15:04, Marco Hugentobler ha scritto:
> Well, taking the constructive parts out of that discussion, I think it
> makes sense to take the opportunity to rewrite the server part
> completely (it will be a while until there are the same number of
> features as now )
Does anybod
Hi René-Luc
Thanks, better to have it on the mailing list than with the github comments.
Well, taking the constructive parts out of that discussion, I think it
makes sense to take the opportunity to rewrite the server part
completely (it will be a while until there are the same number of
feat
Hi devs,
The Qt4 and Python 2.7 is going away from QGIS master, following this PR:
Require python 3 and qt5 https://github.com/qgis/QGIS/pull/3510
But a part of the project directly suffered of this: QGIS Server. As
explain on the Pull Request 'Require python 3 and qt5', all the QGIS
Server te
21 matches
Mail list logo