Tag Info

New answers tagged

1

I've recently setup an elevation lookup service using https://github.com/perliedman/elevation-service. My use case is significantly different than yours, a few requests for lots of points vs lots of requests for a few points: the incoming requests a GeoJSON LineString features with a few thousand points. I currently have it deployed on a single t2.micro ec2 ...


3

Let's start with some assumptions: You really need 5000 web requests per second, and It would be possible to service those requests in only 5 seconds, and The queries could be serviced by exactly one CPU core, and Each core only needs 4GB of RAM, and The optimal core to CPU chassis distribution is 32, and Each CPU chasis has enough SSD disk to service all ...


1

Given the nature of your data and how many attributes you have, you don't have any choice but to split it up into different tables. From the ArcGIS help: Most size limits in a database depend on the DBMS edition and hardware limitations. One exception is the number of fields (columns) supported in a table or feature class; the maximum number is 500. ...


2

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 ...


3

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, ...


4

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.


20

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 ...



Top 50 recent answers are included