Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You are breaking the sp (shapefile) object in multiple ways. You cannot not add data to the dbf independently of the operating on the shapefile. Everything is indexed in one of the binary files (shx) comprising the shapefile. You are also breaking the internal relationship of the sp object by using merge. </p> <p>The most efficient way is to use rgdal to read the shapefile, join the dbf, and finally write out (or overwrite) a new shapefile.</p> <pre><code>require(rgdal) require(sp) require(foreign) # Read data shp &lt;- readORG(getwd(), "ShpName") tbl &lt;- read.dbf("infile.dbf") # Merge data using match shp@data = data.frame(shp@data, tbl[match(shp@data[,"GEO_ID"], tbl[,"GEO_ID"]),]) # Write new shapefile with added attributes, THe additional flags will overwrite if # the name is the same as the original writeOGR(shp, getwd(), "NewShp", driver="ESRI Shapefile", check_exists=TRUE, overwrite_layer=TRUE) </code></pre> <p>If you need a more formal merge function you can use this.</p> <pre><code>########################################################################## # PROGRAM: merge.sp.df # # USE: JOINS A dataframe OBJECT TO A sp CLASS SpatialDataFrame OBJECT # KEEPING INTEGRITY OF DATA # # REQUIRES: sp CLASS SpatialDataFrame OBJECT # PACKAGES: sp # # ARGUMENTS: # x sp SpatialDataFrame OBJECT # y dataframe OBJECT TO MERGE # xcol MERGE COLUMN NAME IN sp OBJECT # ycol MERGE COLUMN NAME IN dataframe OBJECT # # EXAMPLE: # # Not Run (dat.sp is sp object and dat is a data.frame to merge # dat.sp &lt;- merge.sp.df(dat.sp, dat, "dat.sp-ID", "dat-ID") # # VALUE: # A NEW SpatialDataFrame OBJECT WITH MERGED DATA ########################################################################## merge.sp.df &lt;- function(x, y, xcol, ycol) { x@data$sort &lt;- 1:nrow(as(x@data, "data.frame")) xdf &lt;- as( x@data, "data.frame") xdf &lt;- merge(xdf, y, by.x=xcol, by.y=ycol) xdf &lt;- xdf[order(xdf$sort), ] row.names(xdf) &lt;- xdf$sort xdf &lt;- xdf[,- which(names(xdf) == "sort")] x@data &lt;- xdf return(x) } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POError when loading a .shp file after joining attributes from a .csv to a .dbf file
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJeffrey Evans
    1. USJeffrey Evans
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI thought this might be the case, but I have seen a few examples from where others have written similar code, though I can tell that they have probably removed some of their coding steps. I'll have to try something like above and see if it works. If not, I know another way I can do it.
      singulars
      1. PO
      1. USRhonda
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload