Tag Info

New answers tagged

0

The Metadata Toolset will allow you to import metadata from the source feature class into the destination feature class... However, you will only retain metadata from one of the input feature classes, not both: Merging metadata stylesheets does not work with ArcGIS - exporting each input feature class metadata to a template and merging both templates will ...


1

If you do not need to merge topology, but just add new polygons, you can simply use: ab <- rbind(a,b) If you get a "non-unique Polygons ID slot values" error it means that the rownames of the objects are the same. To fix this you can use spChFIDs to change the rownames and associated slot relationships. Since the slots in the object use the rownames to ...


0

Super easy solution provided by @mdsumner: library(sp) library(raster) library(rgeos) library(spatstat) library(rgdal) library(maptools) setwd("C:/...") a<-readOGR(dsn=getwd(), layer="pol.a") b<- readOGR(dsn=getwd(), layer="pol.b") # use union in {raster} package ?raster::union ab<-union(a, b) resulted in : class(ab) [1] ...


1

If you are using ArcGIS 10.x or Pro When you are creating your buffer there should be a "dissolve type" option. For this you will select ALL. This should dissolve the buffers as they are created to make one large overall buffer. Then with the symbology you can make it so it is just represented by an outline by making the fill color set to no color. EDIT: ...


3

You want to do a left outer join on the shapefile's data.frame (data db) with the new table (table data). That will keep all the existing rows of your 'data db', join the appropriate fields together, and fill in missing data for rows that don't match. I'm assuming you're reading the shapefile as an sp object (using rgdal package in my example). I also ...


0

Note: You don't need the FeatureHolders that you have in the above; they accomplish nothing, although they probably aren't hurting either in this case. While you will eventually be able to get your solution to work, it will be a royal pain. Address data is about as inconsistent as it gets as you're discovering. i.e. Is "st" for "street" or "Saint"? How ...


1

Have you checked that the transmission buffer and the merged datasets are in the same coordinate system? Also with your dissolve in the dissolve field, select dissolve all if you want to dissolve everything in that dataset to one polygon. Lastly have you tried Union instead of merging them as merge will give you 4 overlapping polygons whereas in Union ...


2

There is ST_LineMerge function http://postgis.net/docs/manual-2.0/ST_LineMerge.html You could try to serve all your rivers network as one MultiLineString ST_LineMerge(ST_Multi(St_Collect(geometry))) The result is also a MultiLineString with segments sewed together. So after ST_LineMerge you could get sewed segments via ST_Dump.


0

Not tested, but it might give you what you want. With intersections you get those ids and geometries that intersect with others. And the SELECT statement will ST_Union all of these records that intersect exactly with two other geometries. ST_Dump makes sure you don't get MultiLinestrings as a result. WITH intersections AS ( SELECT l1.id, ...



Top 50 recent answers are included