uploading plugins tonight involved having metadata.txt and __init__.py
to be located under /help folder ... bug or new validation rule ?
--
Dott. Agr. Giuseppe De Marco
RSPP settore ATECO 1
Cell./Mobile: +39 3935041115
Fax.: +39 0503869174
PEC: giuseppe.de_ma...@epap.conafpec.it
Hi,
Are there any technical reasons why the new QgsMapRenderer*Job classes [0]
should not be exposed to Python interface?
Then renders could readily be output to QImage like in
QgsRenderChecker::runTest() [1], instead of direct access to QgsMapRenderer.
[0] https://github.com/qgis/QGIS/blob/mast
Hi Tim,
On Thu, Mar 27, 2014 at 5:57 AM, Tim Sutton wrote:
> Hi Larry
>
> I finally have the time to sit down and try to get your recipe for
> building / debugging QGIS under QtCreator a try, but I cant seem to find
> your notes on this. I have two screenies showing some of the settings but
> no
Hi all.
Sorry for flooding the list; the interpolation.rst first command does
not seem to be working (all points filtered away, results in an empty file).
Anyone confirms?
Thanks.
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
On 03/27/2014 08:05 AM, Saber Razmjooei wrote:
> Hi all,
>
> Here is my wish list:
>
> - To be able to access GRASS data within QGIS. Similar to PostGIS and other
> GDAL/OGR data sources, it should be up to users to create GRASS
> geodatabase/location/mapsets. QGIS will be able to simply add laye
Hi all.
Following the training Processing manual, modeler_hydro_calculator.rst,
I have a problem in adding reslts from Calculator: I add the suggested
formula, but when closing the popup all the connecting lines are
disappeared, and the calculation is gone.
Anyone confirms?
All the best.
--
Paolo
We've finally deployed the new plugins website and migrated to the new
server,
beside the new look & feel that integrates with that of the main QGIS
website, the main changes have been a few bug fixes and the addition of the
new "about" metadata field.
thanks to Werner, Richard and all other peop
yep! that would be extremly useful..
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Is-it-possible-to-read-a-OGR-datasource-with-EXecuteSQL-statement-tp5131553p5131601.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
_
Hi all,
Here is my wish list:
- To be able to access GRASS data within QGIS. Similar to PostGIS and other
GDAL/OGR data sources, it should be up to users to create GRASS
geodatabase/location/mapsets. QGIS will be able to simply add layers for
viewing and editing
- Having access to GRASS
Thanks for bringing this up Michael!
Am 27.03.2014, 14:05 Uhr, schrieb kimaidou :
I have one thing in mind which IMHO would be great to have in QGIS
regarding the layer properties dialog :
* Make it non modal, so that the user can still pan/zoom the map, or even
select other tools
+1 What I r
Le 27/03/2014 14:19, Régis Haubourg a écrit :
> Hi,
> I'm trying to developp a processing script that would save a lot of
> complexity if I could open in qgis a ogr datasource using ExecuteSQL
> statement.
> I'm reading my datasources with OGR python API with no problem, and a simple
> SQL allows
On Thu, Mar 27, 2014 at 9:38 AM, Blumentrath, Stefan <
stefan.blumentr...@nina.no> wrote:
> I also understand that at some point in time one will have to use GRASS
> directly in order to access full functionality (e.g. ortho-rectification,
> nviz, mapswipe, animation and stuff), which makes the wa
That sounds very reasonable to me.
Proper GDAL/OGR handling for GRASS 7 would be very nice in any case (see
http://trac.osgeo.org/gdal/ticket/2953).
As for a "GRASS data browser", I think, a plugin would be required with regards
to user friendliness, because one needs to know what files to acce
Hi all.
In the meeting about the location of the next Code Sprint, a general
consensus was reached:
* same period (Feb-March)
* probably same duration (Mon to Fri)
* probably Philadelphia.
We should decide whether to join "officially" or not (of course,
individual QGIS devs will always be welcome.
Hi,
I'm trying to developp a processing script that would save a lot of
complexity if I could open in qgis a ogr datasource using ExecuteSQL
statement.
I'm reading my datasources with OGR python API with no problem, and a simple
SQL allows me to keep only one fields, and calculate on the fly area
Hi list,
I am not in Vienna, but still very interesting by the ongoing discussions.
I have one thing in mind which IMHO would be great to have in QGIS
regarding the layer properties dialog :
* Make it non modal, so that the user can still pan/zoom the map, or even
select other tools
* When the u
;ve got an agreement
on the mockup we can keep reference to it.
Best,
Olivier
Images intégrées 1
__ Information from ESET Security, version of virus signature database
9601 (20140327) __
The message was checked by ESET Security.
part000.txt - is OK
http://www.eset.com
_
Here is my opinion about this:
I think it might not be a good idea to get rid of the GRASS plugin and
leave only Processing, since there are some tools that do not fit into
Processing, So, at least for this tools, there should be a GRASS
plugin to make the available fro QGIS.
Having said that, I
Hi Larry
I finally have the time to sit down and try to get your recipe for building
/ debugging QGIS under QtCreator a try, but I cant seem to find your notes
on this. I have two screenies showing some of the settings but not quite
enough info to get it working. Currently I am getting this (see [
Dear all,
>From my user perspective (I am using both GRASS and QGIS, or the other way
>around, depends on topic), processing is not really a replacement for the
>GRASS plugin.
It is handy and probably better for those who do not use GRASS but are
interested in single functions / modules.
Yet,
Hi,
processing is also limited only to some tools that have input and ouptut.
I think Grass plugin remains necessary (it is to me). Another point,
processing is not yet in a production state, under high developpement, when
plugin is. We should take some time before thinking of dropping a stable a
On 27 March 2014 11:18, Paolo Cavallini wrote:
> Hi all.
Hi all,
> I learned during dinner that GRASS7 RC1 is due very soon. This opens the
> issue of its functioning in QGIS. IMHO:
>
> * the qgis-grass-plugin might stop working (this has to be tested)
I test to compile QGIS master with GRASS7
Hi !
*Bernhard Ströbl :*
>
> but if different symbologies why not having different labels or different
> diagrams. This would become too complicated, I am afraid.
Good point...
I'm not sure if would be a good idea to have the symbology as a tag
anyways, since every layer will necessarily have on
Il 27/03/2014 12:33, Nathan Woodrow ha scritto:
> I would vote for dropping the plugin and just updating the processing
> plugin. Having both ways is bad for us and bad for users, even worse
> when some functions are missing from one but not in the other.
I understand well the point; however, the
I would vote for dropping the plugin and just updating the processing
plugin. Having both ways is bad for us and bad for users, even worse when
some functions are missing from one but not in the other.
- Nathan
On Thu, Mar 27, 2014 at 8:18 PM, Paolo Cavallini wrote:
> Hi all.
> I learned durin
Il 27/03/2014 12:18, Markus Neteler ha scritto:
>> * upgrading Processing GRASS modules
>
> I'll do that. I already started with Pirmin and Victor to discuss it.
good news
>> * changing the current Processing behaviour, avoiding the import-export
>> phase when piping consecutive GRASS commands;
Hi Paolo,
(note: I'm not ready qgis-dev, not sure if this email reaches it)
On Thu, Mar 27, 2014 at 11:18 AM, Paolo Cavallini wrote:
> Hi all.
> I learned during dinner that GRASS7 RC1 is due very soon. This opens the
> issue of its functioning in QGIS. IMHO:
>
> * the qgis-grass-plugin might st
k, and a not-so-nice duplication.
I would like to have an open discussion on this, avoiding things to just
happen, with the possible negative consequences.
All the best.
__ Information from ESET Security, version of virus signature database
9601 (20140327) __
The message was chec
Hi All
Just a note to say that the QGIS Podcast episode 5 is now online. To listen
to the podcast using the web player, and to view the show notes, please
visit [1]. You can also find a link on that page to subscribe to the QGIS
Podcast using your podcast client.
If you would like to contribute t
Il 27/03/2014 08:28, Richard Duivenvoorde ha scritto:
> Besides admin/doc things, one of my plans for this HF was to make it
> possible that the context-help content should come from the
> documentation (that is deeplinking to either the website (first step)
> and then to a local copy of the websit
On 27-03-14 09:48, Alex Mandel wrote:
> FYI, you just need to give Martin Spott the IPs that we need to
> whitelist for OSGeo LDAP. Also it would be nice to get access to help
> out. We can easily provide our ssh public keys.
Hi Alex,
whitelisting ip's is done. Thanks.
please sent me or macho yo
Hi all.
I learned during dinner that GRASS7 RC1 is due very soon. This opens the
issue of its functioning in QGIS. IMHO:
* the qgis-grass-plugin might stop working (this has to be tested)
* some of the module options will be different
* new modules will not be available in QGIS.
I think we can de
FYI, you just need to give Martin Spott the IPs that we need to
whitelist for OSGeo LDAP. Also it would be nice to get access to help
out. We can easily provide our ssh public keys.
Thanks,
Alex
On 03/27/2014 01:38 AM, Werner Macho wrote:
> I also agree with Alex when it comes to ssh ..
> That's
http://plas.io should fulfill or nearly fulfill all of these requirements at
this time.
The only requirement is a WebGL-capable web browser.
Howard
On Mar 27, 2014, at 8:18 AM, Paolo Cavallini wrote:
> FYI. Worth of consideration IMHO.
>
> Da: antonio valanzano
> Inviato il: 25 marzo 2014 2
I also agree with Alex when it comes to ssh ..
That's still a big issue ..
load balancing would be nice too ..
regards
Werner
On Thu, Mar 27, 2014 at 9:33 AM, Alex Mandel wrote:
> Eggs in one basket?
>
> Why not load balance 2 servers in different parts of the world?
> Bandwidth at OSUOSL is un
Shall I create a new container on qgis2?
Richard: are you already at the venue? should we just sit together?
regards
Werner
On Thu, Mar 27, 2014 at 9:11 AM, Richard Duivenvoorde
wrote:
> On 27-03-14 09:00, Paolo Cavallini wrote:
>> Il 27/03/2014 08:44, Richard Duivenvoorde ha scritto:
>>
>>> Be
Hi,
Project -> Export DXF is only for exporting DXF, while dxf to shp is
about importing.
The import of QGIS through OGR is still unsatisfactory. I would still
keep this plugin around.
It seems to still work in master.
The bug mentioned is probably because the user used a format version
that is
Eggs in one basket?
Why not load balance 2 servers in different parts of the world?
Bandwidth at OSUOSL is unlimited, hardware is already paid for (It's
raid SAS drives, not cheap hardware).
Sharing people time also helps. I was the only one awake when this issue
came up because I'm in the wester
BTW, what about removing the obsolete plugin before 2.4?
All the best.
Messaggio originale
Oggetto:[QGIS Application - Bug #6948] (Closed) Dxf to Shape plugin
doesn't work any more
Data: Wed, 26 Mar 2014 17:52:29 -0700
Mittente: redm...@qgis.org
A: undisclos
On 27-03-14 09:00, Paolo Cavallini wrote:
> Il 27/03/2014 08:44, Richard Duivenvoorde ha scritto:
>
>> Because it takes time and nobody (including me) takes, took or has time
>> to do this untill now :-)
>
> could you let us know what would be the steps involved?
> thanks.
Well, it is easy :-)
Il 27/03/2014 08:44, Richard Duivenvoorde ha scritto:
> Because it takes time and nobody (including me) takes, took or has time
> to do this untill now :-)
could you let us know what would be the steps involved?
thanks.
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.fau
On 27-03-14 08:11, Paolo Cavallini wrote:
> Why not moving also the website to the new server?
Because it takes time and nobody (including me) takes, took or has time
to do this untill now :-)
Regards,
Richard Duivenvoorde
___
Qgis-developer mailing
FYI. Worth of consideration IMHO.
Messaggio originale
Da: antonio valanzano
Inviato il: 25 marzo 2014 21:08:24 CET
A: qgis-u...@lists.osgeo.org
Oggetto: [Qgis-user] lidar visualization in qgis
I would like to start a discussion about the minimal functionalities that a
new lida
Why not moving also the website to the new server?
All the best.
On 27 marzo 2014 08:03:35 CET, Richard Duivenvoorde wrote:
>On 27-03-14 03:45, Alex Mandel wrote:
>> So Nathan noticed the website wasn't coming up. Specifically
>> "The requested URL /en/site/ was not found on this server."
>>
>>
Big +1 from me.
Thanks.
On 27 marzo 2014 08:28:13 CET, Richard Duivenvoorde wrote:
>Besides admin/doc things, one of my plans for this HF was to make it
>possible that the context-help content should come from the
>documentation (that is deeplinking to either the website (first step)
>and then to
Besides admin/doc things, one of my plans for this HF was to make it
possible that the context-help content should come from the
documentation (that is deeplinking to either the website (first step)
and then to a local copy of the website (second)).
To me this seems nice because:
1) we have one pl
On 27-03-14 03:45, Alex Mandel wrote:
> So Nathan noticed the website wasn't coming up. Specifically
> "The requested URL /en/site/ was not found on this server."
>
> I believe the issue is disk space. I'm guessing the sphinx is built
> elsewhere and transferred in on a schedule without checking h
47 matches
Mail list logo
