Very helpful video! Glad I'm not the only one who spends a bit of time fixing geometry (other people's 😆). Couple of things to add. 1. The "Fix geometry" tool is also available under "modify features in place". So you don't have to create a new layer of fixed geometry every time. 2. There is also there the "check geometries" tool/plugin under the vector menu that you can use if you still find you are having problems with invalid geometry after you've run the two tools you ran here (lets you drill down and offers solutions at multiple resolutions). I find that ArcGIS and MapInfo are far less bothered by the quality of geometry than QGIS and PostGIS are. GEOS is a much higher standard clearly.
Thanks for the comment. Yes you are quite right there are some other good options. I think at the end of the day it is best to try and ensure the geometry is valid at point of capture - e.g. JS API for ArcGIS you can check for self-intersecting polygons.
@@GISCoordinated Couldn't agree more! I could rant for quite a while but I'll try to avoid that! It really boils down to two things .1. Training - if the data is being collected internally; and 2. Procurement - making sure that if you are commissioning data collection/creation that quality standards are a requirement.
SO simple and helpful thank you so much
Thanks for sharing your method. Excellent work!
Perfekt 👍😃
Thank you very much. That's a very helpful information.
Very helpful video! Glad I'm not the only one who spends a bit of time fixing geometry (other people's 😆). Couple of things to add. 1. The "Fix geometry" tool is also available under "modify features in place". So you don't have to create a new layer of fixed geometry every time. 2. There is also there the "check geometries" tool/plugin under the vector menu that you can use if you still find you are having problems with invalid geometry after you've run the two tools you ran here (lets you drill down and offers solutions at multiple resolutions).
I find that ArcGIS and MapInfo are far less bothered by the quality of geometry than QGIS and PostGIS are. GEOS is a much higher standard clearly.
Thanks for the comment. Yes you are quite right there are some other good options. I think at the end of the day it is best to try and ensure the geometry is valid at point of capture - e.g. JS API for ArcGIS you can check for self-intersecting polygons.
@@GISCoordinated Couldn't agree more! I could rant for quite a while but I'll try to avoid that! It really boils down to two things .1. Training - if the data is being collected internally; and 2. Procurement - making sure that if you are commissioning data collection/creation that quality standards are a requirement.
Where did you find the layer Italy_CAPs? Can you share it? many thanks
this was very informative session.
TY!
how do you fix "no spatial index exists for input layer"?
100 / 5.000
thank you so much, this helpful video🏅 just solved a topological problem🙄 I was struggling with
Thank you for the nice video
Very helpful, thank you! :)
simple but powerfull, thanks
Thank you so much!
Thank you so much
You're the boss ! thanks
Thank you.
Thank youu very helpful!
Thank you this helped😊