-developer-boun...@lists.osgeo.org
[mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf Of Andreas Neumann
Sent: 14. november 2013 10:54
To: qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Bug with avoid intersection - willing to fund fix
Hi,
So if there is so much interest in having
Hi George
I had a lot of trouble with those issues too, and I would really love to see
them fixed. In other words, I agree with Giovanni that these are pretty
important bugs for many and not really uncommon digitization use-cases and
would support his categorization as blocker...
However, my
Hi,
So if there is so much interest in having this issue fixed I assume that
there would be plenty out there who would fund the fix!
The fix won't happen if noone pays for it - just complaining about this
does not help.
Get an estimate from some developer (e.g. Sandro Santilli oder
Sourcepole)
In other words, I agree with Giovanni that these are pretty
important bugs for many and not really uncommon digitization use-cases and
would support his categorization as blocker…
I can't remember how many times I blamed the user not to digitize the
right way, and at the end discovered that is
On Thu, Nov 07, 2013 at 04:26:32PM -0200, George Silva wrote:
QGis does the explicit noding of the first adjancent feature, but the
results are inconsistent.
Noding should involve all nearby features, updating each of them
to include the new node.
Sometimes it works, sometimes it doesnt. I've
Any comments from the QGis crowd?
Thanks
On Sat, Nov 9, 2013 at 9:18 AM, Sandro Santilli s...@keybit.net wrote:
On Thu, Nov 07, 2013 at 04:26:32PM -0200, George Silva wrote:
QGis does the explicit noding of the first adjancent feature, but the
results are inconsistent.
Noding should
On Thu, Nov 7, 2013 at 6:26 PM, George Silva georger.si...@gmail.com wrote:
QGis does the explicit noding of the first adjancent feature, but the
results are inconsistent.
Sometimes it works, sometimes it doesnt. I've tried many things to see if I
could find a reproducible series of steps,
Hello everyone,
We have an important QGis digitizing issue that is blocking and generating
a lot of work for us.
The issue has been described in more then 3 bugs (
http://hub.qgis.org/issues/8174, http://hub.qgis.org/issues/4880, and
others) and it really hurts QGis image as a software.
This is
We have an important QGis digitizing issue that is blocking and generating
a lot of work for us.
The issue has been described in more then 3 bugs (
http://hub.qgis.org/issues/8174, http://hub.qgis.org/issues/4880, and
others) and it really hurts QGis image as a software.
This is something
Hi
I have seen another bug or misbehaviour IMHO : I would expect QGIS to
automatically create a node at the intersection of 2 linestring when
topology editing is ON, with no need to do it manually. This would help a
lot too.
Regards
Michael
2013/11/7 Giovanni Manghi giovanni.man...@faunalia.pt
On Thu, Nov 07, 2013 at 06:28:47PM +0100, kimaidou wrote:
Hi
I have seen another bug or misbehaviour IMHO : I would expect QGIS to
automatically create a node at the intersection of 2 linestring when
topology editing is ON, with no need to do it manually. This would help a
lot too.
+1
11 matches
Mail list logo
