New answers tagged

0

I could not make the UPDATE work so I created a new table CREATE TABLE madclip AS SELECT mad.gid,mad.cat, CASE WHEN ST_CoveredBY(mad.geom,clip.geom) THEN (ST_DUMP(geom)).geom::geometry (Polygon, 904483) ELSE (ST_DUMP(ST_Intersection(mad.geom,clip.geom))).geom::geometry (Polygon, 904483) END AS geom FROM mad AS mad INNER JOIN clip as ...


3

I emphasize that this function might not be useful for everyone. It will depend on what you're trying to do, and your inputs, and how possible it is to do what you're trying to do given your inputs. For instance, if you have a complicated shape with concave sides, forget about it. In my case, I just wanted to cut a box filled with random points down to a ...


0

Here is a reproducible example using sp internal dataset meuse since I don't have access to your shapefiles: r1 = cbind(c(180114, 180553, 181127, 181477, 181294, 181007, 180409, 180162, 180114), c(332349, 332057, 332342, 333250, 333558, 333676, 332618, 332413, 332349)) r2 = cbind(c(180042, 180545, 180553, ...


0

The accepted method did not work for me because my basemap layer wouldn't show up in the Input Features dropdown. I solved this by doing the following: At the View menu, choose Data Frame Options. At the Data Frame Tab look for "Clip Options" Choose Clip to shape Then click the Specify Shape button Then select the boundary layer as input Apply and the ...


2

Sorry I didn't realize the errors were in your image. The approaches that you have tried are correct, you just have an issue with the data. Try removing the m-values from whichever dataset is m-aware. While you're going through this process, I'd make the outputs the same projection/crs just to be safe. I always feel more comfortable with these types of ...


2

A newer version of ArcGIS solves the overlapping zones problem: https://blogs.esri.com/esri/arcgis/2013/11/26/new-spatial-analyst-supplemental-tools-v1-3/


1

You just need to loop over the combinations you need. > combn(1:length(Sl),2) [,1] [,2] [,3] [1,] 1 1 2 [2,] 2 3 3 that gets you (in columns) the line indexes. So then do: MyLines = apply(combn(1:length(Sl),2),2, function(x){ gIntersection(Sl[x[1]], Sl[x[2]]) }) Then MyLines[[1]] is the ...


1

To provide a summary and answer to the issues here: Clip instead of intersect is the correct geoprocessing tool; The QGIS Voronoi tool introduced quite a few imperfections in the polygons produced, and this seems to be the culprit for the later geoprocessing not working as planned; I tried to clean up the Voronoi polygons produced in QGIS, but I found the ...


1

just tested it with my own data. UK boundary plus active GNSS stations voronoi, and I can confirm the intersection is working in my Qgis, however if I manually create a topology error in my boundaries the intersection query will work just partly. Run the topology checker maybe you can see any errors.


3

I think you need to use clip not intersect from vector -> geoprocessing to clip your data to the specific boundary.


2

There is another method that you can do : Before you do, Make a backup of your layer in case if it becomes corrupt. You should be able to do the following: If you are doing a few then do this: Start Editing. Click on the Attributes Use the "Edit Tool " Drag over all of the points or a point. On the Attributes, See if there are two overlaps. If you see two ...


9

Super easy manual process. You use the tool Select by Location. Select points in B that match A Export your selection in B to a new layer C "Switch" the selection in B. You now have selected all the points in B that are not in A. You can Append the selection in B to the layer C. You then do the opposite; Select points in A that match B. "Switch" the ...


2

You can do a Selection by Location. If the points are in the exact same spot, setting your tolerance to zero would only give you results on top of each other. If they are approximate, you will need to adjust that tolerance to figure out which ones are duplicates. You can then either delete the duplicates and use that layer or take the unique points from each ...


4

At the scale of your display, these lines appear to be coincident, but in reality they're not: I've exaggerated the difference between the two lines using the "Magnify Topology" tool in JTS TestBuilder, which I highly recommend for looking into cases like this. Depending on the goal of your analysis, it might be suitable to snap your vertices to a grid ...



Top 50 recent answers are included