[Qgis-user] plugin installer missing in qgis 1.0 (ubuntu hardy binary)

2009-01-04 Thread Agustin Lobo

Hi!

After uninstalling the preview and installing 1.0
I cant find "Fetch python plugins" under Plugins
and Plugin installer is not listed by Manage Plugins.

Also, /usr/share/qgis/doc/index.html points to
/usr/share/qgis/doc/userguide.pdf, while the pdf file is actually under
/usr/share/doc/qgis

Agus

--
Dr. Agustin Lobo
Institut de Ciencies de la Terra "Jaume Almera" (CSIC)
LLuis Sole Sabaris s/n
08028 Barcelona
Spain
Tel. 34 934095410
Fax. 34 934110012
email: agustin.l...@ija.csic.es
http://www.ija.csic.es/gt/obster


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] plugin installer missing in qgis 1.0 (ubuntu hardy binary)

2009-01-04 Thread Otto Dassau
Hi, 

On Sun, 04 Jan 2009 15:01:18 +0100
Agustin Lobo  wrote:

> Hi!
> 
> After uninstalling the preview and installing 1.0
> I cant find "Fetch python plugins" under Plugins
> and Plugin installer is not listed by Manage Plugins.
> 
> Also, /usr/share/qgis/doc/index.html points to
> /usr/share/qgis/doc/userguide.pdf, while the pdf file is actually under
> /usr/share/doc/qgis

Upps - I missed that and saw that the current pdf in the QGIS 1.0.0 sources at
./doc/userguide.pdf is an old version 0.9.1 manual. I suggest that we make some
general changes to:

a) Help -> Help Contents (...qgis/doc/index.html)

Here we have links to the 0.9.1 Installation and User Guide coming with the
source code. These links should be removed, because it the documentation team
will never be able to have the manual updates done, when QGIS is branched or
tagged for a new release. 

Instead I would prefer to link to the web site with the note:

"A current version of the QGIS manual and translations are provided at
http://qgis.osgeo.org/documentation/manuals.html. Older versions are available
at http://download.osgeo.org/qgis/doc/manual/.";

b) We should remove the ./doc/userguide.pdf from the sources. As described
above, that manual will never be up-to-date and therefore doesn't make sense.
 
regards,
 Otto

> Agus
> 
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Re: GRASS raster reading to QGIS 1.0.0 Kore

2009-01-04 Thread Martin Dobias
2009/1/4 Patrick Giraudoux :
> Seems that I can narrow the question now. Actually, QGIS Kore reads GRASS
> maps well except when the maps  have been created from raster ramp color
> have been optimized with i.landsat.rgb. For example in GRASS:
>
> r.composite r=etm7 g=etm5 b=etm2 out=south752brut
>
> makes a map 'south752brut' which is well read within QGIS
>
> Now if I do:
> i.landsat.rgb r=etm7 g=etm5 b=etm2
> r.composite r=etm7 g=etm5 b=etm2 out=south752opt
>
> it makes a map 'south752opt' which is extremly long to read (several
> minutes), and when read makes change (displacement, zoom, etc...) extremely
> long to be displayed at a speed that prevent any work
>
> However, 'south752opt' and 'south752brut' are quick/normally displayed both
> at the same speed when on work within GRASS (e.g. d.rast south752opt)
>
> Any hint ?

Hi Patrick,

we're using GDAL library to access GRASS rasters, so the problem may
be there. I would suggest you to try reading the raster in some other
GDAL-based software [1] to see whether it also suffers slow
performance. If so, file a bug for GDAL, if the problem happens only
in QGIS file a ticket for QGIS with details.

Martin

[1] https://trac.osgeo.org/gdal/wiki/SoftwareUsingGdal
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] plugin installer missing in qgis 1.0 (ubuntu hardy binary)

2009-01-04 Thread Agustin Lobo

True, I was missing a click on the python-qgis package in Synaptic.
Anyway, the problem I have now after installing python-qgis 1.0.0.~hardy 
is that
the plugin manager states that "Plugin Installer (Version 0.06.2) 
[incompatible]"
and cannot select it. (Note that I selected "complete removal" of the 
preview

packages in Synaptic before the new install). I see that the
*.pyc files in /usr/share/qgis/python/plugins/plugin_installer
have date as of 2009-01-04
but the *.py files are dated 2008-12-23

Agus

Borys Jurgiel wrote:

Sunday 04 January 2009 15:01:18 Agustin Lobo napisał(a):

Hi!

After uninstalling the preview and installing 1.0
I cant find "Fetch python plugins" under Plugins
and Plugin installer is not listed by Manage Plugins.

Also, /usr/share/qgis/doc/index.html points to
/usr/share/qgis/doc/userguide.pdf, while the pdf file is actually under
/usr/share/doc/qgis

Agus


Probably the Python support is missing (I assume other Python plugins are also 
missing). Have you the 'python-qgis' or similar package installed? Maybe the 
old one is still present? 



--
Dr. Agustin Lobo
Institut de Ciencies de la Terra "Jaume Almera" (CSIC)
LLuis Sole Sabaris s/n
08028 Barcelona
Spain
Tel. 34 934095410
Fax. 34 934110012
email: agustin.l...@ija.csic.es
http://www.ija.csic.es/gt/obster
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Re: GRASS raster reading to QGIS 1.0.0 Kore

2009-01-04 Thread Patrick Giraudoux

Martin Dobias a écrit :

2009/1/4 Patrick Giraudoux :
  

Seems that I can narrow the question now. Actually, QGIS Kore reads GRASS
maps well except when the maps  have been created from raster ramp color
have been optimized with i.landsat.rgb. For example in GRASS:

r.composite r=etm7 g=etm5 b=etm2 out=south752brut

makes a map 'south752brut' which is well read within QGIS

Now if I do:
i.landsat.rgb r=etm7 g=etm5 b=etm2
r.composite r=etm7 g=etm5 b=etm2 out=south752opt

it makes a map 'south752opt' which is extremly long to read (several
minutes), and when read makes change (displacement, zoom, etc...) extremely
long to be displayed at a speed that prevent any work

However, 'south752opt' and 'south752brut' are quick/normally displayed both
at the same speed when on work within GRASS (e.g. d.rast south752opt)

Any hint ?



Hi Patrick,

we're using GDAL library to access GRASS rasters, so the problem may
be there. I would suggest you to try reading the raster in some other
GDAL-based software [1] to see whether it also suffers slow
performance. If so, file a bug for GDAL, if the problem happens only
in QGIS file a ticket for QGIS with details.

Martin

[1] https://trac.osgeo.org/gdal/wiki/SoftwareUsingGdal

  

Ok. I will try and come back with the result ASAP.

Additionally before your mail I have made some other trials that may (?) 
help to understand what happens... Looks like corroborating your 
suspicion about bad interactions between rgdal and qgis. When I export 
the file using r.out.gdal format=GTiff and then try and read the tif 
file externally from QGIS, I have the same (bad/slow) result as when 
reading the grass file from QGIS within GRASS. Then, if I export the 
GRASS file with r.out.tiff I get a file which is easily read from QGIS 
and correctly (quickly) displayed as a three band tif object (as an 
external raster, of course). Furthermore, what surprises me is that when 
I read a raster GRASS file created with r.composite within QGIS, I get a 
1-grey band file  with "color palette" ("palette de couleur" in French) 
activated in the "properties" box of the layer (however, I was more 
expecting a three band rgb).


Do those info put you a bit more clearly on the track ?

Thanks for your ideas and advice to where to adress the trouble...

Patrick




begin:vcard
fn:Patrick Giraudoux
n:Giraudoux;Patrick
org;quoted-printable:Universit=C3=A9 de Franche-Comt=C3=A9;Chrono-environnement, UMR CNRS 6249 usc INRA
adr;quoted-printable:;;1 place Leclerc;Besan=C3=A7on;;25030;France
email;internet:patrick.giraud...@univ-fcomte.fr
title;quoted-printable:Professeur d'=C3=A9cologie
tel;work:+33 381 665 745
tel;fax:+33 381 665 797
version:2.1
end:vcard

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Re: GRASS raster reading to QGIS 1.0.0 Kore

2009-01-04 Thread Paolo Cavallini
Patrick Giraudoux ha scritto:
> Do those info put you a bit more clearly on the track ?

This (rather intricated, IMV) issue has been extensively discussed on
GRASS ML, so I suggest you to search there to better understand what's
going on.
It does not seem a QGIS problem, however.
All the best.
pc
-- 
Paolo Cavallini: http://faunalia.it/pc
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


[Qgis-user] Re: GRASS raster reading to QGIS 1.0.0 Kore

2009-01-04 Thread Patrick Giraudoux
Seems that I can narrow the question now. Actually, QGIS Kore reads 
GRASS maps well except when the maps  have been created from raster ramp 
color have been optimized with i.landsat.rgb. For example in GRASS:


r.composite r=etm7 g=etm5 b=etm2 out=south752brut

makes a map 'south752brut' which is well read within QGIS

Now if I do:
i.landsat.rgb r=etm7 g=etm5 b=etm2
r.composite r=etm7 g=etm5 b=etm2 out=south752opt

it makes a map 'south752opt' which is extremly long to read (several 
minutes), and when read makes change (displacement, zoom, etc...) 
extremely long to be displayed at a speed that prevent any work


However, 'south752opt' and 'south752brut' are quick/normally displayed 
both at the same speed when on work within GRASS (e.g. d.rast south752opt)


Any hint ?

Patrick



Patrick Giraudoux a écrit :

Dear all,

I am working on Ubuntu Hardy. I have just updated from QGIS Metis to 
Kore 1.0.0, and to my surprise, GRASS raster reading has become 
extremely slow, whatever the context (QGIS launched withing GRASS 6.3 
or from outside). Even small rasters take minutes before being 
displayed (against fraction of second on Metis).


Otherwise, raster import (eg tif) is working OK when GRASS is not 
concerned...


Any idea about what is happening ?

Patrick




begin:vcard
fn:Patrick Giraudoux
n:Giraudoux;Patrick
org;quoted-printable:Universit=C3=A9 de Franche-Comt=C3=A9;Chrono-environnement, UMR CNRS 6249 usc INRA
adr;quoted-printable:;;1 place Leclerc;Besan=C3=A7on;;25030;France
email;internet:patrick.giraud...@univ-fcomte.fr
title;quoted-printable:Professeur d'=C3=A9cologie
tel;work:+33 381 665 745
tel;fax:+33 381 665 797
version:2.1
end:vcard

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] Re: GRASS raster reading to QGIS 1.0.0 Kore

2009-01-04 Thread Micha Silver

Patrick Giraudoux wrote:


Martin Dobias a écrit :

2009/1/4 Patrick Giraudoux :
  

Seems that I can narrow the question now. Actually, QGIS Kore reads GRASS
maps well except when the maps  have been created from raster ramp color
have been optimized with i.landsat.rgb. For example in GRASS:

r.composite r=etm7 g=etm5 b=etm2 out=south752brut

makes a map 'south752brut' which is well read within QGIS

Now if I do:
i.landsat.rgb r=etm7 g=etm5 b=etm2
r.composite r=etm7 g=etm5 b=etm2 out=south752opt

it makes a map 'south752opt' which is extremly long to read (several
minutes), and when read makes change (displacement, zoom, etc...) extremely
long to be displayed at a speed that prevent any work

However, 'south752opt' and 'south752brut' are quick/normally displayed both
at the same speed when on work within GRASS (e.g. d.rast south752opt)

Any hint ?



Hi Patrick,

we're using GDAL library to access GRASS rasters, so the problem may
be there. I would suggest you to try reading the raster in some other
GDAL-based software [1] to see whether it also suffers slow
performance. If so, file a bug for GDAL, if the problem happens only
in QGIS file a ticket for QGIS with details.

Martin

[1] https://trac.osgeo.org/gdal/wiki/SoftwareUsingGdal

  

Ok. I will try and come back with the result ASAP.

Additionally before your mail I have made some other trials that may 
(?) help to understand what happens... Looks like corroborating your 
suspicion about bad interactions between rgdal and qgis. When I export 
the file using r.out.gdal format=GTiff and then try and read the tif 
file externally from QGIS, I have the same (bad/slow) result as when 
reading the grass file from QGIS within GRASS. Then, if I export the 
GRASS file with r.out.tiff I get a file which is easily read from QGIS 
and correctly (quickly) displayed as a three band tif object (as an 
external raster, of course). Furthermore, what surprises me is that 
when I read a raster GRASS file created with r.composite within QGIS, 
I get a 1-grey band file  with "color palette" ("palette de couleur" 
in French) activated in the "properties" box of the layer (however, I 
was more expecting a three band rgb).


Do those info put you a bit more clearly on the track ?

Thanks for your ideas and advice to where to adress the trouble...

Patrick

Some months ago there was discussion on this list pointing to two 
possible reasons for slow rendering of rasters:

http://www.mail-archive.com/qgis-user@lists.osgeo.org/msg00813.html
One was tiled rasters. For some reason it seemed like rasters with tiles 
(created with gdal_translate -co "TILED=YES") rendered somewhat slowly.
The second problem was incorrect CRS headers in the raster. Setting the 
correct projection header with gdalwarp caused tiffs to render faster.
I don't know if this is relevant to your case. (Does i.landsat.rgb set 
CRS headers??) But it's worth checking.

--
Micha







This mail was received via Mail-SeCure System.

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user




This mail was received via Mail-SeCure System.

  


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] plugin installer missing in qgis 1.0 (ubuntu hardy binary)

2009-01-04 Thread Borys Jurgiel
On niedziela 04 styczeń 2009 18:34:54 Agustin Lobo wrote:
> True, I was missing a click on the python-qgis package in Synaptic.
> Anyway, the problem I have now after installing python-qgis 1.0.0.~hardy
> is that
> the plugin manager states that "Plugin Installer (Version 0.06.2)
> [incompatible]"
> and cannot select it. (Note that I selected "complete removal" of the
> preview
> packages in Synaptic before the new install). I see that the
> *.pyc files in /usr/share/qgis/python/plugins/plugin_installer
> have date as of 2009-01-04
> but the *.py files are dated 2008-12-23

The plugin installer in /usr/share/qgis is 0.9.8, but is masked by an old and 
incompatible version (0.06.2) placed in ~/.qgis/python/plugins/ - just remove 
the plugin_installer directory from there.

Unfortunately a plugin in your home directory always masks its instance placed 
in the /usr location regardless of the versions. I'll think how to improve 
this behaviour.

Regards,
B
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user


Re: [Qgis-user] plugin installer missing in qgis 1.0 (ubuntu hardy binary)

2009-01-04 Thread Agustin Lobo

True again, thanks. I should have remembered this as I had the same problem
in previous upgrades!
Perhaps the download page should include a notice telling users
to remove or rename their ~/.qgis/python/plugins directory.
Also, while the masking behaviour is probably appropriate, including
a message in the Plugin manager reminding the user that the masking is 
actually taking place would be very useful. I.e., replacing

"Plugin Installer (Version 0.06.2) [incompatible]"
by
"Plugin Installer Masked by Version 0.06.2 [incompatible] in your
~/.qgis/python/plugins directory"
or something like that,

Agus


Borys Jurgiel wrote:

On niedziela 04 styczeń 2009 18:34:54 Agustin Lobo wrote:

True, I was missing a click on the python-qgis package in Synaptic.
Anyway, the problem I have now after installing python-qgis 1.0.0.~hardy
is that
the plugin manager states that "Plugin Installer (Version 0.06.2)
[incompatible]"
and cannot select it. (Note that I selected "complete removal" of the
preview
packages in Synaptic before the new install). I see that the
*.pyc files in /usr/share/qgis/python/plugins/plugin_installer
have date as of 2009-01-04
but the *.py files are dated 2008-12-23


The plugin installer in /usr/share/qgis is 0.9.8, but is masked by an old and 
incompatible version (0.06.2) placed in ~/.qgis/python/plugins/ - just remove 
the plugin_installer directory from there.


Unfortunately a plugin in your home directory always masks its instance placed 
in the /usr location regardless of the versions. I'll think how to improve 
this behaviour.


Regards,
B



--
Dr. Agustin Lobo
Institut de Ciencies de la Terra "Jaume Almera" (CSIC)
LLuis Sole Sabaris s/n
08028 Barcelona
Spain
Tel. 34 934095410
Fax. 34 934110012
email: agustin.l...@ija.csic.es
http://www.ija.csic.es/gt/obster
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user