Hi all
I am new to this list, as I am new to the QGIS development workflows,
but I am generally very interested in best practices for keeping
documentation.
Together with Paolo Cavallini, we have been considering which best
practices could be considered for keeping the QGIS documentation.
You
2012/1/9 Paolo Corti pco...@gmail.com:
Hi all
I am new to this list, as I am new to the QGIS development workflows,
but I am generally very interested in best practices for keeping
documentation.
Together with Paolo Cavallini, we have been considering which best
practices could be
Hi all.
One QGIS user has added a small bounty to two tickets:
Bug #4583
Bug #3099
Anyone fixing it is entitled to claim it from Bill.
All the best.
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
___
Hi there,
I just commited a larger change to the postgres provider. Mostly it's
refactoring, but it also contains some features.
You should now be able to use primary keys that are not numeric and even
primary keys with more that one column should work (not sure how well the
latter performs).
Il 09/01/2012 11:30, Paolo Corti ha scritto:
I would like to hear your opinion about eventually migrating the whole
QGIS project docs to Sphinx. I am ready to contribute to this, if this
idea is well receipt from all of you :)
I think the barrier for new doc translators is currently rather
Hi,
I would also welcome it if we could have other OGC Server standards
implemented in QGIS Server.
However, personally, I would first be interested in WFS(-T) rather than
WCS-T. But this is just my own personal preference.
Andreas
On Mon, 09 Jan 2012 14:03:37 +0100, Paolo Cavallini
Hello,
Hope to be asking in the right place..
Just trying to find out if anyone knows what happened to the package
qgis-providers that is now marked as brocken (version
1.9.90+git20120104+d04bc8f~oneiric1) on repository
http://qgis.org/debian-nightly?
I'm using Ubuntu 11.10, 64 bit.
All,
Thanks to Andrea Peri, I have just discovered that WFS 1.0.0 apparently
does NOT require a WFS server to report a unique feature ID with every
feature it transmits (a typical newbie misconception?).
The OGC specs are so nested and versioned, it's hard to be certain I've
understood them
Hi Bill,
I guess perhaps you could calculate the
PointOnSurface (don't the centroids) for every single feature received.
The PointOnSurface (available on spatialite for example)
Will Allow you to understand if a new Features received is the same or
is another.
Another technics should be
forwarding this to the list.
I don't have a personal answer to this.
Andreas
Original Message
Subject: Re: [Qgis-developer] WCS-T server
Date: Mon, 9 Jan 2012 14:53:53 +
From: John Donovan mersey.vik...@gmail.com
To: Andreas Neumann a.neum...@carto.net
Well this is a
Hi Alessandro!
We've also shortly talked about automatically build language-specific
snapshots of the QGIS GUI with a custom sphinx directive.
Yes, latest Sphinx version has a first class support for
internationalization [1], so it should not be too hard to build an
optimal solution for QGIS
Hi all, I m not shure, but hasn't somebody already done sth in that
direction? Maybe was it Yves. I remember sth from the hackfest in Zh
Ciao
On Jan 9, 2012 4:02 PM, Paolo Corti pco...@gmail.com wrote:
Hi Alessandro!
We've also shortly talked about automatically build language-specific
Il 09/01/2012 14:49, Andreas Neumann ha scritto:
However, personally, I would first be interested in WFS(-T) rather than WCS-T.
But
this is just my own personal preference.
I think the TinyOWS approach is quite efficient, and we could avoid reimplementing it
here. It should be suffcient to
Hi John
Does the WCS-T service need functionality from the QGIS API (raster
layer, raster provider, ...)? If not, it could also be an option to
build the WCS service directly on top of the GDAL library.
QGIS (wms) server could certainly serve as an inspiration on how to
implement other
Hi,
we started to work on a solution for the documentation and we decided to
migrate the docs from latex to rst - but this has not happened yet. At this
point we have the docs in git and we plan to start using the online tools
provided by github to work on the englisch manual (latex) for the next
Il 09/01/2012 17:36, Otto Dassau ha scritto:
we started to work on a solution for the documentation and we decided to
migrate the docs from latex to rst - but this has not happened yet. At this
point we have the docs in git and we plan to start using the online tools
provided by github to work
Am Mon, 09 Jan 2012 17:41:22 +0100
schrieb Paolo Cavallini cavall...@faunalia.it:
Il 09/01/2012 17:36, Otto Dassau ha scritto:
we started to work on a solution for the documentation and we decided to
migrate the docs from latex to rst - but this has not happened yet. At
this point we
Il 09/01/2012 18:08, Otto Dassau ha scritto:
Migration is one thing and the other is that we are on the one hand lucky to
have so many people who help us translating the manual but on the other
hand only a few people are interested in updating the englisch master
document. So before people can
Hello,
As I said before, I can help to migrate documentation to rst. I am using rst
frequently for all the documentation so it is not a problem for me.
The only issue I see is to create nice PDF documentation. I tested rst2odt
which could help with pdf generator inside OOo but the rst2odt
On Mon, Jan 9, 2012 at 7:59 PM, Yves Jacolin (free) yjaco...@free.fr wrote:
Hello,
As I said before, I can help to migrate documentation to rst. I am using rst
frequently for all the documentation so it is not a problem for me.
The only issue I see is to create nice PDF documentation. I
Hi all,
Following the recent enhancements of QGsExpression, I was wondering whether it
wouldn't make sense to integrate a language intepreter instead of creating
another language.
One candidate would be Google's V8 JavaScript engine
(http://code.google.com/p/v8/). Since embedding this C++
Hi,
I think the language for expressions should be considered carefully. It
can have a fairly big impact on user experience, particularly for people
who aren't programmers.
What other candidates might there be? How do they compare in terms of
intuitiveness? The less time people need to spend
Il 10/01/2012 04:05, Alister Hood ha scritto:
I think the language for expressions should be considered carefully. It
can have a fairly big impact on user experience, particularly for people
who aren't programmers.
Agreed, ease of use is more important than sheer performance. However, I do
Hi,
I have a raster that is georeferenced. When I try to zoom to native
pixel resolution it zooms but definitely it is not native pixel
resolution.
Can anyone confirm this?
This works fine if I have just an unreferenced raster.
Is there any place to upload sample data?
Thanks
-Lauri
24 matches
Mail list logo
