Il giorno lun, 28/02/2011 alle 01.08 +0100, Giuseppe Sucameli ha
scritto:
> Hi guys,
> I added the DBmanager development, maybe this could be a good chance
> to integrate some of the database plugins.
Hi all.
I also added another idea (thanks frankie@debian): to make qgis
scriptable. I think this
Hi Martin,
I would like to propose a couple of Python snippets to be included in the
PyQGIS Cookbook.
1) Load of MySQL geometries:
--
uri =
"MySQL:dbname,host=localhost,port=3306,user=root,password=xxx|layername=my_table"
vLayer = QgsVectorLayer( uri, 'my_table', 'ogr' )
Hi guys,
thanks a lot for your work! The new plugin site it's really nice.
BTW, the https login is still missing. I understand it would be one of the
last features
you'll put on.
Do you have a todo list or a roadmap? I'd like to look at it.
Cheers.
On Fri, Feb 25, 2011 at 1:56 PM, Martin Dobias
Hi,
I was testing a little today. It appears that WMS layers are not being
projected. I would imagine that needs to be corrected before a merge. Also,
openlayers are not correctly projecting based on some quick tests on my end.
I'm not sure if this is a problem with the branch or the plugin.
C
On Mon, Feb 28, 2011 at 1:08 AM, Giuseppe Sucameli wrote:
> adding ... to the gsoc proposal?
> ... add it to the proposal?
>
I forgot the "list" word 2 times... it's time to go bed.
--
Giuseppe Sucameli
___
Qgis-developer mailing list
Qgis-developer@li
Hi guys,
I added the DBmanager development, maybe this could be a good chance to
integrate some
of the database plugins.
As far as there's some work to do before turning to the new symbology (some
features work
in old symbology but are still missing in the new one), but also the new
labelling need
On Sat, Feb 26, 2011 at 12:52 PM, Barend Gehrels wrote:
>>> I can imagine the API is not binary compatible for some upgrades (usually
>>> it
>>> is extended so then still compatible, depending on the model used). Is
>>> there
>>> not a mechanism to check if a plugin corresponds to the version of t
Hi
8<-snip-
>> - it would be nice if the 'collar' - the part outside the image data
>> area in rotated images was made transparent by default.
>
> Isn't it? The data outside source data extent are null. That is the source
> of all the troubles with null values handling and typ
On Sun, Feb 27, 2011 at 7:08 PM, Tim Sutton wrote:
> Thanks its working great now. The grayscale issue I was having I can't
> replicate with the data I have here at home - will try again tomorrow
> on my office pc with the original dataset - as far as I know that
> machine is already set to stretc
Hi Radim
On Sun, Feb 27, 2011 at 6:04 PM, Radim Blazek wrote:
> On Thu, Feb 24, 2011 at 10:00 AM, Tim Sutton wrote:
>> Also I noted that for greyscale images they always seem to load with
>> min 0 / max 0 and I have to manually go into properties to load them
>> from the layer.
>
> For me it loa
On Thu, Feb 24, 2011 at 10:00 AM, Tim Sutton wrote:
> Also I noted that for greyscale images they always seem to load with
> min 0 / max 0 and I have to manually go into properties to load them
> from the layer.
For me it loads with source data type range (tested with UInt16) and
it works the sam
Hi,
thanks for testing, there are really too many combinations of data types,
drawing styles, projections, resolutions etc. which I am not able to test all.
It is fixed now. The problem was not in the color handling but in
source resolution calculation.
Radim
On Thu, Feb 24, 2011 at 10:00 AM, Ti
12 matches
Mail list logo
