Lets say that speed of QGIS Server is good enough for most of my projects. But
it could be faster for more complex rendering and labeling.
UMN feels faster than QGIS Server - but I don't have time for double
configurations for desktop and web. Plus - it is so much easier to configure
QGIS projects compared to editing mapfiles.
"G. Allegri" <[email protected]> schrieb:
>>
>> The one thing were UMN Mapserver is a much better is performance.
>This
>> is where we should really catch up.
>>
>
>I would put this to the higher position! I don't know where the effort
>should be put, because I suppose it's something deep in the rendering
>engine of QGis. Do you see bottlenecks at the server level?
>
>I would also add a point to the whishlist: Qgis Server Python API ;)
>
>giovanni
>
>2012/11/14 kimaidou <[email protected]>
>
>> Hi
>>
>> 2012/11/14 Vincent Picavet <[email protected]>
>>
>>> Hi,
>>>
>>> > * templates for HTML popups (already done this in Lizmap, but why
>not
>>> > having it in Qgis)
>>> You mean accessing the templates through QGIS server ? Because html
>popups
>>> already are in QGIS :)
>>>
>>
>>
>> I mean through Qgis Server (in respect to this thread title ;)
>> Just exposing methods for the server must do it, as Andreas proposed.
>>
>> We should have a look at PyWPS too, which could be an easy way to
>provide
>>> WPS
>>> services around QGIS API.
>>>
>>
>>
>> Yes, pyWPS could help provide this feature, but we still need a way
>so
>> that QGIS Server can use python plugins / processes, etc.. I remember
>> discussion about this during last hackfests, but I do not know if
>someone
>> gave it a try.
>>
>> Anyway, +10000 for focusing on performance first, which is the key
>> "feature" for a Server.
>>
>> Michael
>>
>>
>>
>>>
>>> Vincent
>>>
>>> >
>>> > Good evening
>>> > Michael
>>> >
>>> >
>>> > 2012/11/14 G. Allegri <[email protected]>
>>> >
>>> > > > - integrated tiling
>>> > >>
>>> > >> Why not integrating mapcache directly to mutualize effort on
>this
>>> part ?
>>> > >> Mapcache can be used standalone, and could read its parameters
>>> directly
>>> > >> from a
>>> > >> qgis configuration file. No need to reinvent the wheel here, or
>would
>>> > >> there be a
>>> > >> good reason to it ?
>>> > >
>>> > > I think that a tile generator from the QGis Desktop side would
>>> suffice.
>>> > > Any other TMS/WMS-T server could use the tile structure.
>>> > >
>>> > >> > - mask layers
>>> > >>
>>> > >> That would be great to have in QGIS indeed. It would mean
>having for
>>> > >> each layer an attached mask layer, which is not displayed but
>only
>>> used
>>> > >> to define
>>> > >> hidden places.
>>> > >>
>>> > >> > - symbol placement
>>> > >> > - label offsets
>>> > >>
>>> > >> That's for qgis symbology, not directly a qgis server issue.
>Label
>>> > >> offset in
>>> > >> mapserver definitly looks cool !
>>> > >
>>> > > I agree Vincent.
>>> > >
>>> > >> Vincent
>>> > >> _______________________________________________
>>> > >> Qgis-developer mailing list
>>> > >> [email protected]
>>> > >> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> > >
>>> > > _______________________________________________
>>> > > Qgis-developer mailing list
>>> > > [email protected]
>>> > > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> _______________________________________________
>>> Qgis-developer mailing list
>>> [email protected]
>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>
>>
>> _______________________________________________
>> Qgis-developer mailing list
>> [email protected]
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Qgis-developer mailing list
>[email protected]
>http://lists.osgeo.org/mailman/listinfo/qgis-developer
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
