Re: [Qgis-developer] OpenLayers Plugin - feature request

[Bernd Vogelgesang]

Hi Arne,
adding Stamen terrain background will not take months but a few minutes.

You can either use the Add\Edit\Remove tab under settings, or just copy a  
Stamen folder in qgis2/QuickMapServices/Contribute/data_sources and put it  
into /.qgis2/QuickMapServices/User/data_sources and then adjust the naming  
of the folder and of the settings in the metadata.ini


which looks like this then:

[general]
id = stamen_terrain_background
type = TMS

[ui]
group = stamen
alias = Stamen Terrain Background
icon = stamen.png

[license]
name = CC-BY 3.0
link = http://creativecommons.org/licenses/by/3.0/
copyright_text = Map tiles by Stamen Design, under CC BY 3.0. Data by  
OpenStreetMap, under ODbL

copyright_link = http://maps.stamen.com/
terms_of_use = http://maps.stamen.com/
[tms]
url = http://tile.stamen.com/terrain-background/{z}/{x}/{y}.png
zmin = 0
zmax = 19
y_origin_top = 1

This works quite well, but the service itself is somehow buggy. Lots of  
tiles are missing in deeper zoom levels, both in the browser-based version  
and in QGIS, so the problem is not from QuickMapServices but from the  
service itself.


Hope this helps
Bernd




Am 13.08.2016, 12:11 Uhr, schrieb Arne Wichmann :

begin  quotation  from Bernd Vogelgesang (in  
):

have a look at the QuickMapServices-plugin.
There are already some Stamen backgrounds available.
Maybe the one you look for is there too. Have also a look at  
Settings/More

services/Get contributed pack

As far as I know, OpenLayers will be replaced by QuickMapServices


Thanks, it helped a bit - it still does not have Stamen  
terrain-background
or something comparable, but it has two other maps I might use  
eventually.


I might try to add Stamen terrain-background when I get around to it -=  
but

I expect this will take some months.

cu

AW



--
Bernd Vogelgesang
Siedlerstraße 2
91083 Baiersdorf/Igelsdorf
Tel: 09133-825374
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers Plugin - feature request

[Arne Wichmann]

begin  quotation  from Bernd Vogelgesang (in 
):
> have a look at the QuickMapServices-plugin.
> There are already some Stamen backgrounds available.
> Maybe the one you look for is there too. Have also a look at Settings/More
> services/Get contributed pack
> 
> As far as I know, OpenLayers will be replaced by QuickMapServices

Thanks, it helped a bit - it still does not have Stamen terrain-background
or something comparable, but it has two other maps I might use eventually.

I might try to add Stamen terrain-background when I get around to it -= but
I expect this will take some months.

cu

AW
-- 
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (a...@saar.de)


signature.asc
Description: Digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers Plugin - feature request

[Pirmin Kalberer]

Hi Arne,

On Sonntag, 7. August 2016 14:39:18 CEST Arne Wichmann wrote:
> 
> for my own private anjoyment (role playing) I hacked the OpenLayers Plugin
> to work with Stamen terrain-background. As I think having a background
> which _only_ consists of physical features might be interesting for other
> uses, too, I suggest to you to add this to the OpenLayers Plugin.

You're welcome to open a ticket at [1] and attach your changed files.

Regards
Pirmin

[1] http://hub.qgis.org/projects/openlayers/issues

-- 
Pirmin Kalberer
Sourcepole  -  Linux & Open Source Solutions
http://www.sourcepole.com

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers Plugin - feature request

[Bernd Vogelgesang]

Hi Arne,
have a look at the QuickMapServices-plugin.
There are already some Stamen backgrounds available.
Maybe the one you look for is there too. Have also a look at Settings/More  
services/Get contributed pack


As far as I know, OpenLayers will be replaced by QuickMapServices

Chhers
Bernd

Am 07.08.2016, 14:39 Uhr, schrieb Arne Wichmann :


Hi,

for my own private anjoyment (role playing) I hacked the OpenLayers  
Plugin

to work with Stamen terrain-background. As I think having a background
which _only_ consists of physical features might be interesting for other
uses, too, I suggest to you to add this to the OpenLayers Plugin.

(I would have sent you a patch, but my abilities to hack python are very
rudimentary...)

cu

AW



--
Dipl-Geogr. Bernd Vogelgesang
Siedlerstraße 2
91083 Baiersdorf
Tel.: 09133-825374
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] OpenLayers Plugin - feature request

[Arne Wichmann]

Hi,

for my own private anjoyment (role playing) I hacked the OpenLayers Plugin
to work with Stamen terrain-background. As I think having a background
which _only_ consists of physical features might be interesting for other
uses, too, I suggest to you to add this to the OpenLayers Plugin.

(I would have sent you a patch, but my abilities to hack python are very
rudimentary...)

cu

AW
-- 
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (a...@saar.de)


signature.asc
Description: Digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Openlayers plugin support in QGIS 2.4

[René-Luc Dhont]

Hi Ali,

You can use this method instead of OpenLayers Plugin :
Using Map Tile Servers in QGIS 2.4 
http://www.konstantingreger.net/using-map-tile-servers-in-qgis-2-4/


Based on :
How to display OpenStreetMap data tiles with no plugin inside Qgis 
http://www.3liz.com/blog/rldhont/index.php?post/2012/07/17/OpenStreetMap-Tiles-in-QGIS


Regards,
René-Luc D'Hont

Le 07/07/2014 07:38, Aamir Ali a écrit :

Dear All

I am using QGIS 2.4 built using qgis source code and qt creator in
ubuntu. I am unable to find openlayers plugin in the list of plugin
repository. I have a two questions

1. Whether it is not compatible with this version or my build has some problems?

2. If its not compatible then how long it will take the community to
release the compatible version?


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


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

Re: [Qgis-developer] Openlayers plugin support in QGIS 2.4

[René-Luc Dhont]

Hi Ali,

You'll find examples here :
http://www.gdal.org/frmt_wms.html

Remember that using Google Maps needs to accept the Google licence.

Regards

René-Luc


Le 07/07/2014 09:42, Aamir Ali a écrit :

Thanks for your prompt response

I need to call google maps, how can I use TMS service to call the
tiles from Google Map.

Regards

Ali


On Mon, Jul 7, 2014 at 11:53 AM, René-Luc Dhont rldh...@gmail.com wrote:

Hi Ali,

You can use this method instead of OpenLayers Plugin :
Using Map Tile Servers in QGIS 2.4
http://www.konstantingreger.net/using-map-tile-servers-in-qgis-2-4/

Based on :
How to display OpenStreetMap data tiles with no plugin inside Qgis
http://www.3liz.com/blog/rldhont/index.php?post/2012/07/17/OpenStreetMap-Tiles-in-QGIS

Regards,
René-Luc D'Hont

Le 07/07/2014 07:38, Aamir Ali a écrit :

Dear All

I am using QGIS 2.4 built using qgis source code and qt creator in
ubuntu. I am unable to find openlayers plugin in the list of plugin
repository. I have a two questions

1. Whether it is not compatible with this version or my build has some
problems?

2. If its not compatible then how long it will take the community to
release the compatible version?


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


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


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

Re: [Qgis-developer] Openlayers plugin support in QGIS 2.4

[Etienne Tourigny]

You cannot use the google maps TMS service, it is not allowed under the
Google Maps TOS.


On Mon, Jul 7, 2014 at 4:54 AM, René-Luc Dhont rldh...@gmail.com wrote:

 Hi Ali,

 You'll find examples here :
 http://www.gdal.org/frmt_wms.html

 Remember that using Google Maps needs to accept the Google licence.

 Regards

 René-Luc


 Le 07/07/2014 09:42, Aamir Ali a écrit :

 Thanks for your prompt response

 I need to call google maps, how can I use TMS service to call the
 tiles from Google Map.

 Regards

 Ali



 On Mon, Jul 7, 2014 at 11:53 AM, René-Luc Dhont rldh...@gmail.com
 wrote:

 Hi Ali,

 You can use this method instead of OpenLayers Plugin :
 Using Map Tile Servers in QGIS 2.4
 http://www.konstantingreger.net/using-map-tile-servers-in-qgis-2-4/

 Based on :
 How to display OpenStreetMap data tiles with no plugin inside Qgis
 http://www.3liz.com/blog/rldhont/index.php?post/2012/
 07/17/OpenStreetMap-Tiles-in-QGIS

 Regards,
 René-Luc D'Hont

 Le 07/07/2014 07:38, Aamir Ali a écrit :

 Dear All

 I am using QGIS 2.4 built using qgis source code and qt creator in
 ubuntu. I am unable to find openlayers plugin in the list of plugin
 repository. I have a two questions

 1. Whether it is not compatible with this version or my build has some
 problems?

 2. If its not compatible then how long it will take the community to
 release the compatible version?


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


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


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

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

[Qgis-developer] Openlayers plugin support in QGIS 2.4

[Aamir Ali]

Dear All

I am using QGIS 2.4 built using qgis source code and qt creator in
ubuntu. I am unable to find openlayers plugin in the list of plugin
repository. I have a two questions

1. Whether it is not compatible with this version or my build has some problems?

2. If its not compatible then how long it will take the community to
release the compatible version?


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

[Qgis-developer] OpenLayers plugin bug

[Brent Wood]

Hi,

I have a problem with this very useful plugin.

If I load a Postgis dataset which includes points across 180, for data captured 
around New Zealand, using longitudes in the 0-360 space (which is valid data 
for EPSG:4326) they plot fine in QGIS.

If I then start the plugin  use a Google/Yahoo/etc basemap, the points are 
(usually) initially in the correct place and plot OK. Sometimes the points in 
the W hemisphere fail to render, sometimes they are OK. This is on a zoomed out 
map.

As I zoom in, QGIS starts to omit the points in the W hemisphere altogether, 
even in the configurations that were OK when zoomed out. QGIS also sometimes 
starts to offset the points from the basemap, so that the western points on the 
map plot at an increasingly offset position, and the eastern points are 
missing. As I zoom back out, this offset is retained and the map fails to 
overlay the points correctly.

I'm assuming this is related to the plugin switching the canvas to EPSG:3857 
and failing to support the 0-360 longitude coordinates. Given Proj.4 is used as 
the reprojection engine, there should be no problems with the 0-360 coords 
being correctly mapped to EPSG:3857, as in my experience Proj.4 (cs2cs) has 
supported 0-360 input seamlessly for some years now.


Is there any simple fix I can apply? If some funding is required to make the 
plugin work correctly across 180 with 0-360 longitude data, this is possible.   



inTHANKSvance


Brent Wood___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers plugin

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 18/07/2013 22:26, Richard Duivenvoorde ha scritto:

 the reason to make it available via qgis.nl is to make it only available to
 'expert'-users. It was a very quick fix, so our idea was to give the 'normal' 
 users
 only the 'real fix' from sourcepole later.

that shouldn't be a problem: normal users do not istall qgis-dev

 Besides that, as I'm not the 'owner' of the plugin, I feel that sourcepole 
 should
 have the last word in this.
 
 If it is ok with sourcepole, feel free to take that zip and upload it to
 qgis.plugins.org (I'm abroad with limited internet access now).

ok, let's wait for them then.
All the best.

- -- 
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlHo2/EACgkQ/NedwLUzIr6rOQCfaE8JKEYQpy5aKFRjd2gpX5KO
38sAn31Waz6T6zw1CGn2z7p/cyvaTuHH
=pLIO
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] OpenLayers plugin

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all.
The plugin is currently broken for master. I remember Richard fixed it, but it 
is not
available from the repo: could this please be added, so we can keep on working 
in the
meantime?
Thanks.
- -- 
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlHnvxUACgkQ/NedwLUzIr6HPQCeLgUjLKrMkH6q9RNeprtsxDIA
nYgAn26pyCCWvz5ISyv69GGma/xhePkU
=g2sN
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers plugin

[Werner Macho]

Hi
I remember Pirmin said something about they are going to fix it for
master during the HF in Brighton..

regards
Werner

On Thu, Jul 18, 2013 at 12:10 PM, Paolo Cavallini cavall...@faunalia.it wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi all.
 The plugin is currently broken for master. I remember Richard fixed it, but 
 it is not
 available from the repo: could this please be added, so we can keep on 
 working in the
 meantime?
 Thanks.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Icedove - http://www.enigmail.net/

 iEYEARECAAYFAlHnvxUACgkQ/NedwLUzIr6HPQCeLgUjLKrMkH6q9RNeprtsxDIA
 nYgAn26pyCCWvz5ISyv69GGma/xhePkU
 =g2sN
 -END PGP SIGNATURE-
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers plugin

[Matthias Kuhn]

Based on Tim's expected release date (before Brighton) this will be 
fixed it for 2.0 and not for master there ;-)

Cheers
Matthias

On Don 18 Jul 2013 13:13:36 CEST, Werner Macho wrote:
 Hi
 I remember Pirmin said something about they are going to fix it for
 master during the HF in Brighton..

 regards
 Werner

 On Thu, Jul 18, 2013 at 12:10 PM, Paolo Cavallini cavall...@faunalia.it 
 wrote:


 * *BEGIN ENCRYPTED or SIGNED PART* *

 Hi all.
 The plugin is currently broken for master. I remember Richard fixed it, but 
 it is not
 available from the repo: could this please be added, so we can keep on 
 working in the
 meantime?
 Thanks.
 --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario


 ** *END ENCRYPTED or SIGNED PART* **

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





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

Re: [Qgis-developer] OpenLayers plugin

[Werner Macho]

*lol*
ok yeah .. you are right .. I should not mix up terms when it comes to
a release ..


On Thu, Jul 18, 2013 at 1:25 PM, Matthias Kuhn matthias.k...@gmx.ch wrote:
 Based on Tim's expected release date (before Brighton) this will be
 fixed it for 2.0 and not for master there ;-)

 Cheers
 Matthias

 On Don 18 Jul 2013 13:13:36 CEST, Werner Macho wrote:
 Hi
 I remember Pirmin said something about they are going to fix it for
 master during the HF in Brighton..

 regards
 Werner

 On Thu, Jul 18, 2013 at 12:10 PM, Paolo Cavallini cavall...@faunalia.it 
 wrote:


 * *BEGIN ENCRYPTED or SIGNED PART* *

 Hi all.
 The plugin is currently broken for master. I remember Richard fixed it, but 
 it is not
 available from the repo: could this please be added, so we can keep on 
 working in the
 meantime?
 Thanks.
 --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario


 ** *END ENCRYPTED or SIGNED PART* **

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





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

Re: [Qgis-developer] OpenLayers plugin

[Etienne Tourigny]

There is a working version (thanks to Richard Duivenvoorde) available at
http://www.qgis.nl/2013/06/30/english-temporary-fix-for-openlayers-plugin/?lang=en

Why not upload it now on plugins.qgis.org (for qgis 1.9 only), and then
upload the new (improved) plugin when ready?

cheers
Etienne

On Thu, Jul 18, 2013 at 8:27 AM, Werner Macho werner.ma...@gmail.comwrote:

 *lol*
 ok yeah .. you are right .. I should not mix up terms when it comes to
 a release ..


 On Thu, Jul 18, 2013 at 1:25 PM, Matthias Kuhn matthias.k...@gmx.ch
 wrote:
  Based on Tim's expected release date (before Brighton) this will be
  fixed it for 2.0 and not for master there ;-)
 
  Cheers
  Matthias
 
  On Don 18 Jul 2013 13:13:36 CEST, Werner Macho wrote:
  Hi
  I remember Pirmin said something about they are going to fix it for
  master during the HF in Brighton..
 
  regards
  Werner
 
  On Thu, Jul 18, 2013 at 12:10 PM, Paolo Cavallini 
 cavall...@faunalia.it wrote:
 
 
  * *BEGIN ENCRYPTED or SIGNED PART* *
 
  Hi all.
  The plugin is currently broken for master. I remember Richard fixed it,
 but it is not
  available from the repo: could this please be added, so we can keep on
 working in the
  meantime?
  Thanks.
  --
  Paolo Cavallini - Faunalia
  www.faunalia.eu
  Full contact details at www.faunalia.eu/pc
  Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 
 
  ** *END ENCRYPTED or SIGNED PART* **
 
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer
 
 
 
 
 
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer

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

Re: [Qgis-developer] OpenLayers plugin

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 18/07/2013 15:43, Etienne Tourigny ha scritto:
 There is a working version (thanks to Richard Duivenvoorde) available at 
 http://www.qgis.nl/2013/06/30/english-temporary-fix-for-openlayers-plugin/?lang=en

that's it, thanks

 Why not upload it now on plugins.qgis.org http://plugins.qgis.org (for qgis 
 1.9
 only), and then upload the new (improved) plugin when ready?

+1: Richard?

all the best.
- -- 
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlHoBPkACgkQ/NedwLUzIr7sYACgsGx3aXYgiVEO0mij+ZNl+6bm
NlsAn3dXaH57K3/L2StLPLq6XghKD3Hz
=pOEU
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers plugin

[Richard Duivenvoorde]

On 18-07-13 17:08, Paolo Cavallini wrote:

Il 18/07/2013 15:43, Etienne Tourigny ha scritto:

There is a working version (thanks to Richard Duivenvoorde) available at
http://www.qgis.nl/2013/06/30/english-temporary-fix-for-openlayers-plugin/?lang=en


that's it, thanks


Why not upload it now on plugins.qgis.org http://plugins.qgis.org (for qgis 
1.9
only), and then upload the new (improved) plugin when ready?


+1: Richard?


Hi Paolo,

the reason to make it available via qgis.nl is to make it only available 
to 'expert'-users. It was a very quick fix, so our idea was to give the 
'normal' users only the 'real fix' from sourcepole later.


Besides that, as I'm not the 'owner' of the plugin, I feel that 
sourcepole should have the last word in this.


If it is ok with sourcepole, feel free to take that zip and upload it to 
qgis.plugins.org (I'm abroad with limited internet access now).


Regards,

Richard

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

Re: [Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[Anita Graser]

On Sun, Jun 16, 2013 at 8:45 PM, Pirmin Kalberer pi...@sourcepole.comwrote:


 According to Tims latest plan I don't expect the 2.0 release before
 Brighton.
  So the OL plugin should be ready for 2.0 early enough.



Are we really talking September now?
I'm just asking because then I will stop telling people that 2.0 should be
out soon.

Best wishes,
Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[Tim Sutton]

Hi

On Mon, Jun 17, 2013 at 11:19 PM, Anita Graser anitagra...@gmx.at wrote:
 On Sun, Jun 16, 2013 at 8:45 PM, Pirmin Kalberer pi...@sourcepole.com
 wrote:


 According to Tims latest plan I don't expect the 2.0 release before
 Brighton.
  So the OL plugin should be ready for 2.0 early enough.



 Are we really talking September now?
 I'm just asking because then I will stop telling people that 2.0 should be
 out soon.


Well currently there are 66 blocking issues in the queue. That means
we either need to follow Marco H's suggestion of having a time based
cut off for blockers, or we need to wait an indeterminate time. Once
the PSC has agreed on which way we will continue, we will post a more
precise timeline. I would certainly like to see QGIS 2.0 released
*before* FOSS4G2013.

Regards

Tim


 Best wishes,
 Anita

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




--
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[Anita Graser]

Hi Richard,
If you have a - partially - working version please share it. It will serve
until the official and backwards compatible version is available.
Thanks and best wishes
Anita
 On Jun 16, 2013 10:30 AM, Richard Duivenvoorde rdmaili...@duif.net
wrote:

 On 16-06-13 00:39, Anita Graser wrote:

 I'm a bit worried about not having a functioning Openlayers plugin in
 QGIS 2.0 for two months.
 Can someone with experience in porting plugins estimate how much work it
 really is to make it compatible with the new API


 Hi Pirmin,

 if we manage to release 2.0 before Brighton, I agree that the Openlayers
 plugin is one plugin which should be available at 2.0 launch.

 Here locally I managed to get it running in current master (most of it,
 overview widget is not ok yet).
 But I do not want to force/stress Sourcepole or Matthias to put time in
 looking into it if they have more important things to do.

 And maybe you have (bigger/other) plans with the plugin, like a
 refactoring or upgrade of bigger parts of the code. Or maybe you know with
 QGIS 2.0 there are non sip parts that will give problems?
 I can also imagine that you really want to support only ONE plugin working
 for both sip api versions.

 But that said, I'm happy to put what I have now put on Github and ask for
 a pull request in a 2.0 branch (what I did is NOT compatible with 1.8). I'm
 also available if bugs pop up in that version in short future.

 And I agree that Brighton is then a nice place to do the 'bigger' work for
 this really important plugin.

 Regards,

 Richard Duivenvoorde





 __**_
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/**mailman/listinfo/qgis-**developerhttp://lists.osgeo.org/mailman/listinfo/qgis-developer

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

Re: [Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 16/06/2013 00:39, Anita Graser ha scritto:

 I'm a bit worried about not having a functioning Openlayers plugin in QGIS 
 2.0 for
 two months. 

Agreed - in fact, I think OLP is so important that it should be included in 
master
(for QGIS 2.1, at this point).
Objections?
All the best.
- -- 
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlG9YhQACgkQ/NedwLUzIr6AUQCaA6UY4lbkGEIWAGk2ag8sdoF4
1HcAoKkIv6hWlt4v5PYkYbQ1/TnNO9GG
=muhQ
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[René-Luc D'Hont]

Le 16 juin 2013 08:58, Paolo Cavallini cavall...@faunalia.it a écrit :

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Il 16/06/2013 00:39, Anita Graser ha scritto:

  I'm a bit worried about not having a functioning Openlayers plugin in
QGIS 2.0 for
  two months.

 Agreed - in fact, I think OLP is so important that it should be included
in master
 (for QGIS 2.1, at this point).
 Objections?

I don't think OLP should be included in master.
OLP is important for some users but for better compatibility I think they
should use the OGR WMS driver for OpenStreetMap, Bing Maps and others.
We can integrate in QGIS 2.1 a layer listing menu with some predefined
layers, isn't it ?

Regards,
René-Luc D'Hont
3Liz

 All the best.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAlG9YhQACgkQ/NedwLUzIr6AUQCaA6UY4lbkGEIWAGk2ag8sdoF4
 1HcAoKkIv6hWlt4v5PYkYbQ1/TnNO9GG
 =muhQ
 -END PGP SIGNATURE-
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[Richard Duivenvoorde]

On 16-06-13 00:39, Anita Graser wrote:

I'm a bit worried about not having a functioning Openlayers plugin in
QGIS 2.0 for two months.
Can someone with experience in porting plugins estimate how much work it
really is to make it compatible with the new API


Hi Pirmin,

if we manage to release 2.0 before Brighton, I agree that the Openlayers 
plugin is one plugin which should be available at 2.0 launch.


Here locally I managed to get it running in current master (most of it, 
overview widget is not ok yet).
But I do not want to force/stress Sourcepole or Matthias to put time in 
looking into it if they have more important things to do.


And maybe you have (bigger/other) plans with the plugin, like a 
refactoring or upgrade of bigger parts of the code. Or maybe you know 
with QGIS 2.0 there are non sip parts that will give problems?
I can also imagine that you really want to support only ONE plugin 
working for both sip api versions.


But that said, I'm happy to put what I have now put on Github and ask 
for a pull request in a 2.0 branch (what I did is NOT compatible with 
1.8). I'm also available if bugs pop up in that version in short future.


And I agree that Brighton is then a nice place to do the 'bigger' work 
for this really important plugin.


Regards,

Richard Duivenvoorde





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

Re: [Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[Leyan]

I agree, not having Openlayers would be a sufficient reason not to 
upgrade for me.


Regards,

Leyan

On 06/16/2013 06:39 AM, Anita Graser wrote:

Hi,

I'm a bit worried about not having a functioning Openlayers plugin in 
QGIS 2.0 for two months.
Can someone with experience in porting plugins estimate how much work 
it really is to make it compatible with the new API?
I think it would put a lot of people off if they cannot use their 
background layers anymore.


Best wishes,
Anita



On Sat, Jun 15, 2013 at 10:11 PM, Pirmin Kalberer 
pi...@sourcepole.com mailto:pi...@sourcepole.com wrote:


Hi Paolo,

Am Donnerstag, 13. Juni 2013, 18.06:37 schrieb Paolo Cavallini:

 Hi all.
 Now that the release is approaching: any news from external plugin
 authors? I think that at least some of the most popular and
important
 (e.g. OpenLayers plugin) should be ready by the release.

We plan to update our plugins (OpenLayers, WPS Client, etc.)
during the
Hackfest in Brighton. See also http://hub.qgis.org/issues/8059.

Regards
Pirmin

--
Pirmin Kalberer
Sourcepole  -  Linux  Open Source Solutions
http://www.sourcepole.com

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




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


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

Re: [Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[Pirmin Kalberer]

Am Sonntag, 16. Juni 2013, 10.30:59 schrieb Richard Duivenvoorde:
 On 16-06-13 00:39, Anita Graser wrote:
  I'm a bit worried about not having a functioning Openlayers plugin in
  QGIS 2.0 for two months.
  Can someone with experience in porting plugins estimate how much work it
  really is to make it compatible with the new API
 
 Hi Pirmin,
 
 if we manage to release 2.0 before Brighton, I agree that the Openlayers
 plugin is one plugin which should be available at 2.0 launch.

According to Tims latest plan I don't expect the 2.0 release before Brighton.
So the OL plugin should be ready for 2.0 early enough.

 
 Here locally I managed to get it running in current master (most of it,
 overview widget is not ok yet).
 But I do not want to force/stress Sourcepole or Matthias to put time in
 looking into it if they have more important things to do.
 
 And maybe you have (bigger/other) plans with the plugin, like a
 refactoring or upgrade of bigger parts of the code. Or maybe you know
 with QGIS 2.0 there are non sip parts that will give problems?
 I can also imagine that you really want to support only ONE plugin
 working for both sip api versions.
 
 But that said, I'm happy to put what I have now put on Github and ask
 for a pull request in a 2.0 branch (what I did is NOT compatible with
 1.8). I'm also available if bugs pop up in that version in short future.
 
 And I agree that Brighton is then a nice place to do the 'bigger' work
 for this really important plugin.

We're happy to integrate a pull request earlier. But as statet in the ticket, 
the patch has to be backwards compatible with 1.8. It is no option for us to 
maintain our plugins for two QGIS versions in parallel. This is some initial 
extra work, but will help us during the coming years to keep 1.8 users up to 
date.

Regards
Pirmin

-- 
Pirmin Kalberer
Sourcepole  -  Linux  Open Source Solutions
http://www.sourcepole.com

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

[Qgis-developer] Openlayers plugin in 2.0 Was: QGIS 2.0 release and plugins

[Anita Graser]

Hi,

I'm a bit worried about not having a functioning Openlayers plugin in QGIS
2.0 for two months.
Can someone with experience in porting plugins estimate how much work it
really is to make it compatible with the new API?
I think it would put a lot of people off if they cannot use their
background layers anymore.

Best wishes,
Anita



On Sat, Jun 15, 2013 at 10:11 PM, Pirmin Kalberer pi...@sourcepole.comwrote:

 Hi Paolo,

 Am Donnerstag, 13. Juni 2013, 18.06:37 schrieb Paolo Cavallini:
 
  Hi all.
  Now that the release is approaching: any news from external plugin
  authors? I think that at least some of the most popular and important
  (e.g. OpenLayers plugin) should be ready by the release.

 We plan to update our plugins (OpenLayers, WPS Client, etc.) during the
 Hackfest in Brighton. See also http://hub.qgis.org/issues/8059.

 Regards
 Pirmin

 --
 Pirmin Kalberer
 Sourcepole  -  Linux  Open Source Solutions
 http://www.sourcepole.com

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

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

[Qgis-developer] openlayers plugin: infinite loop when plugin is in shared network folder

[Duarte Carreira]

Hi.

While still trying to get qgis working from a network share (windows), I found 
this particular problem with openlayers plugin.

I have osgeow4 copied to a network share and edit the .bat files and qt.conf to 
point to this share. As far as I can tell everything is working, except for 
openlayers plugin...

The layer I choose loads ok and appears in the legend.

When I click to turn visibility on, qgis waits forever and has to be forced to 
close.

I tried debugging with winpdb and it seems the plugin gets stucked on line 107 
in openlayers_layer.py:

  # wait for page to finish loading
  while not self.loaded:
qApp.processEvents()

If I copy the plugin to the user's .qgis/python/plugins folder then it works 
fine.

I suspected the url created from the location of the plugin would be invalid 
but seems fine to me, and I can load it in chrome.

So I'm out of ideas... can anyone help?

Thanks,
Duarte




Duarte Carreira
Diretor | Dep. Informa??o Geogr?fica e Cartografia

www.edia.pthttp://www.edia.pt
Tel. +351 284315100

[http://www.edia.pt/edia/images/edia_logo2.gif]http://www.edia.pt

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Angus Carr]

Hi,

I am a plugin developer who was bitten by this API change. It's easily
worked around with a try...except... structure, but that becomes unneeded
clutter. I am working on a plugin that I want to work in the future API and
the stable API at version 1.8, so right now I need that clutter to make it
work in both versions.

I also have the opposite problem, that there are features in the dev API
that I want to use, but they are not in the stable API. I am thinking of
the QgsLayer.diagramRenderer() call, which is not found in the older API,
even though it is in the docs... :-)

So, I second your adding the addMapLayer() call back in, if only to keep my
code clutter down :-)

Cheers,
Angus Carr.

On Thu, Jan 31, 2013 at 4:37 PM, Etienne Tourigny
etourigny@gmail.comwrote:

 On Thu, Jan 24, 2013 at 10:40 AM, Martin Dobias wonder...@gmail.com
 wrote:
  On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
  alexander.b...@gmail.com wrote:
  Hi Pirmin,
 
  as I can see in API docs (using your link) there is a note:
 
  Note:
  This method is deprecated since QGIS 1.8, you should use
  addMapLayers rather.
 
  A bit off-topic, but I find it weird that addMapLayer() method has
  been marked as deprecated: even if now we have the possibility to
  specify more layers at once, it is always good to have a convenience
  call that accepts just one layer (as that's what most users will do).

 I also think that this method should be brought back to the api, see
 all the errors that are popping up in both mailing list about
 QgsMapRegistry::addMapLayer().

 Why break things like this when there is no real gain?

 Unless someone objects, I will restore QgsMapRegistry::addMapLayer()

 Etienne

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

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Etienne Tourigny]

On Fri, Feb 1, 2013 at 12:40 PM, Angus Carr angus.c...@gmail.com wrote:
 Hi,

 I am a plugin developer who was bitten by this API change. It's easily
 worked around with a try...except... structure, but that becomes unneeded
 clutter. I am working on a plugin that I want to work in the future API and
 the stable API at version 1.8, so right now I need that clutter to make it
 work in both versions.

 I also have the opposite problem, that there are features in the dev API
 that I want to use, but they are not in the stable API. I am thinking of the
 QgsLayer.diagramRenderer() call, which is not found in the older API, even
 though it is in the docs... :-)

 So, I second your adding the addMapLayer() call back in, if only to keep my
 code clutter down :-)

I wonder why this was marked as deprecated in the first place...
supposedly for keeping devs from calling addMapLayer() multiple times,
when more than 1 layer is added?
Is there a way we can make this suggestion visible, other than adding
it to the api docs?


 Cheers,
 Angus Carr.


 On Thu, Jan 31, 2013 at 4:37 PM, Etienne Tourigny etourigny@gmail.com
 wrote:

 On Thu, Jan 24, 2013 at 10:40 AM, Martin Dobias wonder...@gmail.com
 wrote:
  On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
  alexander.b...@gmail.com wrote:
  Hi Pirmin,
 
  as I can see in API docs (using your link) there is a note:
 
  Note:
  This method is deprecated since QGIS 1.8, you should use
  addMapLayers rather.
 
  A bit off-topic, but I find it weird that addMapLayer() method has
  been marked as deprecated: even if now we have the possibility to
  specify more layers at once, it is always good to have a convenience
  call that accepts just one layer (as that's what most users will do).

 I also think that this method should be brought back to the api, see
 all the errors that are popping up in both mailing list about
 QgsMapRegistry::addMapLayer().

 Why break things like this when there is no real gain?

 Unless someone objects, I will restore QgsMapRegistry::addMapLayer()

 Etienne

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


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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Etienne Tourigny]

On Fri, Feb 1, 2013 at 12:40 PM, Angus Carr angus.c...@gmail.com wrote:
 Hi,

 I am a plugin developer who was bitten by this API change. It's easily
 worked around with a try...except... structure, but that becomes unneeded
 clutter. I am working on a plugin that I want to work in the future API and
 the stable API at version 1.8, so right now I need that clutter to make it
 work in both versions.

actually it's probably easier doing something like:

if QGis.QGIS_VERSION_INT  10900:
  use old api
else:
  use new api


 I also have the opposite problem, that there are features in the dev API
 that I want to use, but they are not in the stable API. I am thinking of the
 QgsLayer.diagramRenderer() call, which is not found in the older API, even
 though it is in the docs... :-)

 So, I second your adding the addMapLayer() call back in, if only to keep my
 code clutter down :-)

 Cheers,
 Angus Carr.


 On Thu, Jan 31, 2013 at 4:37 PM, Etienne Tourigny etourigny@gmail.com
 wrote:

 On Thu, Jan 24, 2013 at 10:40 AM, Martin Dobias wonder...@gmail.com
 wrote:
  On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
  alexander.b...@gmail.com wrote:
  Hi Pirmin,
 
  as I can see in API docs (using your link) there is a note:
 
  Note:
  This method is deprecated since QGIS 1.8, you should use
  addMapLayers rather.
 
  A bit off-topic, but I find it weird that addMapLayer() method has
  been marked as deprecated: even if now we have the possibility to
  specify more layers at once, it is always good to have a convenience
  call that accepts just one layer (as that's what most users will do).

 I also think that this method should be brought back to the api, see
 all the errors that are popping up in both mailing list about
 QgsMapRegistry::addMapLayer().

 Why break things like this when there is no real gain?

 Unless someone objects, I will restore QgsMapRegistry::addMapLayer()

 Etienne

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


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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Jürgen E . Fischer]

Hi Etienne,

On Fri, 01. Feb 2013 at 13:01:35 -0200, Etienne Tourigny wrote:
 Is there a way we can make this suggestion visible, other than adding
 it to the api docs?

There is now.  Apparently since python 2.7 all deprecation warnings where
disabled by default.  The messages now appear in the message log.

Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
committ(ed|ing) to Quantum GIS IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Etienne Tourigny]

On Fri, Feb 1, 2013 at 1:35 PM, Jürgen E. j...@norbit.de wrote:
 Hi Etienne,

 On Fri, 01. Feb 2013 at 13:01:35 -0200, Etienne Tourigny wrote:
 Is there a way we can make this suggestion visible, other than adding
 it to the api docs?

 There is now.  Apparently since python 2.7 all deprecation warnings where
 disabled by default.  The messages now appear in the message log.

Hi,

I have restored addMapLayer() to the API but it is still deprecated,
so hopefully new plugins, and any updated ones, will use
addMapLayers() instead.

Cheers
Etienne


 Jürgen

 --
 Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
 Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
 Software Engineer D-26506 Norden   http://www.norbit.de
 committ(ed|ing) to Quantum GIS IRC: jef on FreeNode

 --
 norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
 Rheinstrasse 13, 26506 Norden
 GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Etienne Tourigny]

On Thu, Jan 24, 2013 at 10:40 AM, Martin Dobias wonder...@gmail.com wrote:
 On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
 alexander.b...@gmail.com wrote:
 Hi Pirmin,

 as I can see in API docs (using your link) there is a note:

 Note:
 This method is deprecated since QGIS 1.8, you should use
 addMapLayers rather.

 A bit off-topic, but I find it weird that addMapLayer() method has
 been marked as deprecated: even if now we have the possibility to
 specify more layers at once, it is always good to have a convenience
 call that accepts just one layer (as that's what most users will do).

I also think that this method should be brought back to the api, see
all the errors that are popping up in both mailing list about
QgsMapRegistry::addMapLayer().

Why break things like this when there is no real gain?

Unless someone objects, I will restore QgsMapRegistry::addMapLayer()

Etienne


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

Re: [Qgis-developer] OpenLayers plugin release and Python API

[Pirmin Kalberer]

Hi Nathan,

Am Mittwoch, 23. Januar 2013, 16.09:43 schrieb Nathan Woodrow:
 
 We are preparing for 2.0 so the plan has always been to break API and
 remove old unused methods.
 
 The select API will break again soon once Martin merges his new vector
 API.

If it's the plan to break plugins then I wait with the next update until 2.0 
is released.
Other OSS projects I'm working with care more for their users. They release a 
new API with a major version and deprecate the old one. The deprecated API 
remains available for at least one release. I'm fine with removing old 
labelling, etc., but not with breaking the plugin API from 1.8 to 2.0 without 
proper deprecation.

Pirmin

 
 - Nathan
 From: Pirmin Kalberer
 Sent: 24/01/2013 9:58 AM
 To: qgis-dev
 Subject: [Qgis-developer] OpenLayers plugin release and Python API
 breaks
 Hi all,
 
 I found the time for an OpenLayers plugin release with merged pull requests
 for Stamen map support and fixes for Python API breaks in master branch (See
 https://twitter.com/PirminKalberer/status/294226472707715072 for credits).
 The second point was quite annoying for many users and myself. It is a
 really bad practice to break the API without deprecation messages when
 calling these methods. There should be enough time (at least one minor
 version) for developers for updating their plugins. In this case it would
 have been easy to keep the old API and add a deprecation message similar to
 http://code.activestate.com/recipes/391367-deprecated/
 
 Regards
 Pirmin
-- 
Pirmin Kalberer
Sourcepole  -  Linux  Open Source Solutions
http://www.sourcepole.com

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Jürgen E . Fischer]

Hi Matthias,

On Thu, 24. Jan 2013 at 08:59:47 +0100, Matthias Kuhn wrote:
 The question is, where and when to communicate it to the developer:
  * The MessageLog (why not)

Already done in f2029b4ec.

Python 2.7 disabled the deprecation warnings by default.  But the would have
gone to stderr anyway (which is invisible for most users).

 I would propose to add a QGS_DEPRECATED macro which could be placed in  
 any deprecated method which will take appropriate actions and  
 deprecation methods will appear in a standardized way.

We (or better put Qt) already have that too (Q_DECL_DEPRECATED).  But there
it's a compile time warning - and apparently not everyone builds with PEDANTIC
enabled...


Jürgen 

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
committ(ed|ing) to Quantum GIS IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Matthias Kuhn]

Hi Jürgen

On 01/24/2013 09:37 AM, Jürgen E. Fischer wrote:

Hi Matthias,

On Thu, 24. Jan 2013 at 08:59:47 +0100, Matthias Kuhn wrote:

The question is, where and when to communicate it to the developer:
  * The MessageLog (why not)

Already done in f2029b4ec.

Nice.
How do I need to tag deprecated methods to trigger this?


Python 2.7 disabled the deprecation warnings by default.  But the would have
gone to stderr anyway (which is invisible for most users).


I would propose to add a QGS_DEPRECATED macro which could be placed in
any deprecated method which will take appropriate actions and
deprecation methods will appear in a standardized way.

We (or better put Qt) already have that too (Q_DECL_DEPRECATED).  But there
it's a compile time warning - and apparently not everyone builds with PEDANTIC
enabled...

... and for python plugins there is no compile time ...


Jürgen



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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Matthias Kuhn]

Hi Jürgen,

On 01/24/2013 10:04 AM, Jürgen E. Fischer wrote:

Hi Matthias,

On Thu, 24. Jan 2013 at 09:43:28 +0100, Matthias Kuhn wrote:

Already done in f2029b4ec.

Nice.
How do I need to tag deprecated methods to trigger this?

/Deprecated/ in the .sip


We (or better put Qt) already have that too (Q_DECL_DEPRECATED).  But there
it's a compile time warning - and apparently not everyone builds with PEDANTIC
enabled...

... and for python plugins there is no compile time ...

Oh, I thought you were talking about C++ - macro didn't sound pythonish to me.
I thought it might be possible to tag it as deprecated independent of 
the language. But I'm not sure if this is possible. And if not, adding 
the /Deprecated/ in the .sip file isn't that much work.


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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Werner Macho]

Hmm
That reminds me on the consolidation efforts ..
There is a lot of outdated, wrong information somewhere in the wiki -
(including my translation pages as well).
And I agree that all this things should be either deleted or made
unavailable to public..
But who is going to do it? I guess thats the question since more than a
year ..
I am also afraid of deleting things I don't know - might be important for
some people I always think..

Unfortunately I have no suggestion howto solve that problem without having
to rewrite everything from scratch.. deleting the old pages immediately
after rewriting..

kind regards
Werner



On Thu, Jan 24, 2013 at 1:26 PM, Pirmin Kalberer pi...@sourcepole.comwrote:

 Hi Alex,

 Am Donnerstag, 24. Januar 2013, 10.40:00 schrieb Alexander Bruy:
 
  please note that most of this methods were marked as deprecated for
  a long time. Some of them are deprecated since QGIS 1.6 or even
  earlier.

 Where exactly is it marked as deprecated? At least not in the API docs [1].
 And the current PyQGIS cookbook shows it as an example [2].
 I'm only asking for a more user friendly way than having to read the C++
 source code first.

 Pirmin

 [1]

 http://qgis.org/api/1.8/classQgsMapLayerRegistry.html#a06a1339cd757608a61e3899a27f39e8a
 [2] http://www.qgis.org/pyqgis-cookbook/loadlayer.html#map-layer-registry

 
  On Thu, 24 Jan 2013 00:57:26 +0100
 
  Pirmin Kalberer pi...@sourcepole.com wrote:
   Hi all,
  
   I found the time for an OpenLayers plugin release with merged pull
   requests
   for Stamen map support and fixes for Python API breaks in master branch
   (See https://twitter.com/PirminKalberer/status/294226472707715072 for
   credits). The second point was quite annoying for many users and
 myself.
   It is a really bad practice to break the API without deprecation
 messages
   when calling these methods. There should be enough time (at least one
   minor version) for developers for updating their plugins. In this case
 it
   would have been easy to keep the old API and add a deprecation message
   similar to
   http://code.activestate.com/recipes/391367-deprecated/
  
   Regards
   Pirmin
 --
 Pirmin Kalberer
 Sourcepole  -  Linux  Open Source Solutions
 http://www.sourcepole.com

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

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Alexander Bruy]

Hi Pirmin,

as I can see in API docs (using your link) there is a note:

Note:
This method is deprecated since QGIS 1.8, you should use
addMapLayers rather.

Regarding PyQGIS CookBook I agree that it should be updated
to reflect all API changes. But I think it is better to update it after
merging new_vector_api branch

2013/1/24 Pirmin Kalberer pi...@sourcepole.com:
 Hi Alex,

 Am Donnerstag, 24. Januar 2013, 10.40:00 schrieb Alexander Bruy:

 please note that most of this methods were marked as deprecated for
 a long time. Some of them are deprecated since QGIS 1.6 or even
 earlier.

 Where exactly is it marked as deprecated? At least not in the API docs [1].
 And the current PyQGIS cookbook shows it as an example [2].
 I'm only asking for a more user friendly way than having to read the C++
 source code first.

 Pirmin

 [1]
 http://qgis.org/api/1.8/classQgsMapLayerRegistry.html#a06a1339cd757608a61e3899a27f39e8a
 [2] http://www.qgis.org/pyqgis-cookbook/loadlayer.html#map-layer-registry

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Marco Bernasocchi]

On 01/24/2013 01:30 PM, Werner Macho wrote:
 There is a lot of outdated, wrong information somewhere in the wiki -
 (including my translation pages as well).
 And I agree that all this things should be either deleted or made
 unavailable to public..
Maybe we could just mark those pages as deprecated as well.

ciao

-- 
Marco Bernasocchi
http://opengis.ch
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Martin Dobias]

On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
alexander.b...@gmail.com wrote:
 Hi Pirmin,

 as I can see in API docs (using your link) there is a note:

 Note:
 This method is deprecated since QGIS 1.8, you should use
 addMapLayers rather.

A bit off-topic, but I find it weird that addMapLayer() method has
been marked as deprecated: even if now we have the possibility to
specify more layers at once, it is always good to have a convenience
call that accepts just one layer (as that's what most users will do).

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Jürgen E . Fischer]

Hi Pirmin,

On Thu, 24. Jan 2013 at 13:26:36 +0100, Pirmin Kalberer wrote:
 Where exactly is it marked as deprecated? At least not in the API docs [1]. 

Well, without an explicit comment that might not be too obvious in doxygen as
it only leaves the Q_DECL_DEPRECATED tag in front of the methods (eg.
addMapLayer in Public Member Functions).

Now there's at least a warning in the message log, if you use something
deprecated.  Not sure that was also visible on stderr with Python 2.7.


 And the current PyQGIS cookbook shows it as an example [2].

That's probably out of sync at many other places too.


Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
committ(ed|ing) to Quantum GIS IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Sandro Santilli]

On Thu, Jan 24, 2013 at 01:40:48PM +0100, Martin Dobias wrote:
 On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
 alexander.b...@gmail.com wrote:
  Hi Pirmin,
 
  as I can see in API docs (using your link) there is a note:
 
  Note:
  This method is deprecated since QGIS 1.8, you should use
  addMapLayers rather.
 
 A bit off-topic, but I find it weird that addMapLayer() method has
 been marked as deprecated: even if now we have the possibility to
 specify more layers at once, it is always good to have a convenience
 call that accepts just one layer (as that's what most users will do).

+1, and it doesn't cost nothing to implement addMapLayer as a oneliner
wrapper around addMapLayers ...

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

[Qgis-developer] OpenLayers plugin release and Python API breaks

[Pirmin Kalberer]

Hi all,

I found the time for an OpenLayers plugin release with merged pull requests 
for Stamen map support and fixes for Python API breaks in master branch (See 
https://twitter.com/PirminKalberer/status/294226472707715072 for credits).
The second point was quite annoying for many users and myself. It is a really 
bad practice to break the API without deprecation messages when calling these 
methods. There should be enough time (at least one minor version) for 
developers for updating their plugins. In this case it would have been easy to 
keep the old API and add a deprecation message similar to 
http://code.activestate.com/recipes/391367-deprecated/ 

Regards
Pirmin

-- 
Pirmin Kalberer
Sourcepole  -  Linux  Open Source Solutions
http://www.sourcepole.com

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

Re: [Qgis-developer] OpenLayers plugin release and Python API

[Nathan Woodrow]

 breaks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

We are preparing for 2.0 so the plan has always been to break API and
remove old unused methods.

The select API will break again soon once Martin merges his new vector
API.

- Nathan
From: Pirmin Kalberer
Sent: 24/01/2013 9:58 AM
To: qgis-dev
Subject: [Qgis-developer] OpenLayers plugin release and Python API
breaks
Hi all,

I found the time for an OpenLayers plugin release with merged pull requests
for Stamen map support and fixes for Python API breaks in master branch (See
https://twitter.com/PirminKalberer/status/294226472707715072 for credits).
The second point was quite annoying for many users and myself. It is a really
bad practice to break the API without deprecation messages when calling these
methods. There should be enough time (at least one minor version) for
developers for updating their plugins. In this case it would have been easy to
keep the old API and add a deprecation message similar to
http://code.activestate.com/recipes/391367-deprecated/

Regards
Pirmin

-- 
Pirmin Kalberer
Sourcepole  -  Linux  Open Source Solutions
http://www.sourcepole.com

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Alexander Bruy]

Hi,

please note that most of this methods were marked as deprecated for
a long time. Some of them are deprecated since QGIS 1.6 or even
earlier.

On Thu, 24 Jan 2013 00:57:26 +0100
Pirmin Kalberer pi...@sourcepole.com wrote:

 Hi all,
 
 I found the time for an OpenLayers plugin release with merged pull requests 
 for Stamen map support and fixes for Python API breaks in master branch (See 
 https://twitter.com/PirminKalberer/status/294226472707715072 for credits).
 The second point was quite annoying for many users and myself. It is a really 
 bad practice to break the API without deprecation messages when calling these 
 methods. There should be enough time (at least one minor version) for 
 developers for updating their plugins. In this case it would have been easy 
 to 
 keep the old API and add a deprecation message similar to 
 http://code.activestate.com/recipes/391367-deprecated/ 
 
 Regards
 Pirmin
 
 -- 
 Pirmin Kalberer
 Sourcepole  -  Linux  Open Source Solutions
 http://www.sourcepole.com
 
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer


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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Werner Macho]

Hi!

I am not sure but I think what Pirmin meant here was that there was no
warning _message_.
We all know that a lot of functions have been declared deprecated since a
very long time. But without knowing or getting a warning message that THIS
function is deprecated, I agree with Pirmin that noone can see the
deprecation until reading the source or .. until it is cleaned out.
Nevertheless it is good to clean the code (otherwise we would collect
deprecated functions forever)..
So just as a reminder here to spit out warning messages for deprecated
functions next time ..
Whenever this will be .. I hope not too soon ;)

kind regards
Werner


On Thu, Jan 24, 2013 at 7:40 AM, Alexander Bruy alexander.b...@gmail.comwrote:

 Hi,

 please note that most of this methods were marked as deprecated for
 a long time. Some of them are deprecated since QGIS 1.6 or even
 earlier.

 On Thu, 24 Jan 2013 00:57:26 +0100
 Pirmin Kalberer pi...@sourcepole.com wrote:

  Hi all,
 
  I found the time for an OpenLayers plugin release with merged pull
 requests
  for Stamen map support and fixes for Python API breaks in master branch
 (See
  https://twitter.com/PirminKalberer/status/294226472707715072 for
 credits).
  The second point was quite annoying for many users and myself. It is a
 really
  bad practice to break the API without deprecation messages when calling
 these
  methods. There should be enough time (at least one minor version) for
  developers for updating their plugins. In this case it would have been
 easy to
  keep the old API and add a deprecation message similar to
  http://code.activestate.com/recipes/391367-deprecated/
 
  Regards
  Pirmin
 
  --
  Pirmin Kalberer
  Sourcepole  -  Linux  Open Source Solutions
  http://www.sourcepole.com
 
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer


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

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

Re: [Qgis-developer] OpenLayers plugin release and Python API breaks

[Matthias Kuhn]

Hi,

Communicating deprecation in a way, the developer will see it sounds 
like a good idea and I agree, that a concept to handle this (starting 
from 2.0) would make sense.


The question is, where and when to communicate it to the developer:
 * The MessageLog (why not)
 * stdout/stderr (sounds good as well, somebody will also see it when 
developing standalone applications)

 * The MessageBar (too obstrusive)
 * Only in debug mode or in release mode as well (A plugin developer 
does not have much reason to run QGIS in debug mode, so release would be 
nice as well)

 * Anything else?

I would propose to add a QGS_DEPRECATED macro which could be placed in 
any deprecated method which will take appropriate actions and 
deprecation methods will appear in a standardized way. (It should take 
an additional string argument, so one can specify the recommended way to 
fix this problem)
Maybe this can then be used to trigger something like the python recipe 
in Pirmins link [1]?


This would help in the case, when we see early, that the change is going 
to happen and when it's possible to leave both possibilities open for a 
while.


But I'm sure, there are still changes which cannot happen that way (i.e. 
The SIP update will convert QString to python unicode strings. Calling 
toString() on these will fail without deprecation. The threading branch 
will add functionality that needs the API to change without the 
possibility to keep deprecated methods). In these cases, a deprecated 
message could be thrown, once the updated is planned, but not when it's 
done.


Regards
Matthias

[1]: http://code.activestate.com/recipes/391367-deprecated/

On 01/24/2013 08:43 AM, Werner Macho wrote:

Hi!

I am not sure but I think what Pirmin meant here was that there was no 
warning _message_.
We all know that a lot of functions have been declared deprecated 
since a very long time. But without knowing or getting a warning 
message that THIS function is deprecated, I agree with Pirmin that 
noone can see the deprecation until reading the source or .. until it 
is cleaned out.
Nevertheless it is good to clean the code (otherwise we would collect 
deprecated functions forever)..
So just as a reminder here to spit out warning messages for deprecated 
functions next time ..

Whenever this will be .. I hope not too soon ;)

kind regards
Werner


On Thu, Jan 24, 2013 at 7:40 AM, Alexander Bruy 
alexander.b...@gmail.com mailto:alexander.b...@gmail.com wrote:


Hi,

please note that most of this methods were marked as deprecated for
a long time. Some of them are deprecated since QGIS 1.6 or even
earlier.

On Thu, 24 Jan 2013 00:57:26 +0100
Pirmin Kalberer pi...@sourcepole.com
mailto:pi...@sourcepole.com wrote:

 Hi all,

 I found the time for an OpenLayers plugin release with merged
pull requests
 for Stamen map support and fixes for Python API breaks in master
branch (See
 https://twitter.com/PirminKalberer/status/294226472707715072 for
credits).
 The second point was quite annoying for many users and myself.
It is a really
 bad practice to break the API without deprecation messages when
calling these
 methods. There should be enough time (at least one minor
version) for
 developers for updating their plugins. In this case it would
have been easy to
 keep the old API and add a deprecation message similar to
 http://code.activestate.com/recipes/391367-deprecated/

 Regards
 Pirmin

 --
 Pirmin Kalberer
 Sourcepole  -  Linux  Open Source Solutions
 http://www.sourcepole.com

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


--
Alexander Bruy
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org mailto:Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer




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


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

Re: [Qgis-developer] OpenLayers plugin

[kimaidou]

Hi Nathan,

If you want to display OpenStreetMap data in Qgis, you can still use
directly Gdal as described here :
http://www.3liz.com/blog/rldhont/index.php?post/2012/07/17/OpenStreetMap-Tiles-in-QGIS

Cheers

Michael

2012/8/7 Nathan Woodrow madman...@gmail.com

 Hi all,

 What are the current plans to migrate the OpenLayer plugin to the
 official plugin repo?

 I have a seen a few people a bit distressed that is no longer
 available in the installer.

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

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

[Qgis-developer] OpenLayers plugin

[Nathan Woodrow]

Hi all,

What are the current plans to migrate the OpenLayer plugin to the
official plugin repo?

I have a seen a few people a bit distressed that is no longer
available in the installer.

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

Re: [Qgis-developer] OpenLayers plugin blocks QGIS

[Paolo Cavallini]

Il 06/02/2012 20:20, Paolo Cavallini ha scritto:

Since several days, loading an OSM layer from the plugin locks the canvas, with 
QGIS
using 100% of the CPU. This happens with master on a couple of Debian machines,
apparently not on windows. Might this have something to do with current changes 
in
reprojection behaviour?

More info:
===
 VERSION 10990
Warning: QHttp: empty path requested is invalid -- using '/'
Warning: divide by zero encountered in divide
Warning: divide by zero encountered in divide
Debug: OpenlayersLayer draw
Debug: page file: 
file:home/paolo/.qgis/python/plugins/openlayers/html/osm.html

Debug: OpenlayersLayer draw
Debug: OpenlayersLayer loadFinished 0
Debug: page file: 
file:home/paolo/.qgis/python/plugins/openlayers/html/osm.html

Debug: undefined[0]: TypeError: 'null' is not an object
Debug: OpenlayersLayer loadFinished 1
Debug: undefined[0]: TypeError: 'null' is not an object
Debug: scaleChanged: 178694226.188784 - olScale: 110936068.181035 - 
Canvas scale: 147914757.574713

Debug: undefined[0]: TypeError: 'null' is not an object
Debug: scaleChanged: 147766842.817139 - olScale: 110936068.181035 - 
Canvas scale: 147914757.574713

Debug: OpenlayersLayer draw
Debug:  extent: -14094359.2442945241928101,-9124518.8873050808906555 : 
26292473.8719484508037567,8273487.6342129483819008

Debug:  center: 6099057.313827, -425515.626546
Debug:  size: 1033, 445
Debug: undefined[0]: TypeError: 'null' is not an object

--
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

[Qgis-developer] OpenLayers plugin error

[Paolo Cavallini]

Hi all.
If I load a layer with incorrect projection I get an error with OL plugin.
Of course the problem is with the user, but the plugin should intercept the 
exception
and present a more meaningful warning.
BTW, is there a redmine instance for this plugin?
All the best.
===
Traceback (most recent call last):
  File /home/paolo/.qgis/python/plugins/openlayers/openlayers_plugin.py, line 
48,
in addLayer
self.plugin.addLayer(self)
  File /home/paolo/.qgis/python/plugins/openlayers/openlayers_plugin.py, line 
180,
in addLayer
self.__setMapSrsGoogle()
  File /home/paolo/.qgis/python/plugins/openlayers/openlayers_plugin.py, line 
237,
in __setMapSrsGoogle
extMap = coodTrans.transform(extMap, 
QgsCoordinateTransform.ForwardTransform)
QgsCsException: trasformazione diretta of
(26402.247872, 81544.425535)
PROJ.4: +proj=longlat +ellps=WGS84 +datum=WGS84 +no_defs +to +proj=merc 
+a=6378137
+b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m 
+nadgrids=@null
+wktext  +no_defs
Error: latitude or longitude exceeded limits

-- 
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] OpenLayers plugin blocks QGIS

[Paolo Cavallini]

Hi all.
Since several days, loading an OSM layer from the plugin locks the canvas, with 
QGIS
using 100% of the CPU. This happens with master on a couple of Debian machines,
apparently not on windows. Might this have something to do with current changes 
in
reprojection behaviour?
Thanks a lot.
-- 
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] OpenLayers plugin error

[Paolo Cavallini]

Il 06/02/2012 20:10, Paolo Cavallini ha scritto:

 BTW, is there a redmine instance for this plugin?

I see (thanks Giovanni): http://hub.qgis.org/projects 
http://hub.qgis.org/projects/openlayers
But why this is not listed (the same is true for many others) in the very handy 
top
right menu Jump to a project?
See also: http://hub.qgis.org/issues/4901
All the best.
-- 
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Openlayers plugin python error

[Luiz Motta]

Giovanni,

The message  error occurr in  MemoryLayerSaver's plugins.

Disable all plugins and work only OpenLayers's plugin.

Open the layer (ex.: shapefile with projection) and try



2011/1/19 Giovanni Manghi giovanni.man...@gmail.com

 Hi,

 under Ubuntu linux (10.04) and qgis trunk I get the following when
 adding layers with the Openlayers plugin. The error is not critical as
 the layer is added in any case.


 An error has occured while executing Python code:

 Traceback (most recent call last):
  File
 /home/gio/.qgis/python/plugins/MemoryLayerSaver/MemoryLayerSaver.py,
 line 41, in connectProvider
if self.isSavedLayer(layer):
  File
 /home/gio/.qgis/python/plugins/MemoryLayerSaver/MemoryLayerSaver.py,
 line 90, in isSavedLayer
if not l.dataProvider():
 AttributeError: 'OpenlayersLayer' object has no attribute 'dataProvider'



 cheers

 -- Giovanni --

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

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

Re: [Qgis-developer] Openlayers plugin python error

[Giovanni Manghi]

Sorry,

you are right, I didn't noticed that the error message was about another
plugin.

Nevertheless the note stays for the MemoryLayerSaver author.


cheers

-- Giovanni --




On Wed, 2011-01-19 at 15:46 -0200, Luiz Motta wrote:
 Giovanni,
 
 
 The message  error occurr in  MemoryLayerSaver's plugins.
 
 
 Disable all plugins and work only OpenLayers's plugin.
 
 
 Open the layer (ex.: shapefile with projection) and try
 
 
 
 
 
 
 2011/1/19 Giovanni Manghi giovanni.man...@gmail.com
 Hi,
 
 under Ubuntu linux (10.04) and qgis trunk I get the following
 when
 adding layers with the Openlayers plugin. The error is not
 critical as
 the layer is added in any case.
 
 
 An error has occured while executing Python code:
 
 Traceback (most recent call last):
  File
 /home/gio/.qgis/python/plugins/MemoryLayerSaver/MemoryLayerSaver.py,
 line 41, in connectProvider
if self.isSavedLayer(layer):
  File
 /home/gio/.qgis/python/plugins/MemoryLayerSaver/MemoryLayerSaver.py,
 line 90, in isSavedLayer
if not l.dataProvider():
 AttributeError: 'OpenlayersLayer' object has no attribute
 'dataProvider'
 
 
 
 cheers
 
 -- Giovanni --
 
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer
 
 


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

[Qgis-developer] OpenLayers plugin and Print Composer

[Aaron Kreider]

I'm trying to print a layer of points (kml) on an Open Street Map.  I'm 
hoping to get the highest resolution possible - so I can print them out 
at 600 dpi. I think I can do this by creating an image that is around 
4800 by 6000 pixels.


QGIS 1.6

I use the OpenLayers plugin to get the OpenStreetMap layer.

I add the kml data.  I zoom in a couple times (to the state of 
Pennsylvania).


It looks fine in QGis.  Now when I try to print it using Print 
Composer, I select add a map and create a box for the map.  The map 
shows up fine.  But when I try to export it to an image (or pdf) it 
shows my kml markers on a *completely different* open street map 
background.  It looks like it zoomed in 3-5 times on openstreet (and 
changed the center point), but the kml layer keeps its original projection.


Is there any way I could get around this bug?

It looks like there is an OpenLayers bug.  Is someone working on it?


Another person had the same problem:
http://forum.qgis.org/viewtopic.php?f=2t=7674p=16449#p16449

There is a ticket, but it looks like nobody is working on it:
http://trac.osgeo.org/qgis/ticket/3195

Aaron

--
Energy Justice Communities Map Developer - http://www.energyjustice.net/map

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

Re: [Qgis-developer] Openlayers plugin and Virtual Earth (i.e.Bing Maps)

[Pirmin Kalberer]

Am Freitag, 3. Dezember 2010, um 04.35:27 schrieb Noli Sicad:
 Hi,
 
 I am trying to add Virtual Earth (Bing Maps) to QGIS Openlayers plugin
 and I have trouble on the projection of Bing Maps (i.e. alignment). My
 shapefile layer (i.e.traces from the Google Maps) and other shapefile
 layers are off when I overlayed the Bing map (Bing Hybrid).
 
 Bing is far better Satellite imagery compare to Yahoo and Google. OSM
 is using Bing for traces lately as result of Steve Coast (OSM founder)
 working with Bing.
 
 http://wiki.openstreetmap.org/wiki/File:Selecting_Bing_in_JOSM.png
 
 I know that Bing uses different projection,
 http://www.cadmaps.com/gisblog/?p=80
 
 
 displayProjection: new OpenLayers.Projection(EPSG:4326),
 
 Inserting this code above does not help at all.
 
 Here the entire code.
[...]

Your code snippet shows the Google layer, not a Bing layer.

Pirmin

-- 
Pirmin Kalberer
Sourcepole  -  Linux  Open Source Solutions
http://www.sourcepole.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer