liche Nachricht-
Von: QGIS-User Im Auftrag von Andrea
Giudiceandrea via QGIS-User
Gesendet: Freitag, 6. Dezember 2024 03:07
An: qgis-user@lists.osgeo.org
Betreff: Re: [Qgis-user] topological editing
> Huesmann, Michaela michaela.huesmann at Stadt-Steinfurt.de Wed Dec 4
> 23:40:26 PST 2024
>
Huesmann, Michaela michaela.huesmann at Stadt-Steinfurt.de
Wed Dec 4 23:40:26 PST 2024
I wonder why topological editing does not work in my case.
Hi Michaela,
in addition to the other info previously requested, I think it is
important to know which is the layer's Coordinate Reference System
Hello Michaela,
Are the polygons in the same layer?
One permiss for the topologic edit to work is that the vertices are
coincident in the first place. Try moving the vertex to snap the other
polygon vertice. Then try to move them together.
Best resgards,
Alex Neto
A quinta, 5/12/2024, 07:40,
Hi Michaela,
I assume both polygons are in the same layer?
Also - the question is: what layers are selected for snapping (second
button). Have you double checked that the layer in question is active?
I generally also advise to enable "Avoid Overlap on Active Layer" (the
button to the right of t
Hi,
this is an unfortunately long standing issue:
https://github.com/qgis/QGIS/issues/29648
In short: project crs and data crs have to be the same
Cheers,
Bernd
Am 27.01.22 um 12:19 schrieb Klaus Mithöfer:
Hello List,
I tried to edit geographic data (Linestrings, 4326) in a Geopackage
but
Hi Sabin,
On 03/10/19 07:57, Sabin Kolarov wrote:
> does anyone have some observation how long does it take for a reported
> bug to be fixed?
>
> I reported a serious regression in April, but it’s not fixed yet.
>
> Here is the link:
>
> https://issues.qgis.org/issues/21833#change-103941
as y
Hi Harrissou,
as others said, the snapping and toplogical edition area is a really
complex part of the code. Currently, developpers that start to fix bugs
will have serious doubts when trying to tackle things that are far away
from their area of knowledge. The current bug triage work is not going s
Saber Razmjooei wrote
> Could you maybe update the QEP with your opinion how exactly things should
> work?
> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/69
>
> I will try to summarise the notes into bugs.
>
> Click-and-drag was decided not to be a good option for precise digitizing.
Could you maybe update the QEP with your opinion how exactly things should
work?
https://github.com/qgis/QGIS-Enhancement-Proposals/issues/69
I will try to summarise the notes into bugs.
Click-and-drag was decided not to be a good option for precise digitizing.
So, unless you'd like that to be re
DelazJ wrote
> Hi Régis,
>
> The issue priority is already set as high, tagged as a regression,
> mentioned (and argumented) in the QEP related to the vertex tool. We are
> in
> bug fixing time. What is missing? An interested dev?
>
> IMO, the vertex tool refactoring brings nice features but havi
On Thu, Oct 18, 2018 at 10:15 AM DelazJ wrote:
> Hi Régis,
>
> The issue priority is already set as high, tagged as a regression,
> mentioned (and argumented) in the QEP related to the vertex tool. We are in
> bug fixing time. What is missing? An interested dev?
>
I'm afraid that not many devs a
Hi Régis,
The issue priority is already set as high, tagged as a regression,
mentioned (and argumented) in the QEP related to the vertex tool. We are in
bug fixing time. What is missing? An interested dev?
IMO, the vertex tool refactoring brings nice features but having used it
more and more thes
Well, we can raise its priority and call developpers that are funded
currently byt QGIS.org to work on it.
Régis
Le jeu. 18 oct. 2018 à 08:40, Alexandre Neto a
écrit :
> Well, if there's a ticket already, there's not much more we can do. Unless
> someone is willing to sponsor that work/fix.
>
>
Well, if there's a ticket already, there's not much more we can do. Unless
someone is willing to sponsor that work/fix.
Best regards,
Alexandre Neto
A qui, 18/10/2018, 05:57, Antongeo76 escreveu:
> Alexandre Neto wrote
> > I can confirm that adding a new vertex to a polygon does not create
> >
Alexandre Neto wrote
> I can confirm that adding a new vertex to a polygon does not create
> vertexes on other other polygons.
>
> You need to create a node on the other polygon, and then snap it to the
> first. Only then the topological node move work on both polygons.
>
> Not sure how it worked
I can confirm that adding a new vertex to a polygon does not create
vertexes on other other polygons.
You need to create a node on the other polygon, and then snap it to the
first. Only then the topological node move work on both polygons.
Not sure how it worked on 2.18, may be considered a regre
Hello Deon,
If you have the chance, exporting both your layers to Postgres\Postgis,
would allow you to, for each district geometry, run ST_Snap[1] against its
related province geometry. With the correct tolerance, this might solve a
big part of your Boundary differences.
Even tho, you would need
If the layers are digitized by different agencies and dissolving is time
consuming for each next higher level, then the automatic snapping of
boundaries within tolerance distance, with keeping one layer as correct
layer will be a useful feature.
Regards
On Tue, Oct 15, 2013 at 7:25 PM, Carlos Cer
... or you can disolve your districts to obtain new provinces and leave the
old layer
Good luck
Carlos Cerdán
2013/10/15 Lene Fischer
> Hello Deon
> You can use the function Avoid Intersection while digitizing.
> In this way you avoid overlap - but not gaps.
> Read more about this issue in t
19 matches
Mail list logo
