Hi,
FWIW:
https://github.com/OSGeo/grass/releases/tag/7.8.1RC1
Best
Markus
On Tue, Oct 29, 2019 at 1:20 PM Andreas Neumann wrote:
>
> Excellent. Thanks all for your efforts! It is appreciated a lot!
>
> Andreas
___
Qgis-user mailing list
Qgis-user@lis
Ah! What you are looking for is the TIN Interpolation tool.
https://docs.qgis.org/testing/en/docs/user_manual/processing_algs/qgis/interpolation.html#tin-interpolation
Alexandre Neto
QGIS Support
www.qcooperative.net
A terça, 29/10/2019, 16:18, Carolina Rey escreveu:
> Thank you for the answ
You can determine how the image resolution in two ways:
1. Using the extent and the size of the pixels (which will calculate the
number of rows and columns necessary), commonly named pixel resolution.
2. Using the extent and dimensions in rows in columns (which will calculate
the size of individua
Thanks Even.
I always thought that the QGIS client and QGIS server shared a common code base?
But if it's the server side WFS implementation that does POST, it of course
doesn't mean that the WFS client side also does, although it would be a natural
assumption to have both run in parallel.
And
On 10/25/19 7:04 PM, Even Rouault wrote:
On vendredi 25 octobre 2019 17:10:40 CEST Matthias Kuhn wrote:
Hi all,
We had the same experience in a project of ours. Multiple users with
read-only access to a gpkg on a (Windows) network share. The results
were freezes on unloading the layer (e.g. clo
Hi Lars,
Thank you for bringing that up. There has been a feature request opened
for this - or at least something very similar - recently
(https://github.com/qgis/QGIS/issues/32348.
The next step will be that someone starts working on this. It is
possible that someone will volunteer his prec
Lars,
https://issues.qgis.org/issues/6535 is about QGIS server side, and here if I
understand well, you are considering QGIS client side, so completely different
parts of the code
> Did the developers forget to implement WFS POST in 3.x ?
It seems https://github.com/qgis/QGIS/issues/32348 was
Hi list.
We're using QGIS 3.4.9 with WFS, and it seems like WFS calls with filters are
being sent using GET, not POST.
Which means that a non-trivial filter eventually generates a too long URL at
some point. I'm currently having problems with an URL with a length of just
1958 characters. An UR
Hi,
On Tue, 29. Oct 2019 at 10:01:26 +0100, Jürgen E. Fischer wrote:
> > Just to be sure, you merge and then RC1?
For PROJ 6.2.1 and GDAL 3.0.2 there are also currently RCs…
Jürgen
--
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rhein
Dear all,
On Tue, Oct 29, 2019 at 10:11 AM Jürgen E. Fischer wrote:
>
> Hi Nyall,
>
> On Tue, 29. Oct 2019 at 13:07:47 +1000, Nyall Dawson wrote:
> > I wonder if there's anything the QGIS project can do to assist here.
> > The options as I see them:
> >
> > 1. Wait for GRASS to update and release
Hi Nyall,
On Tue, 29. Oct 2019 at 13:07:47 +1000, Nyall Dawson wrote:
> I wonder if there's anything the QGIS project can do to assist here.
> The options as I see them:
>
> 1. Wait for GRASS to update and release (doesn't seem a great option
> -- the whole geo stack is being delayed by this (e.g
Hi Luigi
Thanks for the suggestion. However, I was aiming for a more native, generic
solution for working with JSON data in QGIS. I would like to be able to
read, process and write JSON data with a processing model in QGIS. See for
example how FME handles JSON,
https://knowledge.safe.com/articles/3
Hello everyone,
to my last E-Mail (about rasterizing).
I actually don't know how to set the values "horizontal" and "vertical". I
tried with 30, 100 and more and the pixels in the result are big and the image
isn't continuous although it should be.
Thanks
Carolina
[https://ipmcdn.avast.com/ima
13 matches
Mail list logo
