view backend/doc/schema/postgresql-drop-spatial.sql @ 8748:36d7bda0b47a

(issue1788) Fix area split if there are no NaN's in the data The split algorithmn splits in a way that it always creates at least two datasets. One before the NaN, one after the NaN. This is broken in case the dataset does not contain any NaN value as it resulted in two identical datasets. This changed the display and resulted in a broken area calculation. I've also added some commented out debug code that was helpful tracking down this problem.
author Andre Heinecke <andre.heinecke@intevation.de>
date Mon, 08 Jun 2015 16:53:54 +0200
parents cc53aae06303
children c7b200fe343b
line wrap: on
line source
BEGIN;

DROP TABLE river_axes;
DROP SEQUENCE RIVER_AXES_ID_SEQ;

DROP TABLE river_axes_km;
DROP SEQUENCE RIVER_AXES_KM_ID_SEQ;

DROP TABLE cross_section_tracks;
DROP SEQUENCE CROSS_SECTION_TRACKS_ID_SEQ;

DROP TABLE buildings;
DROP SEQUENCE BUILDINGS_ID_SEQ;

DROP TABLE fixpoints;
DROP SEQUENCE FIXPOINTS_ID_SEQ;

DROP TABLE floodplain;
DROP SEQUENCE FLOODPLAIN_ID_SEQ;

DROP TABLE dem;
DROP SEQUENCE DEM_ID_SEQ;

DROP TABLE hws_points;
DROP SEQUENCE HWS_POINTS_ID_SEQ;

DROP TABLE hws_lines;
DROP SEQUENCE HWS_LINES_ID_SEQ;

DROP TABLE floodmaps;
DROP SEQUENCE FLOODMAPS_ID_SEQ;

DROP TABLE hydr_boundaries;
DROP SEQUENCE HYDR_BOUNDARIES_ID_SEQ;

DROP TABLE hydr_boundaries_poly;
DROP SEQUENCE HYDR_BOUNDARIES_POLY_ID_SEQ;

DROP TABLE fed_states;
DROP TABLE hws_kinds;
DROP TABLE sobek_kinds;
DROP TABLE sectie_kinds;
DROP TABLE boundary_kinds;
DROP TABLE axis_kinds;
DROP TABLE building_kinds;

COMMIT;

http://dive4elements.wald.intevation.org