Brent, we've discussed some of those features for spatialreference.org
(at least a better map view). I need to double check with the authors if
the code for site is up somewhere to facilitate taking patches for new
features (It's written in django).
Thanks,
Alex
On 12/11/2012 08:14 PM, pcr...@pcr
On a sort of related topic, (another NZ projection :-)
EPSG:3994 supercedes EPSG:3752, as EPSG got the initial specification wrong.
This is a projection used for the wider region around NZ, rather than the NZ
mainland, and this projection is used primarily in ESRI to avoid 180 meridian
issues.
Hello,
I need to use qgis 1.8 with the last gdal svn 1.10.0 on my Windows 7 64 bits
station.I know that i'm obliged to compile in a 1st time gdal svn & in a 2nd
time qgis targetting the gdal svn version. Up to now, i succeed in compiling
gdal svn thanks to "TortoiseSvn" & Visual Studio. Now, i 'm
Hi Frank,
Yes it would be great if grid shifts are supported in proj.4 by default, but
for more importantly for us within Qgis. Currently I see QGIS builds it's CRS
database using crssync which relies on GDAL OSRExportToProj4 for creating
proj.4 strings. Does that mean that the gdal CSV files a
On Tue, Dec 11, 2012 at 07:42:08AM -0800, Massimo Endrighi wrote:
> Sandro Santilli-2 wrote
> > I think Martin ideas is sensible and I do see the code is going
> > in that direction. But even if the classes are decoupled from
> > the QT tree widget we'll need a way to identify groups, as much
> > a
Sandro Santilli-2 wrote
> I think Martin ideas is sensible and I do see the code is going
> in that direction. But even if the classes are decoupled from
> the QT tree widget we'll need a way to identify groups, as much
> as we do with layers (which do have an ID). I've no problem with
> all elemen
Hi chingchai
Glad you got qgis master working.
No, there shouldn't be any problem with GDAL if you install PostGIS 2.0. I
believe both QGIS and PostGIS are compiled with their own versions of GDAL.
Regards
Ian
- Original Message -
From: chingchai humhong
Date: Tuesday, December 11,
Ok, perfect, now it's clear.
giovanni
2012/12/11 Radim Blazek
> On Tue, Dec 11, 2012 at 2:23 PM, G. Allegri wrote:
> >>
> >> Yes, you are right. Any class inheriting from QgsRasterInterface may
> >> be plugged into the QgsRasterPipe but all interfaces will be in a
> >> single line, no forks.
>
On Tue, Dec 11, 2012 at 2:23 PM, G. Allegri wrote:
>>
>> Yes, you are right. Any class inheriting from QgsRasterInterface may
>> be plugged into the QgsRasterPipe but all interfaces will be in a
>> single line, no forks.
>
>
> Ok, Radim, I'm sorry if I insist on this, it's just to understand it
>
On Dec 11, 2012, at 4:10 AM, Radim Blazek wrote:
> On Mon, Dec 10, 2012 at 11:12 PM, Larry Shaffer
> wrote:
>> The GRASS-6.4.app, which is a bundled Mac app [0, Qt example] from
>> Kyngchaos.com. But the same holds for the bundled QGIS.app: the Mac
>> operating system, by default, does not pass
On Tue, Dec 11, 2012 at 12:02:57PM +0100, Andreas Neumann wrote:
> I would like to see such an improved legend interface. Currently the
> group and layer index even behaves differently between version 1.8
> and version 1.9. I have to check the version and decrease the index
> in case it is version
Andreas Neumann wrote
> Sounds good to me.
>
> I'd also like to see enhancements on groups in the future. Groups can
> be potentially more intelligent if they can hold properties. F.e. some
> web services (like WMS) require metadata on groups (like title,
> abstracts, responsible entities).
Hi,
the same thing happens here. Using Sqliteman the value looks OK but when
using QGis Attribute table it turns into the strange value.
Is suspected it had to do with an int (32) conversion and so made a
small C test to confirm. If you run the C test in the linked ZIP you'll
get the following r
Hi,
the same thing happens here. Using Sqliteman the value looks OK but when
using QGis Attribute table it turns into the strange value.
Is suspected it had to do with an int (32) conversion and so made a
small C test to confirm. If you run the C test in the linked ZIP you'll
get the following r
>
>
> Yes, you are right. Any class inheriting from QgsRasterInterface may
> be plugged into the QgsRasterPipe but all interfaces will be in a
> single line, no forks.
>
Ok, Radim, I'm sorry if I insist on this, it's just to understand it
correctly.
To add a QgsRasterInterface in a QgsRasterPipe I
Sounds good to me.
I'd also like to see enhancements on groups in the future. Groups can
be potentially more intelligent if they can hold properties. F.e. some
web services (like WMS) require metadata on groups (like title,
abstracts, responsible entities). One could also think about group
op
Hi,
the same thing happens here. Using Sqliteman the value looks OK but when
using QGis Attribute table it turns into the strange value.
Is suspected it had to do with an int (32) conversion and so made a
small C test to confirm. If you run the C test in the linked ZIP you'll
get the following
On Tue, Dec 11, 2012 at 1:29 PM, G. Allegri wrote:
>>
>> Do you mean QgsRasterInterface with multiple inputs? This is not
>> currently supported. In theory you can write an interface with
>> multiple inputs, but for example QgsRasterFileWriter is using some
>> info from srcInput, i.e. the first in
On Tue, Dec 11, 2012 at 12:04 PM, Nathan Woodrow wrote:
> I think Martin has some ideas about how we can improve the legend
> based stuff. Might be best to see what he has in mind.
Well... the whole idea is to get rid of that interface and replace it
by something saner. Maybe I have already post
>
>
> Do you mean QgsRasterInterface with multiple inputs? This is not
> currently supported. In theory you can write an interface with
> multiple inputs, but for example QgsRasterFileWriter is using some
> info from srcInput, i.e. the first interface (provider) in the pipe,
> there is no support f
On Tue, Dec 11, 2012 at 12:23 PM, G. Allegri wrote:
> Thanks Radim, I wasn't aware of all these news in trunk!
> The QgsRasterPipe is really powerful.
>
> Is there some doc about it?
> I've run through the code to understand the logic behind QgsRasterPipe (QRP)
> and QgsRasterInterface (QRI).
> I
Good morning to all
I know that qgis don't have the ability to edit and handle Z valuez for
vector layers.
Today I faced a problem with Postgis polygon layer.
I can delete a feature but not add vertices to features.
Qgis don't let me save the edit session if I add some vertices to a feature.
Is th
Thanks Radim, I wasn't aware of all these news in trunk!
The QgsRasterPipe is really powerful.
Is there some doc about it?
I've run through the code to understand the logic behind QgsRasterPipe
(QRP) and QgsRasterInterface (QRI).
I see that for a QRI must be set a an input QRI (setInput method). I
I think Martin has some ideas about how we can improve the legend
based stuff. Might be best to see what he has in mind.
Regards,
Nathan
On Tue, Dec 11, 2012 at 9:02 PM, Andreas Neumann wrote:
> Hi,
>
> I would like to see such an improved legend interface. Currently the group
> and layer index
Hi,
I would like to see such an improved legend interface. Currently the
group and layer index even behaves differently between version 1.8 and
version 1.9. I have to check the version and decrease the index in case
it is version 1.9.
I use this horrible code to find a group and attach a new
On Tue, Dec 11, 2012 at 10:52 AM, G. Allegri wrote:
> Until now I've mostly created vector layers on QGIS, delegating raster
> creation to custom GDAL utilities.
> Recently I looked into QgsGdalProvider and I saw that it exposes the
> QgsRasterDataProvider::Create capability.
> I wonder if it's po
On Tue, Dec 11, 2012 at 08:56:16AM +0100, Sandro Santilli wrote:
> One option would be to store an unique identifier in each LegendGroup object
> and use that identifier for all lookups. There would be a counter within
> each Legend incremented everytime a new group is added. Would this break
> an
On Mon, Dec 10, 2012 at 11:12 PM, Larry Shaffer wrote:
> The GRASS-6.4.app, which is a bundled Mac app [0, Qt example] from
> Kyngchaos.com. But the same holds for the bundled QGIS.app: the Mac
> operating system, by default, does not pass in the full shell
> environment, as per a user's terminal
To be honest, I don't see a use case for the original
DensifyGeometries. It's behavior is quite strange: You tell it to add
10 pts but it will add 20 pts if the linestring happens to consist of
3 nodes and 30 pts if 4 nodes ...
Best wishes,
Anita
___
Qgi
On Tue, 11 Dec 2012 10:48:50 +0100
Anita Graser wrote:
> On Tue, Dec 11, 2012 at 9:33 AM, Werner Macho wrote:
> > Hi!
> > Would it make sense to integrate the "new" algorithm as a selectable option
> > into the "old" algorithm?
>
> Hi Werner!
> Probably, but I don't know how to add optional fie
Hi Bernhard,
Yes - this is definitely on our radar. We need this for our waste-water
application. It is called "data defined symbology" and used to work with
the old symbology.
With the new symbology, data defined symbology is more complex to
implement as we have symbol levels.
I'll contac
Until now I've mostly created vector layers on QGIS, delegating raster
creation to custom GDAL utilities.
Recently I looked into QgsGdalProvider and I saw that it exposes
the QgsRasterDataProvider::Create capability.
I wonder if it's possible to create a brand new raster (geotiff or what
else) usin
On Tue, Dec 11, 2012 at 9:33 AM, Werner Macho wrote:
> Hi!
>
> Would it make sense to integrate the "new" algorithm as a selectable option
> into the "old" algorithm?
Hi Werner!
Probably, but I don't know how to add optional fields - if there is
anything that needs to be considered.
Best wishes,
Dear Devs,
I am wondering if this question has been raised before... Has there been
any thoughts about symbolizing by attribute (similar to the new labeller
where I have the option to set color, transparency, scale etc. by
attribute)?
Background: I have a "map" drawn in CAD. All lines have col
Hi!
Would it make sense to integrate the "new" algorithm as a selectable option
into the "old" algorithm?
regards
Werner
On Tue, Dec 11, 2012 at 9:27 AM, Anita Graser wrote:
> > 2012/12/11 Alexander Bruy :
> >> You need to expose your algorithm is provider. Open file
> FToolsAlgorithmProvider
> 2012/12/11 Alexander Bruy :
>> You need to expose your algorithm is provider. Open file
>> FToolsAlgorithmProvider.py, add import statement with your new alg
>> (use existing statements as example) and then in __init__ method
>> add your algorithm to algorithms list — variable self.alglist.
Tha
Anita
If you algorithm is of general interest and you don't mind sharing it,
we can put it in the SEXTANTE code and distribute it along with the
other ftools algorithms.
If you do not want to have it in the ftools group, then you can also
create you own algorithm provider in its own plugin (the e
37 matches
Mail list logo
