[Qgis-developer] Lecos test
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. Just tested the new Lecos on the sample Alaska dataset, I get an error for Extract Patch edges: Traceback (most recent call last): File /usr/share/qgis/python/plugins/processing/core/GeoAlgorithm.py, line 150, in execute self.processAlgorithm(progress) File /home/paolo/.qgis2/python/plugins/LecoS/lecos_sextantealgorithms.py, line 1205, in processAlgorithm func.exportRaster(results,inputFilename,output) File /home/paolo/.qgis2/python/plugins/LecoS/lecos_functions.py, line 336, in exportRaster band.SetNoDataValue(nodata) File /usr/lib/python2.7/dist-packages/osgeo/gdal.py, line 887, in SetNoDataValue return _gdal.Band_SetNoDataValue(self, *args) TypeError: in method 'Band_SetNoDataValue', argument 2 of type 'double' Where should I report it? All the best, and 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.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJiIggACgkQ/NedwLUzIr4uPgCdEXKBYlolQl+RQxzH49r8IaqD CywAmwTcBpY2mA8ZuKjiyJohOlmhgZzv =PL/k -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Oracle Georaster support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. What is the state of Oracle Georaster support? Is it supposed to work? Is someone actually using it? On the standalone installer there is a button to load them, but it does not seem to be working. On OSGeo4w there is no button, but the format seems to be supported. 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.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJiJOsACgkQ/NedwLUzIr6UCQCePll9kTNQ1pHDUtW5ca4cYBJx 7VIAoI7Fjqe/AFjqP45Sk8mheeByUluk =W9To -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Gdal Tools: extract projection
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 17/10/2013 11:09, Alexander Bruy ha scritto: 2013/10/17 Paolo Cavallini cavall...@faunalia.it: * no feedback is given upon completion (World file written) Agreed, feedback about process completion will be good. http://hub.qgis.org/issues/8916 * name is misleading (it is extracting a world file, not a projection) Hmm, it also extract projection into .prj file (optionally). Maybe both files (wld and prj) should be created by default? * the prj is (optionally) created according to the project settings, so it is empty for layers not loaded; the user should be warned, and the prj not created in this case. Hmm, works for me. Maybe your layers don't contain projection information? unclear to me how to check this: the raster appears on the right place, however. BTW, I think it is better to improve this tool inside Processing as in future IMO it should replace GDALTools. agreed - however, I think having the (editable) plain gdal command line at the bottom is a major advantage of gdal tools for power users. 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.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJiLDMACgkQ/NedwLUzIr5twwCgoIMpvm1O6a+DjwIuqOWRy85p SicAn0GzE0kd6fH8OMU/t08ehaHHRtto =leOp -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Teaching Processing: notes from the wild
On Sat, Oct 19, 2013 at 07:55:36AM +0200, Paolo Cavallini wrote: ok - should I open tickets then, not to forget for future implementation? I think it would be useful to open a ticket for each and specify 2.0.2 as the target version of those which are clearly bugs and known to be fixable in a safe way. Release manager should have the last word about that. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Teaching Processing: notes from the wild
* the Field calculator is barely usable without a dropdown list of fields and functions; on win it does not seem to work (most or all calculations end up with all NULLs); unclear if this is due to minor edit issues from users (quite likely without the dropdowns) Maybe I'm wrong, but currently there is no way to create such widgets and use them in Processing algorithms. this is also what I understand You are both wrong :-) When the algorithm is started, a method called getCustomParametersDialog() is called. If it doesn't exist, the default dialog is used. If you want an algorithm to have a different dialog, you can create it and just return it in here. Right now, no algorithm implements that method, but the architecture of Processing supports that Regarding releasing a new version, I actually do not know how to do it, considering that there is not Processign plugin page, so I cannot publish the zip file using the web interface. However, if you Paolo, or Alex, want to publish it, I definitely like the idea. We are not adding any new functionality lately, but mostly fixing bugs, so I would propose to release regularly, like once a week, to have all new fixed available. I propose to tag versions using the current QGIS version and an extra number, so now we will do 2.0.1.2, then 2.0.1.3and once QGIS 2.0.2 is out, we move to 2.0.2.1. Sounds ok to you? ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Gdal Tools: extract projection
2013/10/19 Paolo Cavallini cavall...@faunalia.it: 2013/10/17 Paolo Cavallini cavall...@faunalia.it: * no feedback is given upon completion (World file written) Agreed, feedback about process completion will be good. http://hub.qgis.org/issues/8916 Fixed * the prj is (optionally) created according to the project settings, so it is empty for layers not loaded; the user should be warned, and the prj not created in this case. Hmm, works for me. Maybe your layers don't contain projection information? unclear to me how to check this: the raster appears on the right place, however. Try with gdalinfo tool, if raster has projection, this tool will show it. Also raster can be displayed in correct place even it doesn't have assigned projection, but has correct wld file. Maybe this is your case. BTW, I think it is better to improve this tool inside Processing as in future IMO it should replace GDALTools. agreed - however, I think having the (editable) plain gdal command line at the bottom is a major advantage of gdal tools for power users. This is true only for tools, that are command line utilities. Extract projection is exception, it uses GDAL API and has no independent command line equivalent. Also it is possible to add text field for additional command line arguments in Processing. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Teaching Processing: notes from the wild
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 19/10/2013 12:21, Victor Olaya ha scritto: You are both wrong :-) much better then I propose to tag versions using the current QGIS version and an extra number, so now we will do 2.0.1.2, then 2.0.1.3and once QGIS 2.0.2 is out, we move to 2.0.2.1. Sounds ok to you? +1 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.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJiZMIACgkQ/NedwLUzIr776wCeKu44zil1srB61h7X8r5ck+3J EYkAn1wA6GgGtWTfmioUqyDXLYQWpCxz =/5l8 -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Gdal Tools: extract projection
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 19/10/2013 12:49, Alexander Bruy ha scritto: http://hub.qgis.org/issues/8916 Fixed thanks a lot Try with gdalinfo tool, if raster has projection, this tool will show You are right: Coordinate System is: LOCAL_CS[unnamed, UNIT[unknown,1]] Origin = (1606490.380039062583819,4894971.249973144382238) Pixel Size = (0.500,-0.500) in this case, a .prj should not be written by the command (even better: the user could be warned about this). This is true only for tools, that are command line utilities. Extract projection is exception, it uses GDAL API and has no independent command line equivalent. sure Also it is possible to add text field for additional command line arguments in Processing. that would be good. however, having the plain gdal command ready at hand (not the processing wrapper) is very useful to prototype scripts. All the best, and 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.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJiZbYACgkQ/NedwLUzIr4FUwCeP3DDjFIfmSbwgaGWOLcP7ezh gAAAn0u/9pM/eRizIKuk4c0yV54YSahM =b5NV -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Teaching Processing: notes from the wild
2013/10/19 Victor Olaya vola...@gmail.com: Regarding releasing a new version, I actually do not know how to do it, considering that there is not Processign plugin page, so I cannot publish the zip file using the web interface. However, if you Paolo, or Alex, want to publish it, I definitely like the idea. We are not adding any new functionality lately, but mostly fixing bugs, so I would propose to release regularly, like once a week, to have all new fixed available. Why not reusing existing SEXTANTE page at plugin website? Maybe it is possible to rename it and use for publishing Processing packages? If this does not violate plugin site and project policy, maybe Nathan or Alessandro can do this (I mean renaming) for us. Or alternatively, we can mark SEXTANTE as deprecated, create new page for Processing and upload packages to this page. And finally, we can publish Processing packages near to the QGIS nightly builds, so users can download it and install manually. This option is less automated for users. I propose to tag versions using the current QGIS version and an extra number, so now we will do 2.0.1.2, then 2.0.1.3and once QGIS 2.0.2 is out, we move to 2.0.2.1. Sounds ok to you? I'm not sure will Plugin manager correctly recognize such four-numbers versions and overwrite them (will try to do some testing). Maybe I'm wrong (Borys know more about this), but we should keep main Processing (in QGIS core) with higher version than version available from plugin repo. This needed for correct overriding when user installed new QGIS build. -- Alexander Bruy ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Teaching Processing: notes from the wild
Why not reusing existing SEXTANTE page at plugin website? Maybe it is possible to rename it and use for publishing Processing packages? If this does not violate plugin site and project policy, maybe Nathan or Alessandro can do this (I mean renaming) for us. I would remove the SEXTANTE plugin website. It makes no sense to have it there, since SEXTANTE does not exist anymore We can use a different version naming scheme, as long as it makes it easy to coordinate independent releases with releases made along QGIS ones. Cheers ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] What's the difference between provider.geometryType() and layer.geometryType()
Hi Victor, I've been porting one of my scripts to the new Processing. Everything seems fine but I'm confused about one issue: It seems like almost everything can be accessed via the layer now, e.g. crs(), pendingFields(), etc. However, if I try to use layer.geometryType() in the VectorWriter constructor, I get an error. It only works if I do: writer = VectorWriter(output, None, fields, provider.geometryType(), layer.crs() ) What's the reason for this unintuitive behavior? Thanks and best wishes, Anita ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What's the difference between provider.geometryType() and layer.geometryType()
Hi Anita looking into the code... the unintuitive part is that these geometryType() methods return values from different enumerations: - provider's geometryType() returns value from WKBType enumeration - layer's geometryType() returns value from GeometryType enumeration (translated from provider's geometryType()) GeometryType has just coarse differentiation (Point, Line, Polygon, UnknownGeometry, NoGeometry), while WKBType is more fine grained (WKBPoint, WKBPoint2D, WKBMultiPoint, ...) I totally agree that it is confusing... they should be at least called differently (e.g. geometryWkbType vs geometryType). Regards Martin On Sat, Oct 19, 2013 at 9:46 PM, Anita Graser anitagra...@gmx.at wrote: Hi Victor, I've been porting one of my scripts to the new Processing. Everything seems fine but I'm confused about one issue: It seems like almost everything can be accessed via the layer now, e.g. crs(), pendingFields(), etc. However, if I try to use layer.geometryType() in the VectorWriter constructor, I get an error. It only works if I do: writer = VectorWriter(output, None, fields, provider.geometryType(), layer.crs() ) What's the reason for this unintuitive behavior? Thanks and best wishes, Anita ___ 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] What's the difference between provider.geometryType() and layer.geometryType()
I wasn't aware of that difference that Martin mentions. I guess that, from the Processing side, the only thing to do is to document clearly which find of enumeration value is expected, and also how to convert it in case you have a value corresponding to the other enumeration. I will try to add that to the Processing documentation thanks for finding this issue 2013/10/19 Martin Dobias wonder...@gmail.com: Hi Anita looking into the code... the unintuitive part is that these geometryType() methods return values from different enumerations: - provider's geometryType() returns value from WKBType enumeration - layer's geometryType() returns value from GeometryType enumeration (translated from provider's geometryType()) GeometryType has just coarse differentiation (Point, Line, Polygon, UnknownGeometry, NoGeometry), while WKBType is more fine grained (WKBPoint, WKBPoint2D, WKBMultiPoint, ...) I totally agree that it is confusing... they should be at least called differently (e.g. geometryWkbType vs geometryType). Regards Martin On Sat, Oct 19, 2013 at 9:46 PM, Anita Graser anitagra...@gmx.at wrote: Hi Victor, I've been porting one of my scripts to the new Processing. Everything seems fine but I'm confused about one issue: It seems like almost everything can be accessed via the layer now, e.g. crs(), pendingFields(), etc. However, if I try to use layer.geometryType() in the VectorWriter constructor, I get an error. It only works if I do: writer = VectorWriter(output, None, fields, provider.geometryType(), layer.crs() ) What's the reason for this unintuitive behavior? Thanks and best wishes, Anita ___ 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] What's the difference between provider.geometryType() and layer.geometryType()
Hi, Currently we have: QgsVectorLayer: * geometryType() returns QGIS geometry type (coarse) * wkbType() returns WKB type (fine) QgsVectorDataProvider: * geometryType() returns WKB type (fine) Unfortunate indeed. To not break existing code, a new method geomType() could be introduced, which returns the QGIS geometry type and the method wkbType() could be implemented for the dataprovider as well. The current methods could be deprecated, but left for a transition period (IMO, there is no need to force people to change working code too fast) Apart from this, a couple of other methods could also be called the same in data provider, vector layer and fields. QgsVectorLayer * int fieldNameIndex( fieldName ) * QgsFields pendingFields() QgsDataProvider * int fieldNameIndex( fieldName ) * QgsFields fields() * QMapQString, int fieldNameMap() QgsFields * int indexFromName( name ) * QgsField field( name ) I would even argue, that QgsVectorLayer should have a common interface (base class) with QgsVectorDataProvider. A lot of code could perfectly be run against any of the two, and with such an interface, this could be done. Just like we don't care if we are working with an iterator from a vector layer or a data provider. Regards, Matthias On Sam 19 Okt 2013 17:33:09 CEST, Martin Dobias wrote: Hi Anita looking into the code... the unintuitive part is that these geometryType() methods return values from different enumerations: - provider's geometryType() returns value from WKBType enumeration - layer's geometryType() returns value from GeometryType enumeration (translated from provider's geometryType()) GeometryType has just coarse differentiation (Point, Line, Polygon, UnknownGeometry, NoGeometry), while WKBType is more fine grained (WKBPoint, WKBPoint2D, WKBMultiPoint, ...) I totally agree that it is confusing... they should be at least called differently (e.g. geometryWkbType vs geometryType). Regards Martin On Sat, Oct 19, 2013 at 9:46 PM, Anita Graser anitagra...@gmx.at wrote: Hi Victor, I've been porting one of my scripts to the new Processing. Everything seems fine but I'm confused about one issue: It seems like almost everything can be accessed via the layer now, e.g. crs(), pendingFields(), etc. However, if I try to use layer.geometryType() in the VectorWriter constructor, I get an error. It only works if I do: writer = VectorWriter(output, None, fields, provider.geometryType(), layer.crs() ) What's the reason for this unintuitive behavior? Thanks and best wishes, Anita ___ 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] What's the difference between provider.geometryType() and layer.geometryType()
Thanks for the explanation Martin! I hope here is a way to have consistency again without necessarily breaking working code. @Victor: A few comments in the example scripts explaining the issue would already help a lot I think. Best wishes, Anita Am 19.10.2013, 19:54 Uhr, schrieb Victor Olaya vola...@gmail.com: I wasn't aware of that difference that Martin mentions. I guess that, from the Processing side, the only thing to do is to document clearly which find of enumeration value is expected, and also how to convert it in case you have a value corresponding to the other enumeration. I will try to add that to the Processing documentation thanks for finding this issue 2013/10/19 Martin Dobias wonder...@gmail.com: Hi Anita looking into the code... the unintuitive part is that these geometryType() methods return values from different enumerations: - provider's geometryType() returns value from WKBType enumeration - layer's geometryType() returns value from GeometryType enumeration (translated from provider's geometryType()) GeometryType has just coarse differentiation (Point, Line, Polygon, UnknownGeometry, NoGeometry), while WKBType is more fine grained (WKBPoint, WKBPoint2D, WKBMultiPoint, ...) I totally agree that it is confusing... they should be at least called differently (e.g. geometryWkbType vs geometryType). Regards Martin On Sat, Oct 19, 2013 at 9:46 PM, Anita Graser anitagra...@gmx.at wrote: Hi Victor, I've been porting one of my scripts to the new Processing. Everything seems fine but I'm confused about one issue: It seems like almost everything can be accessed via the layer now, e.g. crs(), pendingFields(), etc. However, if I try to use layer.geometryType() in the VectorWriter constructor, I get an error. It only works if I do: writer = VectorWriter(output, None, fields, provider.geometryType(), layer.crs() ) What's the reason for this unintuitive behavior? Thanks and best wishes, Anita ___ 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] QGIS inconsistency
Hi Steven, just having a quick look at the data you provided: - your Munros.shp doesn't have 27700 projection, but some user defined and only becomes visible when setting to 27700 manually. - the geojson and the shape file have quite some offset. (75 whatsoevers, meteres, miles ??) Apart from the fact that there might be a bug, your data seems to me more buggy ;) Besides that, i never dare to do any spatial analysis within epsg 4326. Greetz Bernd Am 18.10.2013, 21:13 Uhr, schrieb Steven Horner ste...@stevenhorner.com: Hello, I have been doing a project to calculate mountain viewsheds, basically where a mountain summits can be seen from. I have calculated the viewsheds and polygonized to Vector. So far so good, but then I wanted to show which mountains could be seen from the summit of other mountains I appear to have 2 problems. 1. I ran a spacial query to show how many mountains (Munros) are Within my polgonized viewshed. This returns the Munros. Unfortunately I get a different number in QGIS 1.8 to QGIS 2.0.1, I don't know which is true 2. I had saved my Viewshed originally as a shapefile with a CRS of 27700 (British National Grid), I saved a version as GeoJSON with CRS of 4326. If I run the same spacial query on this file I get a different number of Munros again. So I now have 4 different figures from what I would have expected to be identical. Is data lost when a shapefile is saved as a GeoJSON file in a different CRS? and which should I beleive 1.8 or 2.0.1 or neither? If anyone wants to test this you can download the files here: Viewshed Shapefilehttps://dl.dropboxusercontent.com/u/2657852/AmBodach_shp.zip- CRS of 27700 Viewshed GeoJSONhttps://dl.dropboxusercontent.com/u/2657852/AmBodach_geojson.zip- Converted fromthe above but with CRS of 4326 Munros Shapefile https://dl.dropboxusercontent.com/u/2657852/Munros.zip - CRS of 27700 Wish I had realised there was something wrong before I had calculated 200 of these. Thanks, Steven -- Bernd Vogelgesang * Siedlerstrasse 2 * 91083 Baiersdorf * +49-9133-825374 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [324] PDOK BAG Geocoder approval notification.
Plugin PDOK BAG Geocoder approval by lytrix. The plugin version [324] PDOK BAG Geocoder 0.3 Experimental is now unapproved Link: http://plugins.qgis.org/plugins/pdokbaggeocoder/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [324] PDOK BAG Geocoder approval notification.
Plugin PDOK BAG Geocoder approval by lytrix. The plugin version [324] PDOK BAG Geocoder 0.2 Experimental is now unapproved Link: http://plugins.qgis.org/plugins/pdokbaggeocoder/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
