Re: [QGIS-Developer] [Qgis-developer] OTB and LiDAR tools as separate plugins
Hello from Zanzibar, In the next three days I'd like to tackle recreating the LAStools toolbox the way it was available in QGIS 2.4 through 2.18 to also in QGIS 3.2. Is there a guide / example that I can follow to provide the LiDAR tools provider as a separate plugin as we've discussed it previously? Has anyone else created such a processing plugin that is residing outside of QGIS who is / will come to Tanzania? Regards. Martin On Thu, Aug 23, 2018 at 11:13 AM, Martin Isenburg wrote: > Hello from Zanzibar, > > In the next three days I'd like to tackle recreating the LAStools toolbox > the way it was available in QGIS 2.4 through 2.18 to also in QGIS 3.2. Is > there a guide / example that I can follow to provide the LiDAR tools > provider as a separate plugin as we've discussed it previously? Has anyone > else created such a processing plugin that is residing outside of QGIS who > is / will come to Tanzania? > > Regards. > > Martin > > On Thu, Feb 2, 2017 at 8:36 AM, Victor Olaya wrote: > >> Martin >> >> That might be my fault. I mentioned that, by having the LiDAR tools >> provider as a separate plugin, that allows to ship the tools with it >> (not with QGIS, but with the plugin itself, which you will manage and >> release whenever you want). Of course, you can still provide the >> downloads from your site as usual, this would just be a more practical >> solution, to avoid having to setup the LASTools path in Processing >> >> Cheers >> >> >> >> 2017-02-02 2:04 GMT+01:00 Martin Isenburg : >> > Hello, >> > >> >> One thing to keep in mind is that not all the LIDAR tools are open >> >> sources, 2/3 of the LAStools aren't and slightly distort the output >> after >> >> certain point limits are exceeded. My opinion is that QGIS shouldn't >> ship or >> >> assist the distribution of closed binaries. >> > >> > >> > Not sure who suggested the notion that LAStools binaries will be shipped >> > with QGIS or that there maybe will be an auto-download of sorts ... >> there >> > will not. The LAStools package can be used as a toolbox in ArcGIS, >> IMAGINE, >> > FME, and QGIS or as a stand alone software. I see more and more LiDAR >> > practitioners (those that I am teaching) doing their GIS with the Q >> instead >> > of Argh and the QGIS toolboxes the most up-to-date toolboxes. If a user >> > wants to use LAStools (whether via QGIS or not) the tools will only be >> > available via my site and not be bundled. >> > >> > Regards from the Philippines, >> > >> > Martin >> > >> > >> > ___ >> > 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-developer] OTB and LiDAR tools as separate plugins
Hi Martin, there are a lot of Processing providers which are not part of the QGIS core. You can easily find some of them in the QGIS Plugin repository by "Processing" keyword. Also in QGIS sources there is an example provider which can be used as staring point, see https://github.com/qgis/QGIS/tree/master/python/plugins/processing/algs/exampleprovider. чт, 23 серп. 2018 о 12:19 Martin Isenburg пише: > > Hello from Zanzibar, > > In the next three days I'd like to tackle recreating the LAStools toolbox the > way it was available in QGIS 2.4 through 2.18 to also in QGIS 3.2. Is there a > guide / example that I can follow to provide the LiDAR tools provider as a > separate plugin as we've discussed it previously? Has anyone else created > such a processing plugin that is residing outside of QGIS who is / will come > to Tanzania? > > Regards. > > Martin -- Alexander Bruy ___ 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-developer] OTB and LiDAR tools as separate plugins
Hello Alex,
all the python code is pretty much written. Victor even did some kind of
port already.
https://github.com/volaya/qgis-lidartools-plugin
But I am struggling with how to add this code as a plugin such it can be
searched for. Maybe I should provide it as a zip package ("Install from
ZIP") rather than make it a plugin that can be queried from QGIS. I have
heard that some people are not happy with the LAStools binding scripts
being hosted on the official QGIS site as LAStools is not entirely open
source. The initial attempt of bundling the binaries with the scripts as
you can find it here:
https://github.com/volaya/qgis-lidartools-plugin/tree/master/lidartools/bin/lastools
will also need to change back to how it used to be ("setup the PATH to the
LAStools and - if needed to Wine") as the binaries of LAStools change too
often to have them inside the processing python bindings which almost never
change.
I was looking for documentation on how to prepare such an external plugin
so users can load it into QGIS - either online or as a ZIP.
Martin
On Thu, Aug 23, 2018 at 11:42 AM, Alexander Bruy
wrote:
> Hi Martin,
>
> there are a lot of Processing providers which are not part of the QGIS
> core. You can easily find
> some of them in the QGIS Plugin repository by "Processing" keyword.
> Also in QGIS sources
> there is an example provider which can be used as staring point, see
> https://github.com/qgis/QGIS/tree/master/python/plugins/processing/algs/
> exampleprovider.
>
> чт, 23 серп. 2018 о 12:19 Martin Isenburg
> пише:
> >
> > Hello from Zanzibar,
> >
> > In the next three days I'd like to tackle recreating the LAStools
> toolbox the way it was available in QGIS 2.4 through 2.18 to also in QGIS
> 3.2. Is there a guide / example that I can follow to provide the LiDAR
> tools provider as a separate plugin as we've discussed it previously? Has
> anyone else created such a processing plugin that is residing outside of
> QGIS who is / will come to Tanzania?
> >
> > Regards.
> >
> > Martin
>
>
>
>
> --
> Alexander Bruy
>
___
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-developer] OTB and LiDAR tools as separate plugins
you can add a simple plugin hosted in the official repo to add your custon
plugin repo or a plugin that simplify installation. I agree with that who
assume that offial repo have to host plugin with code compatible with GPL2.
A plugin that install a plugin can simply override this limitation without
affecting licences.
I'm of that person is using point cloud data and avoided to use LAStool
because it's not FOSS, but please believe me, I know and I thrust you, I
like the limitation of your license, but simply I prefer to support PDAL or
PCL because development model is simpler and allow me to contribute is a
simple way and I prefer to invest in a project with an ecosystem of
multiple contributors.
Luigi Pirelli
**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Mastering QGIS 2nd Edition:
*
https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition
* Hire me: http://goo.gl/BYRQKg
**
On Thu, 23 Aug 2018 at 12:06, Martin Isenburg
wrote:
> Hello Alex,
>
> all the python code is pretty much written. Victor even did some kind of
> port already.
>
> https://github.com/volaya/qgis-lidartools-plugin
>
> But I am struggling with how to add this code as a plugin such it can be
> searched for. Maybe I should provide it as a zip package ("Install from
> ZIP") rather than make it a plugin that can be queried from QGIS. I have
> heard that some people are not happy with the LAStools binding scripts
> being hosted on the official QGIS site as LAStools is not entirely open
> source. The initial attempt of bundling the binaries with the scripts as
> you can find it here:
>
>
> https://github.com/volaya/qgis-lidartools-plugin/tree/master/lidartools/bin/lastools
>
> will also need to change back to how it used to be ("setup the PATH to the
> LAStools and - if needed to Wine") as the binaries of LAStools change too
> often to have them inside the processing python bindings which almost never
> change.
>
> I was looking for documentation on how to prepare such an external plugin
> so users can load it into QGIS - either online or as a ZIP.
>
> Martin
>
___
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-developer] OTB and LiDAR tools as separate plugins
Hi Martin,
It is up to you how to distribute your plugin. You can publish it in
QGIS Official
plugins repository, or setup your own repository as many other developers do.
It is even possible to share just a ZIP with the plugin via web-site,
pretty much
similar to how LAStools distributed.
чт, 23 серп. 2018 о 13:06 Martin Isenburg пише:
>
> Hello Alex,
>
> all the python code is pretty much written. Victor even did some kind of port
> already.
>
> https://github.com/volaya/qgis-lidartools-plugin
>
> But I am struggling with how to add this code as a plugin such it can be
> searched for. Maybe I should provide it as a zip package ("Install from ZIP")
> rather than make it a plugin that can be queried from QGIS. I have heard that
> some people are not happy with the LAStools binding scripts being hosted on
> the official QGIS site as LAStools is not entirely open source. The initial
> attempt of bundling the binaries with the scripts as you can find it here:
>
> https://github.com/volaya/qgis-lidartools-plugin/tree/master/lidartools/bin/lastools
>
> will also need to change back to how it used to be ("setup the PATH to the
> LAStools and - if needed to Wine") as the binaries of LAStools change too
> often to have them inside the processing python bindings which almost never
> change.
>
> I was looking for documentation on how to prepare such an external plugin so
> users can load it into QGIS - either online or as a ZIP.
>
> Martin
>
>
> On Thu, Aug 23, 2018 at 11:42 AM, Alexander Bruy
> wrote:
>>
>> Hi Martin,
>>
>> there are a lot of Processing providers which are not part of the QGIS
>> core. You can easily find
>> some of them in the QGIS Plugin repository by "Processing" keyword.
>> Also in QGIS sources
>> there is an example provider which can be used as staring point, see
>> https://github.com/qgis/QGIS/tree/master/python/plugins/processing/algs/exampleprovider.
>>
>> чт, 23 серп. 2018 о 12:19 Martin Isenburg пише:
>> >
>> > Hello from Zanzibar,
>> >
>> > In the next three days I'd like to tackle recreating the LAStools toolbox
>> > the way it was available in QGIS 2.4 through 2.18 to also in QGIS 3.2. Is
>> > there a guide / example that I can follow to provide the LiDAR tools
>> > provider as a separate plugin as we've discussed it previously? Has anyone
>> > else created such a processing plugin that is residing outside of QGIS who
>> > is / will come to Tanzania?
>> >
>> > Regards.
>> >
>> > Martin
>>
>>
>>
>>
>> --
>> Alexander Bruy
>
>
--
Alexander Bruy
___
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-developer] OTB and LiDAR tools as separate plugins
Hello, when the LAStools toolboxes were part of the "built-in" scripts of Processing I had was able to have two entries (i.e. the folder path to the "Wine" and the "LAStools" installation) in the "Processing Settings" menu under the "Providers" section. You can see as an example how GRASS still has such options in the attached screen shot. How can I place these two options back there now that I load the LAStools toolboxes as Processing plugins? Off for beers at the Zanzi-bar ... (-; Martin On Thu, Aug 23, 2018 at 8:26 PM, Alexander Bruy > wrote: > >> Hi Martin, >> >> It is up to you how to distribute your plugin. You can publish it in >> QGIS Official >> plugins repository, or setup your own repository as many other developers >> do. >> It is even possible to share just a ZIP with the plugin via web-site, >> pretty much >> similar to how LAStools distributed. >> > ___ 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-developer] OTB and LiDAR tools as separate plugins
Hello,
my question was answered at the QGIS hackfest by Matteo Ghetta with a
DataPlotly code snippet. (-: You can add your own entries into the
"Processing Settings" menu under the "Providers" section by following the
example below in your own Provider class.
from processing.core.ProcessingConfig import Setting, ProcessingConfig
class LAStoolsProvider(QgsProcessingProvider):
def __init__(self):
QgsProcessingProvider.__init__(self)
def load(self):
ProcessingConfig.settingIcons[self.name()] = self.icon()
ProcessingConfig.addSetting(Setting(self.name(),
'LASTOOLS_ACTIVATED', 'Activate', True))
ProcessingConfig.addSetting(Setting(self.name(), 'LASTOOLS_FOLDER',
'LAStools folder', "C:\LAStools", valuetype=Setting.FOLDER))
ProcessingConfig.addSetting(Setting(self.name(), 'WINE_FOLDER',
'Wine folder', "", valuetype=Setting.FOLDER))
ProcessingConfig.readSettings()
self.refreshAlgorithms()
return True
def unload(self):
ProcessingConfig.removeSetting('LASTOOLS_ACTIVATED')
ProcessingConfig.removeSetting('LASTOOLS_FOLDER')
ProcessingConfig.removeSetting('WINE_FOLDER')
pass
def isActive(self):
return ProcessingConfig.getSetting('LASTOOLS_ACTIVATED')
def setActive(self, active):
ProcessingConfig.setSettingValue('LASTOOLS_ACTIVATED', active)
def loadAlgorithms(self):
[...]
and you can always query those settings with code snippets such as
from processing.core.ProcessingConfig import ProcessingConfig
from processing.tools.system import isWindows
@staticmethod
def hasWine():
wine_folder = ProcessingConfig.getSetting("WINE_FOLDER")
return (wine_folder is not None) and (wine_folder != "")
@staticmethod
def LAStoolsPath():
lastools_folder = ProcessingConfig.getSetting("LASTOOLS_FOLDER")
if isWindows():
wine_folder = ""
else:
wine_folder = ProcessingConfig.getSetting("WINE_FOLDER")
if (wine_folder is None) or (wine_folder == ""):
folder = lastools_folder
else:
folder = wine_folder + "/wine " + lastools_folder
return folder
Regards,
Martin
On Fri, Aug 24, 2018 at 7:11 PM Martin Isenburg
wrote:
> Hello,
>
> when the LAStools toolboxes were part of the "built-in" scripts of
> Processing I had was able to have two entries (i.e. the folder path to the
> "Wine" and the "LAStools" installation) in the "Processing Settings" menu
> under the "Providers" section. You can see as an example how GRASS still
> has such options in the attached screen shot. How can I place these two
> options back there now that I load the LAStools toolboxes as Processing
> plugins?
>
> Off for beers at the Zanzi-bar ... (-;
>
> Martin
>
> On Thu, Aug 23, 2018 at 8:26 PM, Alexander Bruy
>> wrote:
>>
>>> Hi Martin,
>>>
>>> It is up to you how to distribute your plugin. You can publish it in
>>> QGIS Official
>>> plugins repository, or setup your own repository as many other
>>> developers do.
>>> It is even possible to share just a ZIP with the plugin via web-site,
>>> pretty much
>>> similar to how LAStools distributed.
>>>
>>
___
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-developer] OTB and LiDAR tools as separate plugins
Hi Martin, glad that I could had helped you ;) Cheers Matteo ___ 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
