date:20171113

Re: [QGIS-Developer] Rendering of Icons

2017-11-13 Thread Peter King

Hi Calvin

here is the svg optimisation tool which Robert recommended to me,
https://github.com/RazrFalcon/svgcleaner-gui , and the online version
https://jakearchibald.github.io/svgomg/

Pete

On 14/11/17 10:32, Robert Szczepanek wrote:
> Hi Calvin,
>
> How to render sharp icons is described in my design guidelines
> (http://robert.szczepanek.pl/gis-icons-0.1/). It depends on objects
> (lines) location on grid at target resolution.
>
> Inkscape writes in SVG many additional tags. Our goal is to decrease
> SVG icon size, so final vector files are simply optimized by external
> tools.
>
> regards
> Robert
>
> W dniu 13.11.2017 o 21:46, C Hamilton pisze:
>> I was wondering how you turn the QGIS .svg icons into .png icons that
>> are used in the tool bars. I have been using Inkscape and the
>> resulting icons that I produce starting from the QGIS .svg files
>> don't seem to be as sharp and clear as what is distributed with QGIS.
>> The other thing I have found is that the QGIS .svg files are very
>> small. If I read them into Inkscape and save them back out they are
>> much larger.
>>
>> Thanks,
>>
>> Calvin
>>
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
> ___
> 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

This message contains information, which may be in confidence and may be 
subject to legal privilege. If you are not the intended recipient, you must not 
peruse, use, disseminate, distribute or copy this message. If you have received 
this message in error, please notify us immediately (Phone 0800 665 463 or 
i...@linz.govt.nz) and destroy the original message. LINZ accepts no 
responsibility for changes to this email, or for any attachments, after its 
transmission from LINZ. Thank You.
___
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] Rendering of Icons

2017-11-13 Thread Robert Szczepanek


Hi Calvin,

How to render sharp icons is described in my design guidelines 
(http://robert.szczepanek.pl/gis-icons-0.1/). It depends on objects 
(lines) location on grid at target resolution.


Inkscape writes in SVG many additional tags. Our goal is to decrease SVG 
icon size, so final vector files are simply optimized by external tools.


regards
Robert

W dniu 13.11.2017 o 21:46, C Hamilton pisze:
I was wondering how you turn the QGIS .svg icons into .png icons that 
are used in the tool bars. I have been using Inkscape and the resulting 
icons that I produce starting from the QGIS .svg files don't seem to be 
as sharp and clear as what is distributed with QGIS. The other thing I 
have found is that the QGIS .svg files are very small. If I read them 
into Inkscape and save them back out they are much larger.


Thanks,

Calvin


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


___
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] Rendering of Icons

2017-11-13 Thread C Hamilton

I was wondering how you turn the QGIS .svg icons into .png icons that are
used in the tool bars. I have been using Inkscape and the resulting icons
that I produce starting from the QGIS .svg files don't seem to be as sharp
and clear as what is distributed with QGIS. The other thing I have found is
that the QGIS .svg files are very small. If I read them into Inkscape and
save them back out they are much larger.

Thanks,

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

[QGIS-Developer] QGIS Server test on Windows 2016 server.

2017-11-13 Thread Mats Elfström

Wanted to test QGIS server on Windows 2016 server. Please advise on 
installation instructions. Main problem seems to be dll paths.
Postgis, Apache runs fine. 

Hälsning / Regards
Mats.E

Skickat från min / Sent from my iPad, Ursäkta att jag är kortfattad / Excuse my 
brevity. 
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Tom Kralidis

Hi Alessandro: thanks for the info.  I tried this (see Gist in [1]) whichj
also results in the behaviour originally reported.

Thanks

..Tom


[1] https://gist.github.com/tomkralidis/dccb49efa760a585be38ee0c3188b8b3

On Mon, Nov 13, 2017 at 10:59 AM, Alessandro Pasotti  wrote:
>
> I think you can try this first: the WMS 'on_btnConnect_clicked' slot has
> been renamed to  'btnConnect_clicked'
>
>
>
> On Mon, Nov 13, 2017 at 4:37 PM, Tom Kralidis  wrote:
>>
>> On Mon, Nov 13, 2017 at 10:32 AM, Alessandro Pasotti 
>> wrote:
>> > On Mon, Nov 13, 2017 at 4:24 PM, Tom Kralidis 
>> > wrote:
>> >>
>> >> On Mon, Nov 13, 2017 at 10:17 AM, Alessandro Pasotti
>> >> 
>> >> wrote:
>> >> > On Mon, Nov 13, 2017 at 3:59 PM, Tom Kralidis 
>> >> > wrote:
>> >> >>
>> >> >> On Mon, Nov 13, 2017 at 9:18 AM, Alessandro Pasotti
>> >> >> 
>> >> >> wrote:
>> >> >> > On Mon, Nov 13, 2017 at 3:06 PM, Tom Kralidis
>> >> >> > 
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Hi devs:
>> >> >> >>
>> >> >> >> Given https://issues.qgis.org/issues/17347 I'm working on fixing
>> >> >> >> MetaSearch
>> >> >> >> provider connections in master. The core part of the code is
>> >> >> >> currently
>> >> >> >> at
>> >> >> >> [1]. A
>> >> >> >> standalone example can be found at [2].  Result is that the
>> >> >> >> WMS/WMTS
>> >> >> >> provider
>> >> >> >> opens connecting to the selected WMS/WMTS (good).  When clicking
>> >> >> >> 'Ok',
>> >> >> >> 'Close',
>> >> >> >> or 'Add', the WMS/WMTS layer is added (expecting 'Close' to
>> >> >> >> simply
>> >> >> >> close the dialog
>> >> >> >> and 'Ok' to add the layer and then close).  Finally clicking the
>> >> >> >> 'X'
>> >> >> >> (top right) closes
>> >> >> >> the dialog as expected.
>> >> >> >>
>> >> >> >> - are there other slots to call instead?
>> >> >> >> - should the Data Source Manager be used instead [3]?  Are there
>> >> >> >> plans
>> >> >> >> for providing
>> >> >> >> Python binding to this?
>> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > I can't tell if it's a good idea, but you can definitely add
>> >> >> > whatever
>> >> >> > you
>> >> >> > want to the DataSourceManager dialog with plain python:
>> >> >> >
>> >> >> > class ConcreteDataSourceWidget(QgsAbstractDataSourceWidget):
>> >> >> > pass
>> >> >> >
>> >> >> > class ConcreteSourceSelectProvider(QgsSourceSelectProvider):
>> >> >> >
>> >> >> > def providerKey(self):
>> >> >> > return "MyTestProviderKey"
>> >> >> >
>> >> >> > def text(self):
>> >> >> > return "MyTestProviderText"
>> >> >> >
>> >> >> > def icon(self):
>> >> >> > return QIcon()
>> >> >> >
>> >> >> > def createDataSourceWidget(self):
>> >> >> > return ConcreteDataSourceWidget()
>> >> >> >
>> >> >> > def ordering(self):
>> >> >> > return 1
>> >> >> >
>> >> >> > registry = QgsSourceSelectProviderRegistry()
>> >> >> > registry.addProvider(ConcreteSourceSelectProvider())
>> >> >> >
>> >> >> > Note that the DataSourceManager dialog is created when QGIS
>> >> >> > starts,
>> >> >> > you
>> >> >> > will
>> >> >> > want to register your provider early in the startup process, for
>> >> >> > now,
>> >> >> > there
>> >> >> > is no way to refresh the dialog after it has been constructed.
>> >> >> >
>> >> >>
>> >> >> Thanks Alessandro.  Is this example to add a provider type?
>> >> >> MetaSearch
>> >> >> simply wants to open a given existing provider dialog, open based on
>> >> >> a
>> >> >> given
>> >> >> provider type and let the user interact from there.
>> >> >>
>> >> >> ..Tom
>> >> >
>> >> >
>> >> >
>> >> > Yes, that's the way to add a new "provider" (it does not really need
>> >> > to
>> >> > be a
>> >> > provider) to the items in the data source manager dialog.
>> >> >
>> >> > Maybe you wanted to use this:
>> >> >
>> >> >
>> >> > http://qgis.org/api/classQgsDataSourceManagerDialog.html#a6b9046d38467a13ec321a70166bff289
>> >> >
>> >>
>> >> Thanks Alessandro.  Is QgsDataSourceManagerDialog planned to be
>> >> available via Python?  See:
>> >>
>> >> http://qgis.org/api/classQgsDataSourceManagerDialog.html (docs say not
>> >> available in Python
>> >> bindings)
>> >>
>> >
>> >
>> > Yes, that was planned. The idea was to build a generic re-usable widget
>> > to
>> > select data sources.
>> >
>> > But you are probably talking about exposing it through iface, correct?
>> >
>>
>> Would that work currently/is that possible?  At this point the main
>> goal is to fix MetaSearch [1]
>> in master given the changes to the data source/provider dialogs.
>>
>> [1]
>> https://github.com/qgis/QGIS/blob/master/python/plugins/MetaSearch/dialogs/maindialog.py#L754-L792
>>
>> >
>> >
>> >
>> >>
>> >>
>> >> > Btw you can also get the individual source selects from provider
>> >> > registry:
>> >> > QgsProviderRegistry.instance().createSelectionWidget('ogr').show()
>> >> >
>>

Re: [QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Alessandro Pasotti

I think you can try this first: the WMS 'on_btnConnect_clicked' slot has
been renamed to  'btnConnect_clicked'



On Mon, Nov 13, 2017 at 4:37 PM, Tom Kralidis  wrote:

> On Mon, Nov 13, 2017 at 10:32 AM, Alessandro Pasotti 
> wrote:
> > On Mon, Nov 13, 2017 at 4:24 PM, Tom Kralidis 
> wrote:
> >>
> >> On Mon, Nov 13, 2017 at 10:17 AM, Alessandro Pasotti <
> apaso...@gmail.com>
> >> wrote:
> >> > On Mon, Nov 13, 2017 at 3:59 PM, Tom Kralidis 
> >> > wrote:
> >> >>
> >> >> On Mon, Nov 13, 2017 at 9:18 AM, Alessandro Pasotti
> >> >> 
> >> >> wrote:
> >> >> > On Mon, Nov 13, 2017 at 3:06 PM, Tom Kralidis <
> tomkrali...@gmail.com>
> >> >> > wrote:
> >> >> >>
> >> >> >> Hi devs:
> >> >> >>
> >> >> >> Given https://issues.qgis.org/issues/17347 I'm working on fixing
> >> >> >> MetaSearch
> >> >> >> provider connections in master. The core part of the code is
> >> >> >> currently
> >> >> >> at
> >> >> >> [1]. A
> >> >> >> standalone example can be found at [2].  Result is that the
> WMS/WMTS
> >> >> >> provider
> >> >> >> opens connecting to the selected WMS/WMTS (good).  When clicking
> >> >> >> 'Ok',
> >> >> >> 'Close',
> >> >> >> or 'Add', the WMS/WMTS layer is added (expecting 'Close' to simply
> >> >> >> close the dialog
> >> >> >> and 'Ok' to add the layer and then close).  Finally clicking the
> 'X'
> >> >> >> (top right) closes
> >> >> >> the dialog as expected.
> >> >> >>
> >> >> >> - are there other slots to call instead?
> >> >> >> - should the Data Source Manager be used instead [3]?  Are there
> >> >> >> plans
> >> >> >> for providing
> >> >> >> Python binding to this?
> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > I can't tell if it's a good idea, but you can definitely add
> whatever
> >> >> > you
> >> >> > want to the DataSourceManager dialog with plain python:
> >> >> >
> >> >> > class ConcreteDataSourceWidget(QgsAbstractDataSourceWidget):
> >> >> > pass
> >> >> >
> >> >> > class ConcreteSourceSelectProvider(QgsSourceSelectProvider):
> >> >> >
> >> >> > def providerKey(self):
> >> >> > return "MyTestProviderKey"
> >> >> >
> >> >> > def text(self):
> >> >> > return "MyTestProviderText"
> >> >> >
> >> >> > def icon(self):
> >> >> > return QIcon()
> >> >> >
> >> >> > def createDataSourceWidget(self):
> >> >> > return ConcreteDataSourceWidget()
> >> >> >
> >> >> > def ordering(self):
> >> >> > return 1
> >> >> >
> >> >> > registry = QgsSourceSelectProviderRegistry()
> >> >> > registry.addProvider(ConcreteSourceSelectProvider())
> >> >> >
> >> >> > Note that the DataSourceManager dialog is created when QGIS starts,
> >> >> > you
> >> >> > will
> >> >> > want to register your provider early in the startup process, for
> now,
> >> >> > there
> >> >> > is no way to refresh the dialog after it has been constructed.
> >> >> >
> >> >>
> >> >> Thanks Alessandro.  Is this example to add a provider type?
> MetaSearch
> >> >> simply wants to open a given existing provider dialog, open based on
> a
> >> >> given
> >> >> provider type and let the user interact from there.
> >> >>
> >> >> ..Tom
> >> >
> >> >
> >> >
> >> > Yes, that's the way to add a new "provider" (it does not really need
> to
> >> > be a
> >> > provider) to the items in the data source manager dialog.
> >> >
> >> > Maybe you wanted to use this:
> >> >
> >> > http://qgis.org/api/classQgsDataSourceManagerDialog.html#
> a6b9046d38467a13ec321a70166bff289
> >> >
> >>
> >> Thanks Alessandro.  Is QgsDataSourceManagerDialog planned to be
> >> available via Python?  See:
> >>
> >> http://qgis.org/api/classQgsDataSourceManagerDialog.html (docs say not
> >> available in Python
> >> bindings)
> >>
> >
> >
> > Yes, that was planned. The idea was to build a generic re-usable widget
> to
> > select data sources.
> >
> > But you are probably talking about exposing it through iface, correct?
> >
>
> Would that work currently/is that possible?  At this point the main
> goal is to fix MetaSearch [1]
> in master given the changes to the data source/provider dialogs.
>
> [1] https://github.com/qgis/QGIS/blob/master/python/plugins/
> MetaSearch/dialogs/maindialog.py#L754-L792
>
> >
> >
> >
> >>
> >>
> >> > Btw you can also get the individual source selects from provider
> >> > registry:
> >> > QgsProviderRegistry.instance().createSelectionWidget('ogr').show()
> >> >
> >>
> >> This is exactly what MetaSearch is doing currently which results in the
> >> issues originally mentioned.
> >>
> >> ..Tom
> >>
> >> >
> >> >
> >> > Cheers.
> >> >
> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> >>
> >> >> >>
> >> >> >> Thanks
> >> >> >>
> >> >> >> ..Tom
> >> >> >>
> >> >> >> [1]
> >> >> >>
> >> >> >>
> >> >> >> https://github.com/qgis/QGIS/blob/master/python/plugins/
> MetaSearch/dialogs/maindialog.py#L759-L792
> >> >> >> [2]
> >> >> >> https://gist.github.com/tomkralidis/
> dccb49efa760a585be38ee0c3188b8b3
> >>

Re: [QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Tom Kralidis

On Mon, Nov 13, 2017 at 10:32 AM, Alessandro Pasotti  wrote:
> On Mon, Nov 13, 2017 at 4:24 PM, Tom Kralidis  wrote:
>>
>> On Mon, Nov 13, 2017 at 10:17 AM, Alessandro Pasotti 
>> wrote:
>> > On Mon, Nov 13, 2017 at 3:59 PM, Tom Kralidis 
>> > wrote:
>> >>
>> >> On Mon, Nov 13, 2017 at 9:18 AM, Alessandro Pasotti
>> >> 
>> >> wrote:
>> >> > On Mon, Nov 13, 2017 at 3:06 PM, Tom Kralidis 
>> >> > wrote:
>> >> >>
>> >> >> Hi devs:
>> >> >>
>> >> >> Given https://issues.qgis.org/issues/17347 I'm working on fixing
>> >> >> MetaSearch
>> >> >> provider connections in master. The core part of the code is
>> >> >> currently
>> >> >> at
>> >> >> [1]. A
>> >> >> standalone example can be found at [2].  Result is that the WMS/WMTS
>> >> >> provider
>> >> >> opens connecting to the selected WMS/WMTS (good).  When clicking
>> >> >> 'Ok',
>> >> >> 'Close',
>> >> >> or 'Add', the WMS/WMTS layer is added (expecting 'Close' to simply
>> >> >> close the dialog
>> >> >> and 'Ok' to add the layer and then close).  Finally clicking the 'X'
>> >> >> (top right) closes
>> >> >> the dialog as expected.
>> >> >>
>> >> >> - are there other slots to call instead?
>> >> >> - should the Data Source Manager be used instead [3]?  Are there
>> >> >> plans
>> >> >> for providing
>> >> >> Python binding to this?
>>
>> >> >
>> >> >
>> >> >
>> >> > I can't tell if it's a good idea, but you can definitely add whatever
>> >> > you
>> >> > want to the DataSourceManager dialog with plain python:
>> >> >
>> >> > class ConcreteDataSourceWidget(QgsAbstractDataSourceWidget):
>> >> > pass
>> >> >
>> >> > class ConcreteSourceSelectProvider(QgsSourceSelectProvider):
>> >> >
>> >> > def providerKey(self):
>> >> > return "MyTestProviderKey"
>> >> >
>> >> > def text(self):
>> >> > return "MyTestProviderText"
>> >> >
>> >> > def icon(self):
>> >> > return QIcon()
>> >> >
>> >> > def createDataSourceWidget(self):
>> >> > return ConcreteDataSourceWidget()
>> >> >
>> >> > def ordering(self):
>> >> > return 1
>> >> >
>> >> > registry = QgsSourceSelectProviderRegistry()
>> >> > registry.addProvider(ConcreteSourceSelectProvider())
>> >> >
>> >> > Note that the DataSourceManager dialog is created when QGIS starts,
>> >> > you
>> >> > will
>> >> > want to register your provider early in the startup process, for now,
>> >> > there
>> >> > is no way to refresh the dialog after it has been constructed.
>> >> >
>> >>
>> >> Thanks Alessandro.  Is this example to add a provider type?  MetaSearch
>> >> simply wants to open a given existing provider dialog, open based on a
>> >> given
>> >> provider type and let the user interact from there.
>> >>
>> >> ..Tom
>> >
>> >
>> >
>> > Yes, that's the way to add a new "provider" (it does not really need to
>> > be a
>> > provider) to the items in the data source manager dialog.
>> >
>> > Maybe you wanted to use this:
>> >
>> > http://qgis.org/api/classQgsDataSourceManagerDialog.html#a6b9046d38467a13ec321a70166bff289
>> >
>>
>> Thanks Alessandro.  Is QgsDataSourceManagerDialog planned to be
>> available via Python?  See:
>>
>> http://qgis.org/api/classQgsDataSourceManagerDialog.html (docs say not
>> available in Python
>> bindings)
>>
>
>
> Yes, that was planned. The idea was to build a generic re-usable widget to
> select data sources.
>
> But you are probably talking about exposing it through iface, correct?
>

Would that work currently/is that possible?  At this point the main
goal is to fix MetaSearch [1]
in master given the changes to the data source/provider dialogs.

[1] 
https://github.com/qgis/QGIS/blob/master/python/plugins/MetaSearch/dialogs/maindialog.py#L754-L792

>
>
>
>>
>>
>> > Btw you can also get the individual source selects from provider
>> > registry:
>> > QgsProviderRegistry.instance().createSelectionWidget('ogr').show()
>> >
>>
>> This is exactly what MetaSearch is doing currently which results in the
>> issues originally mentioned.
>>
>> ..Tom
>>
>> >
>> >
>> > Cheers.
>> >
>> >>
>> >> >
>> >> >
>> >> >
>> >> >>
>> >> >>
>> >> >> Thanks
>> >> >>
>> >> >> ..Tom
>> >> >>
>> >> >> [1]
>> >> >>
>> >> >>
>> >> >> https://github.com/qgis/QGIS/blob/master/python/plugins/MetaSearch/dialogs/maindialog.py#L759-L792
>> >> >> [2]
>> >> >> https://gist.github.com/tomkralidis/dccb49efa760a585be38ee0c3188b8b3
>> >> >> [3] http://qgis.org/api/classQgsDataSourceManagerDialog.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
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Alessandro Pasotti
>> >> > w3:   www.itopen.it
>> >
>> >
>> >
>> >
>> > --
>> > Alessandro Pasotti
>> > w3:

Re: [QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Alessandro Pasotti

On Mon, Nov 13, 2017 at 4:24 PM, Tom Kralidis  wrote:

> On Mon, Nov 13, 2017 at 10:17 AM, Alessandro Pasotti 
> wrote:
> > On Mon, Nov 13, 2017 at 3:59 PM, Tom Kralidis 
> wrote:
> >>
> >> On Mon, Nov 13, 2017 at 9:18 AM, Alessandro Pasotti  >
> >> wrote:
> >> > On Mon, Nov 13, 2017 at 3:06 PM, Tom Kralidis 
> >> > wrote:
> >> >>
> >> >> Hi devs:
> >> >>
> >> >> Given https://issues.qgis.org/issues/17347 I'm working on fixing
> >> >> MetaSearch
> >> >> provider connections in master. The core part of the code is
> currently
> >> >> at
> >> >> [1]. A
> >> >> standalone example can be found at [2].  Result is that the WMS/WMTS
> >> >> provider
> >> >> opens connecting to the selected WMS/WMTS (good).  When clicking
> 'Ok',
> >> >> 'Close',
> >> >> or 'Add', the WMS/WMTS layer is added (expecting 'Close' to simply
> >> >> close the dialog
> >> >> and 'Ok' to add the layer and then close).  Finally clicking the 'X'
> >> >> (top right) closes
> >> >> the dialog as expected.
> >> >>
> >> >> - are there other slots to call instead?
> >> >> - should the Data Source Manager be used instead [3]?  Are there
> plans
> >> >> for providing
> >> >> Python binding to this?
>
>> >
> >> >
> >> >
> >> > I can't tell if it's a good idea, but you can definitely add whatever
> >> > you
> >> > want to the DataSourceManager dialog with plain python:
> >> >
> >> > class ConcreteDataSourceWidget(QgsAbstractDataSourceWidget):
> >> > pass
> >> >
> >> > class ConcreteSourceSelectProvider(QgsSourceSelectProvider):
> >> >
> >> > def providerKey(self):
> >> > return "MyTestProviderKey"
> >> >
> >> > def text(self):
> >> > return "MyTestProviderText"
> >> >
> >> > def icon(self):
> >> > return QIcon()
> >> >
> >> > def createDataSourceWidget(self):
> >> > return ConcreteDataSourceWidget()
> >> >
> >> > def ordering(self):
> >> > return 1
> >> >
> >> > registry = QgsSourceSelectProviderRegistry()
> >> > registry.addProvider(ConcreteSourceSelectProvider())
> >> >
> >> > Note that the DataSourceManager dialog is created when QGIS starts,
> you
> >> > will
> >> > want to register your provider early in the startup process, for now,
> >> > there
> >> > is no way to refresh the dialog after it has been constructed.
> >> >
> >>
> >> Thanks Alessandro.  Is this example to add a provider type?  MetaSearch
> >> simply wants to open a given existing provider dialog, open based on a
> >> given
> >> provider type and let the user interact from there.
> >>
> >> ..Tom
> >
> >
> >
> > Yes, that's the way to add a new "provider" (it does not really need to
> be a
> > provider) to the items in the data source manager dialog.
> >
> > Maybe you wanted to use this:
> > http://qgis.org/api/classQgsDataSourceManagerDialog.html#
> a6b9046d38467a13ec321a70166bff289
> >
>
> Thanks Alessandro.  Is QgsDataSourceManagerDialog planned to be
> available via Python?  See:
>
> http://qgis.org/api/classQgsDataSourceManagerDialog.html (docs say not
> available in Python
> bindings)
>
>

Yes, that was planned. The idea was to build a generic re-usable widget to
select data sources.

But you are probably talking about exposing it through iface, correct?





>
> > Btw you can also get the individual source selects from provider
> registry:
> > QgsProviderRegistry.instance().createSelectionWidget('ogr').show()
> >
>
> This is exactly what MetaSearch is doing currently which results in the
> issues originally mentioned.
>
> ..Tom
>
> >
> >
> > Cheers.
> >
> >>
> >> >
> >> >
> >> >
> >> >>
> >> >>
> >> >> Thanks
> >> >>
> >> >> ..Tom
> >> >>
> >> >> [1]
> >> >>
> >> >> https://github.com/qgis/QGIS/blob/master/python/plugins/
> MetaSearch/dialogs/maindialog.py#L759-L792
> >> >> [2]
> >> >> https://gist.github.com/tomkralidis/dccb49efa760a585be38ee0c3188b8b3
> >> >> [3] http://qgis.org/api/classQgsDataSourceManagerDialog.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
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Alessandro Pasotti
> >> > w3:   www.itopen.it
> >
> >
> >
> >
> > --
> > Alessandro Pasotti
> > w3:   www.itopen.it
>



-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Tom Kralidis

On Mon, Nov 13, 2017 at 10:17 AM, Alessandro Pasotti  wrote:
> On Mon, Nov 13, 2017 at 3:59 PM, Tom Kralidis  wrote:
>>
>> On Mon, Nov 13, 2017 at 9:18 AM, Alessandro Pasotti 
>> wrote:
>> > On Mon, Nov 13, 2017 at 3:06 PM, Tom Kralidis 
>> > wrote:
>> >>
>> >> Hi devs:
>> >>
>> >> Given https://issues.qgis.org/issues/17347 I'm working on fixing
>> >> MetaSearch
>> >> provider connections in master. The core part of the code is currently
>> >> at
>> >> [1]. A
>> >> standalone example can be found at [2].  Result is that the WMS/WMTS
>> >> provider
>> >> opens connecting to the selected WMS/WMTS (good).  When clicking 'Ok',
>> >> 'Close',
>> >> or 'Add', the WMS/WMTS layer is added (expecting 'Close' to simply
>> >> close the dialog
>> >> and 'Ok' to add the layer and then close).  Finally clicking the 'X'
>> >> (top right) closes
>> >> the dialog as expected.
>> >>
>> >> - are there other slots to call instead?
>> >> - should the Data Source Manager be used instead [3]?  Are there plans
>> >> for providing
>> >> Python binding to this?
>> >
>> >
>> >
>> > I can't tell if it's a good idea, but you can definitely add whatever
>> > you
>> > want to the DataSourceManager dialog with plain python:
>> >
>> > class ConcreteDataSourceWidget(QgsAbstractDataSourceWidget):
>> > pass
>> >
>> > class ConcreteSourceSelectProvider(QgsSourceSelectProvider):
>> >
>> > def providerKey(self):
>> > return "MyTestProviderKey"
>> >
>> > def text(self):
>> > return "MyTestProviderText"
>> >
>> > def icon(self):
>> > return QIcon()
>> >
>> > def createDataSourceWidget(self):
>> > return ConcreteDataSourceWidget()
>> >
>> > def ordering(self):
>> > return 1
>> >
>> > registry = QgsSourceSelectProviderRegistry()
>> > registry.addProvider(ConcreteSourceSelectProvider())
>> >
>> > Note that the DataSourceManager dialog is created when QGIS starts, you
>> > will
>> > want to register your provider early in the startup process, for now,
>> > there
>> > is no way to refresh the dialog after it has been constructed.
>> >
>>
>> Thanks Alessandro.  Is this example to add a provider type?  MetaSearch
>> simply wants to open a given existing provider dialog, open based on a
>> given
>> provider type and let the user interact from there.
>>
>> ..Tom
>
>
>
> Yes, that's the way to add a new "provider" (it does not really need to be a
> provider) to the items in the data source manager dialog.
>
> Maybe you wanted to use this:
> http://qgis.org/api/classQgsDataSourceManagerDialog.html#a6b9046d38467a13ec321a70166bff289
>

Thanks Alessandro.  Is QgsDataSourceManagerDialog planned to be
available via Python?  See:

http://qgis.org/api/classQgsDataSourceManagerDialog.html (docs say not
available in Python
bindings)


> Btw you can also get the individual source selects from provider registry:
> QgsProviderRegistry.instance().createSelectionWidget('ogr').show()
>

This is exactly what MetaSearch is doing currently which results in the
issues originally mentioned.

..Tom

>
>
> Cheers.
>
>>
>> >
>> >
>> >
>> >>
>> >>
>> >> Thanks
>> >>
>> >> ..Tom
>> >>
>> >> [1]
>> >>
>> >> https://github.com/qgis/QGIS/blob/master/python/plugins/MetaSearch/dialogs/maindialog.py#L759-L792
>> >> [2]
>> >> https://gist.github.com/tomkralidis/dccb49efa760a585be38ee0c3188b8b3
>> >> [3] http://qgis.org/api/classQgsDataSourceManagerDialog.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
>> >
>> >
>> >
>> >
>> > --
>> > Alessandro Pasotti
>> > w3:   www.itopen.it
>
>
>
>
> --
> Alessandro Pasotti
> w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Alessandro Pasotti

On Mon, Nov 13, 2017 at 3:59 PM, Tom Kralidis  wrote:

> On Mon, Nov 13, 2017 at 9:18 AM, Alessandro Pasotti 
> wrote:
> > On Mon, Nov 13, 2017 at 3:06 PM, Tom Kralidis 
> wrote:
> >>
> >> Hi devs:
> >>
> >> Given https://issues.qgis.org/issues/17347 I'm working on fixing
> >> MetaSearch
> >> provider connections in master. The core part of the code is currently
> at
> >> [1]. A
> >> standalone example can be found at [2].  Result is that the WMS/WMTS
> >> provider
> >> opens connecting to the selected WMS/WMTS (good).  When clicking 'Ok',
> >> 'Close',
> >> or 'Add', the WMS/WMTS layer is added (expecting 'Close' to simply
> >> close the dialog
> >> and 'Ok' to add the layer and then close).  Finally clicking the 'X'
> >> (top right) closes
> >> the dialog as expected.
> >>
> >> - are there other slots to call instead?
> >> - should the Data Source Manager be used instead [3]?  Are there plans
> >> for providing
> >> Python binding to this?
> >
> >
> >
> > I can't tell if it's a good idea, but you can definitely add whatever you
> > want to the DataSourceManager dialog with plain python:
> >
> > class ConcreteDataSourceWidget(QgsAbstractDataSourceWidget):
> > pass
> >
> > class ConcreteSourceSelectProvider(QgsSourceSelectProvider):
> >
> > def providerKey(self):
> > return "MyTestProviderKey"
> >
> > def text(self):
> > return "MyTestProviderText"
> >
> > def icon(self):
> > return QIcon()
> >
> > def createDataSourceWidget(self):
> > return ConcreteDataSourceWidget()
> >
> > def ordering(self):
> > return 1
> >
> > registry = QgsSourceSelectProviderRegistry()
> > registry.addProvider(ConcreteSourceSelectProvider())
> >
> > Note that the DataSourceManager dialog is created when QGIS starts, you
> will
> > want to register your provider early in the startup process, for now,
> there
> > is no way to refresh the dialog after it has been constructed.
> >
>
> Thanks Alessandro.  Is this example to add a provider type?  MetaSearch
> simply wants to open a given existing provider dialog, open based on a
> given
> provider type and let the user interact from there.
>
> ..Tom
>


Yes, that's the way to add a new "provider" (it does not really need to be
a provider) to the items in the data source manager dialog.

Maybe you wanted to use this:
http://qgis.org/api/classQgsDataSourceManagerDialog.html#a6b9046d38467a13ec321a70166bff289

Btw you can also get the individual source selects from provider registry:
QgsProviderRegistry.instance().createSelectionWidget('ogr').show()



Cheers.


> >
> >
> >
> >>
> >>
> >> Thanks
> >>
> >> ..Tom
> >>
> >> [1]
> >> https://github.com/qgis/QGIS/blob/master/python/plugins/
> MetaSearch/dialogs/maindialog.py#L759-L792
> >> [2] https://gist.github.com/tomkralidis/dccb49efa760a585be38ee0c3188b8
> b3
> >> [3] http://qgis.org/api/classQgsDataSourceManagerDialog.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
> >
> >
> >
> >
> > --
> > Alessandro Pasotti
> > w3:   www.itopen.it
>



-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Tom Kralidis

On Mon, Nov 13, 2017 at 9:18 AM, Alessandro Pasotti  wrote:
> On Mon, Nov 13, 2017 at 3:06 PM, Tom Kralidis  wrote:
>>
>> Hi devs:
>>
>> Given https://issues.qgis.org/issues/17347 I'm working on fixing
>> MetaSearch
>> provider connections in master. The core part of the code is currently at
>> [1]. A
>> standalone example can be found at [2].  Result is that the WMS/WMTS
>> provider
>> opens connecting to the selected WMS/WMTS (good).  When clicking 'Ok',
>> 'Close',
>> or 'Add', the WMS/WMTS layer is added (expecting 'Close' to simply
>> close the dialog
>> and 'Ok' to add the layer and then close).  Finally clicking the 'X'
>> (top right) closes
>> the dialog as expected.
>>
>> - are there other slots to call instead?
>> - should the Data Source Manager be used instead [3]?  Are there plans
>> for providing
>> Python binding to this?
>
>
>
> I can't tell if it's a good idea, but you can definitely add whatever you
> want to the DataSourceManager dialog with plain python:
>
> class ConcreteDataSourceWidget(QgsAbstractDataSourceWidget):
> pass
>
> class ConcreteSourceSelectProvider(QgsSourceSelectProvider):
>
> def providerKey(self):
> return "MyTestProviderKey"
>
> def text(self):
> return "MyTestProviderText"
>
> def icon(self):
> return QIcon()
>
> def createDataSourceWidget(self):
> return ConcreteDataSourceWidget()
>
> def ordering(self):
> return 1
>
> registry = QgsSourceSelectProviderRegistry()
> registry.addProvider(ConcreteSourceSelectProvider())
>
> Note that the DataSourceManager dialog is created when QGIS starts, you will
> want to register your provider early in the startup process, for now, there
> is no way to refresh the dialog after it has been constructed.
>

Thanks Alessandro.  Is this example to add a provider type?  MetaSearch
simply wants to open a given existing provider dialog, open based on a given
provider type and let the user interact from there.

..Tom

>
>
>
>>
>>
>> Thanks
>>
>> ..Tom
>>
>> [1]
>> https://github.com/qgis/QGIS/blob/master/python/plugins/MetaSearch/dialogs/maindialog.py#L759-L792
>> [2] https://gist.github.com/tomkralidis/dccb49efa760a585be38ee0c3188b8b3
>> [3] http://qgis.org/api/classQgsDataSourceManagerDialog.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
>
>
>
>
> --
> Alessandro Pasotti
> w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QgsServer and 3d tiles

2017-11-13 Thread G. Allegri

I see your point Vincent. I'm not planning to implement it and I don't have
a strong opinion on the right design. From a user point of view it doesn't
mske much difference either. So, no problem to converge :)
I agree also on I3S being an Esri oriented standard (as it's been for
GeoPackage, or KML for Google). Well the same could be said for 3D Tiles /
gtTF and AGI, don't you think? Same as before, I totally respect the
choices of who's putting resources on concrete development. It's just to
share thoughts and opinions.

giovanni

Il 13 nov 2017 2:49 PM, "Vincent Picavet (ml)"  ha
scritto:

Hello,

On 09/11/2017 16:49, G. Allegri wrote:
> Hi Vincent,
> I agree tiled static data can, and should, be served as static content
> but what I meant was having something like Tilestache, GeoWebCache,
> MapCache, etc.. They're meant to render and cache on the fly, or
> preseeding the tileset.
>
> My question raised from the fact that QGIS 3D renderer could be a common
> base to produce terrain meshes (a la Cesium) and 3D tiles, both for the
> desktop 3D viewer and for a cached tileset to be served through HTTP.

I would rather have a dedicated terrain mesh generator first, which
could be embedded in QGIS 3D later on. Generating a terrain mesh is a
data processing action, not a rendering one. We should tackle the
problem in this order, or we will end up with code less efficient and
less generic.

> QgsServer could use the same code base to populate the cache, but this
> doesn't prevent having a Processing tool (ore whatever) doing the work
> in advance.

I think we agree on the general issue, but have a different point of
view on the design process. We should converge at some point :-)

> You're working with gltf. What about OGC I3S?

I3S is, like other examples, a standard pushed by ESRI for ESRI
products. It has been designed by ESRI and pushed forward to OGC
community standard in a desire not to adopt 3D tiles.
I do not say that I3S is a bad technical standard. But it is just
another effort from ESRI to favor its own specific formats instead of
collaborating on a real "community" standard.

It is therefore not a strong incentive to dedicate efforts for an
opensource implementation.
If there was funding for it, we could implement it too, as the
specifications are open. But priority goes to 3DTiles as far as we are
concerned.

Regards,
Vincent

>
> giovanni
>
> Il 9 nov 2017 16:29, "Vincent Picavet (ml)"  > ha scritto:
>
> Hello,
>
> On 03/11/2017 21:04, G. Allegri wrote:
> > What if we had a QgsServer service dedicates to serving 3d tiles for
> > Cesium or iTowns?
> > Is anybody working on this?
>
> At Oslandia, we work on 3D topics a lot, and 3d tiles in particular.
We
> are implementing 3D Tiles support in iTowns, and several components to
> serve this format as webservices.
>
> E.g. :
> - https://github.com/Oslandia/building-server
> 
> - https://github.com/Oslandia/lopocs
> 
>
> I do not think having QGIS Server serving 3D tiles is a really good
> idea.
>
> First, 3D tiles is a format ( and protocol) to serve tiles of objects
in
> a mostly static way. Therefore, what would be interesting is for QGIS
to
> have a way to export data as 3d Tiles. These tiles can then be served
> with a simple HTTP server, no need for a QGIS Server component.
>
> Moreover, there are a lot of use cases where we want to serve 3D Tiles
> without using QGIS at all. Component-oriented architecture is better
> than monolithic software.
>
> What I see as best approach would be to mutualize as much code as
> possible regarding 3D tiles in py3dtiles :
> https://github.com/Oslandia/py3dtiles
> 
>
> Using this module, we can write a 3dtile exporter, as a Processing
> module for example. We already have some draft code to do that for
some
> data sets.
> Then, we could have an independant 3D tiles server reusing py3dtiles,
or
> integrate this as QGIS Server module if we want.
>
> We would be happy to work on these subjects and share our experience
on
> all 3D-related topics. Funding is also very welcome.
>
> But for now, I think we should focus on releasing QGIS3 in a usable
> state. We have waited for too long, and there is still work to achieve
> to stabilize the release.
>
> 3D features can wait a bit more, even if call for interest, needs,
> funding and collaboration is welcome.
>
> Best regards,
> Vincent
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org 
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>

Re: [QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Alessandro Pasotti

On Mon, Nov 13, 2017 at 3:06 PM, Tom Kralidis  wrote:

> Hi devs:
>
> Given https://issues.qgis.org/issues/17347 I'm working on fixing
> MetaSearch
> provider connections in master. The core part of the code is currently at
> [1]. A
> standalone example can be found at [2].  Result is that the WMS/WMTS
> provider
> opens connecting to the selected WMS/WMTS (good).  When clicking 'Ok',
> 'Close',
> or 'Add', the WMS/WMTS layer is added (expecting 'Close' to simply
> close the dialog
> and 'Ok' to add the layer and then close).  Finally clicking the 'X'
> (top right) closes
> the dialog as expected.
>
> - are there other slots to call instead?
> - should the Data Source Manager be used instead [3]?  Are there plans
> for providing
> Python binding to this?
>


I can't tell if it's a good idea, but you can definitely add whatever you
want to the DataSourceManager dialog with plain python:

class ConcreteDataSourceWidget(QgsAbstractDataSourceWidget):
pass

class ConcreteSourceSelectProvider(QgsSourceSelectProvider):

def providerKey(self):
return "MyTestProviderKey"

def text(self):
return "MyTestProviderText"

def icon(self):
return QIcon()

def createDataSourceWidget(self):
return ConcreteDataSourceWidget()

def ordering(self):
return 1

registry = QgsSourceSelectProviderRegistry()
registry.addProvider(ConcreteSourceSelectProvider())

Note that the DataSourceManager dialog is created when QGIS starts, you
will want to register your provider early in the startup process, for now,
there is no way to refresh the dialog after it has been constructed.





>
> Thanks
>
> ..Tom
>
> [1] https://github.com/qgis/QGIS/blob/master/python/plugins/
> MetaSearch/dialogs/maindialog.py#L759-L792
> [2] https://gist.github.com/tomkralidis/dccb49efa760a585be38ee0c3188b8b3
> [3] http://qgis.org/api/classQgsDataSourceManagerDialog.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




-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] MetaSearch provider connections in master

2017-11-13 Thread Tom Kralidis

Hi devs:

Given https://issues.qgis.org/issues/17347 I'm working on fixing MetaSearch
provider connections in master. The core part of the code is currently at [1]. A
standalone example can be found at [2].  Result is that the WMS/WMTS provider
opens connecting to the selected WMS/WMTS (good).  When clicking 'Ok', 'Close',
or 'Add', the WMS/WMTS layer is added (expecting 'Close' to simply
close the dialog
and 'Ok' to add the layer and then close).  Finally clicking the 'X'
(top right) closes
the dialog as expected.

- are there other slots to call instead?
- should the Data Source Manager be used instead [3]?  Are there plans
for providing
Python binding to this?

Thanks

..Tom

[1] 
https://github.com/qgis/QGIS/blob/master/python/plugins/MetaSearch/dialogs/maindialog.py#L759-L792
[2] https://gist.github.com/tomkralidis/dccb49efa760a585be38ee0c3188b8b3
[3] http://qgis.org/api/classQgsDataSourceManagerDialog.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] QgsServer and 3d tiles

2017-11-13 Thread Vincent Picavet (ml)

Hello,

On 09/11/2017 16:49, G. Allegri wrote:
> Hi Vincent,
> I agree tiled static data can, and should, be served as static content
> but what I meant was having something like Tilestache, GeoWebCache,
> MapCache, etc.. They're meant to render and cache on the fly, or
> preseeding the tileset.
> 
> My question raised from the fact that QGIS 3D renderer could be a common
> base to produce terrain meshes (a la Cesium) and 3D tiles, both for the
> desktop 3D viewer and for a cached tileset to be served through HTTP.

I would rather have a dedicated terrain mesh generator first, which
could be embedded in QGIS 3D later on. Generating a terrain mesh is a
data processing action, not a rendering one. We should tackle the
problem in this order, or we will end up with code less efficient and
less generic.

> QgsServer could use the same code base to populate the cache, but this
> doesn't prevent having a Processing tool (ore whatever) doing the work
> in advance.

I think we agree on the general issue, but have a different point of
view on the design process. We should converge at some point :-)

> You're working with gltf. What about OGC I3S?

I3S is, like other examples, a standard pushed by ESRI for ESRI
products. It has been designed by ESRI and pushed forward to OGC
community standard in a desire not to adopt 3D tiles.
I do not say that I3S is a bad technical standard. But it is just
another effort from ESRI to favor its own specific formats instead of
collaborating on a real "community" standard.

It is therefore not a strong incentive to dedicate efforts for an
opensource implementation.
If there was funding for it, we could implement it too, as the
specifications are open. But priority goes to 3DTiles as far as we are
concerned.

Regards,
Vincent




> 
> giovanni
> 
> Il 9 nov 2017 16:29, "Vincent Picavet (ml)"  > ha scritto:
> 
> Hello,
> 
> On 03/11/2017 21:04, G. Allegri wrote:
> > What if we had a QgsServer service dedicates to serving 3d tiles for
> > Cesium or iTowns?
> > Is anybody working on this?
> 
> At Oslandia, we work on 3D topics a lot, and 3d tiles in particular. We
> are implementing 3D Tiles support in iTowns, and several components to
> serve this format as webservices.
> 
> E.g. :
> - https://github.com/Oslandia/building-server
> 
> - https://github.com/Oslandia/lopocs
> 
> 
> I do not think having QGIS Server serving 3D tiles is a really good
> idea.
> 
> First, 3D tiles is a format ( and protocol) to serve tiles of objects in
> a mostly static way. Therefore, what would be interesting is for QGIS to
> have a way to export data as 3d Tiles. These tiles can then be served
> with a simple HTTP server, no need for a QGIS Server component.
> 
> Moreover, there are a lot of use cases where we want to serve 3D Tiles
> without using QGIS at all. Component-oriented architecture is better
> than monolithic software.
> 
> What I see as best approach would be to mutualize as much code as
> possible regarding 3D tiles in py3dtiles :
> https://github.com/Oslandia/py3dtiles
> 
> 
> Using this module, we can write a 3dtile exporter, as a Processing
> module for example. We already have some draft code to do that for some
> data sets.
> Then, we could have an independant 3D tiles server reusing py3dtiles, or
> integrate this as QGIS Server module if we want.
> 
> We would be happy to work on these subjects and share our experience on
> all 3D-related topics. Funding is also very welcome.
> 
> But for now, I think we should focus on releasing QGIS3 in a usable
> state. We have waited for too long, and there is still work to achieve
> to stabilize the release.
> 
> 3D features can wait a bit more, even if call for interest, needs,
> funding and collaboration is welcome.
> 
> Best regards,
> Vincent
> ___
> 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] QgsServer and 3d tiles

2017-11-13 Thread Vincent Picavet (ml)

Hello,

On 09/11/2017 16:49, G. Allegri wrote:
> Hi Vincent,
> I agree tiled static data can, and should, be served as static content
> but what I meant was having something like Tilestache, GeoWebCache,
> MapCache, etc.. They're meant to render and cache on the fly, or
> preseeding the tileset.
> 
> My question raised from the fact that QGIS 3D renderer could be a common
> base to produce terrain meshes (a la Cesium) and 3D tiles, both for the
> desktop 3D viewer and for a cached tileset to be served through HTTP.

I would rather have a dedicated terrain mesh generator first, which
could be embedded in QGIS 3D later on. Generating a terrain mesh is a
data processing action, not a rendering one. We should tackle the
problem in this order, or we will end up with code less efficient and
less generic.

> QgsServer could use the same code base to populate the cache, but this
> doesn't prevent having a Processing tool (ore whatever) doing the work
> in advance.

I think we agree on the general issue, but have a different point of
view on the design process. We should converge at some point :-)

> You're working with gltf. What about OGC I3S?

I3S is, like other examples, a standard pushed by ESRI for ESRI
products. It has been designed by ESRI and pushed forward to OGC
community standard in a desire not to adopt 3D tiles.
I do not say that I3S is a bad technical standard. But it is just
another effort from ESRI to favor its own specific formats instead of
collaborating on a real "community" standard.

It is therefore not a strong incentive to dedicate efforts for an
opensource implementation.
If there was funding for it, we could implement it too, as the
specifications are open. But priority goes to 3DTiles as far as we are
concerned.

Regards,
Vincent




> 
> giovanni
> 
> Il 9 nov 2017 16:29, "Vincent Picavet (ml)"  > ha scritto:
> 
> Hello,
> 
> On 03/11/2017 21:04, G. Allegri wrote:
> > What if we had a QgsServer service dedicates to serving 3d tiles for
> > Cesium or iTowns?
> > Is anybody working on this?
> 
> At Oslandia, we work on 3D topics a lot, and 3d tiles in particular. We
> are implementing 3D Tiles support in iTowns, and several components to
> serve this format as webservices.
> 
> E.g. :
> - https://github.com/Oslandia/building-server
> 
> - https://github.com/Oslandia/lopocs
> 
> 
> I do not think having QGIS Server serving 3D tiles is a really good
> idea.
> 
> First, 3D tiles is a format ( and protocol) to serve tiles of objects in
> a mostly static way. Therefore, what would be interesting is for QGIS to
> have a way to export data as 3d Tiles. These tiles can then be served
> with a simple HTTP server, no need for a QGIS Server component.
> 
> Moreover, there are a lot of use cases where we want to serve 3D Tiles
> without using QGIS at all. Component-oriented architecture is better
> than monolithic software.
> 
> What I see as best approach would be to mutualize as much code as
> possible regarding 3D tiles in py3dtiles :
> https://github.com/Oslandia/py3dtiles
> 
> 
> Using this module, we can write a 3dtile exporter, as a Processing
> module for example. We already have some draft code to do that for some
> data sets.
> Then, we could have an independant 3D tiles server reusing py3dtiles, or
> integrate this as QGIS Server module if we want.
> 
> We would be happy to work on these subjects and share our experience on
> all 3D-related topics. Funding is also very welcome.
> 
> But for now, I think we should focus on releasing QGIS3 in a usable
> state. We have waited for too long, and there is still work to achieve
> to stabilize the release.
> 
> 3D features can wait a bit more, even if call for interest, needs,
> funding and collaboration is welcome.
> 
> Best regards,
> Vincent
> ___
> 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] discuss: What's our development gameplan for 3.0 and above?

2017-11-13 Thread Alessandro Pasotti

On Sat, Nov 11, 2017 at 10:27 AM, Richard Duivenvoorde 
wrote:

> On 11-11-17 01:03, Nyall Dawson wrote:
> > The "TLDW" for interested parties:
> > - Qt containers (qlist, qvector, qmap, etc) are unmaintained, They
> > won't be removed by upstream, but you shouldn't use them if you have a
> > choice
> > - QList is absolute rubbish and should never be used, unless you're
> > forced to by Qt API. It's likely to be killed in Qt 6 (becoming just
> > an alias for QVector)
>

Here are my (very subjective) reasons for choosing one or the other approach

WHY USING MAINLY/ONLY QT API
- Qt API is well documented with examples on http://doc.qt.io/qt-5/ and
using a single API instead of a mix it's a clear advantage (you don't have
to constantly ask yourself which API you need to use in a particular call)
- Qt API is simple and intuitive
- Qt API is more readable (camel case, no std:: etc.)
- Qt Containers are simple to use and cheap to copy (with caveats)
- QString has no real alternative for UTF8


WHY USING MAINLY/ONLY STL API
- Qt Containers are not for-range loop friendly (detach issues)
- Qt Containers are kind of deprecated
- STL is part of a standard, may lower barriers to entry for not-Qt devs


CONCLUSIONS
- I feel that the real motivation is to stay away from Qt containers, if it
wasn't for them we would not probably be here discussing in the first place
- I'd try as much as possible to avoid mixing two APIs: if we go for STL,
let's try to minimize Qt API usage or constraint it to certain domains (for
example: QStrings manipulation, dispatcher, GUI)
- no strong opinions here, but the greatest danger is to not decide: we'll
end up with a mixture of APIs and styles and code reviews will become
completely arbitrary, with people asked to switch API depending on who
reviews the code (and when the review is made)
- whatever we agree upon, it *must* be documented clearly in coding
guidelines

WHAT TO DO?

We have a few strong C++ coders in this community, I think that the best
way to proceed would be to let them articulate the different options that
we have and - if the don't agree - let the core devs vote on the proposals
they come out with.


Btw, thanks for binging up this discussion!

Cheers.

-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Rendering of Icons

Re: [QGIS-Developer] Rendering of Icons

[QGIS-Developer] Rendering of Icons

[QGIS-Developer] QGIS Server test on Windows 2016 server.

Re: [QGIS-Developer] MetaSearch provider connections in master

Re: [QGIS-Developer] MetaSearch provider connections in master

Re: [QGIS-Developer] MetaSearch provider connections in master

Re: [QGIS-Developer] MetaSearch provider connections in master

Re: [QGIS-Developer] MetaSearch provider connections in master

Re: [QGIS-Developer] MetaSearch provider connections in master

Re: [QGIS-Developer] MetaSearch provider connections in master

Re: [QGIS-Developer] QgsServer and 3d tiles

Re: [QGIS-Developer] MetaSearch provider connections in master

[QGIS-Developer] MetaSearch provider connections in master

Re: [QGIS-Developer] QgsServer and 3d tiles

Re: [QGIS-Developer] QgsServer and 3d tiles

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

17 matches

Site Navigation

Mail list logo

Footer information