--- a/flys-backend/doc/schema/postgresql-spatial.sql	Fri Mar 08 17:44:12 2013 +0100
+++ b/flys-backend/doc/schema/postgresql-spatial.sql	Fri Mar 08 18:15:48 2013 +0100
@@ -95,19 +95,17 @@
     id       int PRIMARY KEY NOT NULL,
     river_id int REFERENCES rivers(id) ON DELETE CASCADE,
     -- XXX Should we use the ranges table instead?
-    name            VARCHAR(64),
-    lower           FLOAT8,
-    upper           FLOAT8,
-    year_from       VARCHAR(32),
-    year_to         VARCHAR(32),
-    projection      VARCHAR(32),
-    srid	    int NOT NULL,
-    elevation_state VARCHAR(32),
-    format          VARCHAR(32),
-    border_break    BOOLEAN NOT NULL DEFAULT FALSE,
-    resolution      VARCHAR(16),
-    description     VARCHAR(256),
-    path            VARCHAR(256) NOT NULL UNIQUE
+    name             VARCHAR(64),
+    range_id         INT REFERENCES ranges(id);
+    time_interval_id INT REFERENCES time_intervals(id);
+    projection       VARCHAR(32),
+    srid	    int  NOT NULL,
+    elevation_state  VARCHAR(32),
+    format           VARCHAR(32),
+    border_break     BOOLEAN NOT NULL DEFAULT FALSE,
+    resolution       VARCHAR(16),
+    description      VARCHAR(256),
+    path             VARCHAR(256) NOT NULL UNIQUE
 );
 ALTER TABLE dem ALTER COLUMN id SET DEFAULT NEXTVAL('DEM_ID_SEQ');