Plugin AreaPrinter approval by pcav.
The plugin version "[1267] AreaPrinter 0.2 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/AreaPrinter-master/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://list
Plugin AreaPrinter approval by pcav.
The plugin version "[1267] AreaPrinter 0.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/AreaPrinter-master/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://list
Fasiha I used the following steps :
- open the qgs project (xxx.qgs file) in a text editor
- find the layer definition (you can search for the URL you entered)
- add &zmin=17&zmax=22 to the URL
There are probably ways to add the parameters directly in the layer
definition in the brower, which is
Plugin Line direction histogram approval by pcav.
The plugin version "[730] Line direction histogram 2.2" is now approved
Link: http://plugins.qgis.org/plugins/LineDirectionHistogram/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List in
Plugin qgis2web approval by pcav.
The plugin version "[740] qgis2web 2.21.1" is now approved
Link: http://plugins.qgis.org/plugins/qgis2web/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinf
Plugin shptoobs approval by pcav.
The plugin version "[408] shptoobs 0.1.2 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/shp_to_obs/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/m
Plugin shptoobs approval by pcav.
The plugin version "[408] shptoobs 0.1.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/shp_to_obs/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/m
Plugin shptoobs approval by pcav.
The plugin version "[408] shptoobs 0.1.4 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/shp_to_obs/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/m
Plugin shptoobs approval by pcav.
The plugin version "[408] shptoobs 0.1.5 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/shp_to_obs/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/m
Plugin shptoobs approval by pcav.
The plugin version "[408] shptoobs 0.1.6 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/shp_to_obs/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/m
Plugin shptoobs approval by pcav.
The plugin version "[408] shptoobs 0.1.7 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/shp_to_obs/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/m
Hi All,
Currently, QGIS-GDAL seems to be only able to display rasters that are
stored in the database as it displays a black image for PostGIS Out-DB
rasters as described in my post in the link below:
http://osgeo-org.1560.x6.nabble.com/QGIS-GDAL-OUT-DB-RASTER-SUPPORT-td5318735.html
*Please, I wa
Hi devs,
I'm making some test with Processing. I have a quick question: is there
a method to know (via python) the parameter of an algorithm?
To get one algorithm available as an object, I do:
import processing
# get an algorithm of the qgis provider, no matter which one
alg = qgis_list =
QgsAp
Hi Nathan
Only partially related to this thread as a shy reminder:
My intern Simran recently has made a pull request [*] for your nice
Expressions Plus Plugin QGIS plugin.
These are the proposed additional functions:
* max_incremented() - an "autoincrement" id function
* hstore - support of a key
(I havent followed the work on QVariantMaps, I will give it a look).
Nyall, I know that to make it error free and mantainable, we will need some
sort of metadata, which would require some work both to set it up and
mantain it.
This dicussion starts from the benfits of having a schema. If the most
On 30 June 2017 at 19:44, Matthias Kuhn 🌍 wrote:
> On 06/30/2017 11:32 AM, G. Allegri wrote:
>> Normally you start with a schema, and from that create xml. To me it
>> sounds pretty hard to keep a schema updated the other way around? As the
>> api can always add new/changed parts of xm
On 30 June 2017 at 19:39, G. Allegri wrote:
>> Seems like a huge amount of administrative overhead to me. A small
>> change to the project format could result in massive amounts of
>> required changes to the xsd.
>>
>> Given that now it's safe to have multiple QgsProjects at once,
>> couldn't you
On 06/30/2017 11:32 AM, G. Allegri wrote:
> Normally you start with a schema, and from that create xml. To me it
> sounds pretty hard to keep a schema updated the other way around? As the
> api can always add new/changed parts of xml in it?
>
>
> Even QgsProject won't know if a projec
>
> Seems like a huge amount of administrative overhead to me. A small
> change to the project format could result in massive amounts of
> required changes to the xsd.
>
> Given that now it's safe to have multiple QgsProjects at once,
> couldn't you instead just load the project and retrieve the de
>
> Normally you start with a schema, and from that create xml. To me it
> sounds pretty hard to keep a schema updated the other way around? As the
> api can always add new/changed parts of xml in it?
>
Yes, that's hard, but it's quite odd to have a project serialization format
(in this case XML)
On 30 June 2017 at 18:35, G. Allegri wrote:
>
> Hi everybody,
> I know this has been discussed in the past, and maybe I missed more recent
> discussions, but I think this is a point that should be considered.
>
> Working a lot with QGIS projects parsing and processing, we have to rely on
> trial
On 30-06-17 10:45, Matthias Kuhn 🌍 wrote:
> Hi Giovanni,
>
> On 06/30/2017 10:35 AM, G. Allegri wrote:
>> Hi everybody,
>> I know this has been discussed in the past, and maybe I missed more
>> recent discussions, but I think this is a point that should be considered.
>>
>> Working a lot with QGIS
Hi Giovanni,
On 06/30/2017 10:35 AM, G. Allegri wrote:
> Hi everybody,
> I know this has been discussed in the past, and maybe I missed more
> recent discussions, but I think this is a point that should be considered.
>
> Working a lot with QGIS projects parsing and processing, we have to rely
>
Hi everybody,
I know this has been discussed in the past, and maybe I missed more recent
discussions, but I think this is a point that should be considered.
Working a lot with QGIS projects parsing and processing, we have to rely on
trials and errors to validate a QGIS project and create test proj
If you read above, the idea is to set fields *other then the ones selected
for grouping* null. So it wouldn't pick the first one, which is meaningless.
Having aggregate functions to be applied to single non-grouping fields
could be a great plus, keeping the option to leave the field set to null.
25 matches
Mail list logo
