Tag Info

New answers tagged

2

Use the Must not have dangles rule, and if lines are always supposed to meet end to end rather than having an end just touch another line anywhere, use the Must not Intersect or Touch Interior. All line ends that do not meet another line end will appear as a topology error and with the topology tools you will have the option to snap, extend or trim dangle ...


2

If I understand your question correctly, I think @gcarillo has the right idea in his comment. Rather than building the linestrings before the intersection, determine the points inside the polygon first and then build the linestrings based on sequence groups. Although it looks a little complex, the following query will achieve this. I've made some ...


0

You could try deleting the relevant polygons from the "Achlain_Current" shapefile and then running a Merge or Union tool with the "Restock" shapefile. Another option is to try v.clean again on your new shapefile after you copied the polygons and run various tools such as deleting duplicate polygons, removing dangles etc. Hope this helps!


1

I had the same issue. You need to make sure that the polygon is free of any issues, like duplicated point or intersections. Do this by : Select your feature Go Vector -> Geometry Tools -> Check Geometry Validity Here choose Use only selected features to make the process faster Hit OK and delete error if you have some Now retry the splitting


0

For vector shifts you can buffer within a radius, anything remaining would need a manual quality assurance. Quality tends to have a manual element unless you are just testing for regression. Address points same operation. Raster look for differences in values tweening pooled versioned data, same with math, any way that is enough for a light overview. Best in ...



Top 50 recent answers are included