2012/4/18 Larry Shaffer :
> Hi Paolo,
>
> On Tue, Apr 17, 2012 at 2:03 PM, Etienne Tourigny
> wrote:
>>
>> I think it is a good idea - perhaps agree on a common interface and
>> add it to the plugin builder?
>>
>> This might have been discussed before - but it would be nice to have a
>> base "QgsP
Il 17/04/2012 21:42, Tim Sutton ha scritto:
>
> Agreed - any serious objections from the authors?
+1
--
Paolo Cavallini
See: http://www.faunalia.it/pc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinf
Hi Paolo,
On Tue, Apr 17, 2012 at 2:03 PM, Etienne Tourigny
wrote:
> I think it is a good idea - perhaps agree on a common interface and
> add it to the plugin builder?
>
> This might have been discussed before - but it would be nice to have a
> base "QgsPlugin" python class that all plugins woul
Hi All
Please note as per my previous email that we are now in feature freeze in
*master*. String freeze is not yet in effect as we still need to update
various text in the UI, but I encourage translators to start with
translation now if possible.
Regards
--
Tim Sutton - QGIS Project Steering C
>
> Right, it would need some kung-fu across QGIS-GEOS python bindings. It
> was never really a top priority for me since QgsGeometry exposes the
> most important GEOS geometry algorithms.
I would like to extend it, to include the linearref methods exposed by the
C API:
- GEOSInterpolate
(- GEOS
On Mon, Apr 16, 2012 at 11:00 AM, G. Allegri wrote:
> Hi,
> I've just realized that the python api does't support the
> QgsGeometry.asGeos() method.
> I understand that it would require SIP to manage the marshalling and the
> bindings to GEOS too, so what is the best way to obtain a GEOS geometry
Hi,
I remember that french MEDDT, at QGIS day Paris-Défense, tell us they have
developed a little tool to convert mapinfo projects (.wor) to .qgs!?
They have said that they will give it to the community...
Many people and students cannot migrate easily to QGIS because they have worked
several yea
I think it is a good idea - perhaps agree on a common interface and
add it to the plugin builder?
This might have been discussed before - but it would be nice to have a
base "QgsPlugin" python class that all plugins would inherit from and
implement this kind of standardization, but I'm not sure if
Hi
On Tue, Apr 17, 2012 at 3:47 PM, Marco Hugentobler
wrote:
> Hi all
>
> And core plugins that ship with the QGIS code should remove the about dialog
> (currently gdal tools and db manager).
> For third party plugins it is ok.
>
Agreed - any serious objections from the authors?
Regards
Tim
>
Same 404 here
Marco Bernasocchi (mobile)
http://opengis.ch
On Apr 17, 2012 7:48 PM, "Frank Warmerdam" wrote:
> On Tue, Apr 17, 2012 at 7:06 AM, Anne Ghisla wrote:
> > No problem :) just use private osgeo gsoc mentors list, that has been
> > created primarily for ranking discussions.
> > https:/
On Tue, Apr 17, 2012 at 7:06 AM, Anne Ghisla wrote:
> No problem :) just use private osgeo gsoc mentors list, that has been
> created primarily for ranking discussions.
> https://groups.google.com/osgeo-gsoc-mentors
FYI - the above link gives me a 404.
I doubt on I'm that list.
--
Hi,
> But, any other colour that has 255 in either its R, G or B value (e.g.
> [255,0,0]) is also set to transparent. Is it the expected behaviour or
> is it a bug?
gdal translate manual says
"Assign a specified nodata value to output bands."
cheers
-- Giovanni --
__
JFYI,
I have extended QgsDataSourceURI with some generic methods setParam,
param, hasParam, encodedUri, setEncodedUri. QUrl is used to
encode/decode the URI.
I have used the new QgsDataSourceURI for WMS so that various WMS
related hacks in QgisApp and QgsRasterLayer, browser etc could be
removed.
Il 17/04/2012 16:21, Giovanni Manghi ha scritto:
> already tested,
> unfortunately the above build works for the Home Range plugin but does
> not for the ManageR and SDA4PP ones.
>
in any case, rpy* proved a fragile solution, that's why I suggested
porting it to pure R scripts, and use Sextante as
Hi,
> I think we tracked
> down a current version for python 2.7 but haven't tried it yet. Once
> tested could be re-added to osgeo4w.
>
> Here's the link Giovanni found, can someone please test
> https://bitbucket.org/lgautier/rpy2/issue/85/ive-tried-to-compile-rpy2-under-windows-xp
already t
Hi,
+1 with everything you said !
:)
Vincent
> Now that there is (already !) a lot of backends integrated directly into
> the core plugin, I guess there will be more and more people proposing
> improvements. I think moving to a DVCS would help, so that people can
> "pull-request" you, with all th
On Tue, 17 Apr 2012 14:19:53 +0200
Marco Bernasocchi wrote:
> Sorry, my bad for starting it, totally forgot :(
No problem :) just use private osgeo gsoc mentors list, that has been
created primarily for ranking discussions.
https://groups.google.com/osgeo-gsoc-mentors
Almost all mentors are reg
Hi all
And core plugins that ship with the QGIS code should remove the about
dialog (currently gdal tools and db manager).
For third party plugins it is ok.
Regards,
Marco
On 17.04.2012 09:03, Paolo Cavallini wrote:
Hi all.
Currently, most plugins do not have an About dialog, and those who h
Hi,
2012/4/17 Julien Malik :
> Hi,
>
> Does the Qgis plugin system support dependency between plugin ?
AFAIK there is no such support, but this easily can be solved at plugin
level. For example, SAGA module interface plugin needs QGIS Processing
Framework plugin and check in __init__.py for this
Martin Dobias wrote
>
> On Sat, Apr 14, 2012 at 7:39 AM, KSJ wrote:
>> Hi All:
>> I use QgsGraduatedSymbolRendererV2 to simulate colorbar (like
>> matplotlib.colorbar)
>> use rendererV2.setClassAttribute to show using certain field
>> But there are some feature where its valu
Hi,
Does the Qgis plugin system support dependency between plugin ?
Now that there is (already !) a lot of backends integrated directly into
the core plugin, I guess there will be more and more people proposing
improvements. I think moving to a DVCS would help, so that people can
"pull-reque
Sorry, my bad for starting it, totally forgot :(
On 04/17/2012 02:18 PM, Nathan Woodrow wrote:
*headdesk* that's right we talked about this last night :( Sorry about
that.
- Nathan
On Tue, Apr 17, 2012 at 10:12 PM, Anne Ghisla mailto:a.ghi...@gmail.com>> wrote:
Hello all,
the rankin
*headdesk* that's right we talked about this last night :( Sorry about
that.
- Nathan
On Tue, Apr 17, 2012 at 10:12 PM, Anne Ghisla wrote:
> Hello all,
>
> the ranking discussion should not have been made public, as mentioned
> in the soc list email...
>
> Please finalise the ranking list, and
Hello all,
the ranking discussion should not have been made public, as mentioned
in the soc list email...
Please finalise the ranking list, and send it to me in a private mail.
Thanks!
Anne
On Tue, 17 Apr 2012 13:50:02 +0300
Alexander Bruy wrote:
> Hi.
>
> Here is my list:
> - Orfeo Toolbox
Core or Framework sound good to me. It should be something easy for
tester to decide where to put a bug
Regards
El día 17 de abril de 2012 14:08, Julien Malik escribió:
> Hi,
>
> I just updated the categories name to differenciate between backend related
> issues and pure sextante issues.
>
> I
Hi,
I just updated the categories name to differenciate between backend
related issues and pure sextante issues.
I personnally don't like "General", does not really mean anything.
Do we miss a "Core" category ?
Any better proposition ?
Julien
Le 17/04/2012 13:33, Victor Olaya a écrit :
Gre
that is a question that should be discussed.
Algorihtm providers in SEXTANTE can be turned off, so I would prefer
to have them all together, since the size is rather small, and to
activate them within SEXTANTE.
However, there is already a mechanism for creating plugins that
connect their algorith
Il 17/04/2012 13:18, Victor Olaya ha scritto:
> that was exactly what i tried to say :-) That extra effort I mentioned
> is just that public API and that wrapper. But it would be good to try
> to have all analysis tools wrapped somehow, to make the analytical
> side of QGIS more compact and homogen
Hi all,
now SEXTANTE has several backends and more backends are under
development. Most of this backends (like fTools, mmqgis and others)
are distributed within SEXTANTE core plugin. Maybe it is better to
rewrite them a bit and distribute as separate modules, so peoples
will install only required
Il 16/04/2012 18:49, Salvatore Larosa ha scritto:
> Il giorno lun, 16/04/2012 alle 16.10 +0200, Paolo Cavallini ha scritto:
>> It seems that SAGA is not correctly installed in your system.
>>
>> Please install it before running SAGA algorithms.
>>
>>
>> after upgrading to r101
>> All the best.
> it
>Hi Andrea
>
>If you are doing the compilation to use QGIS server, you might disable
>compilation of the bindings (set WITH_BINDINGS to OFF).
>QGIS server does not use python at all (python is for the desktop).
>
>Regards,
>Marco
Hi,
setting WITH_BINDINGS = OFF
will resolve the problem.
:)
As in
Great!
Thanks!
El día 17 de abril de 2012 13:31, Paolo Cavallini
escribió:
> Hi all.
> I've added categories to the Sextante bug tracker[0]. I think this will
> improve the management of the tickets. Please feel free to add or
> suggest other categories, and do not forget to add them to the tick
Hi all.
I've added categories to the Sextante bug tracker[0]. I think this will
improve the management of the tickets. Please feel free to add or
suggest other categories, and do not forget to add them to the tickets.
All the best.
--
Paolo Cavallini
See: http://www.faunalia.it/pc
[0] http://hub
Il 17/04/2012 12:41, Victor Olaya ha scritto:
> One question/suggestion: is it possible to have some kind of
> link/coordination between GSoC projects? I am saying this because the
>
I think we can always cooperate informally, without any impact on the
official GSoC projects.
All the best.
--
Pao
> - Vector Layer Generalization for QGIS
> From what I understand of the proposal, it will be a more lower level core
> QGIS thing. Implemented at the rendering/fetching level into to speed up
> vector layer drawing. Not really a post process step.
>
If it is a rendering tool, then you are righ
Hi Andrea
If you are doing the compilation to use QGIS server, you might disable
compilation of the bindings (set WITH_BINDINGS to OFF).
QGIS server does not use python at all (python is for the desktop).
Regards,
Marco
On 17.04.2012 12:18, Andrea Peri wrote:
>Hi Andrea,
>try to clean the bu
While I think that is a good idea in general. I don't, personally, think
it applies in this case.
- Vector Layer Generalization for QGIS
From what I understand of the proposal, it will be a more lower level core
QGIS thing. Implemented at the rendering/fetching level into to speed up
vector lay
Hi.
Here is my list:
- Orfeo Toolbox backend for the Sextante framework in QGIS
- Symbology Usability Improvments for QGIS
- QGIS for Mobile Devices
- QGIS tool for vector data merging
- Vector Layer Generalization for QGIS
2012/4/17 Paolo Cavallini :
> for me:
> - Orfeo Toolbox backend fo
One question/suggestion: is it possible to have some kind of
link/coordination between GSoC projects? I am saying this because the
main aim of the " Orfeo Toolbox backend for the Sextante framework in
QGIS" one is to improve SEXTANTE and add new tools to it, but it would
be a bad idea not to try to
Hi Viktor,
I find your proposal very interesting. I've worked a lot on GRASS where
data structures are topological, and with ArcGIS GeoDB where topological
rules can be defined to keep geometrical integrity. I feel that this kind
of tools are foundamental to supply sound data management.
As you kno
Il 17/04/2012 12:09, Nathan Woodrow ha scritto:
> +1 that that order from me.
>
> - Nathan
>
> On Tue, Apr 17, 2012 at 7:50 PM, Marco Bernasocchi
> mailto:ma...@bernawebdesign.ch>> wrote:
>
> What do you think:
> - Symbology Usability Improvments for QGIS [0]
> - QGIS for Mobile Devices
Hi All,
I hope this isn't the wrong place for this announcement, though I also sent
it to the soc list. It's a GSoC proposal. I'm Viktor Nagy, an MSc. student
at the University of Szeged, Hungary.
If you are interested, please have a look at my proposal about some
advanced vector data merging.
htt
>Hi Andrea,
>try to clean the build-master folder and re-run ccmake command!
>
>Regards,
>
>-SL*
Hi,
I try it, but the error is still here. :(
I'm using python 2.6 . perhaps QGIS-Server has lost compatibility with
python 2.6 ?
*
--
-
Andrea Peri
. . . . . . . . .
qwerty àèìò
+1 that that order from me.
- Nathan
On Tue, Apr 17, 2012 at 7:50 PM, Marco Bernasocchi
wrote:
> What do you think:
> - Symbology Usability Improvments for QGIS [0]
> - QGIS for Mobile Devices [1]
> - Orfeo Toolbox backend for the Sextante framework in QGIS [2]
> - Vector Layer Generalization fo
What do you think:
- Symbology Usability Improvments for QGIS [0]
- QGIS for Mobile Devices [1]
- Orfeo Toolbox backend for the Sextante framework in QGIS [2]
- Vector Layer Generalization for QGIS [3]
- QGIS tool for vector data merging [4] (NO MENTOR YET)
[0]
http://www.google-melange.com/gso
http://blog.orfeo-toolbox.org/uncategorized/otb-inside-sextante-inside-qgis
saluti!
--
Paolo Cavallini
See: http://www.faunalia.it/pc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Hi Devs,
On 3-band (RGB) byte rasters, if I set the no-data-value to 255 using
GDalTools (translate) then the white [255,255,255] colour is effectively
set as transparent, This is OK.
But, any other colour that has 255 in either its R, G or B value (e.g.
[255,0,0]) is also set to transparent
Hi,
I agree with Paolo's idea, we definitely need more consistent
About dialogs. Regarding two menu items (About and Help)
I think it is better to have only About dialog with button to
open help browser
2012/4/17 kimaidou :
> Hi Paolo,
>
> I agree with your proposal. Automaticly including 2 plugi
Il giorno mar, 17/04/2012 alle 09.48 +0200, Andrea Peri ha scritto:
> I update the SIP version to the last 4.13.2.
> Now the SIP error was gone, but another error there is . :(
> [ 83%] Built target compile_python_files
> [ 83%] Generating analysis/sipanalysispart0.cpp,
> analysis/sipanalysispart1.
Hi,
On 17.04.2012 10:46, kimaidou wrote:
> Hi Paolo,
>
> I
agree with your proposal. Automaticly including 2 plugin menu items ;
"help" and "about" make also sense for me.
>
> 2012/4/17 Paolo
Cavallini
>
>> Hi all.
>> Currently, most plugins do not have an About
dialog, and those who ha
Il giorno lun, 16/04/2012 alle 16.29 -0700, Pedro Venâncio ha scritto:
> Hi Salvatore,
>
>
> I have done this, but anyway:
>
> SAGA execution console output
> Parameters
>
> Grids: No objects
> Files:
> "/home/pedro/SIG/ASTER_GDEM/mdt_aster_pt_D73_GeoTIFF/mdt_aster_pt_D73_GeoTIFF.tif"
>
> lo
>>*Which version of SIP are you running? Looks like it doesn't support the
>>-o*>>*switch introduced in 67c77e553.*>>**>>*Jürgen*>
>
>Hi,
>
>testing with:
>
>>*python*>>*import sip*>>*print '%x' % sip.SIP_VERSION*>
>
>I see the version is:
>
>40903
Hi,
I update the SIP version to the last 4.13.
Hi Paolo,
I agree with your proposal. Automaticly including 2 plugin menu items ;
"help" and "about" make also sense for me.
2012/4/17 Paolo Cavallini
> Hi all.
> Currently, most plugins do not have an About dialog, and those who have
> it are often quite different. Can we choose a layout, make
>Which version of SIP are you running? Looks like it doesn't support the -o
>switch introduced in 67c77e553.
>
>Jürgen
Hi,
testing with:
>python
>import sip
>print '%x' % sip.SIP_VERSION
I see the version is:
40903
The last version of qgis-server I compiled (using this SIP version) was on
Hi Andrea,
On Tue, 17. Apr 2012 at 08:37:45 +0200, Andrea Peri wrote:
>[ 83%] Built target compile_python_files
>[ 83%] Generating analysis/sipanalysispart0.cpp,
>analysis/sipanalysispart1.cpp, analysis/sipanalysispart2.cpp,
>analysis/sipanalysispart3.cpp
>
>sip: Usage: sip [-
Hi all.
Currently, most plugins do not have an About dialog, and those who have
it are often quite different. Can we choose a layout, make a template,
and ask plugin devs to please use it?
A small thing, but it will sooth out the user experience, and will give
a more integrated ovarall look.
All th
56 matches
Mail list logo