Mercurial > gemma

comparison schema/gemma.sql @ 1131:2e6b47cdb2ca

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Store octrees along with sounding results The extra table with 1:1-relation to sounding results was a provisorial solution with the intention to make it easily removable.
author Tom Gottfried <tom@intevation.de>
date Wed, 07 Nov 2018 17:54:50 +0100
parents 72cad6277e3a
children dd4071019676
comparison
equal deleted inserted replaced
1130:42617bba8709 1131:2e6b47cdb2ca
414 area geography(POLYGON, 4326) NOT NULL, 414 area geography(POLYGON, 4326) NOT NULL,
415 surtyp varchar REFERENCES survey_types, 415 surtyp varchar REFERENCES survey_types,
416 coverage varchar REFERENCES coverage_types, 416 coverage varchar REFERENCES coverage_types,
417 depth_reference char(3) NOT NULL REFERENCES depth_references, 417 depth_reference char(3) NOT NULL REFERENCES depth_references,
418 point_cloud geography(MULTIPOINTZ, 4326) NOT NULL, 418 point_cloud geography(MULTIPOINTZ, 4326) NOT NULL,
419 octree_checksum varchar,
420 octree_index bytea,
419 staging_done boolean NOT NULL DEFAULT false 421 staging_done boolean NOT NULL DEFAULT false
420 )
421
422 CREATE TABLE octrees (
423 sounding_result_id int NOT NULL UNIQUE REFERENCES sounding_results,
424 checksum varchar NOT NULL,
425 octree_index bytea NOT NULL
426 ) 422 )
427 423
428 CREATE TABLE sounding_results_contour_lines ( 424 CREATE TABLE sounding_results_contour_lines (
429 sounding_result_id int NOT NULL REFERENCES sounding_results, 425 sounding_result_id int NOT NULL REFERENCES sounding_results,
430 height numeric NOT NULL, 426 height numeric NOT NULL,