Database design is the process of specifying the logical and/or physical parts of a database.

learn more… | top users | synonyms

2
votes
3answers
2k views

Creating unique IDs for file geodatabase using ArcGIS for Desktop?

I use ArcEditor licence level, ArcGIS 10.0 version, and we're talking about a file geodatabase. I have several feature classes (electric energy domain) and I want to connect them using relationship ...
0
votes
2answers
614 views

Is there a way to have a single point feature with multiple records?

Is there a way to have a single point feature and have multiple attributes records associated with it? Multipoint approach won't work as it gives me one attribute set (database row). I am trying to ...
10
votes
2answers
950 views

How to design a Spatial Database for temporal Data?

I am working on a Weather based GIS App. I have the data from several weather stations, and this data will updated daily (by a web service). The obstacles I am facing are: There are currently 40 ...
14
votes
6answers
1k views

Is good database design less important for a spatial database

I have a strong feeling that database design and normalisation often comes in second hand when dealing with spatial data. With software costing a fortune and databases with over 100 fields tables I ...
3
votes
2answers
465 views

What's a good way store borehole data in SQLite / SpatiaLite?

I have a bunch of bores / wells with downhole data. The 'header' info for each borehole can easily go into a single table, but I'm wondering how best to store the downhole log data. Typically they are ...
11
votes
2answers
752 views

When is it safe to use ObjectIDs as keys in a relationship class?

I've always avoided using ObjectIDs when defining relationship classes. It is my understanding that some actions on a geodatabase will re-set objectIDs (like import/export). However I do see a lot ...