Tag Info

Hot answers tagged


I would go the complicated way: Two Tables in a 1:n relation one table with the point location of the graves another table with the Grave-ID and person data You can build a relation between the two tables so that selecting a grave will select all person records in the person-table. The idea of having tables with fields like Person1, Person2... is ...


You can use the Snapper transformer, with End Point Snapping and a tolerance of 6.


I would create a polygon for the grave since the grave itself is a plot of land and have a one to many relationship for the people; one grave can have zero (unoccupied, available, or for sale ?) or many people. You could also use a point instead of the polygon. Polygons would make better presentations for sales and maintenance.


As handy as R is for so many tasks, it is important to remember that 1) R is not a GIS and 2) quality mapping is downright difficult compared to creating maps with QGIS or ArcGIS. The following example borrows heavily from two R-bloggers blogs (blog 1 and blog 2). Here, I simply mapped a polygon shapefile using Google Satellite Imagery as a basemap. ...


It sounds like all you need is a simple join. Use the join tool and use a common field to combine the table and shapefile together. ESRI Help: About Joining and Relating Tables EDIT: I see now it is a new shapefile you want. In that case I would still do the join and then save the joined shapefile as a new shapefile.


I would take DenaliHardtail's suggestion of using polygons to represent accurate sizes of the plots. This layer could have a table with Grave_ID, Grave_Type, Grave_Capacity, and Grave_Occupancy_Number. Then you could have a point layer with points overlying the corresponding grave polygons. Columns for the point layer table could be Person-ID, First_Name, ...


Actually shapefile is an open specification now. Also it "can" support multiple geometry types in one (while it is never just 1 file but a group of files that make a shapefile. which you would still need to either zip or pass more than 1 file anyway). Wiki shows most of the needed information to what you want to do. BUT I do not recommend it. Only open ...


Normalizing the data leads me to some missing ideas/points. Also, I think Excel can do everything you want for the "database" you contemplate. Hint: Use sheets, or multiple files and use variations of Lookup functions. Save into the useful file(s) for imports/lookups from QGIS I envision these discrete tables [or excel sheets], to start off your data ...


As @Jeffrey states, readOGR from the rgdal library imports a CRS if there is one embedded in the shapefile. You can check by (example using a shp I've been playing with): proj4string(india) # from the sp package # [1] "+proj=longlat +datum=WGS84 +no_defs +ellps=WGS84 +towgs84=0,0,0" If this returns NA you can specify a CRS with: proj4string(india) <- ...

Only top voted, non community-wiki answers of a minimum length are eligible