Hi Etienne.
Thanks for your reply.
I checked the Manage and install plugins but I found no updates. However, I
just used a running copy of QGIS and when starting a new instance, the
ValueTool update became available.
I guess I expected the plugin manager to check for updates when entering the
should retrieve legend if WMS server has getLegendGraphic capability and
layer has getCapability url specified... so you HAVE to select a
styling. Otherwise, silently do nothing as before when getLegendGraphic
integration wasn't available.
just tested on your server and it works
ciao Luigi
I forgot to say that if a legendGraphic is available is shown under the
layer in LegendLayer... it's really little and you have to click on it to
open in real dimension (this is due to QgsLegendInterface architectural
limitation)
Legend will be integrated in composer at it's original (dowloaded)
Hi Ramon and others,
I'm assuming Textual Note is an Attribute Value.
No. I intended the Text Note function of QGis, that is the rectangular
baloon with text inside :
http://qgis.org/it/docs/user_manual/introduction/general_tools.html#annotation-tools
I need to fill the text
Hello All,
I have problems with the OSM_Editor_RemoteControl plugin of QGis.
It answers : Could not connect to the OSM editor. Did you start it ?
But... I started Josm, as you can see here :
https://drive.google.com/file/d/0Bwg_m86uaXY1ZTN5U2FwcURVV1k/edit?usp=sharing
Where I wrong ?
Hi Everybody,
I can't use QString class inside QGis Python Console or inside QGis Python
plugins.
If I use inside a stand alone pyw application, I have no problem (please
note that I run pyw from Eclipse).
Here you are what I do and get inside QGis Python Console:
Python 2.7.5 (default, May 15
Hi Francesco,
I might be not using the right terms, but since the new SIP API (version
2), you're not supposed to use Qt types but the standard python types.
So you're suppose to use str() instead of QString.
You my find more details here
On Fri, Apr 4, 2014 at 9:53 AM, Denis Rouzaud denis.rouz...@gmail.com wrote:
Hi Francesco,
I might be not using the right terms, but since the new SIP API (version 2),
you're not supposed to use Qt types but the standard python types.
So you're suppose to use str() instead of QString.
To be
Hi,
after checking with other colleagues, waiting that your refactoring is
finished is ok for us.
We will focuse on user specifications during your refactoring so that we can
launch a contract soon after.
Cheers
Régis
--
View this message in context:
Hi all
Are there any progress about submitting rankings to GSoC? AFAIK only
schematization plugin have mentors and for other propositions there is no
reply from students.
Can we submit ranking for this proposition or there are any obstacles
against it?
Regards
Piotr
-
Piotr Pociask
GIS
Hi all,
sorry, it's my fault. Yesterday I submitted rankings to OSGeo GSoC
admins. Now we need to wait for final decision.
2014-04-04 13:57 GMT+03:00 Piotr Pociask p0c...@o2.pl:
Hi all
Are there any progress about submitting rankings to GSoC? AFAIK only
schematization plugin have mentors and
Thanks for this
Piotr
-
Piotr Pociask
GIS Support sp. z o. o.
http://www.gis-support.pl/
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Ranking-GSoC-proposals-tp5132433p5133095.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
Hi all,
I wonder if value layer Name is correct in QGIS Mapserver GetCapabilities
response. Currently both Name and Title are the same - it is a layer name
as visible in QGIS.
Shouldn't it be more correct if the Name value will contain layer internal
ID (for example roads2013135915389) and
tl; dr: we are proposing MetaSearch for inclusion into QGIS core, to
help the discovery (download/add, find/bind) workflow in QGIS. There
are Python dependencies and build workflows that need to be
discussed/resolved, but overall we believe it's a good time to start
this discussion.
Devs: as
Hi,
Layer title and name are only the same if the title in the metadata is
not set (see metadata tab of a layer). If you set the title in the
metadata tab it will be different from the name in the GetCapabilities
response.
Naming the same layer twice: it's just bad practice. Authors should not
Il 04/04/2014 15:30, Tom Kralidis ha scritto:
tl; dr: we are proposing MetaSearch for inclusion into QGIS core, to
help the discovery (download/add, find/bind) workflow in QGIS. There
are Python dependencies and build workflows that need to be
discussed/resolved, but overall we believe it's a
+1 from me
2014-04-04 16:11 GMT+02:00 Paolo Cavallini cavall...@faunalia.it:
Il 04/04/2014 15:30, Tom Kralidis ha scritto:
tl; dr: we are proposing MetaSearch for inclusion into QGIS core, to
help the discovery (download/add, find/bind) workflow in QGIS. There
are Python dependencies and
Hi
It will be great to have CSW functionality in QGIS out of the box!
Regards,
Marco
On 04.04.2014 15:30, Tom Kralidis wrote:
tl; dr: we are proposing MetaSearch for inclusion into QGIS core, to
help the discovery (download/add, find/bind) workflow in QGIS. There
are Python dependencies and
+1 from me too.
giovanni
PS: The italian national catalog (RNDT) was recently added to the plugin
thanks to a proficous dialog netween some people in the italian gfoss
mailing list and the national agency.
2014-04-04 17:24 GMT+02:00 Marco Hugentobler
marco.hugentob...@sourcepole.ch:
Hi
It
Andreas, thanks for your response. My comments are below:
On Fri, Apr 4, 2014 at 3:54 PM, Andreas Neumann a.neum...@carto.net wrote:
Hi,
Layer title and name are only the same if the title in the metadata is
not set (see metadata tab of a layer). If you set the title in the
metadata tab it
Hi all.
How about adding some popular, well tested plugin of general usage to
main QGIS? We have done this in the past, e.g. for fTools, GDALTools, DB
Manager etc., and they were good additions to QGIS.
Currently the most downloaded (DESC) are:
http://plugins.qgis.org/plugins/openlayers_plugin/
I think it's a great idea.
+1 for openlayers, once it works with master (I don't use the others)
how about adding value tool?
http://plugins.qgis.org/plugins/valuetool/
But we need to fix the pyqwt bug with debian before including it in main
QGIS.
http://hub.qgis.org/issues/7450
On Fri,
Hi devs and users,
New version released for Quick Export plugin wich allows to export vector
layer attribute table to CSV, HTML, PDF and printer in one click.
The version 1.2 brings :
* an option dialog wich let the user choose the delimiter for CSV export
and the ability to decide wether
I think it's a great idea, I was actually thinking about this the other day
and glad you brought the topic.
Although we can install plugins certainly it becomes evident when a plugin
should really become a core feature, example the Openlayers Plugin, I bet
almost all people using QGIS downloads
I agree that adding the plugins to core would be a good idea however I
don't feel that we should just add them in their current state. The plugin
repository has the benefit of of being able to update things faster then
the release of QGIS itself if you find bugs, etc, you can also add features
I agree completely with what you have written specially +1 for adding the
functions but -1 for just bringing the plugins into core. Maybe start with
some of the easier ones like the value tool you mention
From: madman...@gmail.com
Date: Sat, 5 Apr 2014 14:00:41 +1000
Subject: Re:
26 matches
Mail list logo
